THANK YOU! And Curses. This gives me ALL sorts of ideas now on how to better things and potentially kill off all of my Vera scenes.
Initial testing looks good. Fully enabled the rule and waiting for Sunset to test it for real.

I'm on the edge of my seat and can't wait... I've been on and off researching a dashboard replacement for Imperihome and now that I've started my migration away from Vera to Hubitat, I am getting more serious about finding one. I don't know the first thing about json, so I don't know where to start on getting the MSR dashboard customizations going. I have started looking at The Home Remote, but I'm having a heck of a time to get a device to appear within their Designer App.

Knowing that you have lots in store for the dashboard, may I inquire/suggest on a feature or two? Things that I love about Imperihome, yet can't seem to locate in any other dashboard. Everything seems to be around their APIs.

Changing pages/panels via HTTP command
When the temp outside is hotter than inside, I have the tablet make the TTS announcement to close the windows/doors and then have the tablet switch to the page/panel that has all my door and window sensors

The blanking of the screen
When my house mode is <> home, I blank the screen. No sense in having it display when nobody is here. I also use nearby motion sensors to blank or activate the screen when someone is here. If nobody has been upstairs in a while, blank that tablet's screen.

Viewing of my IP Camera
I have a door/window sensor hooked up to my doorbell. When the bell is rung, it changes the tablet display to the IP camera at my front door so I can see who it is.

I also use the tablets main page as a clock and temperature readings, which I know most dashboards can do. But again. Learning curve on the Home Remote and I don't know json.

I have seen that before. I run my own Hue Bridge Emulator within a docker and I believe the issue was narrowed down to having multiple generations of Echo devices on my network. This would cause my $device to appear multiple times within the Alexa app. Amazon had a sale on echo dots, and also gave trade in credits, so I was able to take advantage of that and upgrade my Gen 1 and Gen 2 dots to Gen 3 at about $10 each. Once all my generations were the same, I cleaned up the known devices and initiated a discovery again. Every once in a while I get something similar to below, but it doesn't happen very often.

Alexa, turn $device on
$device does not turn on
'$device is not responding. Check its power supply and network connection'

Alexa, turn $device on
$device turns on
'OK'

Ugh. I've had a few of my Gen 1 switches go out. All over 2 years old and I assumed all would not be under any warranty. I had a friend replace the caps in most of them and put them back into service. I wish I had called GE after my 5th or 6th switch went out. Would have been able to get an upgrade.

@toggledbits said in MSR feedback post RfV migration:

You shouldn't see the index values at all,

This is interesting. Now that you mention this, on a different computer over the weekend, I didn't see the 0, 1, 2 values. I only saw Home, Away, etc. Besides being a different computer, I'm pretty sure my version of Chrome between the two is the same. The only other difference between then and now is that I upgraded my MSR from the generic 1.0 21200 build to the latest 21221 build. Chrome is all I have and use. I just tried Edge and IE, because they are there by default. But they both suck and won't display anything except the left most side panel. None of the links work either.

@toggledbits said in MSR feedback post RfV migration:

Can't cascade;

At least maybe shade the Rule Set labels to set them apart. Or add an option at the top of the list, or a new button all together, to Copy From Set / Copy From Reset? Just ideas.

I have fully migrated off of RfV and onto MSR. A huge thanks for all your work Rigpapa. Amazing products. RfV and MSR. I officially removed RfV from my Vera controller yesterday. During the migration I was noticing things were getting a little more snappy and a little more stable. But now that RfV is off, I'm noticing a big difference. There was always one motion controller that would not behave for me. If I moved it from that area of the house and next to the controller, it worked flawlessly. I figured that the flakiness I was getting was some ZWave delay or a dead spot in the house. But with the migration all the way to MSR, the motion sensor has not skipped a beat. (Yet) I'll give it a few more days to really test. But I am really happy with the move to MSR.

So somethings that I noticed along the way and now that I am adjusting and tweaking my rules.

1. During the import, the house modes would import as a number. I/E: 1,3,4. And the trigger would be set to changes from 1,3,4 to blank. I believe this was already reported, or noted, but the mode doesn't work properly. Any trigger that used a house mode would need to be changed to == and then the 1 to home, or 3 to night, etc. I ended up creating a house mode group if the trigger needed more than one, but less than three modes.
2. When your Set/Reset Reaction involves a change to the House Mode, the predefined values start with 0 = home, 1 = away. Minor cosmetic difference compared to what Vera actually uses. 1 = Home, 2 = Away, etc.
   (See Img1 for examples of 1 & 2)
