Hello all,
I have a Basic Rule that worked correctly for a while prior to this latest round of Hubitat firmware updates, but doesn't work at all anymore.
When Time of Day is 45 minutes before sunset ...
Turn on Chandelier Default Dim S
Rule and pending actions can run ...
Only when mode is Away, Vacation
Things I've checked:
Mode does change to Away when I'm away during that time
I'm using the latest Mode Manager 2.0 app
I have other rules that trigger correctly on sunset (no offset)
Sunset time is correct in the Hub
Logs show that no command is sent to trigger this scene at or around sunset-45
The rule works if changed to specific time of day (not linked to sunset)
Has anyone else experienced issues after the latest firmware updates? Does anyone else have a similar rule that works as expected?
I have several Basic Rules tied to Sunset/Sunrise with and without offset and I don't experience any issues. Being a simple rule that wouldn't take much time to recreate, have you tried deleting and recreating the rule to see if that resolves the problem?
Sorry for the delay in following up, but I think I've found the source of my problem.
My mode was not changing to Away after I installed the new Mode Manager. I have fixed that. Now when my Pixel 6 presence sensor leaves, my mode changes to Away.
I'm curious to see if you guys have presence sensor tables similar to mine with the new Mode Manager.
You need to set it up like this example Bruce provided in a thread a while ago...
I just have Home set up in the "Set Mode at Times" table with a dummy time (0045) so it has an entry in there. I just use Home and Away for modes right now...
Okay, maybe that approach makes more sense, so that Home mode is basically default instead of being presence sensor-based. Seems weird to put a dummy time, but whatever.
Having a vacation mode is important to me, though. So something like this is recommended by Hubitat staff?
However, wouldn't this force the mode to Home at the dummy time, regardless of presence sensor? For example, if turns 12:00AM and the presence sensor is not present, then wouldn't the mode change to Home regardless? This is not the behavior I want, obviously.
Okay, for those still following, after some experimenting, I've found this to be the proper configuration for those who want Home, Away, and Vacation modes.
I am having a similiar(ish?) issue over the last week or so. It is a very basic rule. We have an enclosed mud room and it has a light and a motion sensor. The physical Lutron Caseta switch is located in the house so I use the motion sensor to trigger the light for anyone entering from outside while it is dark out. It has functioned without any issue since last December but now it is triggering ANY time motion is detected. I have not made any changes to this rule. I use a required expression of “time is between sunset and sunrise”. When looking at the rule to edit it you can see it says the required expression is false. However if I look on the apps tab where it lists all my rules it never says the required expression is false whereas other rules clearly state in red that the expression is false. I have already deleted and made the rule all over again and the same issue is occurring. This rule is as basic as can be so I can not figure out what the issue is. What should I do?
I haven't used Rule Machine before, but it looks like you have it configured correctly. However, f you look at the local variable, the Boolean is true when your required expression states false. Not sure if that is the source of your problem. Try a Basic Rule and see if that works better. Or try the new Lighting Controller.
Enable trigger, action, and event logging on this rule (the dropdown towards the bottom of your screenshot), which will give you more information about what's really happening. Then, look at Logs (live logs if you're there at the time, or past logs if not) around the affected times--sunset, when motion becomes active, etc.--and see what's there for this app.
EDIT: I have just realized I posted this in "Basic Rules" but I am actually working within Rule Machine so I will go post over there.
I did this and here are the results. There is something broken with the app's ability to acknowledge the end of the rule time. I turned the log on the day you posted but did not have time to troubleshoot until now. There are some oddities I noticed.
After the last post when I edited the log setting (done during the day time so the required express was false) the red warning on the app list returned to say "(Required Expression False"). However when I looked this morning at the app list it did NOT say that line even though it WAS after sunrise. So it was back to how it was when I first posted. So of course any motion was turning the light on. If I went to edit the rule again it acknowledged on the edit page that sunrise was 7:32am and the expression was false, however motion was still triggering the light. After I hit "Update Rule" it went back to functioning again as it should.
Here is the log:
[app:801](http://192.168.1.11/logs#)2022-10-15 08:25:42.136 AM[info](http://192.168.1.11/logs#)Initialized
[app:801](http://192.168.1.11/logs#)2022-10-15 08:25:42.059 AM[info](http://192.168.1.11/logs#)init: Required Expression now false
[app:801](http://192.168.1.11/logs#)2022-10-15 07:15:35.430 AM[info](http://192.168.1.11/logs#)Action: On: Mud Room Light
[app:801](http://192.168.1.11/logs#)2022-10-15 07:15:35.374 AM[info](http://192.168.1.11/logs#)Triggered
[app:801](http://192.168.1.11/logs#)2022-10-15 07:15:35.364 AM[info](http://192.168.1.11/logs#)Event: Mud Room Motion Sensor motion active
[app:801](http://192.168.1.11/logs#)2022-10-15 07:14:17.904 AM[info](http://192.168.1.11/logs#)Action: On: Mud Room Light
[app:801](http://192.168.1.11/logs#)2022-10-15 07:14:17.853 AM[info](http://192.168.1.11/logs#)Triggered
[app:801](http://192.168.1.11/logs#)2022-10-15 07:14:17.844 AM[info](http://192.168.1.11/logs#)Event: Mud Room Motion Sensor motion active
[app:801](http://192.168.1.11/logs#)2022-10-15 12:53:56.489 AM[info](http://192.168.1.11/logs#)Action: On: Mud Room Light
[app:801](http://192.168.1.11/logs#)2022-10-15 12:53:56.425 AM[info](http://192.168.1.11/logs#)Triggered
[app:801](http://192.168.1.11/logs#)2022-10-15 12:53:56.410 AM[info](http://192.168.1.11/logs#)Event: Mud Room Motion Sensor motion active
[app:801](http://192.168.1.11/logs#)2022-10-14 10:35:17.110 PM[info](http://192.168.1.11/logs#)Action: On: Mud Room Light
[app:801](http://192.168.1.11/logs#)2022-10-14 10:35:17.066 PM[info](http://192.168.1.11/logs#)Triggered
[app:801](http://192.168.1.11/logs#)2022-10-14 10:35:17.056 PM[info](http://192.168.1.11/logs#)Event: Mud Room Motion Sensor motion active
[app:801](http://192.168.1.11/logs#)2022-10-14 10:32:05.380 PM[info](http://192.168.1.11/logs#)Action: On: Mud Room Light
[app:801](http://192.168.1.11/logs#)2022-10-14 10:32:05.338 PM[info](http://192.168.1.11/logs#)Triggered
[app:801](http://192.168.1.11/logs#)2022-10-14 10:32:05.326 PM[info](http://192.168.1.11/logs#)Event: Mud Room Motion Sensor motion active
[app:801](http://192.168.1.11/logs#)2022-10-14 06:38:07.177 PM[info](http://192.168.1.11/logs#)Required Expression now true
[app:801](http://192.168.1.11/logs#)2022-10-14 06:38:07.173 PM[info](http://192.168.1.11/logs#)Event: scheduled event
The event for at 2022-10-15 08:25:42.059 AM saying "Required expression now false" is NOT when it actually should have gone false, it is when I edited the rule myself. The actual time it should have gone false was 7:32am. I am completely stumped by what is happening. On the edit page for this rule it is clearly acknowledging everything is correct and listing proper times however in reality it is not functioning that way. From what I can tell when it hits sunset and the required expression goes true it will stay that way indefinitely until I go in and hit "update rule". It will not acknowledge that the expression has gone false on it's own.
I still have the issue.
