Sengled Element Color Plus Bulb

@mike.maxwell

Mike,

I just paired the newly released Sengled Element Plus Color Bulb to Hubitat. It paired as a 'Device' and I was able to change the driver to "Generic Zigbee RGBW Light" and it seems to be working pretty well. This is my first color bulb, so I doubt I have managed for fully test it. After pressing 'Configure' it reports its status data correctly, responds to On, Off, and Dim commands, and I can set White Color as well as Hue and Saturation without issues. If anyone knows of a standard set of tests to run, I am all ears.

Here is a screen capture from my phone during the Hubitat Pairing Process so you can add this signature to the database.

And here is the link to the new bulb.

https://www.amazon.com/dp/B073ZBYXKQ/ref=asc_df_B073ZBYXKQ5509591/?tag=hyprod-20&creative=394997&creativeASIN=B073ZBYXKQ&linkCode=df0&hvadid=241989147482&hvpos=1o2&hvnetw=g&hvrand=17728337534221083003&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9010078&hvtargid=pla-515852267037

2 Likes

Thanks, I'll get this added.
I should just write a device driver test suite...
See, now you've done it, that's too good of an idea.

4 Likes

Mike,

One thing I have noticed regarding this driver/bulb combination is that if I use the device page's setLevel command to turn on the bulb (bulb off with level set to 10, use setLevel to turn the bulb on to 90), the level attribute gets updated but not to the final value. I have to press Refresh to get the final level updated. Not sure if this is a driver or bulb firmware issue.

Here are the events which demonstrate this behavior. (bulb was set to level 10, then turned off, then setLevel called with value of 90, but level only shows 53 while bulb is truly at 90)

Pressing Refresh afterwards results in the correct level attribute data.

it looks like that bulb is ignoring the transition time that's being specified when the bulb is turned on via setLevel.

If the bulb is off when the setlevel command is executed, we tell the bulb to move to the new level, with a transition time of .1 second, we wait 200ms then request a switch report, then another 200ms and request a level report.
The bulb is ignoring the transition time specified, so when it's responding to the level request we sent, it hasn't actually moved to that level yet...
:grimacing:

1 Like

Can someone explain what I need to put in the device settings for a sengled color bulb. I have it paired with Hubitat but no color changing

Maybe a screenshot or something like that

Here you go... Also, if the bulb is not automatically detected as a 'Generic ZigBee RGBW Light', be sure to press CONFIGURE after you assign the correct Driver and hit SAVE.

It’s showing up as a generic Zigbee RGBW light but still no color. There has to be something I input in the settings but nothing I’ve tried seems to work

Have you pressed CONFIGURE on the device details page?

Yes I have. Do I need to fill anything in at all?

How are you testing? I assume directly from the device page, as shown above, correct? There’s nothing to “fill in” except the color you want. That is greatly simplified now that we have the color picker in the v2.x firmware. After picking a color, click the SET COLOR button to send it to the bulb.

I assume you can turn the bulb on, off, and dim it?

How about setting the color temperature?

And, you’re sure you’re using a Sengled Color Bulb, right? Not the standard dimmable bulb? Not their white color temperature adjustable bulb? Just thinking of all the possibilities.

Ok maybe I’m going about this all wrong. I’ve been trying to get Alexa to change the color. I’ve been able to use a color picker to change the color but the bulb is not showing up in the Alexa app as a colored bulb. Yes I’m sure it a sengled color plus bulb. With SmartThings I was able to control the colors by voice with Alexa which is what I thought I could do with Hubitat

Wow, really? LOL... ok, let’s figure out your Alexa issue...

Are you in the United States? Or Canada? Or the UK? If yes to one of these, I think you’re in luck... In order for Alexa to manipulate color bulbs, you need to use the “Amazon Echo Skill” app on Hubitat. You add this skill via the Amazon Alexa mobile phone app. If the Hubitat Skill doesn’t show up in your Alexa mobile phone app, you’re probably not in a region where it has been released yet.

If you’re using the old “Amazon Echo App” on Hubitat, you can not control color bulbs. Just on, off, and dim if I recall correctly. This older integration is still available in the firmware for users in countries that cannot use the newer Hubitat Alexa Skill.

All the sengled classic bulbs I added to Hubitat are voice control through Alexa and working perfectly but the color plus bulbs aren’t showing up in the Alexa app as color bulbs and there has to be a device handler or something for the colored ones to work. I live in Indiana and using the newest Alexa app.

Are you using the Alexa Skill? Did you enable the Hubitat Skill from within the Alexa App on your phone?

There is no special driver. If you can change the color of the bulb within the Hubitat UI, then you’re all set. But you must use the skill, enabled via the Alexa phone app.

Ok on the amazon app itself yes I have the Hubitat skill enabled. On the Hubitat apps I have amazon echo app and also the amazon echo skill. I’ve added the bulb to amazon using the amazon echo app in Hubitat and then asked Alexa to discover devices. She finds the bulbs. I can control on off and dimming

Remove the “Amazon Echo App” as that is conflicting with the skill. Then remove any of the “offline” devices from Alexa. Next, add your bulbs to the “Amazon Echo Skill” app in Hubitat. Finally, have Alexa Discover Devices.

1 Like

Omg I just figured it out. I never did anything with the amazon echo skill app in Hubitat just had used the amazon echo app in Hubitat.

LOL! I am pretty sure I figured it out!!! You’re welcome! :wink:

1 Like

Yes thank you very much. I was ready to put everything back on the SmartThings hub I was getting so frustrated. I can’t thank you enough

1 Like