Neo NAS-AB02B0 Interview Failed #12788
Comments
|
Can you provide the herdsman debug logging when trying to pair the device? First force remove it, restart z2m and then try to pair. 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. |
|
EDIT: I'm dumb, you specifically asked for the log during pairing. I'll update with the relevant parts below. Wouldn't you believe it, it's now working. I force removed it, rebooted the Pi, tried practically every combination I could think up, and yet it just... works now. Gotta love technology... But now I'm curious why that happened in the first place. Here's the (for better or worse, successful) log anyway, though I figure it won't do much good without something to compare it against: Relevant parts: One line that stood out to me was I'm not sure whether to close this issue since it fixed itself, or if it's worth keeping open to troubleshoot in case anyone else runs into the same issue. Either way, all I have to get working now is integrating Zigbee2MQTT and Mosquitto with SWAG, which is easier said than done but also outside the scope of this issue. |
|
Interviewing can fail for many reason, maybe you tried to pair the device in a different place now? Without the logs of the failed attempt it is impossible to say what went wrong.
This is expected when you repair it (since it will get a new network address) Feel free to close this. |
|
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 |
|
Sorry, forgot all about this because I've been busy! I paired it in the same place. Everything was the same except the time and date, best I can really say. Oh well, since I don't have a proper log of the failed attempt, I guess it's a moot point. Sorry to be a pain, but I appreciate your help. If I come across this problem again in the future, I'll make sure to get a proper log so the issue (if there is one and it's not some anomaly or user error) can be resolved. I'll close this since there's nothing more to be done for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
I am trying to pair a brand new Neo NAS-AB02B0 to Zigbee2MQTT. I was going to avoid posting an issue because this device has been covered a lot, but it seems my scenario is at least a little unique.
I am running Zigbee2MQTT and the Mosquitto broker both under Docker on a Raspberry Pi CM4, with an Electrolama zzh! (CC2652R) coordinator on the latest 3.x.0 coordinator firmware.
Docker images used were koenkk/zigbee2mqtt:latest and :latest-dev (same behaviour on both).
The inside of the siren says it's a model NAS-AB02B0 V3 20190910, exactly the same as shown in #7051#issuecomment-818181554 et al.
This is what the frontend shows after pairing:
Pressing the Reconfigure button simply displays an error saying that the device cannot be configured.
What did you expect to happen?
Judging by #7051 and #8331, I figured this device should be ready to go out of the box now, but instead of returning even partial information like other people (such as manufacturer name), I'm getting almost nothing of value, the interview fails, and the device therefore doesn't work.
I tried manually adding the converters as suggested in https://github.com/Koenkk/zigbee2mqtt/issues/10348#issuecomment-1001136578 but that didn't work (and yes, I added the tuya const as well).
I've looked through all the issues relating to this device and can't find anything that quite matches my exact problem, nor a working solution. I have not tried pairing with a Tuya gateway, however, as I do not own one (nor do I particularly want to buy one).
How to reproduce it (minimal and precise)
After enabling pairing via the Zigbee2MQTT frontend, connecting the siren by long-pressing the button allows it to pair, and then it proceeds to produce this behaviour every time.
This occurs whether I use battery or USB power.
Zigbee2MQTT version
1.25.2
Adapter firmware version
20220219
Adapter
Electrolama zig-a-zig-ah! (zzh!) (CC2652R)
Debug log
Please note that I've removed information from my log on unrelated devices for privacy (it also makes it a lot shorter).
None of the other devices are currently active so they shouldn't be interfering. They do, however, all work flawlessly.
z2mlog.txt
I've also followed Docker's log in real-time whilst trying different methods to get this working, but the results are always identical.
Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: