puddly

Let's keep this discussion on topic. If you'd like to help out, take a look at the quirk for the previous generation device and see if you can get started...

@DeppressedCabbage remove all of that config, you only need `custom_quirks_path`

Are you joining the device with its install code (should be a QR code somewhere on the device/box)? https://www.home-assistant.io/integrations/zha/#action-zhapermit

I think this is basically the only device that refuses to join without the QR code. When it joined before, was ZHA able to read any information about it? Or...

There's no need to open a second pull request (https://github.com/zigpy/zha-device-handlers/pull/4262), you can just update the original one until it's in a good state. We squash the changes at the end....

@mattcee233 Please open a separate issue and attach the ZHA integration diagnostics in addition to a debug log of ZHA starting up (you can enable debug logging, reload the integration,...

Please fill out the issue template, you seem to have deleted it, and attach diagnostics information for the device please.

Can you attach the diagnostics JSON for each device?

> If I try to configure, it does not propose the multiprotocol anymore, only zigbee or Threads. Multiprotocol was frozen [last year](https://www.home-assistant.io/blog/2024/01/25/matter-livestream-blog/#using-home-assistant-yellow-or-home-assistant-skyconnect) and will be formally deprecated in an upcoming...

There should be no changes to how multiprotocol functions and it should still keep working as before. If it isn't, that is a bug. Does ZHA no longer function for...