Domoticz

rostyk wrote:Works good.
Robert today implementing some code changes regarding set temperature (to be able to work with clock mode as well) and introduce a server mode whcih also look reasonable because now for every command you use authentication every cycle which is not so good from server (bosch) side.
We should work like iOs/Android app: open connection -> authenticate > execute commands -> execute next command ... repeat.

rostyk wrote:i know it still not finished but i missing get and put commands in node.
For example i want to read /heatingCircuits/hc1/actualSupplyTemperature
its not possible to do up to now from node-red interface

pepijn wrote:
TESTERS NEEDED

I published the first version of the Node to github.
You can install it using:

Code: Select all

sudo npm install pepijng/node-red-contrib-nefit-easy -g

Doler wrote:

pepijn wrote:
TESTERS NEEDED

I published the first version of the Node to github.
You can install it using:

Code: Select all

sudo npm install pepijng/node-red-contrib-nefit-easy -g

Thanks for all your efforts, being able to see my Nefit Easy in Domoticz makes me happy

Installed the new node with success, had to reboot to make it appear in node-red.

Used your sample flow for testing: after configuring the nefit easy nodes and Domoticz idx-numbers it started to work. Had one error 'lost server connection' but that was solved with a restart. Didn't see that since.
One thing that doesn't work is the update of the set-point. I cannot change it from Domoticz, changes applied using the android app came in very slowly (should take max 30 seconds, right?). I had the same problem with your previous solution using the scripts (others mentioned the problem too). When I change the setpoint running the script nefit-set from the command line things work fine! There must be something that I missed?

Appreciate your help.

Thanks, Mark

pepijn wrote:
Can set your thermostat to manual before changing the temperature from Domoticz? #this is a known issue#

• Using nefit-easy-client as dependency
• Fixed set temperature when program is active

sudo npm remove -g node-red-contrib-nefit-easy
sudo npm install -g pepijng/node-red-contrib-nefit-easy
sudo service nodered restart

pepijn wrote:

rostyk wrote:i know it still not finished but i missing get and put commands in node.
For example i want to read /heatingCircuits/hc1/actualSupplyTemperature
its not possible to do up to now from node-red interface

I did not add Low level GET and PUT operations, my intention is to add these values human readable into the dropdown list.

rostyk wrote:

pepijn wrote:

rostyk wrote:i know it still not finished but i missing get and put commands in node.
For example i want to read /heatingCircuits/hc1/actualSupplyTemperature
its not possible to do up to now from node-red interface

I did not add Low level GET and PUT operations, my intention is to add these values human readable into the dropdown list.

ok. then i added this feature by configuring some backend script

http://rostyk.net/test/node_Red_easy.jpg
yes i forgot rbe filter in a node flowtemp when making screenshot

pepijn wrote:New version:

• Using nefit-easy-client as dependency
• Fixed set temperature when program is active

install

Code: Select all

sudo npm remove -g node-red-contrib-nefit-easy
sudo npm install -g pepijng/node-red-contrib-nefit-easy
sudo service nodered restart

Doler wrote:

pepijn wrote:New version:

• Using nefit-easy-client as dependency
• Fixed set temperature when program is active

install

Code: Select all

sudo npm remove -g node-red-contrib-nefit-easy
sudo npm install -g pepijng/node-red-contrib-nefit-easy
sudo service nodered restart

Updated without a hassle but it doesn't help my case. See if I (being a noob) understand things correct:
MQTT is listening to device updates in Domoticz. When the Setpoint is changed, MQTT and Domoticz communicate using json and when ok, execute action. My guess is that there is something going wrong in communication: I see the log message in Domoticz but see nothing in the debug window in Node-RED. Did I miss some pre-requisites or configuration details?

Thanks, Mark

pepijn wrote:

Doler wrote:

pepijn wrote:New version:

• Using nefit-easy-client as dependency
• Fixed set temperature when program is active

install

Code: Select all

sudo npm remove -g node-red-contrib-nefit-easy
sudo npm install -g pepijng/node-red-contrib-nefit-easy
sudo service nodered restart

Updated without a hassle but it doesn't help my case. See if I (being a noob) understand things correct:
MQTT is listening to device updates in Domoticz. When the Setpoint is changed, MQTT and Domoticz communicate using json and when ok, execute action. My guess is that there is something going wrong in communication: I see the log message in Domoticz but see nothing in the debug window in Node-RED. Did I miss some pre-requisites or configuration details?

