LIFX bulbs coming on at low setting in middle of night

[drmark12pa]

I've started having some issues the last several days with LIFX lights controlled by the Chowmain driver which seems to be after a firmware update to the lights occurred.  1 or 2 of the lights in my master bedroom set of 4 will randomly turn on in the middle of the day or night to the lowest brightness.  As it has been all along, the lowest brightness setting that Control4 can set the LIFX lights to is 1% based on the LIFX app even though the setting in Control4 is set to 0%.  Is there a way to not only prevent this random turning on and also force the value set in Control4 of zero to also be zero in the LIFX app?  Has anyone else had this issue?

 

[alanchow]

The LIFX API has seperate ON and OFF commands along with level commands.  The driver will send an OFF command should it receive a 0% value.  Any other value will cause the driver to send an ON command along with a brightness level.

Note that the driver does not arbitarily send commands so please check your programming to make sure that you don't have any rogue programming causing your lights to turn on.

[drmark12pa]

36 minutes ago, alanchow said:

The LIFX API has seperate ON and OFF commands along with level commands.  The driver will send an OFF command should it receive a 0% value.  Any other value will cause the driver to send an ON command along with a brightness level.

Note that the driver does not arbitarily send commands so please check your programming to make sure that you don't have any rogue programming causing your lights to turn on.

the OFF command does not send a 0% value to LIFX and the set brightness to 0% does not set brightness to 0% both of these commands will only set the bulb to 1% at the lowest as shown in the pictures above.  Now after firmware update of the bulbs via LIFX this past weekend the bulbs will come on at the lowest 1% brightness setting.

[drmark12pa]

Here are the screenshots of the commands in Composer to turn the LIFX bulb to zero brightness...  This has always been like this but now appears to be causing the lights to not be fully turned off with recent firmware update of the bulb itself.

1) trying to use OFF command

2) trying to set the bulb to 0% brightness

3) the actual brightness  as registered by LIFX

[alanchow]

Please get your dealer to reach out to our helpdesk so that we can assist.

[drmark12pa]

This is 1 of 4 LIFX bulbs set at zero percent and OFF at 945pm.... Again since LIFX firmware update, something is awry with the Chowmain driver.

[alanchow]

Please get your dealer to reach out to our helpdesk so that we can assist.

[Andrew luecke]

G'day, just an update.

We've fixed an issue in our latest beta (which has been released to our beta testing team today) where some lights in some circumstances may not turn off 100% when ramping down (although, that issue should happen immediately, not after a few hours). It was due to a timer issue.

We haven't been able to replicate an issue however where lights turn on randomly after a few hours (and, I have reviewed the code, and am unable to find anything which could cause it from our side, so I strongly suspect it may have been rogue programming, or a buggy firmware update). It could be worthwhile giving the new build a test though once it's released  

Andy

 

[Andrew luecke]

On 4/27/2022 at 12:47 PM, drmark12pa said:

This is 1 of 4 LIFX bulbs set at zero percent and OFF at 945pm.... Again since LIFX firmware update, something is awry with the Chowmain driver.

G'day, 

Just a further update. Whilst V2 appeared to have fixed this issue, we've actually now completely rewritten our LIFX Driver, and our 3rd Generation driver with Local control via the UDP protocol is now available to installers for BETA testing (they can contact me directly for a copy). 

Work on the update actually began a long time ago (some people during beta testing of our V2 / OS 3.3 drivers may have noticed the UDP traffic). However, generally, we don't make announcements until it's ready to ship, which is why it wasn't mentioned sooner (we also didn't want people to be forced to wait after OS 3.3 for full colorwheel support).

The 3rd Gen drivers include all the benefits of V2 / V1 (including ColorWheel, which we implemented a few months ago), and also include a few more commands and improvements (with some major backend improvements, and more inbound). They also use the same licencing as our existing LIFX driver (the upgrade is free), however, installers will need to replace your master driver with the new V3 agent, and the original cloud-based V1/V2 lights with the new V3 lights (fortunately, our Auto-Setup makes it easy).

So all these problems should now be eliminated entirely in V3 (although, this particular one was fixed in V2 anyway). V3 uses a direct connection now (so we don't need to contend with the latency issues from the cloud).  

[drmark12pa]

Just an update, I've updated to the version 3 driver and now this issue has again started up again.  From what I can tell, the issue is with the Advanced Lighting Agent.  Apparently, setting the LIFX brightness to 0% in lighting agent does not set the LIFX bulb to 0% but rather 1% as shown in the LIFX app.  

Not sure if this is something that can be fixed but it's pretty damn annoying to wake up in the middle of the night with 1 of 4 light bulbs in your master bedroom coming on randomly for no reason.