Evohome controlling

For heating/cooling related questions in Domoticz
jenssen
Posts: 20
Joined: Wednesday 13 July 2016 22:13
Target OS: Windows
Domoticz version: 3.5834
Contact:

Re: Evohome controlling

Postby jenssen » Tuesday 22 November 2016 22:35

mschut wrote:Hmm. Too bad I don't have a spare Windows 10 device lying around.

Verstuurd vanaf mijn SM-G920F met Tapatalk


More then two weeks running on Windows 10, Domoticz version 3.5864, no problems so far..... What workaround do you use on the pi, scheduled reboots?

Kind regards

mschut
Posts: 134
Joined: Sunday 23 February 2014 22:40
Target OS: Raspberry Pi
Domoticz version: V3.5613
Location: Netherlands
Contact:

Re: Evohome controlling

Postby mschut » Tuesday 22 November 2016 22:38

No work arounds. Rebooted every day is not going to make things stable or reliable. Bought a second hand Mac Mini in order to install and run Domoticz. Hoping to find the same result as you have on the windows machine. Keep you updated, in need of a monitor first to get things going (who does have a spare monitor these days ;) )

Verstuurd vanaf mijn SM-G920F met Tapatalk

DanD
Posts: 125
Joined: Saturday 05 March 2016 10:59
Target OS: Raspberry Pi
Domoticz version: 3.5641
Location: UK
Contact:

Re: Evohome controlling

Postby DanD » Tuesday 13 December 2016 17:24

@Lisa

I've been testing my Evohome set-ups over the last few weeks to try and understand what's causing the Domoticz message sending crash. Unfortunately, I'm no longer able to reproduce the problem on either of my installations (Linux RPi3 and Windows 7). I've tested both installations for at least a week and neither will crash anymore. I've tried various versions of Domoticz, old device lists and new ones, but they all refuse to crash. My best guess is that the problem might possibly be something due to a synchronisation between the Evohome controller and Domoticz, which causes the HGI80 messages to be rejected by the controller. When I was still able to reproduce the crash, all my debugging indicated that the messages were being sent OK from the HGI80. I think it's worth trying switching off your controller by removing its batteries and then restarting, as this is the only thing I can guess that might have fixed my setup (I accidentally did this a few times a month or so ago as my controller has a bad battery contact and I wonder if this has fixed my problem).

Let me know if you have any success.
Thanks,

Dan
Windows 7, Raspberry Pi3, Honeywell Evohome Wifi, HGI80 + RFBee(s)

Lisa
Posts: 89
Joined: Tuesday 01 September 2015 23:18
Target OS: Windows
Domoticz version:
Contact:

Re: Evohome controlling

Postby Lisa » Thursday 15 December 2016 23:12

@DanD, following your post i am investigating the HGI80 as the major suspect. However, mine doesn't have a battery and simply removing and rejoining the USB cable did not work. However, when running DMESG in the command prompt, i noticed this problem:

Code: Select all

 ti_interrupt_callback - nonzero urb status, -71
and this error:

Code: Select all

 ti_usb_3410_5052_1 ttyUSB1: ti_bulk_out_callback - nonzero urb status, -71

So i thought that there might be a problem with the USB connection, so that you can receive HGI80 messages but not send to it.
Since the HGI80 cable was attached to an USB hub, i relocated the USB cable to connect directly to the server usb port.
And.... it worked!
Now i do not have any problems anymore and is it working just fine. So it seems that in my case the USB hub was the problem, unknown to me is the reason for this (nor do i care much).

Thx for your hint!
Last edited by Lisa on Wednesday 28 December 2016 23:23, edited 1 time in total.

DanD
Posts: 125
Joined: Saturday 05 March 2016 10:59
Target OS: Raspberry Pi
Domoticz version: 3.5641
Location: UK
Contact:

Re: Evohome controlling

Postby DanD » Thursday 15 December 2016 23:38

@lisa

Excellent! Thanks for sharing your success. I'll remember next time I hit this problem to troubleshoot the USB status and see if it has died.

Dan
Windows 7, Raspberry Pi3, Honeywell Evohome Wifi, HGI80 + RFBee(s)

jenssen
Posts: 20
Joined: Wednesday 13 July 2016 22:13
Target OS: Windows
Domoticz version: 3.5834
Contact:

Re: Evohome controlling

Postby jenssen » Saturday 13 May 2017 18:23

DanD wrote:Hi,

