Domoticz

A lot of times, the temperature sensor is not working quite well.. It seems like it's just dies when I set the Thermostat to 'away' (in graph below, this would be around 22:00) and it doesn't wake up when I set it back to 21 degrees (at 7:30).
Setting the temperature with Domoticz is not a problem.

I tried forcing the update script: But to no avail.
This script is also present in my crontab: I already removed all devices, and re-installed them with: The reading of the temp is working fine in the Honeywell 'Home' app.

Any thoughts? Any logging I could check?

Well, talking about unused evohome devices. I removed these:
Maybe I've shouldn't have done that . Added them again. Let's see how this goes. Otherwise I should have a look at your C++ stuff .

gordonb3 wrote:Hmmmm.... Is this a single zone setup? Round wireless? Would be strange to receive a different order if there is only one. In any case, if something comes in between you should see one or more of the unused zones change name and/or update time. If you like to get in depth you could get into the evo-update script and add some 'print' lines to see what is different if you set mode to 'Away'.

Yes It's single zone. And round wireless indeed.
Adding some print lines would be a good idea indeed.

gordonb3 wrote:Maybe your home installation actually goes to sleep and stops feeding information to the Evohome central server when in 'Away'.

You could be right about that: I did some extra testing.

Got the same problem again:
At 18:15 I set the thermostat by hand (read: I turned the round thermostat) to 5 degrees. In domoticz, you can see the temperature sensor doesn't get updated, and the 'set' temp also isn't moved back to 5 degrees.

Got it.

I made a mistake placing the evo-update.sh entry in the pi-user's crontab file .
Should've used instead..