Sorry about that! My bad! I do appreciate the help!
Looks like the lights turned on today! Now to see what happens tonight.
1 Like
So the lights turned on again at 12:00 midnight. There seems to be a bug in RM when using Days of the Week as Conditions and with sunrise actions. How do we get this fixed?
@bravenel, It appears that there is a bug in RM when the day of the week is a condition according to @pcgirl.
I already copied in Bruce above.
Probably missed when the device discussion took over this thread last evening.
That's why I re-tagged him. Better safe than sorry.
1 Like
What happens? Sorry, don't have time to read this whole topic.
@bravenel
Hi Bruce.
Here is the rule.
What should happen is when the rule evaluates as true, it turns on a light.
When false there is a delay and the light turns off.
What is happening is at 00:00 (Midnight) the lights turn on even though the rule is false.
When I look in the events for the device I can see an event to turn the light on at 00:00:01.
If I break this up into 2 rules (Mon - Thurs) and (Fri - Sun) and have these days in a restriction then both rules work OK.
Its a if the rule is being re-evaluated at midnight but is returning true for some reason.
If you click on the settings cog for the rule and scroll to the bottom you can see schedules in there for midnight.
Hope that all makes sense.
Yes, it will do an evaluation at midnight to see if the day condition just became true or false. Why it would return true for the whole rule I do not know.
I will try to recreate this....
Also, seems to be a problem with sunrise conditions. When I have this in any RM piston, the lights don't turn off when the time reaches sunrise -30. And it didn't log it in the schedule today.
This one also has the same problem. But it did log a schedule at 7:02am but the lights didn't turn off.
What's turning your lights off?
I can only see turning on if true.
They go off if the piston turns FALSE. So when the time in not between 4:50am and sunrise-30, they will be off.
But you haven't defined what happens when false.
According to @Ryan780 you don't have to because when it isn't TRUE it is FALSE so the lights will go off. I have tried it both ways but seeing as there seems to be a problem with the sunrise condition, it is hard to test. However, looking back at some events, it seems that the lights didn't turn off at 11:00 last night but did on the 27th. See the 12:00 ON but no 11:00pm in the second picture.
That is not what I said at all....if you're going to blame me, don't mention me. LMAO
What I said was you don't have to have a false statement in rules in general. If you want something to happen when the rule is false then you have to put it in there. However, if will happen whenever the rule is false. So, even if you are in the room at sunrise -20 if you have false defined to shut the lights off, they will go off, no matter what.
Also, in all of our discussion about EXACTLY what you wanted to happen, you never mentioned turning the lights off...only turning them on. This is why I asked you to details ALL of the actions you wanted to happen. I can't help you when you don't provide all the information.
EXACTLY!!!! You wanted to know why your lights turned off at 9:30 and it was because of the false statement. You said you didn't want them to turn off you wanted to turn them off with your goodnight routine. So i said take out the false statement. LMAO . Now you say you do want them to turn off. Make up your mind!! or, like i siad, stop trying to do this in one rule and break it apart!!!!!!
Let me put it like this.
Your rule becomes TRUE.
Actions for 'Select Actions For True' will execute.
Your rule becomes FALSE.
Actions for 'Select Actions For False' will execute.
This enables you to have the flexibility do what you want when this happens.
Just fill in the False options that you want to happen and it will work OK.
EDIT: I meant to send the reply to @pcgirl
But youre the one saying that what I said there applies here. So, which is it?
