Today I moved my last device from Vera to HomeAssistant. I do have mixed feelings about it. For all it's flaws and performance issues, it had a very easy interface to get started in and for the average person, could do most of what they needed. Started using PLEG but never got very far with it since I had to spend hours relearning it every time I wanted to add a new automation. Reactor was a breath of fresh air for the Vera and I am eternally grateful for all the assistant I have received from Patrick over the years including some beta code for my Leviton scene controllers and my Venstar thermostat. MSR allowed me to tie my Vera and Home Assistant together while I slowly migrated off Vera and had way more capabilities than I could ever master.

As I get older, my wife keeps telling me that if I die she is selling the house because she cannot run it. That has given me some incentive to simplify my environment so I have gone to only Home Assistant. Would have stayed with MSR if I could have figured out how to get the addon to work in HA, but in the end was easier to move everything to HA and eliminated one more component.
Thanks to all the people that have offered assistance on this community as well as the old Vera forum before EZLO.

Roger

Have a nice Vera Plus available if anyone is interested. In the Seattle area but will ship. Make me an offer.

Went with Patrick's suggested approach. I do like the old reactor a bit better for this instance. Less clutter. Sure there was a technical reason to do it this way. Guess I can create multiple rule sets to group them by.

Doh. Found an ID10t error. Had the wrong IP address in the Reactor config. I definitely have too many computers at my house.

You could build your own. https://community.home-assistant.io/t/mmwave-presence-detection-esphome-style/382778

Same to you and all the others here.

Thanks for the additional details. That worked.

Got it to work again. Now I am on 20.5.1 of openLuup.

@catmanv2 Yeah, it quit working for me as well. Could view it in the wayback machine though.

@LibraSun
Hello, You had a post on the Hubitat forum where you stated this" I realize I'm responding to an old thread, but it bears mentioning that Multi-System Reactor (MSR) indeed has the built-in ability to act as a virtual Deus Ex Machina. If the OP is still contemplating methodologies, that's certainly one I would recommend pursuing."

Am moving off of Vera to Home Assistant and curious how you are using MSR to replace Deus Ex Machina? Is there something built in that I didn't see in the documentation?

Thanks,
Roger

Got it. Thanks for your help.
Plugin Startup Jobs CPU usage (in startup order)

date / time device priority status hhss.sss job # info notes

1 2020-05-03 15:22:33.769 2 1 Done 0.004 1 plugin: openLuup sync in 86.7 s
2 2020-05-03 15:22:33.770 3 3 Done 0.000 2 plugin: Alternate UI
3 2020-05-03 15:22:39.200 5 5 Done 4.403 4 plugin: VeraBridge OK
4 2020-05-03 15:22:39.293 6 5 Done 0.008 5 plugin: Z-Way OK
5 2020-05-03 15:22:39.294 4 Done 0.001 3 plugin: Alternate App Store OK

Hello,
Likely a very obvious solution
I need so help setting up logic. Monitoring 2 parameters A and B.

If A and B go true, turn on switch
I want it to remain true until both A and B go false.

I think it should be done with latch but struggling with how to implement it in MSR.

Quick question. I am in process of moving from Vera to HA. I want to do something similar so I can keep my Homewave dashboard on the wall mounted ipad mini in the kitchen. Have created a virtual dimmer in switchboard and can capture the dimming level into a expression. How do I pass that to the physical dimmer switch I want to control? Have tried set_load_level_target to expression name but that doesn't work. Any hints?

You can do it a lot cheaper using ESP32 board and mqtt.

Thinks for the tips. Figured out the DNS issue was a setting in pihole. Had interface settings set to only respond on interface eth0, changed it to local requests and the install script ran fine. Got me some learnin today, thanks,

Looks like it is working now. Thanks

Found the issue. The port was not set in Network section of zwavejs2mqtt.

Thanks, Fixed it.

Happy Birthday.

That fixed it. Thanks