@vezinpi mine is as such:

Here's the rule's Set Reaction that pulls this in.

I also have another group under this same rule's Set Reaction for Evenings.

Everything I've seen shows this as working as intended. Only rises to 30% in the mornings, 80% at night. Only the mornings get the slow roll ramp up.

@vezinpi can you share screenshots of the rules?

I implemented this and it appears to be working fine (though I want to do some fine tuning).

@Tom_D I've implemented this as it's much slicker than what I'd been previously doing. Of course, now with longer days and Daylight Saving Time in full effect it doesn't get called on very much so I can't confirm success lol

@tbully thanks for putting a smile on my face today. Much needed. Much appreciated.

@therealdb I use those as well. As you see in my AWAY rule there's a catch there using a virtual switch for my calendar integration. If a calendar entry has a specific keyword it turns the switch on. If the switch is on, AWAY knows not to fire.... VACA has it covered.

@toggledbits beat me to it: comments, comments, comments. I've lost too many years off my life trying to remember why this rule does what it does and how.

@tamorgen said in Need help figuring out how to delay a reset on reaction:

Thanks to @gwp1 for reminding me to keep it simple

The thanks goes to @toggledbits who has long endured my questions on things only to have him say "wow... pare this down to smaller bits". Essentially, don't try to do things with "one big beautiful ruleset".

@tamorgen said in Need help figuring out how to delay a reset on reaction:

In the new "Go to Away Mode" rule, I added a condition that the mode needs to "Phones Home" rule needs to be sustained for 60 seconds.

Doesn't the result of that mean the system waits for someone to be home for 60 seconds before flipping mode to HOME?

@tamorgen You're falling into the same pitfalls I did. Notice my Mode SETs don't have resets. No need. The next appropriate rule SETs so there's no reason to reset. Any resets (like from GUEST back to AWAY or VACA) are done via their own SET rulesets.

I don't want to reset... I want to move on to another Mode - even if that mode happens to be the last mode I was in. Make sense?

One thing I have done: every time I change mode I write it to an expression called previous_mode. This let's me do things like "if the previous mode was AWAY, return to AWAY - but if the previous mode was VACA, return to VAC" -- again, these being sep SET rulesets and not RESETs.

Every time I tried to make use of RESETs I got buried as I had too many "what ifs" in my Conditions.

@tamorgen reading thru this twice (and I may go back again and slow down even more) it sounds like there's no "link" between your rulesets. ie, the conditions for AWAY is being met even though the conditions for GUEST are, too.

What does your AWAY ruleset look like?

Here is my GUEST from AWAY ruleset (I don't have the luxury of surfacing the individual user code so I'm stuck being a bit more generic, ie "lock unlocked". As HOME requires my presence, this has been doing the trick.) My only issue: sometimes the lock is slow to report it's state so I've asked my authorized guests to enter their code, count to 10, the open the door. That let's Hubitat Safety Monitor to disarm.

Here is my Change to AWAY for comparison sake.

@toggledbits gave me very sound advise early on as I was prone to making my rulesets "do too much" in addition to waaaaaay overthinking/overcomplicating things.

Instead of trying to make a ruleset that determines presence AND tries to set mode, just have it determine presence. Have one for your immediate family and one for your guests. Then use the TRUE FALSE state of them in your mode rules. (Saves you countless hours later, too, when you add/remove people from either presence ruleset.)

@tamorgen check the edit to my original post.

EDIT:

SO here's how mine is set up. I don't have reset anywhere in mine. I only Set Reaction for the various modes.

Cracking open my Away config

It's similar to yours except I just do a Set Reaction

Each of my modes is this way.

@tamorgen Your conditions for each inhabitant are collapsed. What's in those?

I do a TON based on presence so if you can show all your work I can dig in a bit.

Edit: gonna assume all of the other inhabitants are like Tim. Your current rule says "If Tim=home OR Jen=home OR mom=home OR Nana=home OR Joshua = home OR mode=Guest then".... nothing. You have nothing indicated for it to do. Set Reaction is empty.

But then you have a Reset Reaction which is what will play out when all of the conditions above aren't met, ie no one is home mode=Away, ie undoing the Set Reaction. Since you have no Set the Reset is confused and just flip/flopping around.

I think your goal here is to have the house state flip to away when no one is home. As such, you should have Set Reaction be what mode you want the house mode to be when at least one of those people is home. I don't even know that you need that condition for House mode=Guest. The basic goal here is "no one home, set to away", correct?

Now if you want the house to flip to mode=Away when no one is home, put that in your Reset Reaction. That's not how I've done it personally, but it would get you there if I'm understanding your goal.

@RHCPNG As @toggledbits notes, I've found myself bouncing around a bit. I've settled on what I call Shared Rules - those that impact all things potentially, at a base level. Wx stuff, HVAC stuff, etc.

I kinda branch out from there. Interior lighting, Outdoor lighting, Presence, etc. Sorta using "topics" and then rulesets under them.

I'm also linked to our local community center via site-to-site VPN and am using my home MSR instance to control the Hubitat C7 over there for lighting and outdoor fans

@Tom_D please mark issue thread as solved

@mgvra the landing page issue was addressed here as a side note in another issue thread: https://smarthome.community/post/16764

@toggledbits I have indeed used the code... and no, this isn't critical. Once I saw MSR was running and working as intended I moved on. Release AYC.

@Fanan Re time sync: I did a apt-get install systemd-timesyncd on the Proxmox host. I've not seen the warning since.

@toggledbits @Fanan Oddly, I have this same issue running MSR in Portainer on Proxmox logging in from multiple workstations and have since I updated to the latest version. I did some time sync work and the alert has gone away... but the host time doesn't show for me, oddly. Also, when first loading the MSR page after login it's blank until I click on STATUS.

Brave browser. Will try Vivaldi here shortly. Sorry, haven't had two seconds to even look at logs yet.

@toggledbits Confirmed.

@toggledbits not that you need it but I can confirm this behaviour.

@toggledbits sorry for the delay, day job has a rude habit of interfering in fun.

This solution worked perfectly for this need. It's actually quite similar to how I control the outdoor garden fountain, HVAC, and some other things. As usual, I tried to over-complicate things.

EDIT: in fact, I find I am using this EXACT method for my outdoor LIFX lights. sigh

I am still looking for that context. Will provide when I locate it.

And then I tried a different approach...

This may be another case of me making things more complicated than they need to be...