Connecting HGI80 to Evohome v2

[Knarf7]

Can anyone tel me how to connect a Honeywell HGI80 to a Evohome V2 (none WiFi - Ver.25)?

[DanD]

Hi,

Have you taken a look at the Domoticz Evohome wiki linked below:

https://www.domoticz.com/wiki/Evohome ?

It should all work OK with your Evohome controller.

If you are having trouble with some of the steps, please post the details and also info on the device you're running Domoticz on and I'll try and help.

Dan

[Knarf7]

Hello Dan,

Yes, I have read the Wiki at https://www.domoticz.com/wiki/Evohome
What isn't mentioned is the first step how to connect the HGI80 to the Evohome V2. I understand that de Evohome V3 WiFi has a menu how to connect a wireless device such as the HGI80, whereas the Evohome V2 doesn't have this.

When I read the manual how to connect the HGI80 with the Somfy TaHoma+ you have to type in the Evohome device ID in the TaHoma+/HGI80 so it knows with which Evohome it is supposed connect.
https://www.somfy.nl/file.cfm/Honeywell ... tid=318365
I understand that de Evohome V3 has a setting where you tell which HGI80 (connecting) should talk to the Evohome V3.
I am looking for a possibility to connect the HGI80 like the Somfy TaHoma+ does, in a way that the device ID is recognized.
The connection of the HGI80 with Domoticz isn't the problem - HGI80 is being recognized by Domoticz. The problem is that there is no info from the Evohome V2, because there has never been any connection/hand shake.

Thank you for your help.

Kind regards,

Frank

[DanD]

Hi Frank,

Thanks for the additional information it sounds like your set-up is almost complete in Domoticz so hopefully we can get the HGI80 working. There's no DeviceID set-up required in Domoticz for the HGI80 nor on the Evohome controller unlike the Somfy set-up. Once the HGI80 USB drivers have been successfully installed and the HGI80 USB device added within the Hardware set-up in Domoticz, the HGI80 will begin to listen for any Evohome wireless communication and automatically add all the devices to your Domoticz device list. This process can take about 20-30min to complete, but you should start to see the controller and your zones appear within 2-3min. The Domoticz code automatically identifies your controller and doesn't need to be told its DeviceID.

If you've completed all this set-up, but you're not getting any new devices appearing in your Domoticz device list, are there any error messages in the Domoticz log?

You're correct that the Evohome v3 has the ability to connect to Wfi networks, but this isn't required for Domoticz to work. The HGI80 and Domoticz work in a similar way to the Evohome RFG100 gateway device, but add in a lot more functionality.

Dan

[Knarf7]

Hi Dan,

Thank you for your information. I was under the impression that there needed to be connection first before I could work with the software. Thanks to your advice, I have now succeeded. I really appreciate it.

Regards,

Frank

[DanD]

Excellent, thanks for letting me know it's all working OK.

Regards,
Dan

[ChrisWallwork]

Edit: The new Beta version 3.8807 appears to fix this. A bit more detail in my followup post below this.

I hope it's OK to rejuvenate this thread...
I'm struggling to get an HGI80 to find any devices:

I've run Domoticz (stable) on an RPi2 for a couple of years, including Evohome (non-wifi, so with RFG100) via API. But I preferred not to be reliant on a 3rd-party website, so bought an HGI80 and fired up Domoticz beta (currently 8805) on an RPi3 (Raspbian stretch). But I can't get Domoticz to see any devices. I started by copying the domoticz.db from my stable system, but have deleted the RFXTRX hardware and the Evohome API hardware (and thus all its devices) on the beta system. Evohome currently has 9 zones (one with 2 radiators / 2x HR924UK ) plus DHW.

As per the wiki, I installed ti_3410.fw in /lib/firmware and 46-hgi80_usb.rules into /etc/udev/rules.d
dmesg shows the adapter attached to ttyUSB0:

Code: Select all

[   15.010131] usb 1-1.3: new full-speed USB device number 5 using dwc_otg
[   15.185163] usb 1-1.3: New USB device found, idVendor=10ac, idProduct=0102
[   15.185178] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   15.185186] usb 1-1.3: Product: TUSB3410 Boot Device
[   15.185194] usb 1-1.3: Manufacturer: Texas Instruments
[   15.185202] usb 1-1.3: SerialNumber: TUSB3410        
[   16.633972] usbcore: registered new interface driver usbserial
[   16.634158] usbcore: registered new interface driver usbserial_generic
[   16.634247] usbserial: USB Serial support registered for generic
[   16.639613] usbcore: registered new interface driver ti_usb_3410_5052
[   16.639771] usbserial: USB Serial support registered for TI USB 3410 1 port adapter
[   16.643527] usbserial: USB Serial support registered for TI USB 5052 2 port adapter
[   16.643697] ti_usb_3410_5052 1-1.3:1.0: TI USB 3410 1 port adapter converter detected
[   16.643837] usb 1-1.3: Direct firmware load for ti_usb-v10ac-p0102.fw failed with error -2
[   17.430124] usb 1-1.3: reset full-speed USB device number 5 using dwc_otg
[   17.567063] usb 1-1.3: device firmware changed
[   17.567211] ti_usb_3410_5052: probe of 1-1.3:1.0 failed with error -5
[   17.568124] usb 1-1.3: USB disconnect, device number 5
[   17.670318] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
[   17.712422] fuse init (API version 7.26)
[   17.860805] usb 1-1.3: New USB device found, idVendor=10ac, idProduct=0102
[   17.860814] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   17.860819] usb 1-1.3: Product: TUSB3410 Boot Device
[   17.860823] usb 1-1.3: Manufacturer: Texas Instruments
[   17.860827] usb 1-1.3: SerialNumber: TUSB3410        
[   17.864134] ti_usb_3410_5052 1-1.3:1.0: TI USB 3410 1 port adapter converter detected
[   17.864175] ti_usb_3410_5052: probe of 1-1.3:1.0 failed with error -5
[   17.866271] ti_usb_3410_5052 1-1.3:2.0: TI USB 3410 1 port adapter converter detected
[   17.867733] usb 1-1.3: TI USB 3410 1 port adapter converter now attached to ttyUSB0

