Evohome / Evotouch Wireless protocol?

Pop your questions regarding Home automation Domotica hardware here.....
r_255
Advanced Member
Advanced Member
Posts: 621
Joined: Wed Jun 11, 2008 9:39 pm
Location: Netherlands

Re: Evohome / Evotouch Wireless protocol?

Post by r_255 »

Flashing firmware is always your own responsibility. But nobody ever bricked a evotouch so guess that's good News for you.
If you are familiar with the general flashing rules there is not much that could go wrong i guess.

Honeywell just dont want the roms out in the open, and only lets approved dealers flash your evotouch. so that might be an other option for you, but expect a price tag.

I guess the firmware is the official honeywell v23, and fyi i am running it on the old evotouch controller ( b/w )
arnaudth
Starting Member
Starting Member
Posts: 5
Joined: Sat Jul 04, 2015 1:01 pm

Re: Evohome / Evotouch Wireless protocol?

Post by arnaudth »

I've made my choice, I'll flash it.
I've send you a message.
arnaudth
Starting Member
Starting Member
Posts: 5
Joined: Sat Jul 04, 2015 1:01 pm

Re: Evohome / Evotouch Wireless protocol?

Post by arnaudth »

Evohome is now running with v23 firmware, big thanks r_255 ! This is a big step (and money saving).

Now I come back to my first query : Can RFbee be connected on Raspberry Pi TxD and RxD to do the work ?
mschut
Starting Member
Starting Member
Posts: 32
Joined: Thu Mar 01, 2012 10:38 am
Location: the Netrherlands

Re: Evohome / Evotouch Wireless protocol?

Post by mschut »

Interesting thread. Could anyone help me with connecting the HGI80 to my Synology? I have tried some info out of this thread, but I am not able to convert the code from Linux to my Synology to understand (me, as well as the machine).
Synology DS213+ / Domoticz / RFX Transceiver-e
r_255
Advanced Member
Advanced Member
Posts: 621
Joined: Wed Jun 11, 2008 9:39 pm
Location: Netherlands

Re: Evohome / Evotouch Wireless protocol?

Post by r_255 »

@ arnaudth

i would try the usb option, make sure you understand that domoticz expects the rfbee on a usb port. So unless you are able to change the code and make domoticz look for the rx and tx pins and comunicate with your rfbee, i would stick to usb....

@ mschut

do you have communications thru usb ?
mschut
Starting Member
Starting Member
Posts: 32
Joined: Thu Mar 01, 2012 10:38 am
Location: the Netrherlands

Re: Evohome / Evotouch Wireless protocol?

Post by mschut »

r_255 wrote:@ mschut

do you have communications thru usb ?
I don't think I have. I just tried to connect to a raspberry Pi version of Dooticz, here I have more succes. Not yet working, but more results I expect.

To start with the Pi:
I have connected, and followed instructions on the Domoticz Wiki. I do have a connected HGI80 (weirdly on /dev/ttyAMA0).

Then I succesfully walked through these steps:
HGI80
This has the most complete support, once the kernel module is loaded and configured the rest of the setup can be done in Domoticz. This includes additional support for relays including TPI control, a simulated outdoor sensor using the WU Domoticz device, open window mode and battery level updates. Under linux the driver is available but the specific vendor & product code alias is not know to the current kernel module and must be configured manually.

Bus 002 Device 002: ID 10ac:0102 Honeywell, Inc.

It may be best to try and get this working from the shell first

echo 10ac 0102 | sudo tee /sys/bus/usb-serial/drivers/ti_usb_3410_5052_1/new_id
Then check your kernel messages with dmesg

Depending on your distribution you may need to supply a firmware file or enable the appropriate software sources / repository
Which result is that I end with "Depending on your distribution you may need to supply a firmware file or enable the appropriate software sources / repository". I notice with dmesg indeed some mentions of no firmware:

Code: Select all

[  375.432093] usb 1-1.3: Direct firmware load for ti_usb-v10ac-p0102.fw failed with error -2
[  375.432178] usb 1-1.3: Direct firmware load for ti_3410.fw failed with error -2
[  375.432208] usb 1-1.3: ti_download_firmware - firmware not found
[  375.432277] ti_usb_3410_5052: probe of 1-1.3:1.0 failed with error -5
Now I only have to find the correct firmware. No clue where actually...

The Synology.
I cannot see the HGI80, in Domotic its not showing a "free" usb port, so I don't think I have connection. Don't know how to check properly....
Synology DS213+ / Domoticz / RFX Transceiver-e
mschut
Starting Member
Starting Member
Posts: 32
Joined: Thu Mar 01, 2012 10:38 am
Location: the Netrherlands

Re: Evohome / Evotouch Wireless protocol?

Post by mschut »

XanderF wrote:Fixed. After executing 'echo 10ac 0102 > /sys/bus/usb-serial/drivers/ti_usb_3410_5052_1/new_id' directly from the shell I noticed firware was missing when I read dmesg. Downloaded ti_3410.fw and copied it to /lib/firmware/.
Please, XanderF, can you help me where to find the files you used....
Synology DS213+ / Domoticz / RFX Transceiver-e
r_255
Advanced Member
Advanced Member
Posts: 621
Joined: Wed Jun 11, 2008 9:39 pm
Location: Netherlands

Re: Evohome / Evotouch Wireless protocol?

Post by r_255 »

read and try this one, guess its not a real firmware but a driver that makes your debian talk to the ti_usb3410 chip

https://wiki.debian.org/Firmware

Oh and make sure you understand i just swaped my pi for windows... beacuse of usb issues and a no clue how to solve it.
Also tried to make it run on my netgear ultra2, but i failed hard..... but on the other side i have learned a lot.

PS: the synology also needs the same driver file to communicate with your hgi80
bink
Starting Member
Starting Member
Posts: 4
Joined: Wed Jun 24, 2015 10:41 am

Re: Evohome / Evotouch Wireless protocol?

Post by bink »

Thanks to all the help in the forum I now have my Evohome setup working in Domoticz. Great work!

Now I do have a question wether the following setup would also possible:

Currently I have a HGI80 connected to my domoticz and it's controlling my EvoHome. Next to that I also have Honeywell Round connected to my secondary boiler that I can control through an RFG100 from the honeywell app or with the help of the Evohome client script also inside domoticz. What I notice however is that the HGI80 also picks up this thermostat and see it as a second evohome system. If I change the status with the help of the honeywell app the status also changes inside domoticz. Now I'm wondering if it is also possible to control this "evohome" system through the HGI80 directly inside domoticz (so without the scripting --> Honeywell server --> RFG100 --> thermostat). Obviously I tried this but although the HGI80 can see the traffic being sent from the RFG100 towards the thermostat (and from there update the status inside domoticz) it doesn't seem that I can control it directly from domoticz. I did some capture of the HGI80 traffic and the settings from the RFG100 being sent towards the theromostat look to be repeatable. Just wondering if the HGI80 can be used to send this signal directly to the thermostat?

Below an example of the communication:

==========================heating off=======================================
055 RQ --- 34:004587 30:185974 --:------ 2349 001 00
059 RP --- 30:185974 34:004587 --:------ 2349 013 007EFF02FFFFFFFFFFFFFFFFFF
============================================================================
==========================heating back to normal============================
051 RQ --- 34:004587 30:185974 --:------ 2349 001 00
061 RP --- 30:185974 34:004587 --:------ 2349 013 0006A400FFFFFF00100D0707DF
============================================================================

==========================heating off=======================================
045 RQ --- 34:004587 30:185974 --:------ 2349 001 00
057 RP --- 30:185974 34:004587 --:------ 2349 013 007EFF02FFFFFFFFFFFFFFFFFF
============================================================================
==========================heating back to normal============================
055 RQ --- 34:004587 30:185974 --:------ 2349 001 00
058 RP --- 30:185974 34:004587 --:------ 2349 013 0006A400FFFFFF00100D0707DF
============================================================================

I did try to decode this with the PDF document I found in this forum but I can't make chees of it.. (pardon the dutch expression)
arnaudth
Starting Member
Starting Member
Posts: 5
Joined: Sat Jul 04, 2015 1:01 pm

Re: Evohome / Evotouch Wireless protocol?

Post by arnaudth »

r_255 wrote:@ arnaudth

i would try the usb option, make sure you understand that domoticz expects the rfbee on a usb port. So unless you are able to change the code and make domoticz look for the rx and tx pins and comunicate with your rfbee, i would stick to usb....
I was thinking that it was possible to create symlink between serial port of raspberry pi on /dev/ttyUSB0.

But I'm not to wondering about that, I've just ordered hgi80, thanks anyway !
mschut wrote:
XanderF wrote:Fixed. After executing 'echo 10ac 0102 > /sys/bus/usb-serial/drivers/ti_usb_3410_5052_1/new_id' directly from the shell I noticed firware was missing when I read dmesg. Downloaded ti_3410.fw and copied it to /lib/firmware/.
Please, XanderF, can you help me where to find the files you used....
Hi mschut,
I aven't yet my HGI80 but I configured my raspberry pi. I've found info here domoticz.com/forum/viewtopic.php?f=31&a ... ome#p40217

What I've done (this way it should work after each reboot):

Code: Select all

