Bosch Room Thermostat II issues

[ads1230]

Hi,

I’m struggling to connect my Bosch Room Thermostat II to my network.

I have a Conbee 3 running firmware 26530900. My Phoscon running via docker version is 2.29.1.

I’ve used Postman to add the install code and got a successful response

I have reset the thermostat and it pairs as “0xDEDF” but I cannot get any further, the device is not recognised as a thermostat.

Help would be appreciated, thanks.

[tobias]

Hooking in here as I have the same issue. With both of my Bosch Thermostat II.

Sending api call via Postman to provide installcode was returned with success for both.
I can see the devices even in deCONZ overview but they are not recognized - there is no ddf or + shown in the gui overview.
Both devices’ MAC addresses are shown in sqlite devices table.
Tried removing them in deCONZ and re-pairing already multiple times. No success.

I’d like to avoid the solution which worked at Recently unable to pair Bosch Thermostat 2 as it seems rather “luck” driven and also I don’t want to fully reset the installation.

It seems to me something went wrong with pairing - device is somehow “partially” paired?

Any idea appreciated.

Device: Bosch Thermostat II
Running “latest” image of docker container on an rpi
Product: Conbee III (3)
Gateway Version 2.29.2
Firmware 26530900

[Smanar]

Hello, if you can see it in deconz, can you check the model id and the manufacture name ?

Edit:
Have just see that Fix vendor and state for Bosch Thermostat II 230V by aSauerwein · Pull Request #8084 · dresden-elektronik/deconz-rest-plugin · GitHub

[tobias]

Hi Smanar!
Thanks for responding.
I realized that this thread was regarding the “room thermostat II”. My issue is actually with my two “radiator thermostat II”. I wasn’t aware that bosch also released that room thing with almost the same name - my fault.
Anyway I think the problem is the same as ads1230 has - so I’ll continue in this thread.
Providing some screenshots with information. Unfortunately deconz is not showing the model/manufacturer id.
Is there any other way to detect this? To me it seems that the device is somehow already “wrongly” connected and it doesn’t even try to use the installcode. Because I tested and it doesn’t make a difference if I provide the installcode or not before/while (tried both) trying to pair.
My approach:

1. Remove battery from thermostat.
2. Remove device from deconz by “delete node”
3. Restart deconz docker container
4. Start “add sensor”/permit join in phoscon/deconz (tried both although I think it doesn’t make any difference anyway)
5. Add battery and keep thermostat button pressed to directly trigger factory reset thermostat
6. Exec http PUT call in postman
   Result is always that the device shows up but is not usable. See screenshots.

Any further idea is appreciated.

[Smanar]

Have you tried to force an attribute read ?

How to read Clusters

Model id and manufacture name are in cluster 0x0000

But perhaps you miss all clusters too ?

[Mimiix]

You need to do the postman put before pairing

[tobias]

Hello!
After a busy week I finally found some time to deal with this again. Thanks to the hints. Tried it all - still no luck unfortunately:

• Force reading of clusters is not possible as the clusters are not even shown for (both) my devices: There is no “plus” sign shown in the deconz UI for each of my thermostat devices.
• executing the put http request before starting the “enable permit join” doesn’t work. No difference: Devices do show up but still as “unknown” - reappearing exactly as in my screenshot within my earlier post.

I’ve tried a lot of things now:

• executing the http put call before, while, after pairing
• removing the devices with “delete node” as well as leaving them before trying to pair again
• resetting the devices countless times

What caught my attention - If I do the following:

1. I remove batteries from both my devices 0x30???E06F and 0x30???BB27.
2. I delete both my devices from deconz GUI doing “delete node”.
3. I check via sqlite and verify in table “devices” both devices are gone.
4. I send the PUT call and click “enable permit join” for pairing.
5. I put batteries back into 0x30???E06F device and run “reset to factory defaults” of it.
6. Suddenly both devices, the 0x30???E06F and 0x30???BB27 show up in deconz again (without manufacturer, model, etc)
   What I don’t understand is that the 0x30???BB27 device shows up ALTHOUGH it doesn’t even have a battery inserted and also had been deleted before (step 2) from deconz/phoscon.
   Anyone has an idea why that could be and if that is intended?

Last resort will be to reset my whole deconz/phoscon installation. I’d like to really avoid that. So still hoping for any clue.

[Smanar]

Deleting a device in deconz do nothing, if the device is already paired, it know the coordinator Mac adress and the key for pairing, it still can do request, if deconz see request from a device, it add it in the GUI.

If you reset the device and delete it from deconz, more chance it will not come back (it will forget the zigbee network setting)

But I realy don’t know how work the “install code pairing”, what is blocked by this procedure.

• The device don’t appear in deconz, it seem it’s wrong, as you can see it, even without the procedure.
• The inclusion procedure is bloqued, it seem yes, as you can’t have the clusters.

BTW you have option to “finish” the inclusion on the GUI, with “right clic”, if it don’t work, perhaps we can have an error message on logs. But the device is probably stopping requests waiting for the code ?

[tobias]

Thanks for your response Smanar.
No luck yet on making things work. Tried all your hints and ideas. Max result I get is that the devices show up in deconz but are not identified and node’s cluster data is unreadable. I’m finally convinced that this is some issue with conbee/deconz as I found this thread:

Does deCONZ serial protocol for ConBee/RaspBee Zigbee Coordinator adapters not support joining/pairing via install code and qr code?

And from the posts in there it seems indeed that there is possibly some issue with conbee III and devices which require installcode. See Does deCONZ serial protocol for ConBee/RaspBee Zigbee Coordinator adapters not support joining/pairing via install code and qr code? · Issue #20 · dresden-elektronik/deconz-serial-protocol · GitHub which is same conbee 3 version I am using and also same bosch devices.

Guess I have to wait or I have finally reasoning enough to invest more time and switch away from conbee to a sonoff dongle using zigbee2mqtt.

[Smanar]

Have found a tuto here Bosch water sensor BWA-1: How to set up using install code? - #7 by sbonfert
Except now you don’t need to re compile code
The issue is here Bosch Smoke Alarm II · Issue #6421 · dresden-elektronik/deconz-rest-plugin · GitHub

But all have tried on conbee 2, IDK for conbee 3, but from other devs there is no reason for it work differently.

[tobias]

Thank you for all the help and links provided.
But I simply couldn’t make it work. And I’ve given up and did chickening out after trying out zigbee2mqtt with a Sonoff dongle-e since I have a mqtt broker anyway running nowadays.
Pairing with the Bosch heater thermostat II and the install code worked with zigbee2mqtt instantly.
And I switched my whole zigbee network to that solution now. It works stable and very well so far (doesn’t mean that much yet as it is only running for a week now).
And stability was also never an issue for me with conbee and phoscon as well and additionally I really liked the interface. So will miss it indeed a bit. But after all that connection issue was just simply taking too much time without working out. Will keep monitoring phoscon and maybe give it a try another day again.
Once more: Thanks for the effort to help!