Home Automation Domotica Forum Europe, Bwired Forum

Hi All,

Another user joining wanting to get to the bottom of the evohome communication/protocol.
I'm not so much after controling the system but want to run a datalogger to graph what it going on.
Have recently installed evotouch with 1*HR80, 1*R8810, 1*HCE80, 2*DT92 and HB85 to follow.
Have also received my busware V3 CUL/C1101...

Can anyone share any thoughts on how to setup th CUL for sniffing? (frequency, channel width etc.),
currently running with culfw 1.44 firmware but no joy yet.
Any example code is much appreciated!

Thanks,

Roger

And here is another user with an existing Honeywell Evotouch system that would really like to somehow connect this into a domotica system, like HomeSeer.
I have 6 * HR80 for the various rooms with radiators
1 * HCE80 for the floor heating with 1 * DTS92 and 1 * HCW82 for measuring temperature and set points, using 3 * MT4-230NC on the floor heating valves.
1 * BDR91 for wireless connection to the central heating unit.
Would be really cool if at least I was able to read the temperature sensors in the HR80's...

Try to get in contact with Crazydiamond, he was busy with this, see above topics
I moved away from the Evo, until now still a bridge to far for us.
I now use the Max in the Bwired house.

Well as cd seems to be vanished i guess its only fair to share his findings.

if some one feels i am doing wrong with publishing his work let me know.. ill delete it.

Hopefully Cd can add his latest work to this topic also, so it can be picked up again.

thanks r_255, interesting document.

Maybe we can find some information here as well: http://hometronic.ge51.honeywell.de/sup ... /index.htm (username test, password test)
I did find hcm200 firmware files but decompiling will be difficult.

We have floor heating in the living room and when its on temperature, the rest of the house is cooling down to (almost ) freezing point....
now I was recently looking for a solution to heat the study room of my girlfriend, and also came to EvoHome.

Now i'm orientating on domotica and came to this forum and saw this promising topic. I don't have knowledge on this to share, but i hope that you crack the protocol.

If testers are needed; Contact me via the Forum.

I own a HCM 200, so if it it spossible to decompile the firmware that would be interesting.

Furthermore I assume that the EvoTouch protocol will not be exactly the same.

crazydiamond wrote: If you need the exact parameters of CC1101, I will let you know how evotouch initializes it.

Would be interested how the configuration parameters of the CC1101 have to be initialized.
Any more details about the protocol?

CC1101 settings can be found in the attachment only 5 posts above from yours...

Could the HRA80 (external antenna) perhaps be a useful device to monitor Evohome RF traffic? The HRA80 is connected using a 2 wire bus (B+ and ground it seems). A single device can be used to up to 3 HCE80 devices. Binding is done from the HCE80 so the HRA80. Perhaps this is just a generic bridge for bi-directional communication?

Hi, I recently purchased a second hand evotouch and it needs a new screen, has anyone got any idea who makes the screen so I can purchase a new one? Also does anyone know of any firmware updates out there?

Thanks

Some interesting info about DIY EvoTouch software update on: http://forum.fok.nl/topic/1546028/9/25

I had some success monitoring the communications between HR80UK/CM67z/HC60NG
Taking the previously mentioned pdf file as a starting point:
Receiver seeedstudio.com/depot/rfbee-v11-wireles ... p-614.html with customised firmware, register settings for CC1101 in pdf document are OK.

Section 2.2/2.3 I found message preamble and end of block as described
Section 2.4 Right hand column of manchester decoding look up table is wrong. Any code starting with 0x8.. is manchester-breaking. I have a revised table.
Section 3.1 Checksum passes using my revised decoding table
Section 3.3 Not sure yet, more explanation of the encoding of the header byte and purpose of Param1 and Param2 would be useful
Using the rest of the document and decoding a couple of messages by hand I found commands 0x30C9 and 0x0008.

So very early stuff, just really confirming that with some corrections the pdf looks OK. Not sure how much further I can go than what is already documented, and I don't intend to try more than finding if the room temperatures from the HR80s can be monitored, and reading the demand values sent to the HC60NG.

I am also successfully monitoring the RF traffic using the HoneyComm project on github and and RFBee+UartSBee. Very nice.

The HoneyComm software syncs the CC110 on FF 00 (also show in paragraph 2.2 of the protocol pdf). However I see this a lot:
FF 00 33 55 53 A9 A2 D4 D3 B4 CB AD D4 D5 CD CC D2 B4 B2 D4 D5 ... and directly thereafter:
AA AA AA AA AA AA AA AA AA FF 80 99 AA A9 D4 B5 D4 D3 B4 00 or 01...

Looks like a message starting with FF 80 is some kind of acknowledgement.