I can't seem to figure out why one of my Hue bulbs keep displaying an error message in the Log. I have a dozen Hue bulbs connected through the Hue Hub, and all are working normally. Including the one with the error.
What happens right before that error? Something (either an app or you manually) looks like it's calling the "Set Level" command, so I'd be curious what values it's trying to pass. Also, based on the driver name, are you sure this isn't a Hue White Ambiance (color temperature) bulb? The White (white-only) bulb would use a different driver, but I don't think that would cause a problem for this particular command.
Yes correct the bulb is Hue White Ambiance bulb. I've checked the Logs and can't seem to figure what could be trigger the bulb. I have Motion Lighting turn on the rear hallway light on only in Night mode. But I get this error even when not in Night mode.
Hmm. Anything else under "In use by" on the device page that might be sending this command?
I have it mapped to a Pico, and in a Dashboard. I also have it in a simple lighting automation to turn off in AWAY mode. Motion Lighting is the automation I have setup to dim the bulb.
Weird, something looks like it should be sending a "Set Level" right before this happens. I don't suppose Motion Lighting, if you think it's "triggering" this, has an invalid value for level or (if it even lets you specify this) transition time? And does the command work from the device page both with and without the second (transition time) parameter specified?
Motion Lighting is set to turn on and set to 20% in NIGHT mode. Device dims correctly from the device page and triggers properly with motion lighting. The error seems to randomly show up. I've kept the log open and triggered Motion Lighting in NIGHT mode to see if the error would pop up. Everything works as it should with and without the second parameter. Yet the error message will randomly show up.
Odd. Honestly, I'm out of ideas. 
If it were me, I might consider either re-creating all apps/rules that use this device and, if that fails, removing the device (after first removing it or swapping it out with something else in all apps it's in use by) and re-adding it via Hubitat's Hue Bridge integration, then again reconfiguring any app that uses it. (And if Hubitat's Hue Bridge integration works how I suspect it does, you can probably edit the DNI to swap out the number at the end with some nonsense like "xxOLD" temporarily, then remove the device when you're done with all this instead of right away and keep it in the apps/rules it's in in the meantime just for reference.)
But if everything is working how you think it should be, that might be more effort than it's worth. I'm not sure what could be causing this other than some app/automation that sending unexpected data to this device's "Set Level" command, which either or both of the above might help with.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
