Evohome temperature stops updating after succesful setting temperature

For heating/cooling related questions in Domoticz
thijsvdb
Posts: 6
Joined: Saturday 14 May 2016 20:25
Target OS: Raspberry Pi
Domoticz version:
Contact:

Evohome temperature stops updating after succesful setting temperature

Postby thijsvdb » Saturday 14 May 2016 21:00

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:

[email protected]:~/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!

gordonb3
Posts: 448
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome temperature stops updating after succesful setting temperature

Postby gordonb3 » Tuesday 17 May 2016 12:31

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)
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

BasPost
Posts: 22
Joined: Thursday 25 June 2015 15:14
Target OS: Raspberry Pi
Domoticz version: V2.2563
Contact:

Re: Evohome temperature stops updating after succesful setting temperature

Postby BasPost » Wednesday 18 May 2016 13:44

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
Posts: 40
Joined: Thursday 15 October 2015 12:00
Target OS: Linux
Domoticz version: beta
Location: Wales
Contact:

Re: Evohome temperature stops updating after succesful setting temperature

Postby karl8754 » Wednesday 18 May 2016 14:15

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
Posts: 6
Joined: Saturday 14 May 2016 20:25
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Evohome temperature stops updating after succesful setting temperature

Postby thijsvdb » Wednesday 18 May 2016 16:23

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

thijsvdb
Posts: 6
Joined: Saturday 14 May 2016 20:25
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Evohome temperature stops updating after succesful setting temperature

Postby thijsvdb » Thursday 19 May 2016 22:40

gordonb3 wrote: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
Posts: 16
Joined: Wednesday 07 December 2016 20:13
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Evohome temperature stops updating after succesful setting temperature

Postby markcame » Saturday 07 January 2017 0:12

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

gordonb3
Posts: 448
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome temperature stops updating after succesful setting temperature

Postby gordonb3 » Saturday 07 January 2017 9:53

How about trying this one instead?

Copy evonfig.py to evoconfig (no extension) and add `-l <OUTPUTFILE> ` to the command in cron. If the job runs it will report what's happening in OUTPUTFILE.
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

markcame
Posts: 16
Joined: Wednesday 07 December 2016 20:13
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Evohome temperature stops updating after succesful setting temperature

Postby markcame » Wednesday 11 January 2017 19:46

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 ?

gordonb3
Posts: 448
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome temperature stops updating after succesful setting temperature

Postby gordonb3 » Wednesday 11 January 2017 22:47

The .py extension indicates (or suggests) a python script. In my client this is not the case - it's purely a config file (or ini file if you are more a Windows type of person). Hence the dropping of the extension.

Of course I don't know your specific setup, but let's say you put the client in /home/pi/domoticz/scripts then you could use the following crontab entry:

Code: Select all

*/1 * * * * /home/pi/domoticz/scripts/evo-client -l /tmp/evo-client.log

If you do not see /tmp/evo-client.log appearing then your cron job is not firing. If it does appear it will tell you what is happening and/or why it fails.
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000


Return to “Heating/cooling”

Who is online

Users browsing this forum: No registered users and 2 guests