As an alternative you could hack your evohome scripts. The problem is caused by the device IDs having one digit too many. You can hard code these in the scripts and use some search-and-replace functions to let them communicate a smaller ID with Domoticz. I read your comments on other posts and see ...

Seems like an issue with file/OS rights to me. You should verify who owns the evo-noup file as well as what account is used to run the cron job for the evo-update script (should either be the same or root) Thanks. I created sudo crontab -e to run evo-update.sh instead of crontab -e from the pi user ...

I did not.. I will wait for this to become available. Thanks!

I will look into the file authorizations later this week! Thanks for the replies.

My setup is: - Raspberry Pi 2 with the latest version of Domoticz 4834. - Evohome Wifi Thermostat (ATC928G3000) - 3 rooms with HR92 valves I have followed the steps on the Evohome Docmoticz https://www.domoticz.com/wiki/Evohome#Scripting_for_RFG100. Situation: - EvoTouch and the 3 rooms are ...

My setup is: - Raspberry Pi 2 with the latest version of Domoticz 4834. - Evohome Wifi Thermostat (ATC928G3000) - 3 rooms with HR92 valves I have followed the steps on the Evohome Docmoticz https://www.domoticz.com/wiki/Evohome#Scripting_for_RFG100. Situation: - EvoTouch and the 3 rooms are ...