-
Notifications
You must be signed in to change notification settings - Fork 41
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
Unable to pair devices #231
Comments
The DeviceAnnoucement is received, but we never get handle_join() to start the provisioning process |
I can't replicate this problem, new devices join just fine for me with a CC2652. Please include packet captures from both radios. |
I remember having a similar issue over a year ago or so. Devices would only join through the coordinator. My network was migrated multiple times (lastly EZSP -> ZNP IIRC) with "scripts" back then. @pipiche38 So, was your network also migrated or did you try this on a "fresh network"? Do the devices join fine if you only allow joins through the coordinator? (If that also doesn't work for you, the issue is probably different) |
If I downgrade zigpy and zigpy-znp then pairing is good Envoyé de mon iPhoneLe 4 nov. 2023 à 18:44, TheJulianJES ***@***.***> a écrit :
I remember having a similar issue over a year ago or so. Devices would only join through the coordinator. My network was migrated multiple times (lastly EZSP -> ZNP IIRC) with "scripts" back then.
In the end, I was able to reset and re-join all devices to a new network. Everything worked fine after that.
@pipiche38 So, was your network also migrated or did you try this on a "fresh network"? Do the devices join fine if you only allow joins through the coordinator? (If that also doesn't work for you, the issue is probably different)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
This is a test SonOff dongle and I don't think that I have migrated from EZSP before.
and pairing is back to normal. |
The problem is that you completely replace |
You are right we are also calling super.packet_receive() but what I don't underunderstand is why it works with bellows and not for ZNP. Is there big differences on the way handle_join() is called ? |
I investigated more, and there is something happening in a different way under ZNP than Bellows So when the device is paired again, the Device Annoucement message via super(type(self),self).handle_join(nwk, ieee, parent_nwk)
|
Find here attached 2 logs files (archived). One is the successful pairing with Bellows , and one with ZNP which is un-sucessfull. |
@puddly may be a path. I have added some sleep() between
and it looks looks like it does impact, as I'm getting now the Device Annoucement packet Here after is the logs when successfull !
|
the same when not working
|
@puddly |
If you want to look what we have done from a code perspective Here is the ZNP part Here is the Bellows part and here is where the real logic is (and is common to ZNP, Bellows and deconz) I'm more than ready to accept that there is an issue in our integration, but when it is perfectly working with Bellows, iot works time to time (when adding sleep) with ZNP, I'm very currious to understand how I should track that and when looking at the log #231 (comment) I cannot find any thing |
Running zigpy 0.59.0 and zigpy-znp 0.11.6.
Unable to pair a device with ZNP while it works perfectly with bellows !
plugin-log.txt
The text was updated successfully, but these errors were encountered: