Domoticz RPC for NIBE Uplink
Moderator: leecollings
-
- Posts: 11
- Joined: Tuesday 30 May 2017 15:54
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Domoticz RPC for NIBE Uplink
Couldn't wait... Working fine now for half a day. I only had to fix the valueFactor to 0.1 for the three currents in the config file.
The Domoticz crash is probably due to the upgrade process:
sudo apt-get update && sudo apt-get upgrade -y
so I skipped that part. That is a completely other issue I guess.
Thanks for quick fix!
The Domoticz crash is probably due to the upgrade process:
sudo apt-get update && sudo apt-get upgrade -y
so I skipped that part. That is a completely other issue I guess.
Thanks for quick fix!
-
- Posts: 485
- Joined: Thursday 17 September 2015 10:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
Re: Domoticz RPC for NIBE Uplink
Thanks @LMERLMER wrote:Couldn't wait... Working fine now for half a day. I only had to fix the valueFactor to 0.1 for the three currents in the config file.
The Domoticz crash is probably due to the upgrade process:
sudo apt-get update && sudo apt-get upgrade -y
so I skipped that part. That is a completely other issue I guess.
Thanks for quick fix!
I've released version 1.1.1 that will detect the valueFactor correctly.
-
- Posts: 3
- Joined: Thursday 29 December 2016 21:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V3.8367
- Location: Nederland
- Contact:
Re: Domoticz RPC for NIBE Uplink
How do I change the valuefactor for the 3 currents?
They were added with the latest update, however they stay on 0
They were added with the latest update, however they stay on 0
-
- Posts: 485
- Joined: Thursday 17 September 2015 10:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
Re: Domoticz RPC for NIBE Uplink
Hi. I assume that you've updated your Nibe system to the latest version.
Value factors are changed in the configuration file if necessary. But I'm not sure that's the problem though. Please submit a Software Trouble Report as described in the initial post so I can have a look at it.
Thanks!
Re: Domoticz RPC for NIBE Uplink
Got a download notification for version 1.1.2 today, but the changelog in second post still shows 1.0.4 as latest.
Any major changes?
Any major changes?
-
- Posts: 485
- Joined: Thursday 17 September 2015 10:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
Re: Domoticz RPC for NIBE Uplink
Hi. Thanks for reminding me. That have been fixed.
This morning, the Nibe servers responded with a "server error". I made a small addition so that an appropriate error message will be shown in such cases.
-
- Posts: 3
- Joined: Thursday 29 December 2016 21:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V3.8367
- Location: Nederland
- Contact:
Re: Domoticz RPC for NIBE Uplink
I've downloaded the 1.1.1 version yesterday and the 1.1.2 version today.
The 3 current phases were newly detected and I removed the old.
Lets see what it does the next days
Thanks
The 3 current phases were newly detected and I removed the old.
Lets see what it does the next days
Thanks
-
- Posts: 6
- Joined: Monday 04 September 2017 21:05
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.8389
- Location: Sweden
- Contact:
Re: Domoticz RPC for NIBE Uplink
Hello BakSeeDaa
Thank you for a nice plugin for Domoticz. I have run that for a while with my Nibe VVM310 indoor unit, However now I have invested in an outdoor compressor F2120 16KW, this shows up as "Slave1" in my nibeuplink webpage with its parameters, But when i run the "redefine" non of those new parameters from Slave1 shows up.
Do i miss something, or is the uplink plugin not supporting "Slaves"?
Thank you
/Andreas
Thank you for a nice plugin for Domoticz. I have run that for a while with my Nibe VVM310 indoor unit, However now I have invested in an outdoor compressor F2120 16KW, this shows up as "Slave1" in my nibeuplink webpage with its parameters, But when i run the "redefine" non of those new parameters from Slave1 shows up.
Do i miss something, or is the uplink plugin not supporting "Slaves"?
Thank you
/Andreas
-
- Posts: 485
- Joined: Thursday 17 September 2015 10:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
Re: Domoticz RPC for NIBE Uplink
Hi Andreas. I'm sorry for the late reply. For some reason the subscription for this topic has not been working for me. I would have to look into that to see if we can add "Slaves" but if you can't find it when doing a "redefine" it seems that the Domoticz RPC for NIBE Uplink can't support it yet.andnyg wrote: ↑Sunday 10 September 2017 18:33 Hello BakSeeDaa
Thank you for a nice plugin for Domoticz. I have run that for a while with my Nibe VVM310 indoor unit, However now I have invested in an outdoor compressor F2120 16KW, this shows up as "Slave1" in my nibeuplink webpage with its parameters, But when i run the "redefine" non of those new parameters from Slave1 shows up.
Do i miss something, or is the uplink plugin not supporting "Slaves"?
Thank you
/Andreas
-
- Posts: 485
- Joined: Thursday 17 September 2015 10:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
Domoticz RPC for NIBE Uplink version 1.2.0 released
Domoticz RPC for NIBE Uplink version 1.2.0 has been released.
Domoticz RPC for NIBE Uplink now supports a new System Alarm Domoticz virtual device. After upgrading, run "redefine". Please have a look at the initial post.
Quoted from the initial post:
Getting alarms
Most Nibe systems have a physical alarm output that will reflect the Nibe Systems alarm status, e.g. if there is an error that prevents the system from doing what it normally does (producing heat for example). A dirty filter alarm for example is not considered to be such an error. This alarm output is also watched by Nibe Uplink and can be represented by a virtual device on Domoticz. Its typically called something similar to "F750 X7". It's currently not so well documented by Nibe exactly what kind of alarms that will be passed in the Nibe Uplink API. In addition to the alarm output information (X7) that we receive from Nibe Uplink API, we also get an overall alarm status named "HasAlarmed" (An alarm indication that something in your system's operation is not working as intended). Introduced in version 1.2.0, a new Domoticz virtual alert device is available named "System Alarm" that will reflect the system's current "HasAlarmed" status.
Domoticz RPC for NIBE Uplink now supports a new System Alarm Domoticz virtual device. After upgrading, run "redefine". Please have a look at the initial post.
Quoted from the initial post:
Getting alarms
Most Nibe systems have a physical alarm output that will reflect the Nibe Systems alarm status, e.g. if there is an error that prevents the system from doing what it normally does (producing heat for example). A dirty filter alarm for example is not considered to be such an error. This alarm output is also watched by Nibe Uplink and can be represented by a virtual device on Domoticz. Its typically called something similar to "F750 X7". It's currently not so well documented by Nibe exactly what kind of alarms that will be passed in the Nibe Uplink API. In addition to the alarm output information (X7) that we receive from Nibe Uplink API, we also get an overall alarm status named "HasAlarmed" (An alarm indication that something in your system's operation is not working as intended). Introduced in version 1.2.0, a new Domoticz virtual alert device is available named "System Alarm" that will reflect the system's current "HasAlarmed" status.
-
- Posts: 1
- Joined: Thursday 26 October 2017 20:58
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Domoticz RPC for NIBE Uplink
Thanks for a nice Domoticz plugin!! It’s really nice to see my Nibe data in Domoticz.
I have an outdoor compressor too, which also shows up as ‘Slave1’.
I played a little bit with the Nibe Uplink api trying to retrieve this slave data, I managed to get the connected units (i.e. master, but also my slave unit) by getting api/v1/systems/{systemId}/units.
The systemUnitId from the response is an optional parameter when getting the available catagories (including paramaters as an optional parameter too):
api/v1/systems/{systemId}/serviceinfo/categories?systemUnitId=1¶meters=true (0 = default, 1 is my slave).
It would be nice if the plugin could support this ‘slaves’, thanks.
I have an outdoor compressor too, which also shows up as ‘Slave1’.
I played a little bit with the Nibe Uplink api trying to retrieve this slave data, I managed to get the connected units (i.e. master, but also my slave unit) by getting api/v1/systems/{systemId}/units.
The systemUnitId from the response is an optional parameter when getting the available catagories (including paramaters as an optional parameter too):
api/v1/systems/{systemId}/serviceinfo/categories?systemUnitId=1¶meters=true (0 = default, 1 is my slave).
It would be nice if the plugin could support this ‘slaves’, thanks.
-
- Posts: 485
- Joined: Thursday 17 September 2015 10:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
Re: Domoticz RPC for NIBE Uplink
Thanks for the suggestion.maartenh wrote: ↑Thursday 26 October 2017 21:15 Thanks for a nice Domoticz plugin!! It’s really nice to see my Nibe data in Domoticz.
I have an outdoor compressor too, which also shows up as ‘Slave1’.
I played a little bit with the Nibe Uplink api trying to retrieve this slave data, I managed to get the connected units (i.e. master, but also my slave unit) by getting api/v1/systems/{systemId}/units.
The systemUnitId from the response is an optional parameter when getting the available catagories (including paramaters as an optional parameter too):
api/v1/systems/{systemId}/serviceinfo/categories?systemUnitId=1¶meters=true (0 = default, 1 is my slave).
It would be nice if the plugin could support this ‘slaves’, thanks.
-
- Posts: 10
- Joined: Friday 19 June 2015 13:47
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Domoticz RPC for NIBE Uplink
Hi
I have just paid for access to your script for NIBE API. I wasn't redirected to the download page. How can I download it now?
treb0r
I have just paid for access to your script for NIBE API. I wasn't redirected to the download page. How can I download it now?
treb0r
-
- Posts: 485
- Joined: Thursday 17 September 2015 10:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
Re: Domoticz RPC for NIBE Uplink
Thanks. I already received 3 PM:s from you and I've also sent an answer to you by PM.
Hi XX
You should have received an e-mail from FetchApp with the download link. Have a look in your inbox for XX
In case you can't find that e-mail have a look in your SPAM folder. I also resent the order in case the first e-mail got lost in some way. Thanks.
-
- Posts: 9
- Joined: Wednesday 29 November 2017 10:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Domoticz RPC for NIBE Uplink
Hallo!
Does the RPC require the NIBE premium subscriptions, or will it function with an Uplink account without the payed subscriptions for "manage" and "history"?
B.R /RedTop
Does the RPC require the NIBE premium subscriptions, or will it function with an Uplink account without the payed subscriptions for "manage" and "history"?
B.R /RedTop
-
- Posts: 485
- Joined: Thursday 17 September 2015 10:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
Re: Domoticz RPC for NIBE Uplink
NEWS!
From January 1, 2018 I have decided that this software will be released under GNU General Public License v3.0. In short, you will get it for free. The source code will be available at GitHub.
The hope is that there will be more people that like to collaborate and contribute with adding new features etc.
From January 1, 2018 I have decided that this software will be released under GNU General Public License v3.0. In short, you will get it for free. The source code will be available at GitHub.
The hope is that there will be more people that like to collaborate and contribute with adding new features etc.
-
- Posts: 5
- Joined: Sunday 23 August 2015 9:58
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Domoticz RPC for NIBE Uplink
Hi,
Be a happy user of the software for quite sometime. Had to reinstall the os on the reaspberry pi 3. I'm now running stretch and have som issues when trying to install the RPC software.
First I enter the application's identifier and it works fine. Then i enter the application's secret and after that i get the following erros:
"Unexpected status code from Domoticz: 401"
Are there any thoughts on what might cause this?
regards,
Daniel
Be a happy user of the software for quite sometime. Had to reinstall the os on the reaspberry pi 3. I'm now running stretch and have som issues when trying to install the RPC software.
First I enter the application's identifier and it works fine. Then i enter the application's secret and after that i get the following erros:
"Unexpected status code from Domoticz: 401"
Are there any thoughts on what might cause this?
regards,
Daniel
-
- Posts: 485
- Joined: Thursday 17 September 2015 10:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
Re: Domoticz RPC for NIBE Uplink
Please check that Domoticz is reachable at the IP and port that you have specified in the configuration.dofhus wrote: ↑Saturday 23 December 2017 17:29 Hi,
Be a happy user of the software for quite sometime. Had to reinstall the os on the reaspberry pi 3. I'm now running stretch and have som issues when trying to install the RPC software.
First I enter the application's identifier and it works fine. Then i enter the application's secret and after that i get the following erros:
"Unexpected status code from Domoticz: 401"
Are there any thoughts on what might cause this?
regards,
Daniel
-
- Posts: 5
- Joined: Sunday 23 August 2015 9:58
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Domoticz RPC for NIBE Uplink
There is no problem accessing the webpage of domoticz via the ip and port so that part is correct.BakSeeDaa wrote: ↑Saturday 23 December 2017 17:33Please check that Domoticz is reachable at the IP and port that you have specified in the configuration.dofhus wrote: ↑Saturday 23 December 2017 17:29 Hi,
Be a happy user of the software for quite sometime. Had to reinstall the os on the reaspberry pi 3. I'm now running stretch and have som issues when trying to install the RPC software.
First I enter the application's identifier and it works fine. Then i enter the application's secret and after that i get the following erros:
"Unexpected status code from Domoticz: 401"
Are there any thoughts on what might cause this?
regards,
Daniel
python /home/pi/domoticz/scripts/NibeUplink/nibeuplink.pyc -v
Domoticz RPC for NIBE Uplink Version 1.2.0 running on TTY console...
Unexpected status code from Domoticz: 401
output from running the script.
Who is online
Users browsing this forum: No registered users and 1 guest