Evohome / Evotouch Wireless protocol?

Pop your questions regarding Home automation Domotica hardware here.....

Re: Evohome / Evotouch Wireless protocol?

Postby bruce_miranda » Sun Feb 26, 2017 10:47 pm

Fred, Thanks for posting that code. I've posted a comparison between the actual HGI80 and the RfBee running your code with no modifications at all. There are a few interesting differences. The messages are for the exact same period of measurement.

1. The RFBee still has a few incomplete messages.
2. The RFBee appears to miss a few messages completely.
3. The order of the messages also appears to be different. And when it does it appears to give rise to either an Incomplete situation or Checksum error.
4. However of biggest note is how the RFBee changes the message structure. The Device IDs appear in different places to the HGI80.

But for the first time I appear to have received at least one full message that had only a single device ID in the message, even though the device id is in the wrong column. Several others were either skipped or marked Incomplete.

HGI80 output
Code: Select all
061  I --- 04:098449 --:------ 04:098449 30C9 003 00081C                       
095  I --- 13:031200 --:------ 13:031200 3EF0 003 00C8FF                       
051  I --- 04:098464 --:------ 01:078710 3150 002 0800                         
076  I --- 13:031208 --:------ 13:031208 3EF0 003 00C8FF                       
086 RQ --- 22:068149 13:031200 --:------ 3EF1 002 0000                         
095 RP --- 13:031200 22:068149 --:------ 3EF1 007 0000370037C8FF               
076 RP --- 13:031208 22:068154 --:------ 3EF1 007 0000370037C8FF               
045  I --- 04:057586 --:------ 01:078710 1060 003 01FF01                       
045  I --- 04:057586 --:------ 04:057586 1060 003 00FF01                       
090  I --- 04:057587 --:------ 01:078710 2309 003 050320                       
086  I --- --:------ --:------ 10:067219 1FD4 003 000473                       
092 RP --- 13:050361 22:055075 --:------ 3EF1 007 0000370037C8FF               
045  I --- 04:061402 --:------ 04:061402 30C9 003 000789                       
072  I --- 04:133277 --:------ 01:078710 1060 003 00FF01                       
072  I --- 04:133277 --:------ 04:133277 1060 003 00FF01                       
045  I --- 04:057586 --:------ 04:057586 30C9 003 0006BD                       
045  I --- 01:078710 --:------ 01:078710 1F09 003 FF04B5                       
045  I --- 01:078710 --:------ 01:078710 2309 036 000320010320020320030320040320
0503200603200701F40803200903200A03200B0320                                     
045  I --- 01:078710 --:------ 01:078710 30C9 036 0007AE0106BD0208EC03067A040789
0508240607D80708E40808290908290A07440B081C                                     
080  I --- 04:098474 --:------ 01:078710 3150 002 0A00                         
050  I --- 04:098464 --:------ 01:078710 3150 002 0800                         
045  I --- 04:057586 --:------ 01:078710 3150 002 0100                         
045  I --- 04:061402 --:------ 01:078710 2309 003 040320                       
045  I --- 04:061402 --:------ 01:078710 1060 003 04FF01                       
045  I --- 04:061402 --:------ 04:061402 1060 003 00FF01                       
084  I --- --:------ --:------ 10:067219 1FD4 003 000474                       
047  I --- 04:098455 --:------ 01:078710 3150 002 0B00                         
045  I --- 04:057586 --:------ 01:078710 2309 003 010320                       
045  I --- 01:078710 --:------ 01:078710 3150 002 FC00                         
045  I --- 01:078710 --:------ 01:078710 0008 002 F900                         
053  I --- 04:098306 --:------ 01:078710 2309 003 090320                       
081  I --- 13:031208 --:------ 13:031208 3EF0 003 00C8FF                       
095  I --- 13:050361 --:------ 13:050361 3EF0 003 00C8FF                       
088 RQ --- 22:068149 13:031200 --:------ 3EF1 002 0000                         
052  I --- 04:098306 --:------ 04:098306 30C9 003 000829                       
069 RQ --- 22:068154 13:031208 --:------ 3EF1 002 0000                         
080 RP --- 13:031208 22:068154 --:------ 3EF1 007 0000370037C8FF               
081  I --- 04:098474 --:------ 01:078710 2309 003 0A0320                       
045  I --- 04:061731 --:------ 01:078710 2309 003 030320                       
089 RQ --- 22:055075 13:050361 --:------ 3EF1 002 0000                         
095 RP --- 13:050361 22:055075 --:------ 3EF1 007 0000370037C8FF               
072  I --- --:------ --:------ 10:067219 1FD4 003 000475                       
070  I --- 34:103839 --:------ 34:103839 30C9 003 0007D4                       
095  I --- --:------ --:------ 12:106131 313F 009 00380114D51A0207E1           
053  I --- 04:098464 --:------ 01:078710 1060 003 08FF01                       
052  I --- 04:098464 --:------ 04:098464 1060 003 00FF01                       
059  I --- 04:098449 --:------ 01:078710 3150 002 0B00                         


