puddly

> What's the correct object to subscribe to to get this information? I know Endpoint::handle_message is deprecated, but I don't see a clear path forward for an alternative Zigpy's packet...

This PR is still the one that will be merged at some point, it just needs to be finished. Unfortunately, I haven't had time to pick up where @konistehrad left...

Is there some simple window that we can use for filtering, like 100ms? So if we receive a frame with `zcl.seq == 123` and then 99ms later a second frame...

We added packet filtering a while ago. Does it not help with those devices? If not, could you attach a debug log?

Can you upload the diagnostics JSON for your device?

I can't actually find a single device that uses the `KeyData` data type over-the-wire for me to confirm (the device would need a `Commissioning` / 0x0015 cluster), but I think...

The zigpy-znp network formation tools are deprecated (though this is unfortunately undocumented, sorry!), use zigpy-cli instead: https://github.com/zigpy/zigpy-cli

Also, if you are just trying to perform an energy scan and use ZHA, this information will be in the diagnostic JSON for the integration under an `energy_scan` key:

I can't replicate this problem, new devices join just fine for me with a CC2652. Please include packet captures from both radios.

The problem is that you completely replace `packet_received` within your `ControllerApplication` subclass. This is where the ZDO device announce packet [is parsed](https://github.com/zigpy/zigpy/blob/4570a0a47b6f2ad56f922f8cd5861bbfdda25915/zigpy/application.py#L932C23-L932C23). Either make sure to call `super().packet_received(packet)` within your...