RubenKelevra
commented
1 year ago I got 4 of them, but don't see an issue here. Only difference here may be that mine are all powered by a 3V power supply soldered onto the board.
You don't need to repair them. Just remove the battery cap and install it after 2-3 seconds again. Hit a couple of times the center button to start the adjustments (don't need to set a clock/date) and it will reappear on the ZigBee network.
github-actions[bot]
What happened?
I got myself TS0601_thermostat a few weeks ago and it was working fine. Today I discovered that it doesn't execute any commands I send it, even though there is no error reported by Z2M. Looks like it responds correctly to Z2M but actually doesn't do anything.
At the same time the device seems to be correctly reporting its state, for instance temperature.
I was on 1.28.4 when it happened, then I upgraded to 1.29.0 but nothing has changed.
Here is what appears in the logs when I try to change mode to heat:
Zigbee2MQTT:debug 2023-01-04 15:17:18: Received MQTT message on 'zigbee2mqtt/Grzejnik u dziewczyn/set/system_mode' with data 'heat' Zigbee2MQTT:debug 2023-01-04 15:17:18: Publishing 'set' 'system_mode' to 'Grzejnik u dziewczyn' 2023-01-04T14:17:18.063Z zigbee-herdsman:controller:endpoint Command 0x003c84fffec9338f/1 manuSpecificTuya.dataRequest({"seq":0,"dpValues":[{"dp":106,"datatype":4,"data":[1]}]}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) 2023-01-04T14:17:18.063Z zigbee-herdsman:adapter:zStack:adapter sendZclFrameToEndpointInternal 0x003c84fffec9338f:54002/1 (0,0,1) 2023-01-04T14:17:18.064Z zigbee-herdsman:adapter:zStack:znp:SREQ --> AF - dataRequest - {"dstaddr":54002,"destendpoint":1,"srcendpoint":1,"clusterid":61184,"transid":4,"options":0,"radius":30,"len":10,"data":{"type":"Buffer","data":[17,4,0,0,0,106,4,0,1,1]}} 2023-01-04T14:17:18.065Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,20,36,1,242,210,1,1,0,239,4,0,30,10,17,4,0,0,0,106,4,0,1,1,149] 2023-01-04T14:17:18.084Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,1,100,1,0,100] 2023-01-04T14:17:18.084Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,1,100,1,0,100] 2023-01-04T14:17:18.084Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 1 - 3 - 4 - 1 - [0] - 100 2023-01-04T14:17:18.084Z zigbee-herdsman:adapter:zStack:znp:SRSP <-- AF - dataRequest - {"status":0} 2023-01-04T14:17:18.084Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] 2023-01-04T14:17:18.089Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,3,68,128,0,1,4,194] 2023-01-04T14:17:18.089Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,3,68,128,0,1,4,194] 2023-01-04T14:17:18.089Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 3 - 2 - 4 - 128 - [0,1,4] - 194 2023-01-04T14:17:18.090Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - dataConfirm - {"status":0,"endpoint":1,"transid":4} 2023-01-04T14:17:18.090Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext []
I have not tried to remove batteries or re-pair yet, hoping you can come up with a fix I can test, but I assume it will take time (if at all), so I will probably try to fix it on the device side tomorrow.
What did you expect to happen?
Correctly execute commands.
How to reproduce it (minimal and precise)
Unknown, happened for the first time.
Zigbee2MQTT version
1.28.4, 1.29.0
Adapter firmware version
20220219
Adapter
Sonoff ZBDongle-P ZigBee Dongle Plus CC2652P
Debug log
No response