Evohome WiFi with HGI80 under Windows

[StanHD]

Hi,
Firstly thank you for the Evohome implementation within Domoticz. I have been using it for a couple of years now, and it's excellent.
In the last week or so I have noticed the following error in the log occurring every hour:-

2018-01-29 13:54:31.732 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 1
2018-01-29 13:54:31.732 Error: evohome: unable to decode payload for command 3ef0
2018-01-29 13:54:33.732 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 1
2018-01-29 13:54:33.732 Error: evohome: unable to decode payload for command 3ef0
2018-01-29 13:54:35.737 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 1
2018-01-29 13:54:35.737 Error: evohome: unable to decode payload for command 3ef0
2018-01-29 14:54:32.494 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 1
2018-01-29 14:54:32.494 Error: evohome: unable to decode payload for command 3ef0
2018-01-29 14:54:34.484 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 1
2018-01-29 14:54:34.484 Error: evohome: unable to decode payload for command 3ef0
2018-01-29 14:54:36.489 Error: evohome: ACTUATOR_STATE: Error decoding command, unknown packet size: 1
2018-01-29 14:54:36.489 Error: evohome: unable to decode payload for command 3ef0

Domoticz Version:- V3.8740
Windows 7
HGI80 on USB
Evohome WiFi. Firmware version 2.xx (can't remember the exact number)

Everything in Domoticz is reporting OK, and Evohome is all working fine without any logged errors. So there is no functional problem, but wondered if anyone else is getting this, or knows of a fix?

Thanks,
Stan

[StanHD]

Replying to myself with some more info:-

Searching around on Automated Home forum it would appear the the Evohome firmware has been recently updated and at least 2 users are reporting the same errors from Domoticz / HGI80 set-ups.

The suggestion is that the new Evohome WiFi firmware 02.xx-- (rolled out by Honeywell automatically) may be the cause.

Anyone else?

[StanHD]

Anyone?

I have updated to Version 8944. Same problem, plus, another symptom is that Domoticz now crashes and re-starts when set points are changed using the JSON interface.

If no one else is experiencing these problems then perhaps it's just my installation. That being the case perhaps I should delete then re-install the Domoticz Evohome hardware. Does anyone have any advice if that might help?

Thanks.

[philchillbill]

Those 'errors' have been there for a long time, not just since the recent firmware update. The Honeywell RF protocol is not fully understood by the reverse-engineering community and from time to time the HGI80 spits out stuff that the Domoticz implementation can't quite place correctly. It's all harmless and the HGI80 still does within Domoticz what it should do. Strange you only notice that stuff in your log now - I've had it for 18 months with every beta I've tried.

[StanHD]

@philchillbill,

Thanks for the reply, and I really appreciate the efforts made on this hardware.
I have always had some warnings but not errors. Perhaps something changed in my set-up, and as you point out the errors seem harmless.
I have turned off a few scripts that made adjustments to set points, and avoid using Domoticz for making any changes now, as this causes a crash and re-start. It's unfortunate because the JSON interface capability is a very useful feature.

[subtrEM]

Anyone?

I have updated to Version 8944. Same problem, plus, another symptom is that Domoticz now crashes and re-starts when set points are changed using the JSON interface.

If no one else is experiencing these problems then perhaps it's just my installation. That being the case perhaps I should delete then re-install the Domoticz Evohome hardware. Does anyone have any advice if that might help?

Thanks.

Domoticz v3.8975 on Raspberry Pi 3 (Raspbian Jessie) with HGI80 gateway
Evohome wifi controller v 2.00.17

Same symptom since 2 days: after upgrade of evohome controller, said 3ef0 command errors started appearing, but in increasing frequency: first every few hours, gradually increasing in the course of a day to about every 20 min. Rebooted Domoticz host (Raspi3) and HGI80, error frequency reduced to 2 messages in last 16 hours.

(Note on JSON problem: only seen - also in much earlier versions of Domoticz - when using Domoticz app for iOS v1.08 (free, as test) on iPad. AFAIK, this is indeed another phenomenon than the 3ef0 command error.)

[philchillbill]

I have always had some warnings but not errors.

I think you will find they were always called 'errors' by Domoticz. I have always had them every few minutes for 18 months and they are not an issue. Ask @DanD if you want clarification (he's the main developer on the evohome.cpp code).