Sengled Lights Behaving Erratically

[matthew.wynhoff]

I've had a bunch of Sengled Color bulbs hooked up to hubitat for several years now, with essentially no issues. I typically switch them to be themed by holiday, white in between. Recently, I switched half of them (in a group called "Front Porch") to be orange for Halloween. Then, the fun started. There have been 3 issues.

1. When I first made the change, 2 of the bulbs decided that they wouldn't come on with the schedule anymore. They are set to turn on a few minutes after sunset and go off a few minutes after sunrise.
2. Now, I'm trying to change them back to white, and am unable to do so. Using the "Set Color Temperature" option changes them to a light blue-ish color.
3. I changed them to a different color (doesn't matter what), then turned off the switch and turned it back on. Now, they all reset to Orange again.

This is NOT impacting the other Sengled bulbs that were not switched for Halloween. Those are also in a group on the back porch, and I can reliably turn them on/off, change color (and have it persist through a power cycle) and turn them white. All of my bulbs are currently using the Sengled Element Color Plus (legacy) driver, but I've also tried the non-legacy version and generic Zigbee RGBW drivers. No difference.

Any thoughts?

Here are some logs from the last power cycle. I turned this bulb to Yellow, flipped off the power and back on, and you can see it get reset to Orange.

dev:672022-11-10 08:10:17.359 PMinfoSengled Porch 3A color was set to Orange
dev:672022-11-10 08:10:17.355 PMinfoSengled Porch 3A hue was set to 7%
dev:672022-11-10 08:10:17.348 PMdebugdescMap:[raw:D4900103001000002012010020FE, dni:D490, endpoint:01, cluster:0300, size:10, attrId:0000, encoding:20, command:0A, value:12, clusterInt:768, attrInt:0, additionalAttrs:[[value:FE, encoding:20, attrId:0001, consumedBytes:4, attrInt:1]]]
dev:672022-11-10 08:10:17.325 PMdebugdescMap:[raw:D49001000808000020FE, dni:D490, endpoint:01, cluster:0008, size:08, attrId:0000, encoding:20, command:0A, value:FE, clusterInt:8, attrInt:0]
dev:672022-11-10 08:10:14.127 PMinfoSengled Porch 3A is on
dev:672022-11-10 08:10:14.115 PMdebugdescMap:[raw:D4900100060800001001, dni:D490, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]
dev:672022-11-10 08:10:12.746 PMinfoSengled Porch 3A is on
dev:672022-11-10 08:10:12.744 PMdebugdescMap:[raw:D4900100060800001001, dni:D490, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]
dev:672022-11-10 08:10:12.726 PMdebugdescMap:[raw:catchall: 0000 0006 00 00 0040 00 D490 00 00 0000 00 00 01FDFF040101190000, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:D490, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[01, FD, FF, 04, 01, 01, 19, 00, 00]]
dev:672022-11-10 08:09:56.411 PMdebugdescMap:[raw:D4900103000808003000, dni:D490, endpoint:01, cluster:0300, size:08, attrId:0008, encoding:30, command:0A, value:00, clusterInt:768, attrInt:8]
dev:672022-11-10 08:09:56.384 PMdebugdescMap:[raw:catchall: 0104 0300 01 01 0040 00 D490 00 00 0000 0B 01 0000, profileId:0104, clusterId:0300, clusterInt:768, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:D490, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:672022-11-10 08:09:56.297 PMdebugsetHue(13)
dev:672022-11-10 08:09:56.225 PMinfoSengled Porch 3A color was set to Yellow
dev:672022-11-10 08:09:56.221 PMinfoSengled Porch 3A hue was set to 13%

[matthew.wynhoff]

Figured this out through some trial and error. Documenting for posterity.

The problem was that I had these bulbs connected in a 3 way circuit that included a zen27 dimmer switch (I know, I know, that doesn't really make sense, but it was what I had available).

Someone must have dimmed the switch down to something very low, and it was causing the erratic behavior. Double tapping to restore full power immediately solved the issue.

Now, I've "solved" the problem by setting the minimum brightness on the switch to 99%.

[danabw]

Glad you had a happy ending. If you can just get your family to stop using the lights I bet they'll be perfect.

[rlithgow1]

I hope you also have the smart bulb setting on the switch itself set! Glad things fixed themselves...

[matthew.wynhoff]

@rlithgow1 - I doubt I do, I’m not sure what you mean. Can you clarify for me please?

[Hatallica]

For Zen27, see parameter 15 in the Advanced Settings. Depending on what driver you are using, this may be exposed in the device settings.

Zooz 700 series switches are still on sale if you want to eliminate the dimmer issue all together.

[rlithgow1]

Yes, it keeps constant power need to smart bulbs (so your mesh isn't impacted) eventually making the switch itself a button controller. This is necessary with smart bulbs controlled by switches.

[matthew.wynhoff]

Does this imply that in a 3way switch situation, you'd want to have both switches converted to smart switches? Or alternatively, never use the dumb switch in the configuration?

If you set parameter 15 as noted by Hatallica then the dumb switch would essentially do nothing, right?

[rlithgow1]

Correct. Have smart switches in both locations set with smart light option. The nice thing about this is that even if someone sets the dimmer down low (which shouldn't make it act erratically now), any rule you have set will overide that manual dimming. Also again, having them powered properly stabilizes the mesh because they will always be present on the mesh. From a end user point of view the switch is just a switch....