search

smar000 / evoGateway

Python script for listening in and responding to evohome heating control radio messages
47 stars 17 forks source link

Multiple different "errors" and "unknown" information #8

Closed Maikel-K closed 4 years ago

Maikel-K commented 4 years ago

Hi smar,

I have the setup running for some time now and am wondering what the "errors" mean i see passing by:

2019-11-18 19:48:58 |1| SCHEDULE_SYNC | RQ| GWAY InternetModule -> CONTROLLER | Payload: 00 Payload length: 1 2019-11-18 19:48:58 |1| SCHEDULE_SYNC | RP| CTL Woonkamer thermostaat -> GWAY InternetModule | Payload: 00050E4A Payload length: 4

RAW: 2019-11-18 19:48:58: 1: SCHEDULE_SYNC --- RQ --- 30:134878 01:046829 --:------ 0006 001 00 2019-11-18 19:48:58: 1: SCHEDULE_SYNC --- RP --- 01:046829 30:134878 --:------ 0006 004 00050E4A

2019-11-18 19:51:16 |1| ACTUATOR_STATE | RQ| GWAY InternetModule -> 63:262143 | State update request

RAW: 2019-11-18 19:51:16: 1: ACTUATOR_STATE --- RQ --- 30:134878 63:262143 --:------ 3EF0 001 00

2019-11-18 19:52:46 |1| ZONE_NAME | RQ| GWAY InternetModule -> CONTROLLER | Payload: 0000 Payload length: 2 2019-11-18 19:52:46 |1| ZONE_NAME | RP| CTL Woonkamer thermostaat -> GWAY InternetModule | Payload: 0000576F6F6E6B616D65720000000000000000000000 Payload len gth: 22

RAW: 2019-11-18 19:52:46: 1: ZONE_NAME --- RQ --- 30:134878 01:046829 --:------ 0004 002 0000 2019-11-18 19:52:46: 1: ZONE_NAME --- RP --- 01:046829 30:134878 --:------ 0004 022 0000576F6F6E6B616D65720000000000000000000000

I dont want to post to many at a time, so we can keep track of the reply's.

Thanks for your help, again!

smar000 commented 4 years ago

They are not errors as such, but responses that the script is not really processing such as the schedule_sync messages (I think these are synching schedules between the controller and the corresponding device).

Also as there is no official documentation from Honeywell, all commands have had to be reverse engineered (see credits for links to discussions/Domoticz code etc). Some may not have been worked out and will also appear as errors or unknown etc.

Maikel-K commented 4 years ago

Okay, that sound reasonable then haha.

I do see alot of requests going to this device id: 63:262143 Any idea what that could be? I cant really find a list of the device id's known or am i missing something other then: DEVICE_TYPE["01"] = "CTL" DEVICE_TYPE["02"] = "UFH" underfloorheating DEVICE_TYPE["04"] = "TRV" hr92
DEVICE_TYPE["07"] = "DHW" domestic hot water DEVICE_TYPE["13"] = "BDR" bdr relais DEVICE_TYPE["30"] = "GWAY" gateway
DEVICE_TYPE["34"] = "STAT" thermostat

Is it correct that type 34 could be the Round Wireless thermostat?

smar000 commented 4 years ago

I am not really sure what the 63:262143 is, but I and others have exactly the same device ID showing up from time to time in our logs (with heartbeat messages). Given that the same ID is used, I am guessing that it some standard evohome/Honeywell device address. Could even be a virtual device ID for say the evohome web gateway?

For the other device types: 01: is for controllers 30: is for the internet gateway units, but which I am also defaulting to for the gateway script 34: is for the round thermostats, e.g. T87RF2033