Nefit Easy™

[geezerrr]

Hi,

Trying to find an answer to a simple question. Went through the wiki/forum but couldn't find a clear answer.

If I connect a Nefit Easy to Domoticz what functionality do I get?

Can anyone give me some insights?

Cheers,
Lex

Here is printscreen from my Nefit functions in Domoticz

[felix63]

Installed easy httpserver which is working.

If I call it in a browser: http://192.168.178.50:3001/bridge/syste ... emPressure

I get a JSON response:

Code: Select all

{"id":"/system/appliance/systemPressure","type":"floatValue","recordable":0,"writeable":0,"value":25.5,"unitOfMeasure":"bar","minValue":0,"maxValue":25}

If I check PM2 I get:

Code: Select all

pi@domus:~$ pm2 info 0
 Describing process with id 0 - name nefiteasyhttpserver 
┌───────────────────┬────────────────────────────────────────────────────┐
│ status            │ online                                             │
│ name              │ nefiteasyhttpserver                                │
│ restarts          │ 0                                                  │
│ uptime            │ 5m                                                 │
│ script path       │ /home/pi/nefiteasyhttpserver.sh                    │
│ script args       │ N/A                                                │
│ error log path    │ /home/pi/.pm2/logs/nefiteasyhttpserver-error-0.log │
│ out log path      │ /home/pi/.pm2/logs/nefiteasyhttpserver-out-0.log   │
│ pid path          │ /home/pi/.pm2/pids/nefiteasyhttpserver-0.pid       │
│ interpreter       │ bash                                               │
│ interpreter args  │ N/A                                                │
│ script id         │ 0                                                  │
│ exec cwd          │ /home/pi                                           │
│ exec mode         │ fork_mode                                          │
│ node.js version   │ N/A                                                │
│ watch & reload    │ ✘                                                  │
│ unstable restarts │ 0                                                  │
│ created at        │ 2016-09-28T21:06:38.300Z                           │
└───────────────────┴────────────────────────────────────────────────────┘
 Add your own code metrics: http://bit.ly/code-metrics
 Use `pm2 logs nefiteasyhttpserver [--lines 1000]` to display logs
 Use `pm2 monit` to monitor CPU and Memory usage nefiteasyhttpserver

In domotica I have added Hardware of type Nefit:

Code: Select all

15	Nefit Easy	Ja	Nefit Easy HTTP server over LAN interface	192.168.178.50	3001	Niet actief

But if I look at devices I see no new devices added.

What is going wrong? Can anyone help me out?

Running Domoticz V3.4834 on a Raspberry Pi 3

Thanks for your help!

[SweetPants]

Are you sure your Nefit HTTP server is running? Process id = 0 sounds strange to me, this should be higher then 1. Can you check with ps command?

[felix63]

I see all kinds..

Code: Select all

