I would never rely on automation to keep equipment you are working on off. Turn it off at the breaker or disconnect.
T
Tom_D
@Tom_D
I don't know if you guys are into dashboards, but I am.
For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer.
Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate
I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor.
I also have a new build in the works with support for buttons inside HA.
I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable).
This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down.
I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor).
My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long
I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
https://github.com/dbochicchio/reactor-mqtt-contrib
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me.
While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users.
I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do.
Just an idea
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically.
That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button.
Example: Light 1 ON → OFF, then Light 2 ON → OFF.
The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule.
Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Use case:
When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled.
To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work.
Then another situation: the water pump system and garden irrigation, another switch.
In short, I had to create several virtual switches in Hubitat to disable rules in MSR.
Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR.
If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR.
Would it be possible to do something like this? Any recommendations from the experts?
Probably a really dumb question.
Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great.
Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly.
Any thoughts?
Apologies if the ask is not clear/
TIA
C
...is back....
https://arstechnica.com/google/2025/08/researchers-use-calendar-events-to-hack-gemini-control-smart-home-gadgets/?utm_source=facebook&utm_medium=social&utm_campaign=dhfacebook&utm_content=null&fbclid=IwY2xjawMBq-pleHRuA2FlbQIxMQABHlSqIalzbz1IxcJFzlw8GBE6nC3FwvxcHgR370nJhogU6JjqbmRxG-lysqgh_aem_lx9XboYFKw9tpHnedGQKUA
C
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well.
As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
Updates: (the latest versions first in the list)
OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Posts
-
Stop the MSR by an external switch on Hubitat. -
Comment in Globa ExpressionsI have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting.
Any way to document what is setting the GE? -
Gradually turn on lights.Thank you. I had tried variations of that, but I just needed a bit of a nudge in the right direction.
-
Gradually turn on lights.I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments.
I have tried a few things that came nowhere near working, so here I am. -
Links to MSR from HAI am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
-
Z-Wave Future....I have a lot of Z-Wave devices and it still provides the longest range of devices I have tried. My last few devices were Zigbee and I ended up with 3 repeaters sprinkled around the house. I think it is too soon to plan the Z-Wave funeral.
-
Moving MSR from a QNAP container to RP 5 - some issuesThank you all. After many false starts, I got a bit frustrated with the process and quit with the question here.
After learning along the way, I created a new user on the RP and started fresh. Everything seems to be working now, and I can move on to something else.
Thanks again. -
Moving MSR from a QNAP container to RP 5 - some issuesI have installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.
My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)
I have probably done something stupid or missed a step but I am stuck.
Thanks for any help.
-
Lights switches for warehouseSwitches that don't use a neutral are dimmers that keep the switch powered but dim the lights to "off". If the lights are dimmable then this type of switch would work.
-
Post-DST and MSR not reflecting local time -
Post-DST and MSR not reflecting local time -
Is a global timestamp expression possible ? -
MSR connecting to Ezlo PlusThanks for the reply and help.
The next bit of help I need is in marking this thread solved.
-
MSR connecting to Ezlo PlusWell, never mind. It must have been a formatting problem. After posting I started over again with a fresh cut and paste from the manual and it all worked.
-
MSR connecting to Ezlo PlusReactor (Multi-hub) latest-22080-ae7212f
I am having trouble connecting MSR to a new Ezlo Plus controller.
I've tried different user names and passwords and triple checked the ID and IP. Not only does it not work but it crashes MSR giving a connection refused error.Ezlo Plus:
Controller ID: 90012863
Uptime Info: 2d 0h 39m 2s
Firmware: 2.0.27.1916.1
Advanced Scenes: 1.36reactor.yaml file snippet:
-
id: hubitat
enabled: true
implementation: HubitatController
name: Hubitat Elevation system
config:
source: "http://192.168...dump_all_devices - This is for troubleshooting. Do not enable unless asked.
dump_all_devices: false
id: ezlo
enabled: true
implementation: EzloController
name: Ezlo Plus
config:
source: "wss://192.168.1.131:17000" # change the IP address
serial: "90012863" # put your hub's serial # here
username: "lowercase" # put your username here betw quotes
password: "?PassWord!" # and password -
id: weather
enabled: true
implementation: OWMWeatherController
name: OWM Weather
config:
-
-
Local variable in delay field? -
Local variable in delay field?I have noticed that when I use a local variable in the time for a delay it will change after some time to a fixed number.
I enter this:
And later it is this:
I have noticed similar behavior when using local variables in other fields.
-
Problem with median functionThanks for the MSR update. I've checked the related Expressions several times and they are working fine. Of course, the only way I found this was when lights did not come on when I thought they should so difficult to detect when things are always working correctly.
Related, I tried to set up a Scope to watch the expressions and found they can not be watched in the Scope feature. Will that change in the future?
Thanks again,
Tom -
Problem with median functionThanks. I'll look forward to the fix.
I like comments to remind me of what the hell I was thinking when I wrote that. Also to comment out a line of code to try something different or for a temporary fix. -
Problem with median function