3. When you use the Copy From option in the Reactions, it would be awesome if the list could have a few changes. For one, the Rule Set labeling (grouping) is nearly the same color as the rule name itself. Maybe change the color of the Rule Set name, or a background highlight of that line so you know where the rule sets change? A couple other options, if this would be possible. 1) Put your current Rule Set at the top of the list, then scroll to the rest. For me, I am usually copying my Set Reaction and then changing the On to an Off, or vice versa. Or 2) Cascade them. The initial drop down will only show the Rule Sets, clicking on one would extend that rule set out to the right and show you all the rules. For me, I have a very long list and often scroll past what I'm looking for, or struggle to find it.
   (See Img2 for the Rule Set and Rules being nearly the same color)

Img 1:

Img 2:

All in all though. LOVE MSR and my wheels are already turning on how to do more with it and not cripple my Vera anymore with too many rules. I'm also scared of my Vera Plus's life. Support made a comment to me that they have one or two more firmware updates planned for the unit. Granted the firmware releases are very slow and really far between, but this is making me think that the product could be EOL in the not to distant future. MSR now gives me the option to start migrating to a second controller. Thank you again @toggledbits.

I could use this "Where Used" feature as well. I have 3 Global Expressions that I don't think I have using, but want to make sure before I nuke them. I did not change my logging levels, but did search through all the reactor.log files and do not see anything. Is there a different way to see if they are in use, other than killing them and seeing what breaks?

@gwp1 said in Multiple Holidays, one Ruleset:

Complication: one is a static date each year, the others are "last Monday of" and "first Monday of" respectively

I use a Google Calendar plugin in my Vera controller for the holidays that float around. I/E not always on X day. Labor Day, Memorial Day, Mother's Day, etc. If the gCal device contains the word "Easter", lets say, AND my lights are on, then color them. I used to use PLEG in Vera for this and programing it wasn't as easy as I wished, so I never touched it once I got set. Plus there was a bug with any event that contained an apostrophe. I reported this bug several times, but it remained for several versions. Regardless, this worked flawlessly in RfV, but bogged my Vera down. I also doubled my dates when it because super easy in Reactor. That's what helped bog my controller down. But now I'm on MSR and loving it. And I probably took the color changes a tad too far, but that's why I have them too.

My color changing days:
Easter, Mother's Day, Martin Luther King, President's Day, Memorial Day, D-Day, Flag Day, Juneteenth, Independence Day, Labor Day, Patriots Day, Columbus Day, Peral Harbor Day, Valentine's Day, Black History Month (Start of), Cinco de Mayo, Christmas, Women's History Month (Start of), Purple Heart Day, Thanksgiving, Native American Heritage, Halloween, St. Patrick's Day, Veterans Day, and Father's Day.

Yikes. I may have a problem.

My vote is yes. I was/am running Vera, which we all know is slow and gets bogged down at times. Moving my Reactor for Vera off to its own docker was a huge performance lift in the Vera. I continued to move all of my scenes off next. I now have a Hubitat and Vera, but each are only there for control of the device itself. All my scenes, schedules, modes, etc. are all managed and run by MSR.

I just noticed your signature line. That's funny. I realize you don't have Vera. For me though, getting all the routines and everything vendor neutral has made it super simple for me to move/migrate devices between hubs. And the family doesn't know. My only hold up right now is an easy to use and easy to configure dashboard. But I've got a plan for that. Just need to do a bulk migration one day of a group of sensors. I look forward to the day that MSR has its Dashboard running.

@gwp1 said in About page after every update:

I'm guessing the code we enter is cached in the browser

This is my guess too. I don't clear my cookies for MSR, so I only get the prompt to re-enter the characters after an upgrade. Still curious if there is a way to enter this variable into a docker and by pass it. I do recall something @toggledbits posted about it a really long time ago. I'll try to see if I can find that.

@toggledbits You are correct. I had an extra motion sensor and was planning on putting it on the opposite side. While I was testing, with three sensors in the AND group, it dawned on me that all three would have to have triggered and gone false for this to work. This won't happen if you only enter the garage a few feet and never to the other side. I ended up creating my rules exactly how your example was and it's working great. Thanks for the insight and example.

@toggledbits I like your off rule. It is a different approach than what I have. The end result of both is the same though.

My off rule has the sensors in an AND group (when the sensor is true) with a delay reset of 10 minutes. There is no Set reaction. Only a reset reaction to turn the light off.

I've memorized my code, so it's easy to enter without looking. But I am curious if there is a way to do this.

Thank you for the very detailed explanation. I haven't really dove into constraints before and clearly I need to so I understand them better.