Unfortunately still no fix yet for the Domoticz Evohome commands failing problem. I've replicated the problem in Windows and on a Pi, but the variable amount of time for the problem to occur (between a few hours and many days on my systems) means that the troubleshooting is taking a very long time. My best guess at the moment is that its a memory allocation problem within the SendQueue function. Hopefully I'll get this fixed before next Winter :)!

A potential temporary workaround for those installations where it runs OK for a day or so might be to automatically stop and restart the Domoticz service each day.

Dan


Hello Dan, do you know if this problem is solved now on Linux?

DanD
Posts: 125
Joined: Saturday 05 March 2016 10:59
Target OS: Raspberry Pi
Domoticz version: 3.5641
Location: UK
Contact:

Re: Evohome controlling

Postby DanD » Saturday 13 May 2017 19:09

@jenssen

Hi,

I can confirm that I've not experienced this problem with the latest Domoticz beta code since late last year (I run and test Domoticz on Linux & Windows 7 and compile the latest beta code every 2-3 months). I didn't make any updates to the Domoticz code to fix the problem, but it disappeared from my systems last year (I run Domoticz on 4 different machines). I've since used additional USB devices (RFBee's) which function the same as the HGI80 and my guess is that the problem is most likely related to either a USB driver problem or its lock-out feature, as I do occasionally hit brief problems with the HGI80 refusing to send any messages, but it still receives perfectly OK. The RFBee USB devices allow me to monitor whether the HGI80 is actually sending messages. The HGI80 has a lock-out feature which blocks message sending if too many messages are sent within a fixed period of time. It is possible that some of my changes to the Domoticz code have reduced the frequency of messages sent and hence the problem has disappeared, but this is just a guess.

Are you still experiencing this problem on your system and if so, what version of Domoticz are you running?

Dan
Windows 7, Raspberry Pi3, Honeywell Evohome Wifi, HGI80 + RFBee(s)

jenssen
Posts: 20
Joined: Wednesday 13 July 2016 22:13
Target OS: Windows
Domoticz version: 3.5834
Contact:

Re: Evohome controlling

Postby jenssen » Saturday 13 May 2017 20:28

DanD wrote:@jenssen

Hi,

I can confirm that I've not experienced this problem with the latest Domoticz beta code since late last year (I run and test Domoticz on Linux & Windows 7 and compile the latest beta code every 2-3 months). I didn't make any updates to the Domoticz code to fix the problem, but it disappeared from my systems last year (I run Domoticz on 4 different machines). I've since used additional USB devices (RFBee's) which function the same as the HGI80 and my guess is that the problem is most likely related to either a USB driver problem or its lock-out feature, as I do occasionally hit brief problems with the HGI80 refusing to send any messages, but it still receives perfectly OK. The RFBee USB devices allow me to monitor whether the HGI80 is actually sending messages. The HGI80 has a lock-out feature which blocks message sending if too many messages are sent within a fixed period of time. It is possible that some of my changes to the Domoticz code have reduced the frequency of messages sent and hence the problem has disappeared, but this is just a guess.

Are you still experiencing this problem on your system and if so, what version of Domoticz are you running?

Dan


Hello Dan,

Thanks for your fast answers. At this moment I am still running the same OS that I switched to last year (Windows 10), I do not have any problems. I only had the problem on my other setup, Linux on PI3. I want to switch back to Linux (Debian) so that why I was asking. When I am switched I can let u know if this is working properly.

mschut
Posts: 134
Joined: Sunday 23 February 2014 22:40
Target OS: Raspberry Pi
Domoticz version: V3.5613
Location: Netherlands
Contact:

Re: Evohome controlling

Postby mschut » Friday 19 May 2017 21:52

I am running on the latest beta for a while now and it seems it is working without issues (knock on wood). Or at least, it continues wordking already for I would guess at least 2 weeks. Really, really glad indeed.

The only issue I could have noticed (i didn't drill down my logs enough to be certain), is switching my Evohome status (e.g. from Away to Home) by a json command, and it being switched back again (perhaps it didnt arrive well enough and the controller told Domoticz again it was Away, which it shouldnt). Anyway, I realise explaining this situation is hard enough to be logical, ony if I am certain I still do have a small issue, I would report here again. For now, I am enjoying the possibility to control my Evohome by my Domoticz setup.


Return to “Heating/cooling”

Who is online

Users browsing this forum: No registered users and 1 guest