Sonoff SNZB-01

[hijamie32]

What happened?

All my Sonoff SNZB-01 fail to send any data after pairing.

I have confirmed with the supplier of the Smartlight zigbee lan CC2652P they also are having the same issue.

Pairs fine and recognises it as the correct switch but then get this error during configuration:

Failed to configure '0x00124b002135b2c0', attempt 1 (Error: Bind 0x00124b002135b2c0/1 genOnOff from '0x00124b0014dbbe5d/0' failed (AREQ - ZDO - bindRsp after 10000ms) at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (internal/timers.js:557:17) at processTimers (internal/timers.js:500:7))

Many Thanks

What did you expect to happen?

To pair and work correctly.

How to reproduce it (minimal and precise)

Remove and try to repair with new CC2652P coordinator.

Zigbee2MQTT version

1.22.2

Adapter firmware version

20210319

Adapter

Smartlight zigbee lan CC2652P

Debug log

No response

[Bumblebeee19]

Hello,

I had a similar problem with the SNZB-02. I found the solution on a forum (but I can't remember which one), after pairing, you have to press the reconfigure button on Z2M

while pressing the SNZB button very regularly (1x per second).

This operation must be repeated until there are no more error messages.

Hope this works for you.

[hijamie32]

Hey,

Thanks for your suggestion, sadly just tried this with all three and still no response.

Strange pairs straight away but then is like it instantly drops from the network again......

Cheers

[s4ntz]

@hijamie32

OMG! you fixed my problems!!!
thank you! so obvious.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[enigmaspb]

Same problem - reconfigure and fast click no helped

[heisenberg2980]

@Koenkk it looks like some update has broken the integration with these 3 Sonoff devices and they cannot be paired anymore: SNZB-01, SNZB-02 and SNZB-03. According to #9216 the issue started in October 2021 with version 1.21.2 (version 1.20.0 seems to be working fine, but I haven´t tested it), can you help with this?

I can confirm the issue is happening with my SNZB-02. I haven´t been able to pair it no matter how many times I have tried while pressing the button in the device every second. I also try to hit reconfigure (as mentioned above) with no success.

I have sniffed the zigbee traffic with the device while pairing:

After the pairing process fails the device is doing data request during a minute, and after that it doesn´t send any more data even if the device button is pressed.

[Koenkk]

@heisenberg2980 could you provide a sniff when pairing it to z2m 1.20.0 and 1.24.0, provide the pcapng files here.

[heisenberg2980]

@heisenberg2980 could you provide a sniff when pairing it to z2m 1.20.0 and 1.24.0, provide the pcapng files here.

Sure, is there a way to downgrade z2m to an earlier version in Home Assistant OS? I have done that with integrations by downloading the repo to the custom folder, not sure if something similar can be done with addons.

[Koenkk]

@heisenberg2980 not sure if that is possible (not really familiar with HA addons tbh). Maybe you can setup another setup on a pi with just the coordinator + sonoff snzb-01 in the network.

[heisenberg2980]

@Koenkk I setup mosquitto and z2m on another pi running Debian version 11 (bullseye), and the first time I tried to pair the device using the latest version of z2m (1.24.0) it actually paired successfully (which was unexpected tbh, but it was good to get the sniff because I hadn´t figured out yet how to run a previous version of z2m). After that I tried to pair it again and it failed every time I tried.

I am not sure why it worked the first time (maybe for some reason the fresh installed made the pairing to succeed), but I got the sniff of both executions:
Sniffer in Rpi 4.zip

This is a screenshot of the log when the pairing fails:

[heisenberg2980]

I just figured out how to run previous versions of z2m, this is the sniff of a successful pair using z2m 1.20.0:

SNZB-02 paired successful - z2m_1.20.0.pcapng.zip

This is the log:

With this version 1.20.0 the pairing is successful every single time I try.

[Koenkk]

@heisenberg2980 interesting, could you check wether the device always pairs successfully with z2m 1.24.0 when:

• force remove the sonoff device via the frontend
• restart zigbee2mqtt
• start zigbee2mqtt, pair the device

If it does not pair successfully, could you provide the sniff again + herdsman debug log of this? Note that the restart is crucial here, between z2m 1.20.0 and 1.24.0 there were some changes to the interviewing process. When a device did already join before, z2m will not fully interview it anymore which may explain the issues.

[heisenberg2980]

@Koenkk you are right!! Following those steps (force-remove device, restart z2m, pair) the device pair successfully on z2m 1.24.0 every time (I have tested it twice), so that must be the issue.

I guess this half-interview if the device has already been paired was implemented to improve performance in the pairing process, but if it is making some devices to fail the interview (not sure if it is happening just with these sonoff or with other devices as well), maybe it is better to do the full interview? or is it something that can be enable/disable depending on the device in the z2m code? if so, clearly the interview should be full for these 3 sonoff devices

[Koenkk]

@heisenberg2980 thanks for confirming. Think I've found the issue, could you check wether it is fixed in the latest dev?

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

[heisenberg2980]

Great job @Koenkk, I can confirm the issue is fixed in the dev branch.

@hijamie32 please test it using the dev branch (alternatively you can wait until the changes are applied to the main branch) and if it works you can close this issue.

[snowyu]

I've tried the dev branch ad24c4f. But

1. SNZB-01 can not unbind the default one: Failed to unbind cluster 'genOnOff' from '0xXXXXXX' to 'Coordinator' (Error: Unbind 0xXXXXX/1 genOnOff from '0xXXXXXX/1' failed (AREQ - ZDO - unbindRsp after 10000ms))
2. SNZB-01 can not bind new one: Failed to unbind cluster 'genOnOff' from '0xXXXXXX' to 'Coordinator' (Error: Unbind 0xXXXXX/1 genOnOff from '0xXXXXXX/1' failed (AREQ - ZDO - unbindRsp after 10000ms))

[heisenberg2980]

@snowyu have you tried removing the device using "force remove" and then pair it again?

[snowyu]

Yes, I've tried "force remove". Still same error.

[heisenberg2980]

I've tried the dev branch ad24c4f. But

1. SNZB-01 can not unbind the default one: Failed to unbind cluster 'genOnOff' from '0xXXXXXX' to 'Coordinator' (Error: Unbind 0xXXXXX/1 genOnOff from '0xXXXXXX/1' failed (AREQ - ZDO - unbindRsp after 10000ms))
2. SNZB-01 can not bind new one: Failed to unbind cluster 'genOnOff' from '0xXXXXXX' to 'Coordinator' (Error: Unbind 0xXXXXX/1 genOnOff from '0xXXXXXX/1' failed (AREQ - ZDO - unbindRsp after 10000ms))

Both error messages say "Failed to unbind", can you try again ensuring the device has been removed from z2m and then try to pair it again? If you still get an error please share the error message.

[snowyu]

Sorry, maybe my typo. Anyway, I've cleaned all devices. and try again:

First, pair The SNZB-01 button OK, then unbind the default:

Failed to unbind cluster 'genOnOff' from '0xXXXXX' to 'Coordinator' (Error: Unbind 0xXXXXX/1 genOnOff from '0xXXXX/242' failed (AREQ - ZDO - unbindRsp after 10000ms))

Then add another switch to test bind:

Failed to bind cluster 'genOnOff' from '0xXXXXXX' to '0xXXXXX' (Error: Bind 0xXXXXXX/1 genOnOff from '0xXXXXXX/1' failed (AREQ - ZDO - bindRsp after 10000ms))

[cat2devnull]

This error has been an issue for me with multiple Sonoff devices but I just upgraded to Zigbee2MQTT
1.25.0 commit: 6f1460e and also upgraded my Sonoff USB Zigbee 3.0 Coordinator to zStack3x0 revision 20220219 and for the first time ever, every device is connected and working.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[snowyu]

Did someone try to bind or unbind it working fine?

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[avviano]

It does not really matter if you use Zigbee2MQTT or ZHA integration, I tried both with IKEA and SonOFF buttons, they work a few days, if you are lucky a few weeks. Then one or two buttons stop working. Since this keeps recurring, I simply gave up on the button and only use NFC tags. It's the only thing I was able to get to works realiably so far. All my WLAN devices work great. Zigbee is terrible. The worst of all my devices, as they are totally unreliable. At least in my experience. I didn't count, but I must have reconfigured all my Zigbee devices a gazillion times. They work a week or two, then just stop working.

BTW, if you put NFC tags on all your buttons, you have a nice fallback.

[rafaelreis-r]

Hey @Koenkk this is still going on with the latest version of Z2M. I had a button work for years and lately it went kaplooft after updating HA and Z2M.

Let me know if you need any pcap sniffs, I have all the stuff I used to try and get the A100 working at #13087

[vaderag]

This issue is still going in 2024... Having the same problem with the switch. Was connected, but needed to reconnect and after removal it's not connecting again with issues above

[Bmiest]

Had this issue, reconnected after force remove, seems to work for the time being.