jacekk015 / zha_quirks

All quirks in one place
MIT License
119 stars 18 forks source link

Moes tze204_aoclfnxz thermostats | time at display not synced #23

Closed cwm77 closed 9 months ago

cwm77 commented 10 months ago

Hi, thanks again for providing Moes tze204_aoclfnxz thermostats with the latest ts0601_thermostat_avatto.py quirk. Everything works fine except for the time synchronization on the physical display. The also connected tze200_aoclfnxz Moes thermostats synchronize the time without problems.

Here is the corresponding log file when connecting one of these thermostats. home-assistant_zha_2023-10-26T10-32-14.883Z.log

jacekk015 commented 10 months ago

Since you've cut out the logs I can't tell you much. Next time send full logs - I always write that.

Mechanism of time update is that the Device need to ask for time update, and the HA Zigpy responds with time. You can't force that message without first Device ask.

In the logs you have:

2023-10-26 12:32:06.930 DEBUG (MainThread) [zigpy.zcl] [0xE778:1:0xef00] Decoded ZCL frame: AvattoManufCluster:set_time_request(param=[170, 0])
2023-10-26 12:32:06.932 DEBUG (MainThread) [zigpy.zcl] [0xE778:1:0xef00] Received command 0x24 (TSN 62): set_time_request(param=[170, 0])

and then response

2023-10-26 12:32:06.940 DEBUG (MainThread) [zigpy.zcl] [0xE778:1:0xef00] Sending request: set_time(param=[101, 58, 64, 38, 101, 58, 92, 70])

but since you've cut-out the logs I don't know what that 0xE778 is - which device is that.

cwm77 commented 10 months ago

but since you've cut-out the logs I don't know what that 0xE778 is - which device is that.

It is such a thermostat.

0xe778

I attached a full log now.

home-assistant_2023-10-26T21-38-46.536Z.log

And here another even bigger one.

home-assistant_zha_2023-10-26T21-49-49.628Z.log

Just in case.

jacekk015 commented 10 months ago

But previous logs contained pairing process for: 0x4b24 That's why I've seen pairing of 0x4b24 but time request of 0xE778 That doesn't match. Will check the logs later.

2023-10-26 12:31:27.138 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=0, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_RETRY|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 320>, groupId=0, sequence=167), 255, -74, 0x4b24, 255, 255, b'\x18C\x01\x04\x00\x00B\x10_TZE204_aoclfnxz\x05\x00\x00B\x06TS0601']
cwm77 commented 10 months ago

I have exactly two thermostats of this type. One is the one with Nwk identifier 0x4b24, which I paired while recording the first log provided. The other is the one that has the Nwk identifier 0xE778.

jacekk015 commented 10 months ago

Quirk has been modified. Restart is needed. Device sends time request and HA responds properly. Next the device doesn't accept data that was sent. Let's try if that works.

cwm77 commented 10 months ago

Thanks, it seems to work. The time is now synchronized on the display. I will continue to monitor.