To keep it more interesting, the rule 2 will only work between the times described in rule 1.
If rule 1 is paused / deleted, the motion rule also stops working.
What point am I missing? I am sure it's simple, but I am struggling to figure it out somehow
PS.
Clicking the light "accent light switch" on the dashboard turns the light on and off as expected:
I've tried some dimmer switch drivers, but got various results ( slow switching on / off ) or even not working at all.
When looking on the forum I came across people recommending to use the bulb hence the choice.
Have you tried putting two times a couple of minutes apart, to run soon, just in case there is something it doesn't like about on and off times going over midnight... And making sure the bulbs are really off before they try to turn on, (just thinking of that thing where a fresh event isn't triggered unless there is an actual change of state) Though I have to say your rule looks fine you've certainly not made any errors in it
Yeah, tried the timer with all sorts of different times and still no luck.
Even when I totally delete the "motion rule" the lights will still not come on, yet I can switch them on and off perfectly fine from the dashboard.
At first I thought that perhaps the "turn off after 3 minutes" motion rule overrides the timer but even with this rule deleted the light still won't come on.
On the screenshot you shared above, activate "Enable Logging", then change the starting time to 5 min in the future. Then open Logs page and watch/capture what happens in 5 min. If nothing happens, you may have a problem with the hub's time. It could just be the time zone that you set up. To validate that time is set correctly, go to Hub Details from Settings and make sure location coordinates are set correctly.
Is this likely to be a driver issues?
I just can't understand why it would be, when the light turns on off / dims perfectly fine from the dashboard and motion detection.
I've enabled the logs, and will post result in a few minutes.