Thermostat valve always leaves after interview

Configuration Zigbee
, , ,
1

I’m trying to add a smart thermostat via Zigbee2Mqtt but the device always leaves right after starting the interview. Any idea how to solve the problem and get it connected? The next Zigbee router device is 2m away, so signal strength shouldn’t be the problem.

Info 2024-02-23 11:20:09Device '0x0c4314fffe45300a' joined
Info 2024-02-23 11:20:09MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0c4314fffe45300a","ieee_address":"0x0c4314fffe45300a"},"type":"device_joined"}'
Info 2024-02-23 11:20:09Starting interview of '0x0c4314fffe45300a'
Info 2024-02-23 11:20:09MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0c4314fffe45300a","ieee_address":"0x0c4314fffe45300a","status":"started"},"type":"device_interview"}'
Warning 2024-02-23 11:20:37Device '0x0c4314fffe45300a' left the network
Info 2024-02-23 11:20:37MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0c4314fffe45300a","ieee_address":"0x0c4314fffe45300a"},"type":"device_leave"}'
2

Zigbee herdsman debug shows this, but I must say, I cannot “read” what went wrong.

2024-02-23T11:42:17.717Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x23: {"_cls_":"childJoinHandler","_id_":35,"_isRequest_":false,"index":0,"joining":0,"childId":6175,"childEui64":{"type":"Buffer","data":[12,67,20,255,254,69,48,10]},"childType":4}
2024-02-23T11:42:17.717Z zigbee-herdsman:adapter:ezsp:driv Unhandled frame childJoinHandler
2024-02-23T11:42:17.723Z zigbee-herdsman:adapter:ezsp:uart <-- [1704b5a9702a0aaa53a40fdb5541d1459e4dd85408c27e]
2024-02-23T11:42:17.723Z zigbee-herdsman:adapter:ezsp:uart --> parsed 1704b5a9702a0aaa53a40fdb5541d1459e4dd85408c27e
2024-02-23T11:42:17.723Z zigbee-herdsman:adapter:ezsp:uart <-- DATA (1,7,0): 1704b5a9702a0aaa53a40fdb5541d1459e4dd85408c27e
2024-02-23T11:42:17.723Z zigbee-herdsman:adapter:ezsp:uart --> ACK  (2)
2024-02-23T11:42:17.723Z zigbee-herdsman:adapter:ezsp:uart --> [82503a7e]
2024-02-23T11:42:17.724Z zigbee-herdsman:adapter:ezsp:uart <-- ACK (7): 1704b5a9702a0aaa53a40fdb5541d1459e4dd85408c27e
2024-02-23T11:42:17.724Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: 46940124001f180a3045feff14430c0203ffff
2024-02-23T11:42:17.724Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x24: {"_cls_":"trustCenterJoinHandler","_id_":36,"_isRequest_":false,"newNodeId":6175,"newNodeEui64":{"type":"Buffer","data":[12,67,20,255,254,69,48,10]},"status":2,"policyDecision":3,"parentOfNewNodeId":65535}
2024-02-23T11:42:17.724Z zigbee-herdsman:adapter:ezsp:debg Device left network request received: 6175 0c4314fffe45300a
2024-02-23T11:42:17.725Z zigbee-herdsman:controller:log Device leave '0x0c4314fffe45300a'
2024-02-23T11:42:17.725Z zigbee-herdsman:controller:log Removing device from database '0x0c4314fffe45300a'
2024-02-23T11:42:17.725Z zigbee-herdsman:controller:database:log Writing database to '/config/zigbee2mqtt/database.db'
Zigbee2MQTT:warn  2024-02-23 12:42:17: Device '0x0c4314fffe45300a' left the network
Zigbee2MQTT:info  2024-02-23 12:42:17: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0c4314fffe45300a","ieee_address":"0x0c4314fffe45300a"},"type":"device_leave"}'
2024-02-23T11:42:17.788Z zigbee-herdsman:adapter:ezsp:uart <-- [2704b1a9702a0aaa53a40fdb5541d1459e4dd85445907e]
2024-02-23T11:42:17.789Z zigbee-herdsman:adapter:ezsp:uart --> parsed 2704b1a9702a0aaa53a40fdb5541d1459e4dd85445907e
2024-02-23T11:42:17.789Z zigbee-herdsman:adapter:ezsp:uart <-- DATA (2,7,0): 2704b1a9702a0aaa53a40fdb5541d1459e4dd85445907e
2024-02-23T11:42:17.789Z zigbee-herdsman:adapter:ezsp:uart --> ACK  (3)
2024-02-23T11:42:17.789Z zigbee-herdsman:adapter:ezsp:uart --> [83401b7e]
2024-02-23T11:42:17.789Z zigbee-herdsman:adapter:ezsp:uart <-- ACK (7): 2704b1a9702a0aaa53a40fdb5541d1459e4dd85445907e
2024-02-23T11:42:17.790Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: 46900124001f180a3045feff14430c0203ffff
2024-02-23T11:42:17.790Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x24: {"_cls_":"trustCenterJoinHandler","_id_":36,"_isRequest_":false,"newNodeId":6175,"newNodeEui64":{"type":"Buffer","data":[12,67,20,255,254,69,48,10]},"status":2,"policyDecision":3,"parentOfNewNodeId":65535}
2024-02-23T11:42:17.791Z zigbee-herdsman:adapter:ezsp:debg Device left network request received: 6175 0c4314fffe45300a
2024-02-23T11:42:17.791Z zigbee-herdsman:controller:log Device leave '0x0c4314fffe45300a'
Zigbee2MQTT:warn  2024-02-23 12:42:17: Device '0x0c4314fffe45300a' left the network
Zigbee2MQTT:info  2024-02-23 12:42:17: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0c4314fffe45300a","ieee_address":"0x0c4314fffe45300a"},"type":"device_leave"}'