Sengled Element Zigbee bulbs turn off immediately after powering on

🛎️ Get Help
1

This is an odd one, I've seen posts about Sengled bulbs randomly turning ON, but not off. Here's what happens:

Bulbs are in sockets that have regular power switches attached to them. I've had them for quite a while, and they run without issue. In the last couple of months, when we switch on the socket the bulbs will turn off after a delay of anywhere from 1-30 seconds.

I moved a couple of bulbs from one hubitat to another, and the behavior persisted. My second hub has no real automation on it, so I don't think that was it.

I checked my associated Echo rules, and these bulbs don't appear in any of them.

No other brands are malfunctioning this way.

FInally, I removed 3 of the bulbs from the hubitat entirely and thus far the behavior has not occurred on those bulbs.

Any ideas or help would be much appreciated!

2

I can confirm this behavior.

I have a Sengled E11-G13 bulb, using the Sengled Element Classic driver, in a ceiling fixture controlled in HE 2.2.5.131 by a door contact sensor: Contact Open: bulb on; Closed bulb off.

Occasionally, with the door open, I intentionally turn off the bulb using the manual dumb wall switch. Later when turning on the switch, with the door still open, the bulb turns on, then immediately turns off. Closing then opening the door resets proper behavior.

3

Just an observation. Turning off the manual switch kills the bulb on the network, Zigbee Gone.. Turning it back on again I would imagine it see A/C and boots/configs and turn off waiting for a digital command.

4

I don't disagree with this assessment, but here's the challenge: this is a new behavior. The bulbs have been in place for well over a year, and this is something new. AFAIK, the bulbs haven't received a firmware update, or at least I haven't deliberately done that.

I'm hoping that there is some setting that I've completely missed.

Also, I have other brands of bulbs in similar configurations and none of them are exhibiting this behavior.

5

I know that the Sengled drivers were updated in 2.2.5, but they added the old ones back in the last patch. They are marked as "legacy" I believe. You could try changing to those and then hitting "configure" on the device page, or try switching to the new Advanced Zigbee driver that matches your bulbs capabilities and changing the preferences for power loss recovery (on the device page) and then hitting save and configure.

2 Likes
6

I can confirm that using the legacy sengled fixed the odd behavior on my side.

2 Likes
7

Same here. Switching to legacy is the solution.

1 Like
8

BOOM Fixed! Thanks a ton to the community, that was an awesome help!

2 Likes
9

Same problem here, same solution. Thanks!

10

Where do I find the driver to update it?

11

Just select it from the drop-down menu on the device page. Make sure to hit configure after saving with the new (old) driver.

1 Like
14

Thanks!!!

1 Like
15

Oh good. That fixed it for me as well.

In my case, I wanted the ability to adjust the bulb's intensity without replacing the switch with a dimmer.