zigbee2mqtt
zigbee2mqtt copied to clipboard
Koenkk
Bosch Twintguard was not paired
What happened?
z2m work so far on my HA Yellow device. I was able to pair 106 devices. (73 routers, 33 end-devices)
Now I´m fighting with my Bosch Twintguards.
- Installation code was added.
- Paring was activated just for coordinator
Device joined, interview was started but every time it will stop with an error successful paring not possible. Twintguard were factory reseted.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.34.0
Adapter firmware version
7.3.1.0 build 176
Adapter
EZSP v12
Debug log
What happened?
z2m work so far on my HA Yellow device. I was able to pair 106 devices. (73 routers, 33 end-devices)
Now I´m fighting with my Bosch Twintguards.
- Installation code was added.
- Paring was activated just for coordinator
Device joined, interview was started but every time it will stop with an error successful paring not possible. Twintguard were factory reseted.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.34.0
Adapter firmware version
7.3.1.0 build 176
Adapter
EZSP v12
Debug log
Hi, I have these problems too with the Sonoff Dongle E. Some members write here that it is the Sonoff Dongle E that causes the issues. Last week I successfully paired a Bosch BSD-2 smoke detector, also with installation code. I tried everything possible to pair the Twinguard - all without success. Do you also have the dongle E (eszp v12)? Do you have the FW on? 7.3.1.0 build 176 flashed?
Same Problem here with a Sonoff Dongle-E. BSD-2 with install code works just fine. I bought the E exclusively to pair devices with install codes and now the TwinGuard doesn’t pair/interview :( (Also flashed with current MultiPan)
Also problem with pairing. I have 9 pieces of BSD-2. 8 paired OK, but the last has problem.
Coordinator: zStack3x0 (SLZB-06) Revision: 20240315 Z2M: 1.38.0 commit: fe048e6
Info 2024-06-02 18:50:56MQTT publish: topic 'Z2M/0xf082c0fffe0ab753', payload '{"last_seen":"2024-06-02T16:50:56.209Z"}'
...
Error 2024-06-02 18:51:01Interview failed for '0xf082c0fffe0ab753 with error 'Error: Interview failed because can not get node descriptor ('0xf082c0fffe0ab753')'
Error 2024-06-02 18:51:01Failed to interview '0xf082c0fffe0ab753', device has not successfully been paired
Info 2024-06-02 18:51:01MQTT publish: topic 'Z2M/bridge/event', payload '{"data":{"friendly_name":"0xf082c0fffe0ab753","ieee_address":"0xf082c0fffe0ab753","status":"failed"},"type":"device_interview"}'
Info 2024-06-02 18:51:01MQTT publish: topic 'Z2M/bridge/log', payload '{"message":"interview_failed","meta":{"friendly_name":"0xf082c0fffe0ab753"},"type":"pairing"}'
Info 2024-06-02 18:51:01MQTT publish: topic 'Z2M/0xf082c0fffe0ab753', payload '{"last_seen":"2024-06-02T16:51:01.456Z"}'
Info 2024-06-02 18:51:01Interview for '0xf082c0fffe0ab753' started
Info 2024-06-02 18:51:01Starting interview of '0xf082c0fffe0ab753'
Info 2024-06-02 18:51:02MQTT publish: topic 'Z2M/bridge/event', payload '{"data":{"friendly_name":"0xf082c0fffe0ab753","ieee_address":"0xf082c0fffe0ab753","status":"started"},"type":"device_interview"}'
Info 2024-06-02 18:51:02MQTT publish: topic 'Z2M/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0xf082c0fffe0ab753"},"type":"pairing"}'
After clicking to DEV CONSOLE on device:
