Just tried the changing the device to a switch:
And no change. The light remained on. Here's all that's in the logs:
Same here. If I enable this device for "Off" commands, then it turns off just fine. The issue is that I need the light to turn off with the Activate command as I have large scenes that turn on some lights and turn off others.
It looks like a possible issue. What do the device logs show? @bravenel is the one to address any issue.
Nothing for the device. That was the entire log for the Activation.
OK, let Bruce chime in.
1 Like
The device is off, and your activation is to turn it off. So nothing happened. If the device is not reporting off correctly (evidently), then there's a device issue. The Force option doesn't really have anything to do with this. Room Lights won't send an off command to a device that is currently off. If that's really what you want to do, you could use one of the rule apps to do it.
Why is the device not reporting on? What happens when you toggle the device with the little circle o the left side of the table?
Could you expand on this a bit? It seems to contradict the documentation:
This option is used when there are devices that do not reliably report their on or off state. Ordinarily, Room Lights will not Activate a light that has reported it is on, nor Turn Off a light that has reported it is off. However, when a device doesn't report reliably, this may cause problems. Selecting this option causes another column of checkboxes to become available in the Devices to Automate Table, called "Force". If the Force box is checked for a device, that device will be Activated or Turned Off irrespective of its reported state.
1 Like
This device is an old first generation Z-Wave device and doesn't report status. When I click on the little red circle, the light comes on but the current status remains off.
The only log entry is this:
I agree with @dcaton1220 that a force should force both ons and offs during an activate. That would certainly solve my issue.
I have put this in as a fix, for Force to actually force an off command.
6 Likes
Bruce, that's fantastic. Thanks everyone for your feedback and help. Love Hubitat and the community. 
1 Like
This is what i was talking about, the same issue in motion and mode lighting app...
and the bunch of nonsense that room lighting imports.
Amazing how providing requested information including logs gets questions answered and issues resolved.
6 Likes
I don’t think you ever explained what you were talking about in your recent posts regarding room lighting.
2 Likes
I provided a buch of screenshots so u just ignored them
You did indeed provide some screen shots. Yet you ignored other requests. In that interaction we did find that RL was not importing some CT values correctly from the Motion app and Bruce got the fix in the repair queue. Your original Motion app had some leftover cruft in it and you did not try my suggested RL example. Your scenario was simple. Yet the issue got dragged out and never resolved because it was more important to complain about Room Lighting than get your problems fixed. If you have an issue lay it out and follow suggestions. It will get resolved. As shown by this thread and many others.
8 Likes
I hate to be the bearer of bad news, but the problem is not resolved in 2.3.8.122, even though it's listed in the bug fix list. I am seeing the exact same (non) behavior as I've described earlier.
1 Like
Yep, you're right. Will find the right fix....
Found the problem. Sorry about that. Next release.
3 Likes
Can confirm Bruce, 2.3.8.123 has fixed the problem and all is good in my world. Thanks for the quick fix!
3 Likes
I am still having the problem in RL with my light not turning off after motion has ceased for 1 minute. I just found this message board. I have been pulling my hair out trying to get it to work. It was working for a long time and then a month or two ago it wouldn't shut off the light after motion stopped. I have the latest version 2.3.8.139 on C8.
