Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
3

3rdStng

@3rdStng
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Caution: zwave-js-ui docker 11.4.0 is broken
toggledbitsT
About 20 hours ago, the author of zwave-js-ui posted build 11.4.0 of that product, and it contains an error and won't start (at all) under docker. The author is aware and working on a fix. In the meanwhile, stick with 11.3.1 or earlier. Ref: Issue 4401
Software
Shelly Wall Display XL
therealdbT
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.
Hardware
Handling Dead Entities and Renamed Entities
PablaP
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).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
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
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
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
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
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.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
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?
Multi-System Reactor
Expose MSR entities
CatmanV2C
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
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I 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?
Multi-System Reactor
Little Bobby tables...
CatmanV2C
...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
General Discussion
Home Assistant Voice TTS is Easy
toggledbitsT
Topic thumbnail image
Home Assistant
Play Audio through Home Assistant Voice Unit
toggledbitsT
Topic thumbnail image
Home Assistant
Home Assistant Voice
CatmanV2C
Has anyone had a play with the local voice control for HA? I've got one on order because... https://www.home-assistant.io/voice-pe/ C
Home Assistant
Unofficial thread for compatibility
tunnusT
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
Multi-System Reactor
Gradually turn on lights.
Tom_DT
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.
Multi-System Reactor
About
Posts
113
Topics
26
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial

  • Rule Set UI bug - RESOLVED
    3 3rdStng

    Docker image "latest-25264-2fbe9217" running on unRAID.
    Running this in Chrome Version 140.0.7339.[128 or 208] with the same results in Edge.

    The UI, when searching within the Rule Set, does not reset/self clear when you click outside of the rule set area.

    To reproduce the issue:
    Click on Rule Sets and type in something within the Search window that does not exist for a rule name. "french" in my example.
    12295a06-0fc3-444d-94c9-9522b26dad42-image.png 397bdea2-670c-4600-8c09-03c169b8b5d9-image.png

    Click outside of the gray area, where my mouse is in the screen grabs, which will close the Rule Sets pop over.
    Click on Rule Sets again and none of the rules will appear. The search term isn't sticky either.
    e0a29f89-abcd-4afa-9bfa-56e5e1871f04-image.png

    The rules won't appear again until you type any character, or press the backspace, in the "Search for rule" field.
    10ddb064-86e1-446c-a69b-a8297f6d90f1-image.png

    Multi-System Reactor

  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
    3 3rdStng

    I don't know if my issue is related or not here. It seems like it should, but I also understand that local expression handling has changed within the last couple of builds. I don't know exactly when my issue started, nor what build I was on. My guess would be Sept 7th as my rule was last "SET" on that date.

    I am running latest-25254-f6a45e41 in a docker on unRAID. The following rule has been in place for years and has been working pretty reliably, until recently.

    image.png

    The Set Reaction is just to turn on the shower exhaust fan. I collapsed it for screenshot space.
    If I change the Local Expressions to: (and in this order)

    MBath_HumityRise = "CurrentHumidity - MBath_prevHumidity"
    MBath_prevHumidity = "CurrentHumidity"
    CurrentHumidity = (some # value like 48)
    

    And then manually change the CurrentHumidity value to 54 (something >=3), the rule triggers. The MBath_HumidityRise value changes to 6 too. Setting the CurrentHumidity to 50, changes the HumidityRise value to -4.

    When I set these expressions back to pull from the device, I see the prevHumidity value change, but the HumidityRise value always stays 0. I set up global expression under different names and watched the values too. In the same order with the Rise expression above the Prev expression, I never see the Rise value change.

    I will see if I have 25260 available for my docker update and test that, but for the life of me I cannot figure out why this rule stopped working.

    EDIT: Updated to 25260 and I'm still not seeing the HumidityRise expression change. I kept my global expressions since they update and refresh on the page, where the local expressons don't appear to do so within the rule. Watching these two expressions, as soon as the prevHumidity sensor updates, the expression turns green. But the Rise expression didn't and still showed 0. In this screen grab, the humidity went from 46 to 45. I would have expected the top expression to show a -1.

    d9db6c59-4592-4acb-8baf-87dc8ae1a5dd-image.png daaa5ce6-8bd1-440c-af88-b3870297a781-image.png

    Multi-System Reactor

  • Feature Request - Wait for an event/trigger within Reaction [Solved with Work Around]
    3 3rdStng

    Refined my actions to include a timeout, just in case someone comes home, but they leave without entering the door.

    Actions:
    Set variable 'lastLockEvent' to "pending entry"
    Turn on porch light
    Turn on driveway lights
    Repeat While:
    -- Triggers:
    -- [lastLockEvent] contains "manually locked"
    -- [OR]
    -- [lastLockEvent] contains "pending entry" (condition sustained for 20 minutes)
    -- Actions:
    -- Delay 10 seconds
    Delay random between 1 to 5 minutes
    Turn off porch light
    Turn off driveway lights

    Multi-System Reactor

  • Feature Request - Wait for an event/trigger within Reaction [Solved with Work Around]
    3 3rdStng

    @toggledbits said in Feature Request - Wait for an event/trigger within Reaction:

    hub variable should appear as an entity with the string_sensor capability, and it should have an extended action (x_hubitat_Variable.setVariable) to let you change the value.

    Worked perfectly!

    Thank you for the feedback and allowing me to type out my thoughts to refine this rule.

    Multi-System Reactor

  • Feature Request - Wait for an event/trigger within Reaction [Solved with Work Around]
    3 3rdStng

    @toggledbits said in Feature Request - Wait for an event/trigger within Reaction:

    As you disclose details, it's beginning to look like you've imagined a solution based on some other product, and you're trying to get Reactor to work its way, instead of doing it "the Reactor way."

    That is very possible. I'm still mentally mapping this out too. And I 100% know that an image of my rule set would really help clear things up. I'm not in a position to get a screenshot at the moment. I'll try to put my thoughts in to text. (scary)

    Rule set as of today:
    Triggers:
    After midnight AND
    Before sunrise AND
    Any Presence Sensor in the group changes from Not Present to Present

    Actions:
    Turn on the porch light
    Turn on the driveway lights
    Wait for a random period of time between 10-15 minutes
    Turn off the porch light
    Turn off the driveway lights

    What I am after is within the Actions only. The Triggers are still the same.

    Actions:
    Turn on the porch light
    Turn on the driveway lights
    Wait until the HE Hub variable "lastDoorLockEvent" reports "Manually locked"
    Wait for a random period of time between 10-15 minutes
    Turn off the porch light
    Turn off the driveway lights

    The waiting until the hub variable is what's potentially causing the issue. When I go to bed, and assuming the door was open, I'll close it and lock it. So the hub variable now reports "Manually locked". If someone arrives after midnight and before sunrise, the variable will still report "Manually locked" since the lock status hasn't changed yet. So theoretically MSR won't wait since it already sees the variable as what it is looking for.

    And as I type this out, I suppose I could insert a set variable into the actions. I honestly haven't looked yet, but can MSR set a variable that is local to the hub only? Not within MSR.

    Actions:
    Turn on the porch light
    Turn on the driveway lights
    Set HE Hub variable "lastDoorLockEvent" to "waiting entry"
    Repeat Until the HE Hub variable "lastDoorLockEvent" reports "Manually locked"
    Wait for a random period of time between 10-15 minutes
    Turn off the porch light
    Turn off the driveway lights

    The entire concept stems from Hubitat's Rule Machine's "Wait for event" that you can define in a rule. I have a couple of these at my remote HE, where I can't run MSR easily.

    Multi-System Reactor

  • Feature Request - Wait for an event/trigger within Reaction [Solved with Work Around]
    3 3rdStng

    Hmm.... Thanks for this, I think I can make it work, but it may take two Repeat While actions. It doesn't appear that I can wait for a change. It's only waiting for a True or False and not a change from Opened to Closed.

    I believe in my rule I would need a "Repeat While the door is false" (open) to wait for someone to actually open the door. Then a "Repeat While the door is true" (closed) to wait for them to close the door and then continuing on the actions to turn off the lights.

    Multi-System Reactor

  • Feature Request - Wait for an event/trigger within Reaction [Solved with Work Around]
    3 3rdStng

    I think this feature request could be accomplished with the use of two or more rules, but it would be great if there was a way to wait for an event or trigger to occur before continuing on in the reactions.

    For example, I have a rule that will turn on some exterior lights if you arrive home after the porch lights have been turned off. Right now this rule randomly will turn off between 5-10 minutes after the person has entered the geofence. On some occasions this 5-10 minutes isn't long enough, say if you are unloading the car or something. I would like to kick off the reaction, but pause it part way through and wait for the door to close and lock, then continue it on. Hubitat Rule Machine has a "Wait for event" option, but I really want to keep all my logic within MSR.

    Multi-System Reactor

  • Free to a new home
    3 3rdStng

    I have an older Vera Plus controller that has been collecting dust for a little while. I know the hardware is no longer supported but I would prefer it to go to a good home vs the eWaste center. No charge, just pay for shipping and it's yours. If you are interested, let me know.

    Vera

  • [RESOLVED] Troubleshooting assistance/ideas needed
    3 3rdStng

    I love it when solutions come to you in your dreams. It dawned on me that my Hub Security on the hub was reset but I still had it enabled on MSR. As soon as I enabled it on my hub and restarted MSR, and literally had a kid walk through the entire house, every motion sensor was tripping back and forth from inactive to active back to inactive.

    Multi-System Reactor

  • [RESOLVED] Troubleshooting assistance/ideas needed
    3 3rdStng

    Running MSR latest-23344-ca53d088 within a Docker.

    My Hubitat (HE) hub suffered almost a 4 day outage from a corrupt backup that failed to restore. During this time I had my MSR docker stopped. Well, I didn't stop it until the the hub had been down for 24 hours. Anyway, I finally got the hub back online this morning and am fixing my MSR rules for everything that was lost. Support needed to purge out the Apps section of the backup.

    So my issue. So far everything I have fixed is working as expected, with the exception of my motion controllers. I can see them go "Active" within my HE, but the Entity within MSR never changes from false to true. I ran through a slew of rooms that have motion sensors and only 1 out of 6 changed to true.

    I removed the sensor I'm testing with from Maker API, restarted MSR, re-added it, restarted MSR, but no difference. I then Deleted it from MSR and restarted MSR. It was re-added, but again no change. How can I go about testing this further to find out why/what is going on?

    Multi-System Reactor

  • [RESOLVED] PSA for Hubitat 2.3.7.x upgrade
    3 3rdStng

    Hmm.. OK. I was re-reading the HubitatController section of the docs and realized that I removed my Hub Information device a couple of months back. Perhaps that was part of the issue? I put it back and then upgraded to 2.3.7.140. So far so good. Hopefully it was the missing Hub Information device, or perhaps my HE was just having an off day? I'll monitor things and report back if there is any issues. Thanks all.

    Multi-System Reactor

  • [RESOLVED] PSA for Hubitat 2.3.7.x upgrade
    3 3rdStng

    Same here. Docker image latest-23344-ca53d088. And I am aware that he would need more details. I'm not reporting this has a bug since he hasn't blessed 2.3.7 yet. I actually upgraded earlier in the day and some rules were triggering just fine. It wasn't until the evening when a lot of my logic was SUPER slow, delayed, or not working at all. Which would make sense if MSR couldn't chat with the hub.
    I don't subscribe to the remote backups, so I don't think that bug will effect me. But good to know, thanks.

    Multi-System Reactor

  • [RESOLVED] PSA for Hubitat 2.3.7.x upgrade
    3 3rdStng

    If you are thinking about upgrading your Hubitat Elevation hub from 2.3.6 to 2.3.7, and you are using MSR.... wait! I was trying to resolve a different issue with the HE and didn't even think twice about how MSR would react. Well... MSR was not happy and was complaining that the events feed had become unresponsive. And my automations were not working either. I have since reverted back to 2.3.6 and will happily wait for @toggledbits to do his magic.

    5a147634-6008-4d4c-a698-c22f6936ee0c-image.png

    Multi-System Reactor

  • Possible Typo/Correction in Manual
    3 3rdStng

    Hi @toggledbits,

    I had an idea about my Echo speaking which windows or doors are open when an announcement is made reminding the family to close things up when it is hotter outside. Let me start off by saying I'm not great with expressions and in no way any programmer. To get started I read the How To: Expressions and what do you know, you have an example on how to do exactly what I am looking for. However I think I found a typo/correction that may be needed? Again, not a programmer here.

    In the How To: Expressions with Entities section you state the new expression called open_perimeter_doors and give the example with the end of null : doorid. In the description you state you order them this way because when the door_sensor.state is true, the door is closed/secure. I have a few different brands of contact sensors and all of them are just the opposite. They are true when they are open and false when they are closed. For me, this was an easy fix. I swapped them.

    What blew my mind and took a bit of thinking was a little further down in your example of joining the getEntity ID and getName.

    join( each doorid in perimeter_doors: do
               e = getEntity( doorid ),
               e.attributes.door_sensor.state ? null : e.getName()
           done
        , ", " )
    

    The "e.getName()" in the example would cause the expression to never evaluate. I needed to change this to "e.name". With e already being set as "getEntity( doorid )", only name was needing to be appended. In your example you are appending ".getName()", resulting in "getEntity( doorid).getName()"

    Again, NOT a programmer, but perhaps a stale How To example from before a major update to the expression logic? Just wanted to share my results in case the manual does need an update.

    295ee66b-f5a2-437f-8686-4a835db6c02d-image.png

    Multi-System Reactor

  • Reactor Ex Machina
    3 3rdStng

    I'm not in need of it. As I was moving off Lighting Director I just happened to notice they had a max number of lights. I think the OG DeusExMachina did too. I think how you have it would be more lifelike. Especially when you couple of a few specific OFF rules so the lights turn off faster than 10-20 minutes.

    Multi-System Reactor

  • Function sanity check please
    3 3rdStng

    MSR: latest-23078-d592d400
    --Docker image on unRAID
    Hubitat C-7: 2.3.5.121

    I'm always looking to simplify my rules and reactions and having finally grasped the Array function with a loop of perform.Action, I decided to re-write one of my rules. The kids like to play music on the Echo devices at a high volume, and I also have TTS loud during the night if a door/window are to open. In order to not have her yell at me later, I wrote a rule that resets the volume on each Echo device to a level of 2. However having 7 Echo's, there are many steps in my Reaction. Set the volume on device 1, wait a few seconds, set the volume on the device 2, wait, and so on.

    Sample snippet of the set reaction: (This works BTW.)
    2f5aafc0-bf97-4622-b41c-60649253590e-image.png

    To make it better, I created an array of the devices and want to run a perform.Action command. Less steps with the same results. Or so I thought. The end result is now a volume level of 0 or 1. I think the Echo gets confused. Either way, not a level of 2 like I was expecting. BTW volume 1 across the room is too low, in case you were wondering.

    New set reaction:
    da62dfb0-f433-4fc6-897f-d38c190f8c9a-image.png

    ${{ each device in Echo_devices: performAction( device, 'volume.set', { level:0.20 } ); 0 }}
    

    The av_transport.stop works as expected. The issue is with the volume.set, {level:0.20}. Do I have something wrong in my command?

    Global expressions used:
    8d054dca-20dc-4e97-aa6d-4537c9da4ea9-image.png

    e3e388d3-f18e-4744-8eee-432234161739-image.png

    Multi-System Reactor

  • Reactor Ex Machina
    3 3rdStng

    @kellyjelly32 Is there a way to specify how many lights should be on at one time? I tested REM last night and the most on at the same time appeared to be two. I'm fine with this, but curious if there was an option or way to adjust it. Again, thanks for sharing your logic.

    Multi-System Reactor

  • Reactor Ex Machina
    3 3rdStng

    Ahh... I miss that app. Probably one of my favorites from my Vera days. The "Lighting Director" app on Hubitat just isn't the same.

    Thanks for posting your setup @kellyjelly32. I've mocked this into my MSR and if all works well, DeusExMachina returns. Well kinda

    Multi-System Reactor

  • [RESOLVED] How quickly should logs rotate?
    3 3rdStng

    @toggledbits Awesome. Thank you.

    I know you know, but for others, the rule ID is also noted in the logs. Makes it easier to copy and paste without having to look up the ID within the GUI.
    f5fc7a07-2b33-4574-b3ec-d2dca45c70f6-image.png

    Multi-System Reactor

  • [RESOLVED] How quickly should logs rotate?
    3 3rdStng

    Thank you. I changed all my rules that had a presence sensor written in them. As well as a few other rules that have an app that phones home every minute. Just restarted MSR for good measure and can see a different. I'm over 30 minutes right now between .log and .log.1.

    Multi-System Reactor
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved