Frient joins Works with Home Assistant

[Hedda]

@RenatoY

@MatthiasU

what’s the github bug?

Here

As I mentioned above, suggest that if you and everyone else that discover these type of problems with specific devices missing or showing the wrong entities and values would like to expidite thoubleshooting then try to assist the development of custom ZHA Device Handlers (a.k.a. zha-quirks) by also reporting what you see as a bug or support request as an issue to the upstream zha-device-handlers repository on GitHub. This usually help the small community of ZHA quirk developers. Please see:

• GitHub - zigpy/zha-device-handlers: ZHA device handlers bridge the functionality gap created when manufacturers deviate from the ZCL specification, handling deviations and exceptions by parsing custom messages to and from Zigbee devices.

That process of reporting issues to that upstream ZHA Device Handlers project repository on GitHub is actually covered in steps on the ZHA integration documentation troubleshooting section:

• https://www.home-assistant.io/integrations/zha#how-to-add-support-for-new-and-unsupported-devices

For a more detailed explaination on the underlying reading why custom ZHA Device Handlers are sometimes needed please read this community guide here:

• Zigbee Guide: How-to add/setup local custom ZHA Device Handlers (also known as ”quirks”) in the ZHA integration

@ShadowFist

EDIT: The linked thread makes it pretty clear that you might need zha_toolkit for this. Use that if the change isn’t applied using zha alone.

@ShadowFist Please note that zha-toolkit is a third-party custom component that needs to be installed though HACS so that should not ever be needed as a fix to resolve problems like this. Again, to resolve the root cause of this problem properly it should be reported by users to the upstream ZHA Device Handlers project repository on GitHub so that a zha-quirk can be developed as a proper solution.