cd /lib/firmware/
sudo wget ftp://ftp.renatasystems.org/pub/XenServer/tmp/lib/firmware/ti_3410.fw
cd /etc/udev/rules.d/
sudo nano 46-hgi80_usb.rules
Write that itoo it (from wiki http://www.domoticz.com/wiki/Evohome)

Code: Select all

# Rules for hotplugging Honeywell HGI80 USB device
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="10ac", ATTR{idProduct}=="0102", NAME="ttyUSB0", RUN+="/sbin/modprobe ti_usb_3410_5052"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="10ac", ATTR{idProduct}=="0102", NAME="ttyUSB0", RUN+="/bin/sh -c 'echo 10ac 0102 > /sys/bus/usb-serial/drivers/ti_usb_3410_5052_1/new_id'"
Add in /etc/udev/rules.d/99-usb-serial.rules to have persistent USB device

Code: Select all

SUBSYSTEM=="tty", subsystems=="usb", ENV{ID_VENDOR}=="10ac", SYMLINK+="ttyUSB13"
Maybe reboot after that. I haven't test this way of connecting HGI80, I haven't receive it, but this method make sense !

If you want to try it, tell me what result you've got or wait I receive my HGI80 (can be long, shop is in replenishment)

Arnaudth
mschut
Starting Member
Starting Member
Posts: 32
Joined: Thu Mar 01, 2012 10:38 am
Location: the Netrherlands

Re: Evohome / Evotouch Wireless protocol?

Post by mschut »

arnaudth wrote:Arnaudth
Thanks a lot! I keep your post in mind. However, I did some digging myself already...

Yesterday I decided to try the Pi first. I consulted Google a bit and downloaded a fw file, and put it on the Pi. After some rebooting, it worked. I wanted to use the Pi as a second Domoticz server, and share the Evohome devices. However, the devices didn't come through all that well. The master Domoticz didn't recognise them as Evohome devices.

So, I decided to switch back completely to the Pi, whcich is wiorking now including the Evohome devices.

I have now 1 general Evohome device, and seperate ones for my thermostats.Controling the main Evohome device works like a charm. Whenever I change the status to "away", "Eco" or whatever, it changes directly on the Evohome controller. And vise versa. Brilliant.However, changing the settings of the sepoerate thermostats don't sync to the Evohome conbtroller, and change back after a sync with the evohome conbtroller.

So, mainly happy, but still nog woirking completely as I hoped. Is this normal behaviour, or should the controlling of the seperate thermostats work as smooth as the main controller?
Synology DS213+ / Domoticz / RFX Transceiver-e
Uranday
Starting Member
Starting Member
Posts: 1
Joined: Sun Aug 23, 2015 8:28 pm

Re: Evohome / Evotouch Wireless protocol?

Post by Uranday »

Hi

After some tinkering I got the honeywell working with the evohome. Though for some reason I cannot see it in the event editor. I assume I would see there some devices?

Regards,
Patrick
squix78
Starting Member
Starting Member
Posts: 1
Joined: Thu Sep 17, 2015 11:50 am

Re: Evohome / Evotouch Wireless protocol?

Post by squix78 »

Hi board

I would like to use fullTalgoRhythm's RFBee V1.2 firmware to monitor my HCW82 room thermostats and eventually manipulate the floor control unit with it. To my big surprise I am receiving data almost out of the box, except that it contains a lot of incomplete messages:

Code: Select all

--- Unknown header=0xFF
---  I --- 01:028730 --:------ 01:028730 2309 018 00092E01083802088A0406C60608D0070750
---  I --- 01:028730 --:------ 01:028730 30C9 018 00092E0108FC0209060408F20608DE0708CA
---  I --- 03:203088 --:------ 03:203088 1A30 201 030108E8EF*INCOMPLETE*
--- Unknown header=0xF7
---  I --- 03:203088 --:------ 03:203088 1A30 201 030108E8EF*INCOMPLETE*
--- Unknown header=0xF7
---  I --- 03:201612 --:------ 03:201612 0123 137 0302FB508D*INCOMPLETE*
--- Unknown header=0xFF
---  I --- 02:017708 --:------ 02:017708 0008 002 *INCOMPLETE*
---  I --- 01:028858 --:------ 01:028730 1F09 003 FF05BE*CHK*
--- Unknown header=0xFF
---  I --- 01:028730 --:------ 01:028730 2309 018 00092E0106DA02072C0405CC0607D6070656
---  I --- 01:028730 --:------ 01:028730 30C9 018 0009*INCOMPLETE*
---  I --- 01:028730 --:------ 01:028730 3B00 002 FCC8
---  I --- *INCOMPLETE*
Any idea what I might have to tweak or tune to get better data quality?
hvxl
Senior Member
Senior Member
Posts: 1965
Joined: Sat Jun 05, 2010 11:59 am
Contact:

Re: Evohome / Evotouch Wireless protocol?

Post by hvxl »

You somehow managed to put ^Q characters in your message, which causes invalid XML in the RSS feed. I'm just posting this to bump your post out of the XML feed.
Schelte
r_255
Advanced Member
Advanced Member
Posts: 621
Joined: Wed Jun 11, 2008 9:39 pm
Location: Netherlands

Re: Evohome / Evotouch Wireless protocol?

Post by r_255 »

Does your system gives any problems, or is it just the log saying these things ?

Not sure, but if i am right decoding is done at the end, and the decoder looks if the packages are fitting the protocol specifications.
If not they are rejected. So i guess what you see are receptions that get rejected due to protocol specifications.

It also can be undocumented commands, but most stuf for controlling the system are covered.

I dont know how exact how the decoder works, but the protocol and encoding is very strict.
Dont forget that we have multple devices talking on the same band, and they could interfere due overlapping transmissions.
Post Reply

Return to “Questions & Discussions Forum”