RFBee VERSION_NO "0.9alpha"
Code: Select all
---  I --- 04:098449 --:------ 04:098449 30C9 003 00081C                       
---  I --- 04:098464 --:------ 01:078710 3150 002 0800                         
---  I --- 13:050361 --:------ 13:050361 3EF0 003 00C8FF                       
--- RP --- 13:031200 --:------ 22:068149 3EF1 007 0000370037C8FF               
--- RQ --- 22:068154 --:------ 13:031208 3EF1 002 0000                         
--- RP --- 13:031208 --:------ 22:068154 3EF1 *INCOMPLETE*                     
---  I --- 04:057586 --:------ 01:078710 1060 003 01FF01                       
---  I --- 04:057586 --:------ 04:057586 1060 003 00FF01                       
---  I --- 10:067219 --:------ --:------ 1FD4 003 000473                       
--- RQ --- 22:055075 --:------ 13:050361 3EF1 002 0000                         
--- RP --- 13:050361 --:------ 22:055075 3EF1 007 0000370037*INCOMPLETE*       
---  I --- 04:061402 --:------ 04:061402 30C9 003 000789                       
---  I --- 04:133277 --:------ 01:078710 1060 003 00FF01*CHK*                   
---  I --- 04:057586 --:------ 04:057586 30C9 003 0006BD                       
---  I --- 01:078710 --:------ 01:078710 1F09 003 FF04B5                       
---  I --- 01:078710 --:------ 01:078710 2309 036 000320010320020320030320040320
0503200603200701F40803200903200A03200B0320                                     
---  I --- 01:078710 --:------ 01:078710 30C9 036 0007AE0106BD0208EC03067A040789
0508240607D80708E40808290908290A07440B081C                                     
---  I --- 04:098474 --:------ 01:078710 3150 002 0A00                         
---  I --- 04:057586 --:------ 01:078710 3150 002 0100                         
---  I --- 04:133277 *INCOMPLETE*                                               
---  I --- 04:061402 --:------ 01:078710 2309 003 040320                       
---  I --- 10:067219 --:------ --:------ 1FD4 003 00*INCOMPLETE*               
---  I --- 04:098455 --:------ 01:078710 3150 002 0B00                         
---  I --- 04:057586 --:------ 01:078710 2309 003 010320                       
---  I --- 01:078710 --:------ 01:078710 3150 002 FC00                         
---  I --- 01:078710 --:------ 01:078710 0008 002 F900                         
---  I --- 13:031200 --:------ 13:031200 3EF0 003 00C8FF                       
---  I --- 13:050361 --:------ 13:050361 3EF0 003 00C8FF                       
---  I --- 04:098306 --:------ 01:078710 3150 002 0900                         
--- RP --- 13:031200 --:------ 22:068149 3EF1 007 00*INCOMPLETE*               
---  I --- 04:098306 --:------ 04:098306 30C9 003 000829                       
--- RQ --- 22:068154 --:------ 13:031208 3EF1 002 0000                         
--- RP --- 13:031208 --:------ 22:068154 *INCOMPLETE*                           
---  I --- 04:061731 --:------ 01:078710 2309 003 030320                       
--- RP --- 13:050361 --:------ 22:055075 3EF1 007 0000370037C8FF               
---  I --- 34:103839 --:------ 34:103839 30C9 003 0007D4                       
---  I --- 04:098464 --:------ 01:078710 1060 003 08FF01                       
---  I --- 04:098464 --:------ 04:098464 1060 003 00FF01                       
---  I --- 04:098449 --:------ 01:078710 3150 002 0B00                         


Any thoughts?
bruce_miranda
Starting Member
Starting Member
 
Posts: 21
Joined: April 2014

Re: Evohome / Evotouch Wireless protocol?

Postby bruce_miranda » Sun Feb 26, 2017 10:54 pm

There is something definitely not quite right whenever the messages of format --- --:------ --:------ xx:xxxxxx are received. It's like the RFBee doesn't know how to handle those messages.

