Hi everybody!
I was following this web site as non-member. Finally I have a new Synology Nas to try the new @toggledbits 's reactor project and this post is first of all to thank @toggledbits for his effort and passion to share his projects and to make them accessible even for those who are not a programmer. I know many of you reading the posts from the vera community and would like to express my gratitude for the advice you give to understand things. So a big Thanks and congratulations to Patrick for this new project !!!
I just installed MSR and I am excited to try it out!
N
noelab
@noelab
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
-
Release 1.0.0 -
Dashboard extended to guests with visible/hidden icons - an idea?Hi, I like a lot the MSR Dashboard: it's quick and easy without an authentication system and this is great.
Not really a good idea if I give this possibility to my wife to power off all switches included the nas with MSR or to a guest to power off the light in my room.
Is it scheduled to have a main dashboard and a guest dashboard? as a sub-dashboard
Maybe from the main dashboard, using a built-in GUI editors that can set icons as visible or hidden and automatically reflect on a guest dashboard with a different ip
Just an idea
for MSR -
Merry Christmas/Happy HolidaysHappy Holidays and very best wishes for a wonderfull and reactor New Year!
-
Synology Docker installation@librasun yes, of course I agree with you. In Vera I based my logic using a virtual dimmer (Switchboard Plugin) per room to interact with Alexa commands behind conditions/rules in a Reactorsensor per room and only some global reactor for the house. In this way it is possible to have until 100 voice commands per room associated to 100 preset rules per dimmer, controlling them in web gui, in mobile app or alexa. So at the moment trying to understand if there is a new approach in MSR to emulate virtual devices or to find another way.
-
Plugin InfluxFeed - Selecting Capabilities for Export - how toThanks to you!
The fix is working.
Now I can truck energy consuption on Influxdb. The idea is to try to make in MSR what in HA is doing with utility_meter, Trend and Lovelace UI togheter. Maybe in future we will see a standard MSR energy plugin too.
-
Power_switch.state - no change state - EzloPlus - Msr v. 21351-a3aef - Synology DockerHi, it seems working ok. Thanks! If you need more infos to test, just tell me how I can produce them.
L Bulb FibaroDimmer2 ezlo>device_61425874129e29124dfcd75e 0.65 7:30:07 PM dimming.level=0.65 dimming.step=0.1 energy_sensor.units="KWh" energy_sensor.value=11.3400001525879 power_sensor.units="W" power_sensor.value=6.90000009536743 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Fibaro" x_ezlo_device.model="FGD-212" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2024129e2912114c093b" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_in_wall" x_ezlo_device.type_id="271_258_4096" x_ezlo_item.dimmer=65 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.electric_meter_kwh=11.3400001525879 x_ezlo_item.electric_meter_watt=6.90000009536743 x_ezlo_item.hw_state="hardware_failure" x_ezlo_item.load_error_state="unknown" x_ezlo_item.meter_reset=0 x_ezlo_item.over_current_state="unknown" x_ezlo_item.over_load_state="unknown" x_ezlo_item.power_surge_state="no_surge" x_ezlo_item.switch=true x_ezlo_item.voltage_drop_drift_state="unknown" x_ezlo_object.id="61425874129e29124dfcd75e" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Fibaro","FGD-212",null] zwave_device.node_id=27 zwave_device.version_info=null Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighborsanother
K Bulb Domitech ezlo>device_61423589129e29124dfcd756 0.65 7:35:42 PM dimming.level=0.65 dimming.step=0.1 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Domitech" x_ezlo_device.model="ZE27EU" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2020129e2912114c093a" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_bulb" x_ezlo_device.type_id="526_19522_12596" x_ezlo_item.dimmer=65 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.switch=true x_ezlo_object.id="61423589129e29124dfcd756" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Domitech","ZE27EU",null] zwave_device.node_id=26 zwave_device.version_info=null Capabilities: dimming, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighborsanother
H Bulb Widom dimmer ezlo>device_6147578c129e29124dfcd814 1 7:36:56 PM dimming.level=1 dimming.step=0.1 energy_sensor.units="KWh" energy_sensor.value=0.651000022888184 power_sensor.units="W" power_sensor.value=2.47000002861023 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Unknown" x_ezlo_device.model="Unknown" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2012129e2912114c0938" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_in_wall" x_ezlo_device.type_id="329_4628_2560" x_ezlo_item.dimmer=100 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.electric_meter_kwh=0.651000022888184 x_ezlo_item.electric_meter_watt=2.47000002861023 x_ezlo_item.meter_reset=0 x_ezlo_item.switch=true x_ezlo_object.id="6147578c129e29124dfcd814" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Unknown","Unknown",null] zwave_device.node_id=41 zwave_device.version_info=null Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors -
Need Testers@toggledbits happy to help!
I'm running Reactor>Docker>Synology NAS
-
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.040 = L Bulb Ball 1 Z-RGBW2
036 = R3 Bulb Roof 1 HKZW-RGB01
033 = R3 Bulb Wall 1 A-ZWA002
Utility Meter
