BOSCH Thermostat II does not complete onboarding with deCONZ 2.25.3

deCONZ General Support
1

I own a bunch of BOSCH Radiator Thermostat II devices and connected them successfully in 2.23.1 and before (following the procedure as described here). They work more or less OK, but sometimes drop from the network. Recently I upgraded deCONZ to 2.25.3 after the corresponding HA add-on was finally updated :wink: . While the new deCONZ version shows much better performance in general and is more stable, I am not able to complete the onboarding of my recently dropped Thermostat II anymore.

What happens is that the device is recognized by deCONZ & Phoscon (see below), however, the device is flashing the “connecting” sign and shows occasionally an “E25” code. I can read values but not set the target temperature. Also, it does send Device Announce messages in quick intervals, which for me could indicate that the device somehow thinks it is not yet fully connected.

Any ideas?

image

image
image783×521 32.1 KB

Some (filtered) logs:


15:56:01:338 DeviceAnnce of SensorNode: 0x18FC2600000CC216
15:56:01:310 DeviceAnnce of SensorNode: 0x18FC2600000CC216 
15:56:01:099 ZCL attribute report 0x18FC2600000CC216 for cluster: 0x0201, ep: 0x01, frame control: 0x1C, mfcode: 0x1209 
15:56:00:126 DeviceAnnce of SensorNode: 0x18FC2600000CC216 
15:55:57:301 ZCL attribute report 0x18FC2600000CC216 for cluster: 0x0001, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
15:55:56:286 ZCL attribute report 0x18FC2600000CC216 for cluster: 0x0001, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
15:55:55:779 DeviceAnnce of SensorNode: 0x18FC2600000CC216
15:55:55:771 ZCL attribute report 0x18FC2600000CC216 for cluster: 0x0201, ep: 0x01, frame control: 0x1C, mfcode: 0x1209 
15:55:54:312 DeviceAnnce of SensorNode: 0x18FC2600000CC216
15:55:51:426 ZCL attribute report 0x18FC2600000CC216 for cluster: 0x0001, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
15:55:48:417 ZCL attribute report 0x18FC2600000CC216 for cluster: 0x0001, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
15:55:44:689 ZCL attribute report 0x18FC2600000CC216 for cluster: 0x0001, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
15:55:44:465 DeviceAnnce of SensorNode: 0x18FC2600000CC216
2

This is resolved now, I eventually managed to get get it fully paired. Still maybe interesting to note that this is on my “production” network with ConBee II. Out of curiosity, I also tried to pair it with a ConBee III with deCONZ 2.26.0-beta and latest firmware, but this did not work at all, even the node description was not complete (“unknown” for manufacturer) and the cluster descriptions have not been loaded.