<knip>
avahi      413  0.0  0.2   4008  2428 ?        Ss   02:00   0:08 avahi-daemon: running [domus.local]
message+   414  0.0  0.3   5616  3136 ?        Ss   02:00   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
mosquit+   417  0.0  0.4   5432  3836 ?        S    02:00   0:09 /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf
nobody     430  0.0  0.1   2292  1440 ?        Ss   02:00   0:00 /usr/sbin/thd --daemon --triggers /etc/triggerhappy/triggers.d/ --socket /var/run/thd.socket --pidfile /var/run/t
avahi      440  0.0  0.0   3876   240 ?        S    02:01   0:00 avahi-daemon: chroot helper
root       446  0.0  0.2  14892  2468 ?        Sl   02:01   0:03 /usr/bin/monit -c /etc/monit/monitrc
pi         466  0.0  6.1 138336 58092 ?        SNl  02:01   0:07 node-red                                                                  
root       484  0.0  0.0      0     0 ?        S<   02:01   0:00 [kworker/2:1H]
root       485  0.0  0.3   7156  3336 ?        Ss   02:01   0:00 /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan0.pid -i wlan0 -D nl80211,wext -c /etc/wpa_supplicant/wpa_s
root       491  0.0  0.0      0     0 ?        S<   02:01   0:00 [kworker/0:1H]
root       494  0.0  0.2  32144  2832 ?        Ssl  02:01   0:00 /usr/sbin/rsyslogd -n
root       501  0.0  0.5  35900  5204 ?        Ssl  02:01   0:00 /usr/sbin/lightdm
root       615  0.0  2.7 111440 26336 tty7     Ssl+ 02:01   0:00 /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
root       624  0.0  0.0      0     0 ?        S<   02:01   0:00 [kworker/u9:0]
root       625  0.0  0.0      0     0 ?        S<   02:01   0:00 [hci0]
root       626  0.0  0.0      0     0 ?        S<   02:01   0:00 [hci0]
root       627  0.0  0.0   2068   132 ?        S    02:01   0:00 /usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow -
root       629  0.0  0.0      0     0 ?        S<   02:01   0:00 [kworker/u9:2]
root       632  0.0  0.3   5008  3352 ?        Ss   02:01   0:00 /usr/lib/bluetooth/bluetoothd
root       655  0.0  0.5  27912  5516 ?        Sl   02:01   0:00 lightdm --session-child 17 20
lightdm    659  0.0  0.3   4976  3272 ?        Ss   02:01   0:00 /lib/systemd/systemd --user
lightdm    663  0.0  0.1   7020  1412 ?        S    02:01   0:00 (sd-pam)  
lightdm    666  0.0  3.5  65248 33220 ?        Ssl  02:01   0:07 /usr/sbin/lightdm-gtk-greeter
lightdm    691  0.0  0.1   3692  1488 ?        S    02:01   0:00 /usr/bin/dbus-launch --autolaunch 3882d14b5e8d408bb132425829ac6413 --binary-syntax --close-stderr
lightdm    753  0.0  0.2   5492  2120 ?        Ss   02:01   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
root       754  0.0  0.1   2564  1724 ?        Ss   02:01   0:01 /sbin/dhcpcd -q -w
lightdm    756  0.0  0.5  44428  4788 ?        Sl   02:01   0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
root       757  0.0  0.4   7864  4392 ?        Ss   02:01   0:00 /usr/sbin/sshd -D
lightdm    761  0.0  0.3   5492  2908 ?        S    02:01   0:00 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
lightdm    764  0.0  0.4  17616  4256 ?        Sl   02:01   0:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
root       812  0.0  0.3   7912  3228 ?        S    02:01   0:00 sudo -u pi DEBUG=* /usr/local/bin/homebridge
root       835  0.0  0.1   4052  1752 tty1     Ss+  02:01   0:00 /sbin/agetty --noclear tty1 linux
ntp        837  0.0  0.3   5776  3680 ?        Ss   02:01   0:02 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -c /var/lib/ntp/ntp.conf.dhcp -u 106:111
pi         847  0.0  0.3   4976  3268 ?        Ss   02:01   0:00 /lib/systemd/systemd --user
pi         851  0.0  0.1   7020  1416 ?        S    02:01   0:00 (sd-pam)  
pi         860  0.0  3.6 140968 34800 ?        Sl   02:01   0:05 homebridge                    
snmp       905  0.1  0.5  12992  5244 ?        S    02:01   0:39 /usr/sbin/snmpd -Lsd -Lf /dev/null -u snmp -g snmp -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid
root       906  5.4  2.1 253092 20056 ?        Ssl  02:01  26:28 /home/pi/domoticz/domoticz -daemon -www 8080 -daemon sslwww 443
root      1011  0.0  2.0  93176 19696 ?        Ss   02:01   0:01 /usr/sbin/apache2 -k start
root      1027  0.0  0.4   9356  4100 ?        S    02:01   0:00 lightdm --session-child 13 20
pi        1042  0.0  3.3 128860 31748 ?        Ssl  02:01   0:04 PM2 v2.0.15: God Daemon (/home/pi/.pm2)                          
pi        1200  0.0  0.2   4620  2320 ?        Ss   02:01   0:00 bash /home/pi/nefiteasyhttpserver.sh
pi        1201  0.0  3.6 130152 34428 ?        Sl   02:01   0:26 node /usr/local/bin/easy-server --serial=XXX --access-key=XXX --password=XXX --port=3001 
<knip>

[SweetPants]

Hmm, the PID of the easy-server is 1201 not 0 as pm2 is telling you. So the HTTP server is running.
if you run:
curl http://127.0.0.1:3001/bridge/ecus/rrc/uiStatus
on the shell, what do you see?
Does your port (3001) match the Domoticz setting (default = 3000)
Enabled 'Accept new hardware"?

[felix63]

running in the shell:

Code: Select all

curl http://127.0.0.1:3001/bridge/ecus/rrc/uiStatus
curl: (7) Failed to connect to 127.0.0.1 port 3001: Connection refused

curl http://192.168.178.50:3001/bridge/ecus/rrc/uiStatus
{"id":"/ecus/rrc/uiStatus","type":"uiUpdate","recordable":0,"writeable":0,"value":{"CTD":"2016-09-29T20:49:54+01:00 Th","CTR":"weather","UMD":"manual","MMT":"14.0","CPM":"auto","CSP":"24","TOR":"off","TOD":"0","TOT":"14.0","TSP":"19.0","IHT":"21.40","IHS":"ok","DAS":"off","TAS":"off","HMD":"off","ARS":"init","FPA":"off","ESI":"off","BAI":"No","BLE":"false","BBE":"false","BMR":"false","PMR":"false","RS":"off","DHW":"on","HED_EN":"true","HED_DEV":"true","FAH":"false","DOT":"false","HED_DB":""}}pi@domus:~$