and the symlink shows OK within /dev :

Code: Select all

crw--w---- 1 root tty       4,   8 Jan 11 21:58 tty8
crw--w---- 1 root tty       4,   9 Jan 11 21:58 tty9
crw-rw---- 1 root dialout 204,  64 Jan 11 21:58 ttyAMA0
crw------- 1 root root      5,   3 Jan 11 21:58 ttyprintk
crw-rw---- 1 root dialout 188,   0 Jan 13 21:46 ttyUSB0
lrwxrwxrwx 1 root root           7 Jan 11 21:59 ttyUSB.Evo0 -> ttyUSB0
crw------- 1 root root     10, 239 Jan 11 21:58 uhid
crw------- 1 root root     10, 223 Jan 11 21:58 uinput
crw-rw-rw- 1 root root      1,   9 Jan 11 21:58 urandom

I've setup the Evohome USB hardware (and tried both ttyUSB0 and ttyUSB.Ev0). Clicking the "All Sensors" returns a brief message, but the devices don't appear, even after 24 hours. One or two devices do show, but with 0 degC temp:

Screen Shot 2018-01-13 at 22.02.43.png (49.02 KiB) Viewed 5038 times

And the Domoticz log reports a set of errors

Code: Select all

2018-01-13 21:26:36.996 evohome: WARNING unrecognised message structure - possible corrupt message '00' (3)
2018-01-13 21:34:46.876 evohome: WARNING unrecognised message structure - possible corrupt message '000503BA' (3)
2018-01-13 21:44:41.791 evohome: WARNING unrecognised message structure - possible corrupt message '05' (3)
2018-01-13 21:49:30.752 evohome: WARNING unrecognised message structure - possible corrupt message '000503BA' (3)
2018-01-13 22:00:00.461 Starting automatic database backup procedure...
2018-01-13 22:00:01.639 Ending automatic database backup procedure...
2018-01-13 22:03:20.640 evohome: WARNING unrecognised message structure - possible corrupt message '00FFFFFFFFFFFF00' (3)

If I do cat/dev/ttyUSB0 I see far more frequent data going past - but don't know enough about the protocol to understand if it is valid. Here's some recent output:

Code: Select all

045 RQ --- 30:066831 01:064918 --:------ 0006 001 00
045 RP --- 01:064918 30:066831 --:------ 0006 004 000503BA
045  I --- 04:216971 --:------ 01:064918 12B0 003 000000
045  I --- 04:216971 --:------ 01:064918 12B0 003 000000
045  I --- 04:216971 --:------ 01:064918 2309 003 0003E8
045 RQ --- 30:066831 01:064918 --:------ 1260 001 00
045 RP --- 01:064918 30:066831 --:------ 1260 003 0013FA
045 RQ --- 30:066831 01:064918 --:------ 0006 001 00
045 RP --- 01:064918 30:066831 --:------ 0006 004 000503BA
045  I --- 04:027026 --:------ 04:027026 30C9 003 000802
045 RQ --- 30:066831 01:064918 --:------ 0006 001 00
045 RP --- 01:064918 30:066831 --:------ 0006 004 000503BA
045  I --- 01:064918 --:------ 01:064918 1F09 003 FF080C
045  I --- 01:064918 --:------ 01:064918 2309 027 0003E80103E80203E80303E80403E80503E80603E80703E80803E8
045  I --- 01:064918 --:------ 01:064918 30C9 027 0007E50106EB0207380306FE04088D0507300605DF0708020806D9
045 RQ --- 30:066831 01:064918 --:------ 0006 001 00
045 RP --- 01:064918 30:066831 --:------ 0006 004 000503BA
045 RQ --- 30:066831 01:064918 --:------ 0006 001 00
045 RP --- 01:064918 30:066831 --:------ 0006 004 000503BA
045  I --- 04:088267 --:------ 04:088267 30C9 003 0006E9
045 RQ --- 30:066831 01:064918 --:------ 0006 001 00
045 RP --- 01:064918 30:066831 --:------ 0006 004 000503BA
095 RQ --- 18:002741 14:139298 --:------ 1260 001 00

Although I have occasional experience with Linux since v0.99, I'm very definitely not a guru, nor am I a coder. So any help, or ideas, in simple language, would be greatly appreciated!

Thanks.

[ChrisWallwork]

Further to my post above, I updated to beta version 3.8807 which appeared today, and this seems to have fixed my problem - I clicked the "All Sensors" button on the Evohome USB hardware, and the devices list gradually populated with my evohome devices.

I'm fairly sure this is a result of the new Beta - I didn't change anything else, and had tried many different things over several days with the previous two Beta versions.

Thanks to Gizmocuz, gordonb3, DanD, FullTalgoRhythm and the several others whose work has got Evohome working with Domoticz!

Chris