-
Notifications
You must be signed in to change notification settings - Fork 703
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Device Support Request] Bosch Radiator Thermostat 2 #3300
Comments
FYI, if it is "BOSCH Radiator Thermostat II" (Model: BTH-RA) then this is a duplicate of this existing open issues being tracked: Also see this related discussion thread in the Home Assistant community forum: Notes: To pair this device you have to install the device via its installation code. The installation code can be obtained by scanning the QR-code on the inside of the battery cover with your smartphone. Then get the device into pairing mode. Paste the code you got from the QR-code ... https://www.home-assistant.io/integrations/zha#action-zhapermit PS; Also note that support for commissioning Zigbee 3.0 devices via “Install Code” or “QR Code” via the zha.permit action has so far only been implemented for ‘ezsp’ (Silicon Labs EmberZNet) or ‘znp’ (Texas Instruments) radio type in ZHA. Other radio types are missing support in their respective radio libraries for zigpy or manufacturer’s firmware commands/APIs. That is you need a Zigbee Coordinator that uses a Silabs or TI chip. See ZHA limitations: https://www.home-assistant.io/integrations/zha#limitations and https://www.home-assistant.io/integrations/zha#recommended-zigbee-radio-adapters-and-modules |
Thanks, yes is then a duplicate. Would be better that I ask support there then? Quick questions regarding the Zigbee limitation and ZHA Permit. Since I saw that my ConBee3 doesn't have Silicon Labs EmberZNet or Texas means that I cannot pair devices via zha.permit? Thanks |
Yes please do, (you should close this #3300 if it is a duplicate of #2476 and post/continue in that existing #2476 issue instead).
That is correct, (there is no good reason to buy a ConBee 3 if you use ZHA as it has this limitation and not maintained for as much as missing expansive doucmentation and lack developers activly interested in it for zigpy/ZHA). Recommend that you get the Home Assistant SkyConnect / Home Assistant Connect ZBT-1 USB dongle as it is best supported and you indirectly sponsor the development of Home Assistant): https://community.home-assistant.io/t/zigbee-buyers-guide/654695/2 FYI, it is really easy to migrate to a new radio in ZHA if you buy a other adapter (and you do not even need to re-pair devices): You can otherwise address the lack of support for ConBee in ZHA directly to Dresden Elektronik (who makes ConBee/RaspBee radio adapters and the deconz firmware for them), as while deconz firmware that ConBee/RaspBee uses might already have support for install-code and qr-code provisioning or not, but in any case, Dresden Elektronik has not yet published any specific documentation for how to use it with their serial protocol that ZHA/zigpy and other third-party applications depends on so they can not use it. This has been requested for a long time but slow respons from Dresden Elektronik's deconz developers in this regard, see: and |
Problem description
Hi All,
I hope that someone can help me :)
I would like to add to my HA OS the Bosch Radiator Thermostat 2 via a Conbee V3.
I'm trying to add the Thermostat via ZHA.permit and inserting the IEEE Source and Installation code. I tried also with the QR code but I got always the following error:
"Translation Error: The intl string context variable "services" was not provided to the string "Impossibile eseguire l'azione: {services}" Unknown error"
Any idea on what I could try? Thank you so much!!!
Solution description
No solution so far.
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]
Device signature
Device signature
[Paste the device signature here]
Diagnostic information
Diagnostic information
[Paste the diagnostic information here]
Logs
Logs
Custom quirk
Custom quirk
Additional information
No response
The text was updated successfully, but these errors were encountered: