Using the new Sengled driver (Sengled Element Color Plus) and the hubitat/google home integration will not recognize the light bulb. I have tried adding and removing other light bulbs to google home and they work as expected. While using the new Sengled driver, the HE app will let me add the bulb with a check mark. I then hit update and then done. I wait and verify the Sengled light is still there. I check google and then HE and the bulb will be removed from the list of devices in the app in HE and the check mark removed as well.
any ideas?
[edit] Under the previous driver the bulb worked fine. I haven't had time atm to check but I am going to see if using the old driver allows it to be recognized. I am guessing google don't know it is a bulb.
Hit configure in the driver, then post a screen shot of the driver current states.
The GH app will kick out devices that dont have all the attribute values populated as they should be.
Ok thanks for the direction!
When I swapped it to the new driver, I did it by removing and re-adding the Sengled bulb and let it auto-discover.
You're right the states didn't fully populate during the auto-discovery. So I changed it to a generic zigbee RBGW light, it then populated with all the right states. Then I changed it back to the Sengled driver and it worked correctly!
Thanks again!
now that i see what happened, I think if you just set a hue value, then a ct value then all of the attributes would have been populated.
The GH app identified the device as RGBW, however the hue and saturation values weren't populated (even though it was in CT mode), so it rejected it...
2 Likes
@mike.maxwell just letting you know that this is still an issue. When I refreshed my new bulbs (firmware updated to the latest) it showed:
I couldn't get it to add to Google, even after manually setting the Hue, Saturation, and Level values, hitting Configure, hitting Refresh... So I swapped to the Generic Zigbee RBGW Light driver, and hit refresh to this result: when I switched back to the built-in Sengled driver it now shows colorMode:
This might be a different issue than the previous one (I feel like I fixed it with bulbs in the past by setting the Hue value), so I wanted to let you know in case an update can be made to the driver to recognize the bulb type. I hope RGB is correct, I would have expected RGBW.
If it helps to know, the device was automatically added under the Sengled Element Plus driver and I changed it to the (proper) color driver. Maybe that was the root of the issue?
probably, I'll need the fingerprint for the bulb, and the bulb type (color, color plus, ect)
