When I click to activate it, it reverts to X. The switch turns on and off from Devices, but sometimes does not turn off when deactivated by Room Lighting.
Thanks,
Dan
I think it just indicates there's an issue between RL and the device. You can enable logging for the switch and logging for the RL instance and go look at the logs the next time it happens. Post them here if you're unsure of what they're telling you.
I've seen this ("X") even when the device is reporting change in status (on to off or vice-versa) in logs promptly, so not sure why RL sometimes doesn't "see" what the device is up to.
As far as I can tell, in my case things did seem to still work even when RL was showing "X" state for a device. I haven't done extensive testing, but in general use things seem OK. I was playing w/an automation yesterday that turns five lights on and off if any of the five light switches are turned on or off. RL didn't consistently show the correct state of the devices, but it seemed to be able to turn the five lights on and off correctly. Still monitoring this.
Yeah...my experience was with some Tuya bulbs. RL would send the setColor command to turn the lights on. In the case of the Tuya bulbs, setColor wouldn't actually turn them on, so RL would give me the X. I presume once RL sent the command, but didn't see the status of the bulb update to "on" then it gave the X.
Of course as soon as I say things seem OK, they aren't. RL automation worked fine last night, this AM not working. Different from this issue (status is now updating accurately in RL) so to avoid thread-hijack I'll post elsewhere...
I'm getting an X in the state column a few seconds after it reports the correct state. Like if I turn a switch on while that spread sheet is up, first I get the Red Circle, and a few moments later it turns into a Red X, even though no additional state change has occured.
I just transitioned over to the new Lighting App last night and had a few instances of lights not turning on, due to the app thinking a light was already on when it wasn't. For now the fix seems to be selecting the option to command a device even if the state is already supposedly correct (send command regardless).
FWIW the devices not correctly showing, or showing and then changing status, are inovelli dimmer/switches. I don't think the dimmer/switch is the problem, as the state correctly shows in the device page. Possibly something with the lighting app?
Possibly...but just like what I said above. Enable logging for the device and the RL instance and grab the logs from both whenever the issue happens.
I did, the log says something like, not turning light on, Already Activated, even though the light is off and the device page for the light confirms such.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
