Greenwave Reality (TCP Connected lights) custom component fails to load after update to 0.91

Since switching to HA, I’ve been using the fix provided in

as a custom component. After updating to 0.88 and receiving the structure warnings, I modified the custom component directory structure and file naming as advised. This worked and eliminated the warnings.

After updating to 0.91, the custom component no longer loaded. The system loads the core component which results in the original errors the @dfiel code corrects.
There are no warning/errors in the log indicating the reason for failing to load the custom component.

Solution:
Modify platform name from greenwave to my_greenwave…The custom component loads correctly and previously existing light bulbs are accessible.

change directory
from
  custom_component/greenwave
to
  custom_component/my_greenwave

modify configuration.yaml to

light:
  platform: my_greenwave
  host: xxx.xxx.xxx
  version: n

My greenwave custom component broke after the .92 changes and thanks to gbealmer, this repo fixed it: https://github.com/gbealmer/my_greenwave. It includes the new init.py and manifest files required after the great migration.

Hi does this work for the powernodes connected to the greenwave hub?

If I change the light: to switch:
Could it work? I have 5x 6 port powernodes and 2 X 1 port powernodes.

I have the greenwave hub as my zwave hub as i don’t have a USB dongle zwave device at the moment.

If this also covers powernodes does it provide the power usage monitoring?

Thanks

Ezekiel

Sorry, the custom component is only for the obsolete Connected by TCP hub and bulbs. It’s based on a core component, but fixes a problem that was never properly corrected.