Hardware setting in Domoticz is ip: 192.168.178.50 and port: 3001

[felix63]

Enabled 'Accept new hardware"? was the trick... sorry Thanks for your help!

[jimmyb]

This is an observation of the Worcester Wave more than an issue with this software.

I have a server running Domoticz monitoring my Worcester Wave heating controller via the nefit web server. I have found since monitoring that the wave becomes unresponsive after a couple of days and needs to be reset before coming back to life.

The controller becomes inaccessible from both the nefit web server and the mobile applications which makes me think the issue is with the controller.

Anybody else has this kind of problem?


James

[SweetPants]

The controller becomes inaccessible from both the nefit web server and the mobile applications which makes me think the issue is with the controller. Anybody else has this kind of problem?

Yes, and this has been discussed in this thread before. Last few days it seems to happen more often, possibly because of maintenance on the Bosch backend server(s). It has been stable for me for several months, but now I have issues in the last two days. I also noticed that using the app and HTTP Server at the same time increases the change on 'timeouts' (see domoticz logs). I also inserted a switch (I also use the Nefit Easy Adapter) to power off/on the adapter and therefor the thermostat as well, to restart the connection to the backend by the thermostat in case of 5 minutes no response. Most of the time this helps getting the thing running again, but last few days something else is going on, and an off/on of the adapter not always works.

[mvveelen]

Is it possible to turn on/off the hot water boiler using Domoticz in combination with the Easy-httpd-server ?

[edwin1234]

Can someone please explain how to install this under windows?
Step by step pls
Sorry i a noob at this but want to learn
Thanks

[Kochmeister]

Hi,

I could not find this using the search, but is it possible to switch on and off warm water as well?

That would be great!

nefit.png

Hi all,

I was in contact with Robert Klep and he was very helpfull.
I asked him how to switch the hot water supply on/off
In the Pi's commandline you can do:

Code: Select all

	easy put /dhwCircuits/dhwA/dhwOperationManualMode '{"value":"off"}' --serial=xxxx --access-key=xxxx --password=xxxx

I aksed if he could integrate this in het CommandLineInterface and after an update of the CLI there is an easier way to switch on/off
Update:
npm i -g nefit-easy-cli

Now the hot water supply will show up in 'easy -h' as
easy [options] hot-water-supply [ on | off ]

from domoticz lua I can now switch on/off:

Code: Select all

	os.execute ("easy hot-water-supply on --serial=xxxx --access-key=xxxx --password=xxxx")

So all there is left is that someone integrates this with a nice button in domoticz
I hope this is something 'Holland' can do?!

This is the info I have till now.

Have fun!

[mvveelen]

This should be something the nefit-easy-http-server would be able to do, right?

I managed to break my installation of node.js on my Synology, but got it running again The final step would be to be able to switch the boiler ON and OFF with the nefit-easy-http-server..... So if he could update that package, that would be great. Especially now when the cold period has arrived

[Kochmeister]

This should be something the nefit-easy-http-server would be able to do, right?

Not sure, I am quite a new to this. Only thing I know is that the commandline via LUA is working now.
If I know what is needed I could contact Robert again if he can do an update on the nefit-easy-http-server if that is what it takes to get a on/off button in domoticz.
Maybe he already didan update, but I am not sure.

Anyone who can check?

[pepijn]

No, the http server is not updated but there is no need to do that. You can send this uri directly. What you are looking for is an updated Nefit class in Domoticz to support this feature.

[Kochmeister]

No, the http server is not updated but there is no need to do that. You can send this uri directly. What you are looking for is an updated Nefit class in Domoticz to support this feature.

OK, sounds good, as said, I am quite new to this.
What or who do I need to get this feature in? It would be great to have this feature!

[mvveelen]

So, when Gizmocuz implements this in Domoticz, it could already work ?

@Kochmeister : (if yes) then you probably have to ask Gizmocuz if he can add it to Domoticz.

[mvveelen]

I see Gizmocuz already built this in. Unfortunately, when I add it as a switch and turn it off, in the Nefit app it isn't turned off and after a little while the switch in Domoticz turns on. So, is something overruling the switch in Domoticz or something?

[Kochmeister]

Still work in progress i guess.
He built a beta and the switch operates the hot water on/off fine in my case.
However when I switch the hot water on the thermostat it does not update the switch in domoticz yet.
Little more patience needed

[mvveelen]

So when you switch off the hot water switch in Domoticz, it switches off in the Nefit Easy app on your smartphone? Or do you check it on the wall panel itself?

Edit: can't try it myself right now, because my wife is taking a shower atm