Thanks, Mark

Can you check the device id in filter checkpoint idx

renebiemans wrote:Hi I've tried to get the client working but I can't get it working on a clean install of domoticz(with the SD card for Raspberry PI). I tried on RPI1 and PRI2. When I look in node-red I can't see the nefit easy part. Are there some parts that has to be installed before installing the client?

During the installation the installer gives an warning about engine wanted node :>=4.0 current node: 0.12.1 npm 2.5.1 I tried to install a newer version of node.js but not maybe not with succes.

pepijn wrote:

renebiemans wrote:Hi I've tried to get the client working but I can't get it working on a clean install of domoticz(with the SD card for Raspberry PI). I tried on RPI1 and PRI2. When I look in node-red I can't see the nefit easy part. Are there some parts that has to be installed before installing the client?

During the installation the installer gives an warning about engine wanted node :>=4.0 current node: 0.12.1 npm 2.5.1 I tried to install a newer version of node.js but not maybe not with succes.

Did you restart node-red after installing the nefit-easy node?

rostyk wrote:

pepijn wrote:

rostyk wrote:i know it still not finished but i missing get and put commands in node.
For example i want to read /heatingCircuits/hc1/actualSupplyTemperature
its not possible to do up to now from node-red interface

I did not add Low level GET and PUT operations, my intention is to add these values human readable into the dropdown list.

ok. then i added this feature by configuring some backend script

http://rostyk.net/test/node_Red_easy.jpg
yes i forgot rbe filter in a node flowtemp when making screenshot

rostyk wrote:@pepijn
i got once per hour a error with crash of node-red:

Code: Select all

Error: read ECONNRESET
    at exports._errnoException (util.js:870:11)
    at TLSWrap.onread (net.js:544:26)

looks like connection are closed (dropped by nefit easy) after a 40-50 minutes.

i will report after clean reinstall (probably caused by mine changes in a code)

6 Jan 17:26:26 - [red] Uncaught Exception:
6 Jan 17:26:26 - Error: read ECONNRESET
    at exports._errnoException (util.js:855:11)
    at TLSWrap.onread (net.js:544:26)

Re: Nefit Easy™ client library (How to install on the Pi)

Postby pepijn » Wednesday 06 January 2016 16:57




renebiemans wrote:
Hi I've tried to get the client working but I can't get it working on a clean install of domoticz(with the SD card for Raspberry PI). I tried on RPI1 and PRI2. When I look in node-red I can't see the nefit easy part. Are there some parts that has to be installed before installing the client?

During the installation the installer gives an warning about engine wanted node :>=4.0 current node: 0.12.1 npm 2.5.1 I tried to install a newer version of node.js but not maybe not with succes.

Did you restart node-red after installing the nefit-easy node?

renebiemans wrote:

Re: Nefit Easy™ client library (How to install on the Pi)

Postby pepijn » Wednesday 06 January 2016 16:57




renebiemans wrote:
Hi I've tried to get the client working but I can't get it working on a clean install of domoticz(with the SD card for Raspberry PI). I tried on RPI1 and PRI2. When I look in node-red I can't see the nefit easy part. Are there some parts that has to be installed before installing the client?

During the installation the installer gives an warning about engine wanted node :>=4.0 current node: 0.12.1 npm 2.5.1 I tried to install a newer version of node.js but not maybe not with succes.

Did you restart node-red after installing the nefit-easy node?

Yes I tried that. I think the problem is in deed with the update of node. I have tried to update to 5.3.0 but I get an error when I want to copy to package with the command: sudo cp -R * /usr/local/

I get the following error: cp: cannot create regular file '/usr/local/bin/node': text file busy. I allready tried to reboot remove the files but I can't get premission. I also tried a complete clean installation(sd image).

Doler wrote:

rostyk wrote:@pepijn
i got once per hour a error with crash of node-red:

Code: Select all

Error: read ECONNRESET
    at exports._errnoException (util.js:870:11)
    at TLSWrap.onread (net.js:544:26)

looks like connection are closed (dropped by nefit easy) after a 40-50 minutes.

i will report after clean reinstall (probably caused by mine changes in a code)

I have the same problem, 7 minutes after a restart of red-node

Code: Select all

6 Jan 17:26:26 - [red] Uncaught Exception:
6 Jan 17:26:26 - Error: read ECONNRESET
    at exports._errnoException (util.js:855:11)
    at TLSWrap.onread (net.js:544:26)

Mark