-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Installcode no more working with 2.0.0 for Bosch Twinguard #25885
Comments
Same for me: Home Assistant Core 2025.1.4 |
After unsuccessfully trying to pair my Twinguard using a Conbee III (see Koenkk/zigbee-herdsman#1184)
|
FYI I've
I successfully paired a Bosch BSD-2/Smoke alarm II under 1.42.0 One thing I noticed is that the install code of the Twinguard is smaller than the one of the Smoke alarm II. Might be unrelated though.
|
Same for me. I have spent so long troubleshooting this. So happy I came across this thread.
|
I downgraded to version 1.42.0 again. So I was able to connect my Bosch Twinguards again. @raoulbhatia I think you propably have another problem. Did you read this thread https://github.com/Koenkk/zigbee2mqtt/issues/20169? I had the same problem like you at the beginning. I was not able to connect the Bosch Twinguards with ZBDongle-E. Then I switched to ZBDongle-P, where I successfully could connect the Bosch Twinguards until zigbee version 2.0.0. |
Same for me. I have also spent some time troubleshooting.
FYI: Install code for Bosch Thermostat II worked flawless |
I can confirm both observations with my setup, Thermostat works with install code, Twinguard does not work and needs inital pairing with 1.42. Once it is paired it works just fine with 2.0.0. |
Do you mean running zigbee2mqtt as version 1.42 and then it works? I'm abit of a newbie, how would I do that (I am running this on HA) |
Any news regarding this topic? I have exactly the same issue. Worked fine with 1.42 but with 2.1.0-1 it is not working anymore. How can I downgrade without a backup? |
I found the solution here: https://community.home-assistant.io/t/how-to-downgrade-addons/331223/20
|
That works! Thank you so much, Johannes! |
@Koenkk would you debug this issue if somebody would donate you a device? |
Could you provide the debug log when adding the install code on both 1.42 (works) and on 2.0.0 (doesn't work)? See this on how to enable debug logging. |
Thanks @JohannesBY for posting that. @Koenkk I tried running it on both versions and it wont add. Although on version 1.4.1 and 1.4.2 (I tested both) I do NOT get the missing CRC error. Logs below. Although my twinguard does not run as I get the node descriptor does not exist. I have the bosch twinguard model 8750001215 --v2.1.0-1 msg --v1.4.1 msg |
Hi +1 Exactly the same problem since >=v2.0 |
@kooori It will only work in version 1.4.1 if you use the ZBDongle-P. Unfortunately, it does not work with the ZBDongle-E. |
thanks for coming back to me. It's the first time I am going Zigbee. Would this TubesZB device work (https://tubeszb.com/product/cc2652p2-based-zigbee-to-poe-coordinator-2023/) with the Twinguard(I need something POE based)? If so I will go ahead and get this and keep the other one for down the track. I'm paranoid that the model I have is different to the supported model on the z2m website. The last digit is different. 8750001215 is the model I just received from Amazon UK (8750001213 is supported on the website). |
I can't say for sure, but the chipset looks very similar, so chances are good, I guess. Maybe someone else can provide more insights
This is one of the Twinguards I paired yesterday with version 1.4.1 and the ZBDongle-P. No problems! |
@w0nk1 I just ordered the SLZB-06 adapter (as it has POE). It has the same CC2652P chipset so theoretically should work. I'll report back here on how I go with the new device and fingers crossed it connects otherwise I might have to buy the bosch smart home controller. |
In 2.1.0 I get this error
I am using zstack with a zigstar CC2652P controller. |
For some reason I cannot downgrade to 1.42.0 anymore it crashes after a few seconds. So I cannot join the 2 remaining twinguards or provide any addtional logs at the moment from 1.42.0 :( I do not know why it is crashing with this error:
|
okay I got 1.42.0 running again this is the full log of a twingaud joining:
|
@Koenkk I did a little investigation: Maybe the CRC is the problem Since version 2.0.0 a missing crc will be calculated and the install code will be adjusted. Till version 1.42.0 this doesn't happen and the 'installCodeFormat' is '1' instead of '2' Logfiles working and failing: 45df7312_zigbee2mqtt_2025-02-08T10-11-09.807Z.log |
I'm not sure how you are running z2m, but could you try making the following change and see if that works? docker exec -it CONTAINER_NAME sh
apk add nano
nano /app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js
# Change: const payload = { installCodeFormat: key.length === 18 ? 1 : 2, ieeeaddr: ieeeAddress, installCode: key };
# To: const payload = { installCodeFormat: 2, ieeeaddr: ieeeAddress, installCode: key };
exit
docker restart CONTAINER_NAME |
@kooori I was able to pair three 8750001213 twinguards with Z2M < 1.4.2. Thus, I assume that it will work once it is fixed for version 2.x |
@Koenkk I was able to join a Twinguard 8750001213 (91 character install code) with these changes in Z2M 2.1.1-1 (Coordinator is SLZB-06 with zigbee fw 2.7.1) Thank you very much for the quick support! |
What happened?
I detected after updating to version 2.0.0, the install code seems not longer working for Bosch Twinguard.
I have several Bosch Twinguards in my Zigbee Network. It was possible to connect them with the old version 1.42 without problem. Some days ago I updated to version 2.0.0. Today I wanted to connect a new Bosch Twinguard,. But it's not possible. I also tried to reconnect another Bosch Twinguard, which was already in my network before. Also here I can't get a connection with the version 2.0.0.
So I think there is something wrong with the install code "adjustment" which was included with the install code fix?
I get following messages in the log:
So it seems, that the Install code will be "adjusted", but it will be not successful to connect the device.
The Bosch Twinguard have a 91-digit install code.
What did you expect to happen?
It should work like already in the previous versions
How to reproduce it (minimal and precise)
Everytime when I try to connect a Bosch Twinguard with 91-digit install code at the frontend with "tools->add install code"
Zigbee2MQTT version
2.0.0
Adapter firmware version
20210708
Adapter
zstack
Setup
Home Assistant Core 2025.1.4, Pi4, SONOFF ZBDongle-P
Debug log
No response
The text was updated successfully, but these errors were encountered: