I am about as newb as it gets, so please bare with me. I am trying to get some basic automations going with RL using a lutron dimmer. I have setup the smart bridge pro and seems to be ok.
I have setup "means to activate" as a time period of -60 before sunset on some exterior lights, and to turn them off at 9pm. The dimmer doesnt seem to change anything, if it is on, it will just stay on, or off etc.
I even tried using the "setup lighting periods" and nothing seems to work. Can someone point me in the right direction? Here is a screenshot of my RL instance
Look at the Scheduled Jobs at the bottom of the App Status page (you get this by clicking on the gear icon, upper right of the main app page, or left of the app in the Apps page). See if there is a schedule there for the right time. Show a screenshot perhaps of that section.
Ok, here is a screenshot of the scheduled jobs for you. Also, it now seems to be working after enabling the "force" option. Some of my light dimmers would not turn off unless I kept "Act=on" and set level to "0". By doing this the dimmer would report "off" finally. It seems if I don't use "force" on any lighting adjustments they don't respond.
Something amiss with this. setLevel(0) does cause an off, but so should off(). Try all of this from the device page for the light. You shouldn't need force unless the light is not responding to the commands sent to it. Those commands are the same in RL as in using the device page. You can also turn on Debug logging in RL and see the responses from the light as they come in.
Thank you for the help, I have attached my devices page on one of my dimmers, and it looks like the "off" setting aren't populated here. Do I need to indicate "0" for the level at which "off" is and then set a transition duration? I will run some more tests with the debug logging on and see why things don't seem to respond without the "force" option enabled also.
"off" is the switch attribute. It's either "on" or "off". Setting level to 0 means turn it off, but don't actually set the level. So this device shows that it is in fact off. If you hit On, it should turn on to 30, and if you hit Off it should turn off.
Thanks for explaining that, so far everything is working now, just have to keep it in the forced mode for some reason. I will be checking the debug logs to see what might be happening.
