Evohome temperature stops updating after succesful setting temperature

[thijsvdb]

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#S ... for_RFG100.

Situation:
- EvoTouch and the 3 rooms are available in Domoticz.
- Temperatures are being updated every minute.
- EvoTouch is not being updated.

I have the following behaviour:
- On Domoticz I update the temp of one the rooms for the next two hours succesfully.
- The temperature keeps on changing every minute succesully.
- Now if I click Cancel Override on that particular room nothing happens.
- Next to that, the temperature stops updating for all rooms.

I log on using SSH to use the evo-update.sh command and get the following:

pi@raspberrypi:~/evohome-client$ ./evo-update.sh
Traceback (most recent call last):
File "./evo-update.sh", line 24, in <module>
os.remove("/var/tmp/evo-noup.tmp")
OSError: [Errno 1] Operation not permitted: '/var/tmp/evo-noup.tmp'

I now first need to remove the .tmp file and run evo-update.sh again to have the temperature updated.

Any ideas on how to ensure that the action Cancel Override for a room does not cause this behaviour?

Thanks!

[BasPost]

I have the exact same issue, it worked for months, I've installed an update from the beta channel and stopped working. I don't know what version I had before updating though

[karl8754]

Similar situation here. Working fine for months but last night Domoticz seemed to 'lose' the Evohome (via HGI80); just stopped working and wouldn't pick it back up. I did eventually get it working again, not really sure which bit fixed it but I:

1. Updated Domoticz (beta, 3.5143)
2. Restarted the Evohome controller (pulled a battery as I couldn't find any other way)
3. Unplugged HGI80 and reconnected it to PC

It's currently reporting and working okay at the moment, but no idea if it's actually fixed or just a temporary solution.

[thijsvdb]

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

[thijsvdb]

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. Now it works perfectly.

[markcame]

Hello,

I have the same problem, I've tried to setup a sudo crontab -e but seems that the script was not executed....
On the syslog the cronjob was logged but actually no temperature update was performed, if I trigger manually the script all is ok.

I have to change some path ?

Thanks

[markcame]

No I didn't have tried againg but I will look, seems promising

I didn't have understand why you rename evoconfig.py to evoconfig without extension.. the cronjob in the log appear to be executed as root but I'm not able to read it's output..

What is wrong ?