zigbee2mqtt
zigbee2mqtt copied to clipboard
Koenkk
Bosch twinguard Pairing fails
What happened?
Hi, My new Bosch Twinguard just arrived. I‘ve tried many attempts but everytime the pairing fails.
Can anybody help me please ?
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.33.1
Adapter firmware version
6.10.3.0 build 297
Adapter
Sonoff Dongle E EZSP v8
Debug log
No response
You'll need to add the install code from the back of the device into Zigbee2MQTT before it will pair
Z2MGUI->Settings->Tools->Add Install Code
You'll need to add the install code from the back of the device into Zigbee2MQTT before it will pair
Z2MGUI->Settings->Tools->Add Install Code
I‘ve done this already. The .log says „successfully added Install code“ but no pairing success. Weeks ago I added a BSD-2 Bosch Smoke Alarm and I know the Install code procedure.
Same here, added a BSD-2 with install code just fine. But the TwinGuard fails at interviewing. Tried everything, no shot.
Same here, added a BSD-2 with install code just fine. But the TwinGuard fails at interviewing. Tried everything, no shot.
Which Coordinator do you use ? I‘ve tried with Sonoff dongle E and now I‘m switched over to Sonoff dongle P. I will start to try with the dongle P hoping with success.
Same here, added a BSD-2 with install code just fine. But the TwinGuard fails at interviewing. Tried everything, no shot.
Which Coordinator do you use ? I‘ve tried with Sonoff dongle E and now I‘m switched over to Sonoff dongle P. I will start to try with the dongle P hoping with success.
Also Dongle-E flashed with MultiPan. Dongle-P ist now ordered, will try it tomorrow night with the P.
Same here, added a BSD-2 with install code just fine. But the TwinGuard fails at interviewing. Tried everything, no shot.
Which Coordinator do you use ? I‘ve tried with Sonoff dongle E and now I‘m switched over to Sonoff dongle P. I will start to try with the dongle P hoping with success.
Also Dongle-E flashed with MultiPan. Dongle-P ist now ordered, will try it tomorrow night with the P.
Did you have success ? My new Twinguard will arrive next days. Will try it too.
Same here, added a BSD-2 with install code just fine. But the TwinGuard fails at interviewing. Tried everything, no shot.
Which Coordinator do you use ? I‘ve tried with Sonoff dongle E and now I‘m switched over to Sonoff dongle P. I will start to try with the dongle P hoping with success.
Also Dongle-E flashed with MultiPan. Dongle-P ist now ordered, will try it tomorrow night with the P.
Did you have success ? My new Twinguard will arrive next days. Will try it too.
Sadly my order is delayed, i don’t know when it will arrive. Will update here when i’ve tried it.
Successfully paired the Twinguard with the Dongle-P via install code.
Same as mine. 👍
I‘ve got no measurement values until now like battery, temperature, humidity … I think it will take some time ? How long did you have to wait ? Smoke alarm, self test, burglar alarm and pre alarm are working well from the beginning of pairing.
I've successfully paired the Twinguard. Smoke alarm, self test, burglar alarm and pre alarm are working well from the beginning of pairing (with a small delay 4-5 sec) but not values like battery, temperature, humidity,... After switching z2m off and on the measurements are available exept the battery value. What's going wrong ?
Hi there,
sams here. I'm using the SkyConnect Dongle and paring (with using the install-code) fails. Tried it several times and with and without push the button to keep the device awake. :(
Hi, Similar here, I'm also using the Skyconnect and pairing fails all the time. Is it an issue of the adapter? Is there anyone who sucessfully connected with the Skyconnect to the twinguard?
Hi there,
I am experiencing the same with an Smlight SLZB-06M PoE Coordinator. Install code starts interview but pairs an unsupported device...
Any ideas on how to get that interviewing?
Thanks
I bought a Sonoff P stick, as it was stated above that it works. After I found out that I need to change the adapter to zstack in the z2m configuration, the twinguard was connected.
Hi Christian, is the battery status connected too ? Mine isn't
Christian81IN @.***> schrieb am Fr., 26. Jan. 2024, 08:13:
I bought a Sonoff P stick, as it was stated above that it works. After I found out that I need to change the adapter zu zstack in the z2m configuration, the twinguard was connected.
— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/20169#issuecomment-1911591586, or unsubscribe https://github.com/notifications/unsubscribe-auth/APJM4IU6DW4UHUMH6YNSEALYQNJSXAVCNFSM6AAAAABAQM6UXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJRGU4TCNJYGY . You are receiving this because you authored the thread.Message ID: @.***>
Yes, it is connected. All values can be seen. Just the CO2 took some while until it was not null anymore.
"battery": 100, "co2": 540, "heartbeat": "ON", "humidity": 46.7, "illuminance_lux": 63, "linkquality": 72, "pre_alarm": "ON", "self_test": false, "siren_state": "clear", "smoke": false, "temperature": 23.9
Thanks Christian, I think the zstack could do the trick, problem is that my device has the EFR32MG21 chip (sames as skyconnect) and I only found the zstack firmware for the CC2652P chip. I guess that is the same issue skyconnect folks are having, did some research but did not manage to go much further than that.
From Chatgpt: If the controller and device are based on different Zigbee protocol stacks or support different versions/profiles of the Zigbee standard, they may not be able to properly negotiate these parameters during the pairing process. This can result in failed pairing attempts or incomplete pairing, where the device is recognized but cannot fully integrate into the network or communicate effectively with the controller.
Can it be that this is a Hardware incompatibility problem?
The EFR32MG21 chip devices still under experimental devices in z2m, I hope it is a question of time since the EFR32MG21 chip seems to be the way to go as it is more powerful than the cc2652p. I have over 100 zigbee devices of all kinds the twinguard is the only one bothering so far
I have the same issue, I had a conbeeII adapter but I now bought a SLZB-06M and I have exactly the same issue :( Anybody that managed to solve this?
Exactly the same problem with the SLZB-06M. Pairing does not work. It would be great if there was a solution for this.
I have the same problem. I add the installation code, can pair my Twinguard, but I get the message that the device is not supported/interview failed. I also use the Skyconnect.
Failed to interview '0x000d6f0018b5a968', device has not successfully been paired.
I've successfully paired the Twinguard. Smoke alarm, self test, burglar alarm and pre alarm are working well from the beginning of pairing (with a small delay 4-5 sec) but not values like battery, temperature, humidity,... After switching z2m off and on the measurements are available exept the battery value. What's going wrong ?
I have the same issue, but restarting Z2M does not help, it successfully paired, lighting up green aswell and the LQI seems to update regularly, but no other values are populating. I have set the adapter to zstack aswell. I am using the Zigstar UZG-01 with a CC2652P7.
I can also activate the alarm sounds and initiate the self test, but all measurement values show null, except the siren state, which changes when i activate a diffrent alarm sound.
@Christian81IN Could we get a debug log (of you pairing the device to z2m) from your zstack since it appears you were able to make this device work there?
Sure, can you point me to a manual how to create the debug log? Or is it just the normal log of z2m addon?
If you are on 1.37.0 it's all in one place yes. Just switch log level to debug. See docs. The log file is in your installation/config folder (depends on your setup).
Edit/Updated: I have now paired the rest of my Twinguards, they all reported values within ~10-15 minutes this time and even reported battery. I have also re- paired the first twinguard and same for this one. Within 10-15 minutes it reported values and also reports battery now, which it did not do before. When i first tried pairing it, i did setup my zigbee network from scratch with the Zigstar only a day earlier, so either its the update from 1.37.0 to 1.37.1 that made a diffrence or it was taking so long due to the fresh zigbee network maybe still setteling? Either way, worked fine for me now.
I have let it paired since my last post and because of the activity here today i checked back if anything changed. And now it seems to report almost all the values, i am unsure if they updated regularly yet. It definetly took more then 24h to show values since i checked a day after pairing and there was nothing. Only Battery seems to have not reported yet and the Siren state did not reset from what i last set, so that doesnt seem to update aswell. As you can see below it took a few days until it started reporting. very weird, in the bosch app/bridge it took about 30min-2h until it reported values.
Not sure if this is important, but i think that was not there the first time i paired it, or atleast there were less entries i think.
But this is definetly interessting, it took about 5 days until it started to report, good thing i can look at the history graph.
@Nerivec i also have the problem with skyconnect/yellow (ezsp driver) that the pairing worked but no values were reported. I saw multiple post that the issue only occurs with silicon labs chips. Thats also for ZHA... Till now i didn't test this with ember. I will test this the next days.
I have just tried something else. I flashed the firmware 7.4.2.0 to the Skyconnect and used "ember" as the adapter. Unfortunately, I was unable to connect the Twinguard despite this.
Info 2024-05-08 16:35:00Interview for '0x000d6f0018b5a968' started
Info 2024-05-08 16:35:00Starting interview of '0x000d6f0018b5a968'
Warning 2024-05-08 16:35:02Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
Error 2024-05-08 16:35:29Interview failed for '0x000d6f0018b5a968 with error 'Error: Interview failed because can not get node descriptor ('0x000d6f0018b5a968')'
Error 2024-05-08 16:35:29Failed to interview '0x000d6f0018b5a968', device has not successfully been paired
Info 2024-05-08 16:35:37Interview for '0x000d6f0018b5a968' started
Info 2024-05-08 16:35:37Starting interview of '0x000d6f0018b5a968'
Warning 2024-05-08 16:35:47Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
Error 2024-05-08 16:36:06Interview failed for '0x000d6f0018b5a968 with error 'Error: Interview failed because can not get node descriptor ('0x000d6f0018b5a968')'
Error 2024-05-08 16:36:06Failed to interview '0x000d6f0018b5a968', device has not successfully been paired
Info 2024-05-08 16:36:22Interview for '0x000d6f0018b5a968' started
Info 2024-05-08 16:36:22Starting interview of '0x000d6f0018b5a968'
Warning 2024-05-08 16:36:32Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "61221".
Warning 2024-05-08 16:36:46Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
Error 2024-05-08 16:36:51Interview failed for '0x000d6f0018b5a968 with error 'Error: Interview failed because can not get node descriptor ('0x000d6f0018b5a968')'
Error 2024-05-08 16:36:51Failed to interview '0x000d6f0018b5a968', device has not successfully been paired
Info 2024-05-08 16:36:53Interview for '0x000d6f0018b5a968' started
Info 2024-05-08 16:36:53Starting interview of '0x000d6f0018b5a968'
Warning 2024-05-08 16:36:55Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
Error 2024-05-08 16:37:22Interview failed for '0x000d6f0018b5a968 with error 'Error: Interview failed because can not get node descriptor ('0x000d6f0018b5a968')'
Error 2024-05-08 16:37:22Failed to interview '0x000d6f0018b5a968', device has not successfully been paired
Info 2024-05-08 16:38:12[STACK STATUS] Network closed.
[2024-05-08 16:31:30] info: z2m: Connected to MQTT server
[2024-05-08 16:31:30] info: z2m: Started frontend on port 8099
[2024-05-08 16:31:31] info: z2m: Zigbee2MQTT started!
[2024-05-08 16:33:58] info: z2m: Successfully added new install code
[2024-05-08 16:33:58] info: z2m: Zigbee: allowing new devices to join.
[2024-05-08 16:33:58] info: zh:ember: [STACK STATUS] Network opened.
[2024-05-08 16:34:20] info: zh:controller: Interview for '0x000d6f0018b5a968' started
[2024-05-08 16:34:20] info: z2m: Device '0x000d6f0018b5a968' joined
[2024-05-08 16:34:20] info: z2m: Starting interview of '0x000d6f0018b5a968'
[2024-05-08 16:34:30] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:31] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:33] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:34] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:36] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:38] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:39] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:41] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:42] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:44] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:46] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:47] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:34:49] error: zh:controller: Interview failed for '0x000d6f0018b5a968 with error 'Error: Interview failed because can not get node descriptor ('0x000d6f0018b5a968')'
[2024-05-08 16:34:49] error: z2m: Failed to interview '0x000d6f0018b5a968', device has not successfully been paired
[2024-05-08 16:35:00] info: zh:controller: Interview for '0x000d6f0018b5a968' started
[2024-05-08 16:35:00] info: z2m: Starting interview of '0x000d6f0018b5a968'
[2024-05-08 16:35:02] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:04] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:05] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:08] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:10] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:12] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:13] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:15] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:16] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:18] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:20] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:21] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:23] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:25] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:26] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:28] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "46375".
[2024-05-08 16:35:29] error: zh:controller: Interview failed for '0x000d6f0018b5a968 with error 'Error: Interview failed because can not get node descriptor ('0x000d6f0018b5a968')'
[2024-05-08 16:35:29] error: z2m: Failed to interview '0x000d6f0018b5a968', device has not successfully been paired
[2024-05-08 16:35:37] info: zh:controller: Interview for '0x000d6f0018b5a968' started
[2024-05-08 16:35:37] info: z2m: Starting interview of '0x000d6f0018b5a968'
[2024-05-08 16:35:47] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:35:48] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:35:50] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:35:52] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:35:53] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:35:55] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:35:56] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:35:58] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:36:00] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:36:01] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:36:03] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:36:04] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "55506".
[2024-05-08 16:36:06] error: zh:controller: Interview failed for '0x000d6f0018b5a968 with error 'Error: Interview failed because can not get node descriptor ('0x000d6f0018b5a968')'
[2024-05-08 16:36:06] error: z2m: Failed to interview '0x000d6f0018b5a968', device has not successfully been paired
[2024-05-08 16:36:22] info: zh:controller: Interview for '0x000d6f0018b5a968' started
[2024-05-08 16:36:22] info: z2m: Starting interview of '0x000d6f0018b5a968'
[2024-05-08 16:36:32] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "61221".
[2024-05-08 16:36:33] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "61221".
[2024-05-08 16:36:35] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "61221".
[2024-05-08 16:36:46] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:36:49] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:36:51] error: zh:controller: Interview failed for '0x000d6f0018b5a968 with error 'Error: Interview failed because can not get node descriptor ('0x000d6f0018b5a968')'
[2024-05-08 16:36:51] error: z2m: Failed to interview '0x000d6f0018b5a968', device has not successfully been paired
[2024-05-08 16:36:53] info: zh:controller: Interview for '0x000d6f0018b5a968' started
[2024-05-08 16:36:53] info: z2m: Starting interview of '0x000d6f0018b5a968'
[2024-05-08 16:36:55] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:36:57] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:36:59] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:00] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:02] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:03] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:05] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:07] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:08] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:10] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:11] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:13] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:15] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:16] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:18] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:19] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:21] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "43663".
[2024-05-08 16:37:22] error: zh:controller: Interview failed for '0x000d6f0018b5a968 with error 'Error: Interview failed because can not get node descriptor ('0x000d6f0018b5a968')'
[2024-05-08 16:37:22] error: z2m: Failed to interview '0x000d6f0018b5a968', device has not successfully been paired
[2024-05-08 16:38:12] info: zh:ember: [STACK STATUS] Network closed.
I tested it with zigbee2mqtt edge.
I use the Twinguard 8750001215. Do the others also use this model or the model 8750001213?