HGI80
Code: Select all
047  I --- 04:061402 --:------ 04:061402 30C9 003 000782                       
045  I --- 04:061731 --:------ 01:078710 3150 002 0300                         
047  I --- 04:098455 --:------ 01:078710 1060 003 0BFF01                       
046  I --- 04:098455 --:------ 04:098455 1060 003 00FF01                       
045  I --- 04:057586 --:------ 01:078710 3150 002 0100                         
052  I --- 04:098306 --:------ 01:078710 2309 003 090320                       
051  I --- 04:098464 --:------ 04:098464 30C9 003 000809                       
085  I --- 13:031208 --:------ 13:031208 3EF0 003 00C8FF                       
057  I --- 34:147397 --:------ 34:147397 30C9 003 000818                       
094  I --- --:------ --:------ 12:027384 0008 002 006C                         
092  I --- --:------ --:------ 12:027384 0008 002 006C                         
092  I --- --:------ --:------ 12:027384 0008 002 006C                         
089  I --- 13:050361 --:------ 13:050361 3EF0 003 00C8FF                       
088 RQ --- 22:068149 13:031200 --:------ 3EF1 002 0000                         
069 RQ --- 22:068154 13:031208 --:------ 3EF1 002 0000                         
084 RP --- 13:031208 22:068154 --:------ 3EF1 007 0000370037C8FF               
045  I --- 04:061731 --:------ 01:078710 3150 002 0300                         
090 RQ --- 22:055075 13:050361 --:------ 3EF1 002 0000                         
092 RP --- 13:050361 22:055075 --:------ 3EF1 007 0000380038C8FF               
050  I --- 34:103601 --:------ 34:103601 30C9 003 0008EE                       
066  I --- --:------ --:------ 10:067219 1FD4 003 000493                       
088  I --- 04:057587 --:------ 01:078710 3150 002 0500                         
045  I --- 04:057586 --:------ 01:078710 2309 003 010320                       
073  I --- 04:098449 --:------ 01:078710 2309 003 0B0320                       
095  I --- --:------ --:------ 12:007412 0008 002 00C6                         
084  I --- 04:098474 --:------ 01:078710 3150 002 0A00                         
051  I --- 04:098464 --:------ 01:078710 1060 003 08FF01                       
050  I --- 04:098464 --:------ 04:098464 1060 003 00FF01                       
045  I --- 01:078710 --:------ 01:078710 1F09 003 FF04B5                       
045  I --- 01:078710 --:------ 01:078710 2309 036 000320010320020320030320040320
0503200603200701F40803200903200A03200B0320                                     
045  I --- 01:078710 --:------ 01:078710 30C9 036 00078F0106D50208EE030674040782
0508180607CE0708CF08080909081C0A07440B0802                                     
070 RQ --- 22:054901 13:133379 --:------ 3EF1 002 0000                         
045  I --- 04:057586 --:------ 01:078710 1060 003 01FF01                       
045  I --- 04:057586 --:------ 04:057586 1060 003 00FF01                       
045  I --- 04:061731 --:------ 01:078710 1060 003 03FF01                       
045  I --- 04:061731 --:------ 04:061731 1060 003 00FF01                       
076  I --- 04:098449 --:------ 04:098449 30C9 003 000802                       
047  I --- 04:061402 --:------ 01:078710 1060 003 04FF01                       
046  I --- 04:061402 --:------ 04:061402 1060 003 00FF01                       
046  I --- 04:061402 --:------ 01:078710 2309 003 040320                       
061  I --- --:------ --:------ 10:067219 1FD4 003 000494                       
045  I --- 04:057586 --:------ 01:078710 3150 002 0100                         
050  I --- 04:098306 --:------ 01:078710 2309 003 090320                       
091  I --- 04:057587 --:------ 01:078710 3150 002 0500                         
075  I --- 04:133277 --:------ 04:133277 30C9 003 00077C                       
093  I --- 22:006688 --:------ 22:006688 0008 002 006C                         
082  I --- 13:031208 --:------ 13:031208 3EF0 003 00C8FF                       
094  I --- 22:006688 --:------ 22:006688 0008 002 006C                         
094  I --- --:------ --:------ 12:027384 0008 002 005E                         
051  I --- 04:098306 --:------ 01:078710 3150 002 0900                         


RFBee (no OSCCAL override and baud 74880)
Code: Select all
---  I --- 04:061402 --:------ 04:061402 30C9 003 000782                       
---  I --- 04:061731 --:------ 01:078710 3150 002 0300                         
---  I --- 04:098455 --:------ 01:078710 1060 003 0BFF01                       
---  I --- 04:098455 --:------ 04:098455 1060 003 00FF01                       
---  I --- 04:057586 --:------ 01:078710 3150 002 0100                         
---  I --- 04:098306 --:------ 01:078710 2309 003 090320                       
---  I --- 04:098464 --:------ 04:098464 30C9 003 000809                       
---  I --- *INCOMPLETE*                                                         
---  I --- 13:031208 --:------ 13:031208 3EF0 003 00C8FF                       
---  I --- 34:147397 --:------ 34:147397 30C9 003 000818                       
---  I --- 13:050361 --:------ 13:050361 3EF0 003 00C8FF                       
--- RP --- 13:031200 --:------ 22:068149 3EF1 007 0000370037C8FF               
--- RQ --- 22:068154 --:------ 13:031208 3EF1 002 0000                         
--- RP --- 13:031208 --:------ 22:068154 3FF1 007 0000370037C8FF*CHK*           
---  I --- 04:061731 --:------ 01:078710 3150 002 0300                         
--- RQ --- 22:055075 --:------ 13:050361 3EF1 002 0000                         
--- RP --- 13:050361 --:------ 22:055075 3EF1 007 0000380038C8FF               
---  I --- 34:103601 --:------ 34:103601 30C9 003 0008EE                       
---  I --- 04:057586 --:------ 01:078710 2309 003 010320                       
---  I --- 04:098449 --:------ 01:078710 2309 003 0B0320                       
---  I --- 04:098464 --:------ 01:078710 1060 003 08FF01                       
---  I --- 04:098464 --:------ 04:098464 1060 003 00FF01                       
---  I --- 01:078710 --:------ 01:078710 1F09 003 FF04B5                       
---  I --- 01:078710 --:------ 01:078710 2309 036 000320010320020320030320040320
0503200603200701F40803200903200A03200B0320                                     
---  I --- 01:078710 --:------ 01:078710 30C9 036 00078F0106D50208EE030674040782
0508180607CE0708CF08080909081C0A07440B0802                                     
--- RQ --- 22:054901 --:------ 13:133379 3EF1 002 0000                         
---  I --- 04:057586 --:------ 01:078710 1060 003 01FF01                       
---  I --- 04:061731 --:------ 01:078710 1060 003 03FF01                       
---  I --- 04:061731 --:------ 04:061731 1060 003 00FF01                       
---  I --- 04:098449 --:------ 04:098449 30C9 003 000802                       
---  I --- 04:061402 --:------ 01:078710 1060 003 04FF01                       
---  I --- 04:061402 --:------ 04:061402 1060 003 00FF01                       
---  I --- 04:133277 *INCOMPLETE*                                               
---  I --- 04:057586 --:------ 01:078710 3150 002 0100                         
---  I --- 04:098306 --:------ 01:078710 2309 003 090320                       
---  I --- 04:133277 --:------ 04:133277 30C9 003 00077C                       
---  I --- *INCOMPLETE*                                                         
---  I --- 13:031208 --:------ 13:031208 3EF0 003 00C8FF                       
---  I --- 04:098306 --:------ 01:078710 3150 002 0900                         
bruce_miranda
Starting Member
Starting Member
 
Posts: 21
Joined: April 2014

Re: Evohome / Evotouch Wireless protocol?

Postby bruce_miranda » Sat Mar 04, 2017 5:36 pm

Fred, any clue what might be causing my issues?
bruce_miranda
Starting Member
Starting Member
 
Posts: 21
Joined: April 2014

Re: Evohome / Evotouch Wireless protocol?

Postby DanD » Sun Mar 05, 2017 8:03 pm

Bruce, Fred,

Just to let you know that I've now published my tweaks to the original FullTalgoRhythm to a new branch in my GitHub area in a similar way to you Fred:

https://github.com/Evsdd/EvohomeWirelessFW.git

I've added support for the messages with only 1 deviceID '--:------ --:------ xx:xxxxxx' and fixed a small, but frustrating bug which was causing a memory leak and prevented any messages from sending when compiling with Arduino on a Windows 32bit machine with the atmega328 as target. I've not yet taken a look at the details of your optimisations Fred, and I'll see if I can add these in too, but retain compatibility with Arduino.

I'll also take another look at what might be causing your problems, Bruce. My best guess is still that it's a similar memory problem and that making all the type casting more specific (uint8_t etc) will fix it.


Dan
DanD
Starting Member
Starting Member
 
Posts: 19
Joined: June 2016

Re: Evohome / Evotouch Wireless protocol?

Postby bruce_miranda » Thu Mar 09, 2017 10:15 pm

fredh wrote:Bruce,

I've changed the firmware in the following areas:

  • Correctly handle messages with only one parameter;
  • After the preamble bit sequence, I sync on 32 bits instead of 16 bits. This causes less 'false starts';
  • The 1101 has the capability to 'catch' the actual frequency of the transmission and reports the discovered 'offset'. I'm using the reported offset to adjust the frequency after every message received, using a low pass filter to suppress spikes. Sofar the final frequency will converge to a stable value. The benefit is that the recovered clock signal is of a better quality and thus the sampled value presented to the interrupt service routine is 'better'. This causes less errors in breaking the manchester code and checksum;
  • A very, very, very small optimisation to the receiving interrupt service routine shaving a few instructions from the resulting compiled code.

Fred


I still seem to be unable to receive messages with only one parameter. Those messages seem to be chopped off prematurely by the Sync word discovery. How did you arrive at the 32bit sync word to be used?
bruce_miranda
Starting Member
Starting Member
 
Posts: 21
Joined: April 2014

Re: Evohome / Evotouch Wireless protocol?

Postby DanD » Fri Mar 10, 2017 10:50 am

@colintd

Great work on the new CUL firmware, adding the Ramses/Evohome functionality!

You may have seen some of the posts about the work that a few of us are doing at the moment on the FullTalgoRythm RFBee firmware to improve its performance and expand the message structures it can decode. I've only just found the time to look at your firmware in some detail and I've noticed that you're using different settings for the CC1101 registers compared to the FullTalgoRythm firmware. Did you revert back to the settings that Hydrogenetic first posted which were obtained by reading the CC1101 registers on a RFG100 or did you dig into the CC1101 and optimise the settings? The reason that I ask is that Bruce and I are having some trouble successfully receiving messages, specifically from HR80s, and I'm beginning to wonder whether the CC1101 settings are the cause.

I don't have any of the CUL hardware (just RFBees), but if you think there's anything I can usefully do to help at all with the next steps with your integration of Evohome support into CULFW, please let me know.

Thanks,

Dan
DanD
Starting Member
Starting Member
 
Posts: 19
Joined: June 2016

Re: Evohome / Evotouch Wireless protocol?

Postby Happyboy » Fri Mar 10, 2017 12:36 pm

Hi,

Thanks for the great work !

I have next setup :

Living room floor heating, Pump, of the floorheating, is switch on/off with BDR91 (set up as valvue controller), temp measurment is the ATC928G2000.
Hallway and other rooms have a HR80 ( 4 x times), in one room a honenywell round is used as temp sensor, instead of the HR80 it self.
Self build RFbee (ft232 + Arduino Pro mini + CC1101), running still at 115k2.

I have to say, with the 0.92a firmwire, a lot less error's but have the impression also a lot " less " recieved.
If i run 0.8, I recieve quickly a lot, with 0.92 it takes some time. But, lets say after 30 minutes, it runs well.

After 12 hours running have next errors in domoticz :

2017-03-09 23:54:25.085 Error: evohome: too many message ids - possible corrupt message
2017-03-09 23:54:25.085 Error: evohome: too many message ids - possible corrupt message

2017-03-10 02:55:47.027 Error: evohome: no payload size - possible corrupt message
2017-03-10 02:55:47.029 Error: evohome: no payload size - possible corrupt message
2017-03-10 04:22:30.108 Error: evohome: no payload size - possible corrupt message
2017-03-10 04:53:18.316 Error: evohome: no payload size - possible corrupt message
2017-03-10 10:21:00.818 Error: evohome: no payload size - possible corrupt message
2017-03-10 10:55:30.819 Error: evohome: too many message ids - possible corrupt message
2017-03-10 10:55:30.819 Error: evohome: too many message ids - possible corrupt message

Looks to me (but quick first impression) if there is a general command, eg, switch from Normal mode to eco mode, the there is to many to process.

Let me know if I can help with an other way of logging, testing, I will dive in the software later to understand how it works, but my background is more Hardware design.
If any suggestion how to improve further my setup... very welcome offcourse :)
Happyboy
Starting Member
Starting Member
 
Posts: 9
Joined: September 2012

Re: Evohome / Evotouch Wireless protocol?

Postby bruce_miranda » Fri Mar 10, 2017 4:03 pm

Where has V0.92a come from?
bruce_miranda
Starting Member
Starting Member
 
Posts: 21
Joined: April 2014

Re: Evohome / Evotouch Wireless protocol?

Postby Happyboy » Sat Mar 11, 2017 10:52 am

Sorry.. typo... 0.9alpha, the one from fredh, which you also use.

I understand that orginal version now also is updated (DanD), but Dan you forgot to udpdate the version number ? it still say 0.8 (?)

Transmitting, in my case also doesn't work with 0.9 alpha, does anyone have that working ?
Happyboy
Starting Member
Starting Member
 
Posts: 9
Joined: September 2012

Re: Evohome / Evotouch Wireless protocol?

Postby Happyboy » Sat Mar 11, 2017 12:28 pm

Sorry typo, 0.9alpha, same you also use.
I only compiled it with Arduino, reading the post, not sure if this impliment all changes..?

Also understand that Daan updated the orignale one, (can also see it on the date) but, version number is still 0.8 ?

Until know running ok :

Total error log in Domoticz is now :

2017-03-09 23:54:25.085 Error: evohome: too many message ids - possible corrupt message
2017-03-09 23:54:25.085 Error: evohome: too many message ids - possible corrupt message
2017-03-10 00:11:24.971 Error: WUnderground: Invalid data received!
2017-03-10 02:55:47.027 Error: evohome: no payload size - possible corrupt message
2017-03-10 02:55:47.029 Error: evohome: no payload size - possible corrupt message
2017-03-10 04:22:30.108 Error: evohome: no payload size - possible corrupt message
2017-03-10 04:53:18.316 Error: evohome: no payload size - possible corrupt message
2017-03-10 10:21:00.818 Error: evohome: no payload size - possible corrupt message
2017-03-10 10:55:30.819 Error: evohome: too many message ids - possible corrupt message
2017-03-10 10:55:30.819 Error: evohome: too many message ids - possible corrupt message
2017-03-10 13:02:48.402 Error: evohome: no payload size - possible corrupt message
2017-03-10 19:38:02.394 Error: evohome: no payload size - possible corrupt message
2017-03-10 21:00:43.167 Error: evohome: no payload size - possible corrupt message
2017-03-10 21:07:20.349 Error: evohome: no payload size - possible corrupt message
2017-03-10 22:12:01.114 Error: evohome: no payload size - possible corrupt message
2017-03-10 23:58:15.469 Error: evohome: no payload size - possible corrupt message
2017-03-10 23:58:15.471 Error: evohome: no payload size - possible corrupt message
2017-03-11 00:33:58.247 Error: evohome: too many message ids - possible corrupt message
2017-03-11 00:33:58.247 Error: evohome: no payload size - possible corrupt message
2017-03-11 01:47:10.859 Error: evohome: no payload size - possible corrupt message
2017-03-11 05:48:26.546 Error: evohome: too many message ids - possible corrupt message
2017-03-11 05:48:26.546 Error: evohome: too many message ids - possible corrupt message
2017-03-11 05:48:26.546 Error: evohome: no payload size - possible corrupt message
2017-03-11 07:14:39.546 Error: evohome: no payload size - possible corrupt message
2017-03-11 07:27:00.842 Error: evohome: no payload size - possible corrupt message
2017-03-11 07:36:02.143 Error: evohome: too many message ids - possible corrupt message
2017-03-11 07:36:02.143 Error: evohome: too many message ids - possible corrupt message
2017-03-11 07:36:02.143 Error: evohome: too many message ids - possible corrupt message
Happyboy
Starting Member
Starting Member
 
Posts: 9
Joined: September 2012

Re: Evohome / Evotouch Wireless protocol?

Postby bruce_miranda » Sat Mar 11, 2017 2:28 pm

Are you using HR80 or HR92?

I've not seen any RFBee firmware working well with the HR80 and Evohome. And that's what we need to fix. Also V0.9alpha changes the message structure as well which needs fixing. It does however work very well and fixes a lot of issues found in the 0.8 version.

Also the RFBee itself has moved to V1.2 which has an external 8MHZ oscillator, this means that the clock speed cannot be adjusted in the firmware.
bruce_miranda
Starting Member
Starting Member
 
Posts: 21
Joined: April 2014

Re: Evohome / Evotouch Wireless protocol?

Postby Happyboy » Sun Mar 12, 2017 11:49 am

The Osscal part I also figerd out .. I had a small programm to minimize the error, but by changing the osscal value nothing happend.
Then indeed reading the datasheet, osscal is only for the internal oscilator.

Could you see, with lowering the baudrate, the error's decrease ?

By picking 74880, the programm had still enough " air" ?

I could modify my version to a fosc = 11.0592 MHz or lower to fosc = 7.3728 MHz (different X-tal) but didn't check yet if this have any impact on other parts of the code (timers... ?).
11.0592, is still in side the spec of the Atmel, for sure cause no issue, the Jeenode's even still run at 16 mhz at 3.3V (which is outside spec).
Happyboy
Starting Member
Starting Member
 
Posts: 9
Joined: September 2012

Re: Evohome / Evotouch Wireless protocol?

Postby Happyboy » Sun Mar 12, 2017 11:58 am

Oh and my setup is :

HR80 V2.04 x 4 (soon 5 or 6)
HRB91 relay on the floorheating pump

first color screen + internet gateway

Raspbery pi2+ with own made RFbee (arduino mini Pro + CC1101 + FT chip).
Happyboy
Starting Member
Starting Member
 
Posts: 9
Joined: September 2012

