-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Interview fails for Sonoff SNZB-03 motion sensor #13600
Comments
This problem happens a lot with my battery sensors. I often have to delete and re-pair after battery replacement and then frequently experience this behaviour of a failed interview. Let me know if there's more info needed to help diagnose |
@Koenkk - any chance we could investigate. I'm happy to try and tests to debug. I'm seeing this a lot on the Sonoff battery devices |
Does this only happen with Sonoff devices?
Can you provide the herdsman debug log when repairing this device? Also when this fails; does the following help?
|
Now, of course pairing is working. I tried a few times and it works and as I said the problem is intermittent. I will leave herdsman debug logging on and update when i next have to change a battery. For now, the only log I have of failure is the one above without the DEBUG detail
Yes, but I only have Sonoff battery devices. But I had it happen with multiple motion and temperature ones. |
OK. I found a failed interview after installing (trying to) this brand new contact sensor. I first did the usual allow join and it did see it very quickly. The interview did seem to take a long time and then showed the | triangle warning 'Interview failed' I then clicked Reconfigure and the device appears to be partially working but still showing interview failed.
|
Can you try to repair the device closer to the coordinator? Could be a temporary hickup. |
I did and it did pair. Actually I was limiting it to pairing with a specific router not the coordinator |
After much trial and error and I have found a new reliable way of re-pairing Sonoff SNZB-0x devices including making them live and accepting of reporting update changes
I found with the default of 62000s max internal and 25 hours default availability window if one broadcast is missed by the router then the device is flagged offline. With 7200s it would mean 13 broadcasts would have to have been missed. |
This doesn't seem to work very well for SNZB-03 Motion Detectors but does work reliably for SNZB-02 and SNZB-04 |
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 |
I've the same issue. But, unfortunately, I can't change the settings which you wrote about, get errors: |
Yes. But it only worked for me immediately (within a few seconds) of having pressed the device button for 5s, enabling join and then changing as soon as join pop ups started appearing. It is messy. |
Many thanks! Now it works properly |
This solution is working for me. It's been over a week and my button still works (despite now having a failed interview status). I also have a few motion detectors (SNZB-03) also staying on the network. Thanks! |
@blacknell, thanks for posting this solution. |
Can you advise which PR addresses this? Is it in this repo or the converters?
Regards
Paul
… On 2 Jan 2023, at 08:18, Koen Kanters ***@***.***> wrote:
@brindille91 <https://github.com/brindille91> should be fixed now, can you confirm?
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)
—
Reply to this email directly, view it on GitHub <#13600 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACDT75CGJU7LC6TBZJFOI7DWQKFPBANCNFSM5673DJYA>.
You are receiving this because you were mentioned.
|
@blacknell whoops, this comment was meant for a different issue. Can someone provide the herdsman debug log when trying to pair this device? See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files. |
I did add the hersdman debug log see above 27/9 |
@blacknell I've included your fix now. The 3600/7200 rep interval will now immediately be applied upon pairing. Thanks! 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) |
I think/suggest this is the same for all the Sonoff SNZB-0x family. I'm happy raise a PR for this if it helps? |
…onnected from the network (#5258) relates Koenkk/zigbee2mqtt#13600
Thanks for the pr, I assume this can be closed now. |
…onnected from the network (#5258) relates Koenkk/zigbee2mqtt#13600
Mine just dropped again after a few days without issues Friendly name is "vindue soveværelse"
|
The same for my sonoff-snzb-04. |
I hope this will get fixed and pushed soon… I have 21 sonoff devices (snzb-02 and 04), and they keep disappearing from the network again and again… The only way to get them back online is to pair again, which works for a few hours before dropping out again… |
I have the same issue with my SNZB-04 too (running latest Z2M from last week). Has anyone come up with any other potential solutions perhaps? Should this issue be-reopened? (the max 7200s / min 3600s solution, which is the default in Z2M sadly doesn't work for SNZB-04) |
don't know for the others, but for me the devices (despite the fact that interview is not-finished and tab reports is not showing anything set) ARE working, that means SNZB-04 is providing 'contact' updates and SNZB-03 is providing 'occupancy'. Apart from those, both types are also properly providing 'battery_low'. out from 10 of those, one SNZB-04 managed to finish interview, no clue what was different. maybe it is worth saying that for 1 year I was running version 1.26, there was no issue with those. this behavior started after I upgraded to 1.29 and 1.30 for EZSP adapter support (tubeszb-efr32 POE adapter). but again, I don't care to see the battery % , so (for me) definitely critical. |
I have the same problem here. Two SNZB-3 and they disconnect after one to two weeks. |
I got a cheap Zigbee lightbulb, which acts as a router at the same, and is plugged very close to my SNZB-04 to ‘expand/extend’ the network. No more drops. I guess the zigbee sensors in SNZB-04 must be quite weak and need some sort of a repeater/router nearby to ensure they stay in the network. |
I have a lot of Zigbee devices in the same room, but it still disconnects. If the SNZB-03 & SNZB-04 is as week as you describe it, I will replace them immediately. |
I have all manner of devices (not just Sonoff) dropping randomly, with both Ti coordinators and EFR ones. I asked ChatGPT to write an extension to automatically apply the max report interval for all devices as they are interviewed, you can add it in the 'extensions' tab.
|
What happened?
Periodically, I lose connectivity with devices. This has mostly occurred when the battery runs low. However, reconnecting is very problematic.
I can no longer properly pair this SNZB-03. It has a new battery and I'm admitting it via a nearby switch which is a router on the network (with good LQI).
What did you expect to happen?
I expected it to pair, interview and start working.
How to reproduce it (minimal and precise)
I first removed the device from the network
Then I selected Permit Join from Dining Room Dimmer
Then I initiated pairing on the motion sensor.
Zigbee2MQTT version
1.27.0
Adapter firmware version
20220219
Adapter
Sonoff Zigbee 3.0 USB Dongle Plus × 1
Debug log
The text was updated successfully, but these errors were encountered: