Sengled e1c_nb7 not showing monitoring

Just picked up 2 of these and HA is not showing any power entities. Connected 1 to smartthings and it showed power there. Tried rebooting HA and still the same.

I have the same ones and they work perfectly with zigbee2mqtt. Can’t comment on ZHA.

If it indeed suport power monitoring (not all do) then you probably need a ZHA Device Handler (a.k.a. a quirk) for it so post a new device request as an issue to that here repo → Issues · zigpy/zha-device-handlers · GitHub

The reason why ZHA Device Handlers (a.k.a. a quirks) are sometimes needed i explained in the ZHA docs here → https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling

Summery in relevant technical layman’s terms;

Not all Zigbee devices make device firmware for their products that strictly follow Zigbee specification standards, (with Chinese brands made by Tuya or Aqara/Xiaomi being infamous for never following it).

Anyway, deviating from Zigbee specifications standard attributes and values (as well as standard Zigbee clusters) will break practically all Zigbee solutions until they implement custom workarounds for each and every individual device that does not follow the standards of the set specifications, and manufacturers keep releasing new devices so to developers of any third-party Zigbee solutions that did not make that non-standard device it is like a never-ending game of playing catch-up in order to implement a new custom workaround for each new such device that is found in the wild.

To make things a little bit easier such workarounds for individual devices in different Zigbee solutions are implemented in the same way so much can be reused via shared device handlers that deal with conversions of non-standard quirks and deviations from the official specification standards set by the Zigbee Alliance.

Therefore each brand new device needs parsing and translation to convert the messages so are presented as virtual device representations that actually do follow the Zigbee specification standards. That is when someone needs to write a custom “quirk” (sometimes also referred to as a “converter”).

Device handlers/converters parse and translate/convert any non-standard Zigbee attribute(s) and value(s) or other deviating quirks into standard Zigbee attribute(s) and value(s) which then the ZHA integration can understand.

By the way, unlike some proprietary Zigbee solutions such as for example Tuya or Aqara/Xiaomi own Zigbee gateways the ZHA integration implementation and its zigpy dependency has been designed to follow the official Zigbee specification standard and therefore all devices that actually do follow the Zigbee specification standard should just work out-of-the-box without the need of any custom device handlers.

Samsung SmartThings also ship with Zigbee Device Handlers for the deviating devices that it supports.

Zigbee2MQTT also require Zigbee Device Handlers but they call them " zigbee-herdsman converters":

https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

https://github.com/Koenkk/zigbee-herdsman-converters/tree/master/