Re: Evohome / Evotouch Wireless protocol?

Postby DanD » Sun Mar 12, 2017 9:10 pm

@Happyboy

Apologies for any confusion caused by my keeping the numbering of the firmware as 0.8 in my master branch. I decided to not update the version info yet as my first change was simply to fix a compiler problem which prevented my RFBee from sending and was a very minor change to the code. I've also added a fix for messages with single device IDs in the master branch. My other 2 branches are for testing versions of the code. It does look like you're hitting problems with message corruption on the serial port and many issues can cause this, not just the firmware. I've had similar trouble with my HGI80 which was caused by the USB port becoming corrupted after a few hours of use which could be fixed by removing the device and reconnecting. I spent many months troubleshooting a similar problem in Domoticz, but gave up in the end as it seemed to be a USB device problem that resolved itself (other users had a similar problem). However, if yours is caused by a problem with the firmware, hopefully we'll have an improved version ready in the next few weeks for you to try. It's great to hear that the current version at least works OK for a while with your home-built Atmega328+CC1101+FT232.

If you are interested in digging into the problem, then a good place to start is to enable debugging in the Evohome code (see the Domoticz Evohome wiki for details). This will produce an evoraw.log file and print a little more detail in the main Domoticz log. If you have the time and are interested, I can also suggest 1 or 2 small changes to the code which will show further details of messages with errors.

Dan
DanD
Starting Member
Starting Member
 
Posts: 19
Joined: June 2016

Re: Evohome / Evotouch Wireless protocol?

Postby Happyboy » Mon Mar 13, 2017 8:52 pm

@ Dan,

No need for apologies :) just wondering, now running "your" firmware, ( called it 0.8Dan :))

Seems that I have now many "new"errors. Not sure but did you put additinal logs on ?
The "external_sensor" i never see before. pay load size, see before.
But when i am looking to the temp sensors in Domoticz I can't see i miss any thing.

You are talking about "Sending" are you able to set your Evohome (e.g. change from normal to economy mode ?)
Mine doesn't respond to this.. (it change in Domoticz but not on the Evohome screen..).

I am running now the script AND the RFbee in domoticz (to compare) via script i can offcourse change the " mode " .

Does any one have an overview (picture?) of the hardware which is used in the HGI80 ?

Time is limited to aprox 1 hour in the evening, but very intressted in sugestions to see more "errors" .


Code: Select all
2017-03-13 14:57:44.872 Error: evohome: no payload size - possible corrupt message
2017-03-13 15:00:32.210 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 15:00:32.210 Error: evohome: unable to decode payload for command 0002
2017-03-13 15:09:54.740 Error: evohome: no payload size - possible corrupt message
2017-03-13 15:10:28.905 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 15:10:28.905 Error: evohome: unable to decode payload for command 0002
2017-03-13 15:20:25.950 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 15:20:25.950 Error: evohome: unable to decode payload for command 0002
2017-03-13 15:26:22.493 Error: evohome: too many message ids - possible corrupt message
2017-03-13 15:27:49.886 Error: evohome: too many message ids - possible corrupt message
2017-03-13 15:27:49.886 Error: evohome: too many message ids - possible corrupt message
2017-03-13 15:30:17.592 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 15:30:17.592 Error: evohome: unable to decode payload for command 0002
2017-03-13 15:40:12.062 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 15:40:12.062 Error: evohome: unable to decode payload for command 0002
2017-03-13 15:50:06.932 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 15:50:06.932 Error: evohome: unable to decode payload for command 0002
2017-03-13 15:59:33.996 Error: evohome: too many message ids - possible corrupt message
2017-03-13 15:59:33.996 Error: evohome: too many message ids - possible corrupt message
2017-03-13 16:00:03.202 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 16:00:03.202 Error: evohome: unable to decode payload for command 0002
2017-03-13 16:09:57.073 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 16:09:57.073 Error: evohome: unable to decode payload for command 0002
2017-03-13 16:19:55.644 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 16:19:55.644 Error: evohome: unable to decode payload for command 0002
2017-03-13 16:25:16.321 Error: evohome: too many message ids - possible corrupt message
2017-03-13 16:25:16.321 Error: evohome: too many message ids - possible corrupt message
2017-03-13 16:29:51.114 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 16:29:51.114 Error: evohome: unable to decode payload for command 0002
2017-03-13 16:39:42.154 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 16:39:42.155 Error: evohome: unable to decode payload for command 0002
2017-03-13 16:49:41.680 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 16:49:41.680 Error: evohome: unable to decode payload for command 0002
2017-03-13 16:53:44.812 Error: evohome: no payload size - possible corrupt message
2017-03-13 16:59:33.696 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 16:59:33.697 Error: evohome: unable to decode payload for command 0002
2017-03-13 17:09:23.937 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 17:09:23.937 Error: evohome: unable to decode payload for command 0002
2017-03-13 17:19:21.938 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 17:19:21.938 Error: evohome: unable to decode payload for command 0002
2017-03-13 17:20:49.594 Error: evohome: too many message ids - possible corrupt message
2017-03-13 17:20:49.594 Error: evohome: too many message ids - possible corrupt message
2017-03-13 17:20:49.594 Error: evohome: too many message ids - possible corrupt message
2017-03-13 17:25:10.340 Error: evohome: too many message ids - possible corrupt message
2017-03-13 17:25:10.340 Error: evohome: too many message ids - possible corrupt message
2017-03-13 17:28:48.171 Error: evohome: too many message ids - possible corrupt message
2017-03-13 17:28:48.171 Error: evohome: too many message ids - possible corrupt message
2017-03-13 17:29:19.008 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 17:29:19.008 Error: evohome: unable to decode payload for command 0002
2017-03-13 17:39:15.078 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 17:39:15.078 Error: evohome: unable to decode payload for command 0002
2017-03-13 17:49:07.919 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 17:49:07.920 Error: evohome: unable to decode payload for command 0002
2017-03-13 17:59:05.191 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 17:59:05.191 Error: evohome: unable to decode payload for command 0002
2017-03-13 18:09:04.292 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 18:09:04.292 Error: evohome: unable to decode payload for command 0002
2017-03-13 18:18:55.831 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 18:18:55.831 Error: evohome: unable to decode payload for command 0002
2017-03-13 18:27:31.317 Error: evohome: too many message ids - possible corrupt message
2017-03-13 18:27:31.317 Error: evohome: too many message ids - possible corrupt message
2017-03-13 18:28:50.403 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 18:28:50.403 Error: evohome: unable to decode payload for command 0002
2017-03-13 18:38:42.442 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 18:38:42.442 Error: evohome: unable to decode payload for command 0002
2017-03-13 18:42:27.143 Error: evohome: too many message ids - possible corrupt message
2017-03-13 18:42:27.143 Error: evohome: too many message ids - possible corrupt message
2017-03-13 18:48:35.214 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 18:48:35.214 Error: evohome: unable to decode payload for command 0002
2017-03-13 18:58:29.785 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 18:58:29.785 Error: evohome: unable to decode payload for command 0002
2017-03-13 18:59:50.785 Error: evohome: too many message ids - possible corrupt message
2017-03-13 18:59:50.786 Error: evohome: too many message ids - possible corrupt message
2017-03-13 19:08:25.855 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 19:08:25.855 Error: evohome: unable to decode payload for command 0002
2017-03-13 19:18:20.450 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 19:18:20.450 Error: evohome: unable to decode payload for command 0002
2017-03-13 19:28:17.606 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 19:28:17.606 Error: evohome: unable to decode payload for command 0002
2017-03-13 19:35:00.765 Error: evohome: no payload size - possible corrupt message
2017-03-13 19:38:08.347 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 19:38:08.347 Error: evohome: unable to decode payload for command 0002
2017-03-13 19:47:58.988 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 19:47:58.988 Error: evohome: unable to decode payload for command 0002
2017-03-13 19:57:53.658 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 19:57:53.658 Error: evohome: unable to decode payload for command 0002
2017-03-13 20:07:48.028 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 20:07:48.029 Error: evohome: unable to decode payload for command 0002
2017-03-13 20:11:23.108 Error: evohome: too many message ids - possible corrupt message
2017-03-13 20:11:23.108 Error: evohome: too many message ids - possible corrupt message
2017-03-13 20:13:34.634 Error: evohome: no payload size - possible corrupt message
2017-03-13 20:17:41.299 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 20:17:41.299 Error: evohome: unable to decode payload for command 0002
2017-03-13 20:27:36.140 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 20:27:36.140 Error: evohome: unable to decode payload for command 0002
2017-03-13 20:34:27.734 Error: evohome: too many message ids - possible corrupt message
2017-03-13 20:34:27.734 Error: evohome: no payload size - possible corrupt message
2017-03-13 20:37:01.701 Error: evohome: no payload size - possible corrupt message
2017-03-13 20:37:33.741 Error: evohome: EXTERNAL_SENSOR: Error decoding command, packet size too small: 1
2017-03-13 20:37:33.741 Error: evohome: unable to decode payload for command 0002
Happyboy
Starting Member
Starting Member
 
Posts: 9
Joined: September 2012

PreviousNext

Return to Questions & Discussions Forum

Who is online

Users browsing this forum: No registered users and 1 guest