LEDVANCE Sylvania 74284 Strips - can't turn on to <100 in RL, any suggestions?

Posting this here because I think this may be more a device than app issue...

Odd results using RL w/one of these light strips...if I have RL set up to turn on the light strip to 100 on motion trigger, the light stip always works normally. If I set it up in RL to turn on to <100, it fails. Motion trigger may sometimes work once or more but then the stip inevitably stops turning on when motion is triggered.

Wondering if anyone using these strips has seen similar flakiness w/them.

Things look normal in logs...don't see any clues there...logs say the light turned on, but I'm standing right there when motion is triggers and the light is not on. If I toggle the light at that point (via a button I have set up to control the light strip) the light will flash on very briefly and then turn off. Toggle it again and it turns on/off normally. So it's getting into some weird state...

Logs and RL setup below: I've tried it at 40, 50, and 60 w/same results.


2023-07-17 15_11_32-Hubs, Network, & Tech

What driver? I haven’t seen this using the Advanced Zigbee RGBW Driver, but I’m not using RL, just ML and BC

1 Like

Do you have any "Enable prestaging" options enabled on the affected devices (if available)? This is a classic sign of that.

If so, you'll need to disable it (my recommendation) or find another way to create your desired automation.

1 Like

I'm using the Generic Zigbee RGBW Light driver...

Prestaging is disabled.

Thanks to both of you for your feedback. I'm going to try switching to the Advanced Zigbee RGBW driver that Ken is using, and see how that goes.

1 Like

Let us know if that fixes it. I had some odd behavior with the Generic Zigbee Driver and my Sylvania light strips and can lights. I can’t remember exactly what it was, but remember that it was fixed by using the Advanced driver. The Advanced driver also has less overhead and was noticeably more responsive than the Generic driver when I tried them back to back.

It seemed to be OK last night, but we had an odd night (home from a movie after 10:30pm) and we were pretty beat from a long day, so we just went to bed directly and I didn't consciously monitor the lights. However, I would notice if they weren't turning on and don't have any memory of them not working normally, so they likely did.

Going to go change do a quick test now and confirm that it's working normally w/the updated driver.

Okay just tested it, went in once and it turned on, waited a while and went back in and it turned on again, this is with it set to the lower level (50).

So pretty clearly a driver issue with the generic driver with these LED strips.

Thanks very much Ken, I wouldn't have thought of changing the driver on my own.

1 Like

Oh crap, just went into the area and the light did not come on. This is for the daytime setting of 100% which I wasn't having problems with.

So not fixed by driver change.

Time for more troubleshooting...

I turned the light on w/the RL activator and it didn't turn on (it thought it was already on) then turned it off w/the RL activator, and then moved in the space and it turned on w/motion...

Maybe it got into a wierd state...I'll keep testing and see how it goes. Next step I'll reset/re-join the strip.

I imagine that the message that the light was off got lost somewhere between the light and the hub. Have you had anymore zigbee reboots?

Thanks. Wasn't a ZigBee reboot, not sure what happened.

Things worked fine since then and tonight the strip came on at 50% as desired.

So looks now like I'm good! Fingers crossed, of course. :wink:

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.