Evohome V1 (monochrome) with HGI80 and Domoticz v3.8742

For heating/cooling related questions in Domoticz

Moderator: leecollings

Post Reply
japie101
Posts: 8
Joined: Tuesday 03 March 2015 10:42
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Evohome V1 (monochrome) with HGI80 and Domoticz v3.8742

Post by japie101 »

Hi,

I am running Domoticz 3.8742 on a RasPi 2 with a Honeywell HGI80 to mange my Evohome V1 (the monocrome version).

Actually I had some issues so I decided to do a fresh integration, throwing the HW away and create a new one (this has been working for years).

So now when I add my HGI80 hardware, I just select the USB port and the serial speed at 115200 (which should be the one HGI80 is using).

Normally I start seeing my zones within minutes but for some reason, at this point no zones at all are popping up in Domoticz.
I did see some Evohome messages, about opening the USB port, which is going fine, but no single device is created.

Anyone does have the same setup or had the same experience?
japie101
Posts: 8
Joined: Tuesday 03 March 2015 10:42
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Evohome V1 (monochrome) with HGI80 and Domoticz v3.8742

Post by japie101 »

Even after more than 24 hours no devices popped up.

However I do have some errors in the logging: (this is also the only logging coming from the HGI80 as far as I can see)

2017-11-23 04:37:18.701 Error: evohome: uneven payload - possible corrupt message
2017-11-23 05:54:29.262 Error: evohome: uneven payload - possible corrupt message
japie101
Posts: 8
Joined: Tuesday 03 March 2015 10:42
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Evohome V1 (monochrome) with HGI80 and Domoticz v3.8742

Post by japie101 »

Some interesting info to share, it seems I have managed to solve this, probably this might help others.

I changed the USB port on my Raspi 2 this morning, and checked the logging afterwards (in Domoticz)
It showed the following:

2017-11-23 08:48:40.307 evohome serial: Opening serial port: /dev/ttyUSB-Evo@115200

2017-11-23 08:48:47.294 evohome: controller detected, ID:0xaaaaa
2017-11-23 08:48:50.697 evohome: controller detected, ID:0xbbbbb

This is kinda strange it's detecting two controllers, for some reason (never saw this before, but probably my neighbor also started using Evohome?)

So I waited couple of minutes and suddenly Domoticz was not responding, it crashed!
So I went to the Domoticz logging to see what happened:

2017-11-23 08:53:40.488 Error: evohome serial: multiple controllers detected! Please set controller ID in hardware settings.
2017-11-23 08:53:40.489 Error: Domoticz received fatal signal 6 !...
2017-11-23 08:53:40.493 Error: /home/pi/domoticz/domoticz() [0x230390]
2017-11-23 08:53:40.494 Error: /home/pi/domoticz/domoticz(_Z14signal_handleri+0x4c) [0x230448]
2017-11-23 08:53:40.494 Error: /lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer_v2+0) [0x76c0b180]
2017-11-23 08:53:40.494 Error: /lib/arm-linux-gnueabihf/libc.so.6(gsignal+0x38) [0x76c09f70]

So I saved the two controllers and instead of not using the Controller ID (HEX) in Hardware configuration (this was only introduced recently, I never used it before) I decided to enter the first controller ID which showed up earlier in the Domoticz logging, and it started working immediately!

Offcourse I also tried the second controller, and thats working either, with the same devices popping up (my devices).

So for some reason my setup (HGI80 with Evohome V1, BDR91 and HR80 radiator bulbs) is generating two controller IDs, which is causing Domoticz to crash since it's not making a decision out of the two.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest