https://forum.z-wave.me/viewtopic.php?f=3417&t=36140
That's not a good thing I think 
Time to switch again?
D
DesT
@DesT
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'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’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.
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions;
Fix an error in OWMWeatherController that could cause it to stop updating;
Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later;
Improve error detail in messages for EzloController during auth phase;
Add isRuleSet() and isRuleEnabled() functions to expressions extensions;
Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases);
Fix a place in the UI where 24-hour time was not being displayed.
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page.
Once logged back in I can no longer remove errant panes nor is the + available to add new ones.
Brave Browser v1.80.122 (Jul 16, 2025)
What have I done?!
Will check other browsers on my M1.
UPDATE: Safari exhibits same behaviour.
I've tried both sans last-four public key entry and with - no change.
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of.
Thanks.
Posts
-
Z-Wave Future.... -
Migrating from Vera Plus to Home Assistant (or other?)@sammy2 old vera user too, i moved to z-way (https://z-wave.me/) AND i'm using openLuup from @akbooer to bridge to z-way and have the same plugin as on Vera.
I'm running that setup for the last 4-5 years.
-
Chat seems broken (still)@toggledbits sorry for the delay, got quite busy at the office. Next time feel free to email me!
-
full devices resetyeah I made a couple of changes and save them, I confirm the file got updated too, I reloaded openLuup, still having my changes...
The only little issue I have it's a cache issue, when I change a rule, save it, re-open it, sometime it's the old version BUT the file timestamp is newer and opening a new browser show me the right version.
so there's something in your last openLuup version Feb 29 that fixed that too
-
full devices reset@akbooer just did a little test... and in the browser console, I can see in the network, that, when saving a rule... it call upload_upnp_file.sh
I just did some test again and the file C_RulesEngine_Rules.xml is modified properly...
Is it possible that's related to the issue with openLuup console ?
-
full devices resetI just check again, and I'm never having any kind of error in the console, not even a warning.
-
full devices reset@akbooer about RulesEngine... I think I found something... if I modify a rule, it work except, the data is not saved. That mean, if I "edit" again, it's the old data and if I reload openLuup, of course it's again the old data.
The problem is the "save" function.
-
full devices reset -
full devices reset@akbooer no worries
2023.01.01 api.lua
2024.02.23 init.lua
2022.12.20 historian.lua
2019.07.19 http.lua
2023.02.18 panels.lua
2023.03.04 console_util.lua
2022.11.05 chdev.lua
2021.05.08 gateway.lua
2023.02.10 wsapi.lua
2024.01.06 loader.lua
2019.10.14 client.lua
2024.02.09 mqtt.lua
2020.03.30 L_AltAppStore.lua
2024.05.01 scheduler.lua
2024.02.11 L_ShellyBridge.lua
2023.03.04 userdata.lua
2018.07.28 backup.lua
2021.03.05 shelly_cgi.lua
2024.02.26 L_openLuup.lua
2022.12.20 whisper.lua
2018.04.23 pop3.lua
2021.01.03 L_VeraBridge.lua
2021.06.14 L_TasmotaBridge.lua
2023.01.06 luup.lua
2024.01.05 devices.lua
2024.02.22 virtualfilesystem.lua
2021.08.21 whisper-edit.lua
2024.02.25 servertables.lua
2018.07.28 sysinfo.lua
2021.05.01 json.lua
2018.03.25 logs.lua
2024.02.12 timers.lua
2021.02.20 requests.lua
2022.12.11 L_Zigbee2MQTTBridge.lua
2016.06.30 compression.lua
2021.04.23 xml.lua
2023.03.03 scenes.lua
2018.01.27 hag.lua
2021.03.25 http_async.lua
2019.08.12 graphite_cgi.lua
2024.01.03 tcp.lua
2024.01.03 io.lua
2024.01.03 server.lua
2016.06.23 rooms.lua
2018.04.12 smtp.lua
2021.04.30 servlet.lua
2024.02.26 console.lua -
full devices reset -
full devices reset -
full devices reset2024-02-26 12:27:36.315 openLuup.wsapi:: using openLuup/console.lua for openLuup
2024-02-26 12:27:36.316 openLuup.wsapi:: using REQUIRE to load CGI openLuup/console.lua
2024-02-26 12:27:36.328 scheduler.context_switch:: ERROR: [dev #0] ./openLuup/panels.lua:69: attempt to call field 'SID' (a nil value)
2024-02-26 12:27:36.328 openLuup.server:: ./openLuup/panels.lua:69: attempt to call field 'SID' (a nil value) -
full devices resetJust updated...
Got
2024-02-26 12:25:03.339 openLuup.wsapi:: using openLuup/console.lua for openLuup
2024-02-26 12:25:03.339 openLuup.wsapi:: using REQUIRE to load CGI openLuup/console.lua
2024-02-26 12:25:03.339 openLuup.wsapi:: can't find WSAPI application entry point -
Forum sysopsFor the chat... found it
Just go under your profile, then theme settings and enable the last checkbox
-
full devices reset -
full devices reset -
full devices reset -
full devices reset -
full devices reset -
full devices reset