@toggledbits said in Group in Reset Reaction is being ignored:

open the condition options for your OR group, and in the "Follow" section for "delay reset", add a 600 second delay. This is a resettable delay that will restart every time motion is detected, so if motion is detected during the 10 minute delay, the delay will restart anew

This is exactly how I have all my Motion rules defined. And they work as expected. But in this particular rule, I want the Set reaction to trigger again if it detected motion by either sensor after their timeout and before the 10 minute reset delay within MSR.

Use case: I enter the garage, the lights turn on. I leave the garage and manually turn the lights off. (Assuming there is a 10 minute delay reset defined) I return to the garage 2 minutes later, the sensors detect movement, I would like the lights to turn back on.

With the 10 minute reset delay defined, MSR will see the rule still as true at that 2 minute mark and not fire the Set reaction again, correct?

@toggledbits said in Group in Reset Reaction is being ignored:

please don't reuse/plagiarize another existing thread's title

I will fix this.

EDIT: If the solution for this is to have two rules, I am perfectly fine with that. I just happened to see that Groups were an option within the reactions now and was determining if there is a way to consolidate rules. But if I need an ON and and OFF rule, I'm good with that.

They say plagiarism is the best form of flattery, right? Or something like that. Thanks go to @gwp1 for the great title of this subject. I'm trying to get into using the new (to me) group option within the Set and Reset Reactions. I have the Set action working beautifully, however my reset reaction is not. What I am after, which maybe this isn't even possible, is one rule for the motion sensed in my garage. Upon motion, and it night time, turn on the lights. And upon no motion, and no motion for 10 minutes, turn off the lights.

MSR Docker on unRAID: latest-22293
Hubitat 2.3.3.137
HaaS 2022.10.4

Trigger:
If motion is detected by either sensor

Set Reaction:
Only turn the lights on between 30 minutes before sunset and 30 minutes after sunrise.

Reset Reaction: (I've tried a few variations, each with conditional options set.)
Tried: Both Motion sensors, in an AND group or individually as an AND, are False and sustained false for 10 minutes.
Tried: Rule State (this rule itself) is False and sustained false for 10 minutes.

Basically the additional condition I am putting into the Reset Reaction group is being ignored and as soon as either motion sensors is false from it's normal reset time, the lights turn off. I would like to have a 10 minute delay before the lights go off. In case I'm moving around and re-trigger a sensor. Are additional conditions allowed within the Reset Group option? Or am I way off and should just break this into two rules? One for on and one for off?

EDIT: Forgot to include my reasoning for not putting the Delay reset for 600 within the Trigger. I want the garage lights to come on again, if they are off, after the motion sensors native timeout has reset. For example, if I go in the garage, the lights automatically turn on. When I leave the garage, I will turn them off. But if I return within 2 minutes, and less than 10 minutes, turn the lights back on again for me.

Following to see when the UI issue is fixed. Just learned about the groups and it would allow me to consolidate a number of rules.

@toggledbits said in Upcoming HubitatController z-wave polling feature:

I think that's right

It is correct. My polling config left the default frequency at 60000ms (1 minute) and I did not include the interval settings on my devices, of which I am polling 3 until I can get around to replacing them. Upon reactor startup, the first device in the list is polled, one minute later the second device, another minute later, the third device. Seven minutes from there, or ten minutes from the initial poll, device 1 is polled again.

Thank you @toggledbits for adding this feature.

Thank you. So if I have 10 devices, all with the interval set at 60 seconds, essentially it will poll one device at minute 1, the second device at minute 2.
In other words, one device polled per minute, or based on the poll frequency.

If I'm understanding this correctly, I'm better off upgrading my z-wave to z-wave plus devices and only poll those that are critical, and not upgraded, yet.

Super excited to see in the upcoming release notes about MSR being able to poll HE z-wave devices. I've attempted to use the native HE poller and in less than an hour after installing it, I was removing it. I only have a small number of devices that give me trouble, but I wanted to verify that I'm pre-building my YAML file correctly.

poll_frequency: 60000  # poll a device at most every 60000ms (60 seconds)
poll_entities:
     - id: 110  # Hallway Light
       interval: 300  # 300 seconds = 5 minutes
     - id: 111  # Kitchen Light
       interval: 900  # 900 seconds = 15 minutes
     - id: 112  # Disco Light
     - id: 113  # Ballroom Light

Am I correct in my thoughts? Based on the above snippet, the default polling will be every minute for the Disco and Ballroom lights? But because the Kitchen and Hallway light have a defined interval, they will be polled at those intervals instead? Or does there need to be an "interval:" definition following every id:?