puddly
puddly
The network restore overwrites all of those NVRAM entries but you can do a full erase and then a restore if you want, it shouldn't hurt. Before you do that,...
> I saw the key but my understanding was it is a key that is valid only for the one - unknown - device. Was that incorrect? Every APS link...
That's good to hear! Maybe the corrupted NVRAM entries are negatively affecting Z-Stack somehow, as I do recall seeing the coordinator broadcasting the `0xFFFE` devices in Wireshark in a "parent...
Hmm. Is this only when the ZDO request is being sent to the coordinator itself?
Does this happen for every end device? I glanced over the relevant pieces of Z-Stack and no immediate location jumped out at me for where the order of these fields...
I believe I just ran into this issue. I formed a test network with three devices on a freshly-erased zzh! stick running the latest build of Z-Stack. The following devices...
If I can find a way recreate it again, I will try with devices with less similar IEEE addresses (and hopefully capture the packet responsible for this). Unfortunately it did...
Zigpy doesn't control any part of the key exchange, this is all handled by the firmware.
Can you post a complete Python debug log of the device communicating with the coordinator? zigpy-znp should be receiving the ZDO node descriptor request callback.
> Is there an zigpy-znp API There's no autogenerated documentation but just about everything is completely documented in the source and the API is pretty stable at this point. zigpy-znp...