It works correctly now, thanks!

Been struggling some time sending commands to the Round from the Domoticz controller: ended up getting error 256 everytime. Stupid me did not check the log file (thought it was something with file permissions), but now I see I get 'ERROR: bad timestamp value on command line'. When I adjust the ...

I believe the key was empty, yes.

Found the problem: I did not have any schedule set up in the Honeywell-app. After I created some, the client does add my thermostat correctly, showing current temperature etc. Tonight I will continue playing with it. Thanks so far for the help.

Terminal returns: root@DietPi:/home/root/evohomeclient-1.2.0# /home/root/evohomeclient-1.2.0/evo-client --init identify zones collect data for zone 0 [OK] Segmentation fault Log file: evo-client start: 2017-06-06 16:27:09 connect to Domoticz server got ID '-1' for Evohome hardware with name 'evohome ...

Sure, would be nice if it works! Please advice what I should do.

-iv outputs the following: evo-client start: 2017-06-06 13:16:11 connect to Domoticz server got ID '5' for Evohome hardware with name 'evohome' init mode enabled create hardware in Domoticz WARNING: hardware device evohome already exists connect to Evohome server retrieve Evohome installation info ...

Good day, I compiled client version 1.2.0 on a rPi Zero W running DietPi, and this worked. However, I cannot get my thermostat to show up properly in Domoticz. The client does create a lot of zone devices, but all of them show 0.0 C (actually I only got one zone, just the living room). I use a Round ...