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'

@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.

@toggledbits said in TypeError on build 21270-48528ec:

OK. I've updated the docker images as well.

Just double checking that the deref lines should still be there after the docker update to 21270-46679ac.

I did run one of my rules that set variables, and there is no task error in MSR. So I'm assuming the expr change was a work around and you fixed it elsewhere?

Following - Getting the same issue, but within a Docker and don't see the vera yaml file.

EDIT: Consoled into the docker and updated the yaml file. Restarted the docker and tested OK. Thanks.

Found the errors, thank you, and confirm the other thread is the same issue. I do have SetVariable actions. However I am running in a docker and don't see the vera yaml file.

EDIT: Consoled into the docker and updated the yaml file. Restarted the docker and tested OK. Thanks.

I updated to the latest build this morning, even though my inner voice said no. I'm getting a Reaction task "###" failed due to an exception error now. I've cleared away 2 already thinking it was me messing around with a test to set a variable. I looked through the logs, but I don't see anything outside of a bunch of these entries.

2021-09-28T02:03:31.694Z <HubitatController:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
2021-09-28T02:03:31.697Z <HubitatController:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
2021-09-28T02:03:31.698Z <HubitatController:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation
2021-09-28T02:03:31.699Z <HubitatController:ERR> HubitatController#hubitat mapped capability x_hubitat_healthcheck has no implementation

Is there something more specific I can look at to track this down?

@toggledbits said in (no data) constraints:

Those are triggers by the way, not constraints...

Oops.

Thanks for the immediate turn around. That resolved the issue.

I don't know if this was a result of the 21256 update or 21257, but all of my constraints triggers are showing no data. Even if the device has a triggered change. In addition, it is not showing the Conditional match either. In my screenshot, the Front door - auto locks (Day Time) is all true, but it has to be true for 15 minutes. I am not seeing the timer counter either. I tried a couple of browsers and even my tablet. No Data is seen on every rule. The actions are still running though. My lock did auto lock after 15 minutes.

@cw-kid Thank you for this. I know this is slightly off topic, but I'm having a difficult time with The Home Remote to get a door/window sensor status to appear within my grid. Is there something I missed? Granted I did not watch all of the videos as the ones I skipped didn't really elude to adding in a device like you can do on the mobile app. I don't want to control the sensor, so a button seemed incorrect. I literally just want to display if the window is open or closed. Is that added as an Icon? Image? Or something else?

TIA

@toggledbits - Have you enabled the option to switch Modes within Hubitat? I added the x_hubitat_sys_mode.set action on a couple of rules but it never seemed to change in the hub. I was manually testing this out via an action, and straight from the Entities page, and it doesn't look like it does anything. If I create a virtual button within Hubitat and then using the Home Mode Manager app, I can switch the modes based on the button I press, but it would be simpler if I could just assign the mode within an action.

I've tried the variable "away" as well as 3 in the Perform now action, but neither appears to do anything.

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.

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.