Latest build gets rid of the extra notifications on reload. Thanks for doing this instead of me having to figure out another hack. It's a shame we have to do any of this but I suppose we've beat that horse to death over the years.

Update on my weird variable issue: I was noting that the sl_User_code (and even the sl_User_code_updated) variables were only sporadically updating. After a lot of head-scratching, I noted that the servo was moving a little slow even though the batteries were showing 66%. I decided to replace them just in case. I noted much faster servo response but, more importantly, the variable writes stabilized. Very strange but I'm happy it's better.

Many thanks, @toggledbits , for your workarounds and your forum advice. My system has been mostly stable for a few years so I'm a little rusty.

In my exhaustion (anger? Lol), I mistyped. I’m at 22.04.

I do fire an email just before the reboot. I took a break to check emails and wrap up for the day and this is what triggered it for me. If it wasn’t for this, I think I’d still be digging. I send lots of emails, perhaps too many, when different things happen. This is a great idea!

I have to go look at the rule today. I thought I set a variable on reboot which would only allow one event/reboot. At least I thought about this possibility but I clearly missed something.

Thanks for the consoling, gents. I’ve appreciated both of your support over the past year as I’ve slowly moved away from Vera to HASS with Reactor being the central rules engine.

Kids -

Remember to run "npm run deps" after an update. (I knew I'd regret this post)

Apologies.

Thank you. For some reason I was thinking/reading that the 1.0 branch was the latest. I updated as you suggested which fixed my issue. Much appreciated.

@toggledbits Understood.

I'll test more when I get free from work. So far I'm seeing inconsistent variable updates but nice to see it worked for @MikeReadington .

One thing I've noticed is that when Vera reloads (which, let's face it, happens often), the last PIN triggers because the sl_User_code_updated gets updated to the reload epoch time.

Wondering of ways around this. I think one way could be to use a local expression that gets the current time (in epoch) and add a reasonable buffer (few minutes)? I'm not familiar with expressions but maybe something like that?

Something easier?

@toggledbits read through the noise and got it. I'm depending on Vera (and their app) to manually execute certain scenes (which I think should be converted MSR Reactions or Rules) until I can fully get off the platform. I'm also trying to figure out how to do the same from a Hass dashboard. I agree that I'm sure it's possible. I just need to dig a little more.

The virtual switch idea is interesting. Basically using them as a variable. But I think a direct call from the Vera scene may work. I'll look in to the wget function.

Thanks for the feedback, both.

@Pabla - Thanks again for your help. This was finally the answer (for anyone searching later)....

{
    "recirculation_minutes" : 5,
    "entity_id": "water_heater.bully_house_water_heater"
}

I have the rules migrated and running on the external Reactor (doing some tweaking as you mentioned). That's not my issue.

My issue is I'm now starting to exclude some devices from Vera and adding them to HASS. For the most part, I've been successful in knowing where the device is used in my ruleset. However, on a few occasions, I've forgotten / missed some rules.

It would be great to look up an entity in MSR and see where it's used (either in rules or reactions) so I can account for the myriad places some devices exist.