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.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. MSR Set Reaction not working anymore
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
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
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
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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.
Multi-System Reactor
Can't customize home page
G
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.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@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.
Multi-System Reactor

MSR Set Reaction not working anymore

Scheduled Pinned Locked Moved Multi-System Reactor
6 Posts 2 Posters 699 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    basai
    wrote on last edited by
    #1

    Iron: QNAP NAS
    Running MSR and HAAS on Docker (QNAP Container Station)
    Reactor (Multi-hub) stable-22203-81a2f3cc
    Home Assistant Core 2022.6.7
    Vera 1.7.5186 (7.31)
    Config files are stored in shared volumes on the NAS.
    Office light in example is joined to Vera-Plus

    Hello all,

    I decided to upgrade MSR to latest-amd64. It wasn’t until afterwards that I noticed all rulesets broken. So unfortunately I’m not sure if this was already broken before or I broke it after upgrading. Yes poor judgement on my part for being complacent.

    Never the less, this is broken globally across all rulesets, even though I can see the triggers change to “True” (Turn green).

    For this example, I have a boolean helper toggle in HAAS called “TV MODE HAAS SW”.

    When toggled ‘on’, MSR should turn my Vera office light OFF and it doesn’t, but if I manually select the play button to the right of the line in the Set Reaction, it executes properly and turns off the Vera office light.

    The MSR Rule does not have any Constraints set.

    I can see in MSR it recognizes the state changes yet doesn’t execute the “Set Reaction”.

    Any help greatly appreciated.

    Log files from reactor.log and screen shots to follow:

    Reactor.log when toggling the haas helper, Set Reaction doesn’t execute.

    [stable-22203]2022-10-02T21:21:34.799Z <Rule:INFO> TV MODE ON (Rule#rule-l2hvuz8r) starting evaluation; because entity-changed Entity#hass>input_boolean_tv_mode
    [stable-22203]2022-10-02T21:21:34.800Z <Rule:INFO> TV MODE ON (Rule#rule-l2hvuz8r) evaluated; rule state transition from RESET to SET!
    [stable-22203]2022-10-02T21:21:34.819Z <Rule:INFO> TV MODE ON (Rule#rule-l2hvuz8r) evaluation complete
    [stable-22203]2022-10-02T21:21:34.820Z <Engine:INFO> Enqueueing "TV MODE ON<SET>" (rule-l2hvuz8r:S)
    [stable-22203]2022-10-02T21:21:34.835Z <Engine:NOTICE> Starting reaction TV MODE ON<SET> (rule-l2hvuz8r:S)
    [stable-22203]2022-10-02T21:21:34.835Z <Engine:INFO> TV MODE ON<SET> all actions completed.
    

    Reactor.log when manually triggering the Set Reaction with the play button which correctly turns off the light

    [stable-22203]2022-10-02T21:23:25.035Z <HassController:null> HassController#hass: sending payload for power_switch.off on Entity#hass>light_office_86 action: [Object]{ "type": "call_service", "service_data": { "entity_id": "light.office_86" }, "domain": "homeassistant", "service": "turn_off" }
    

    When toggled ON
    toggled_on.png

    Rule config screen
    tv_mode_config.png

    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #2

      I'm seeing a lot of conflicting information in your report. 22203 is not latest, it's the older stable (and your log entries confirm this as well). Your office light being turned off in the SET reaction you show is on Hass, not on Vera.

      I would upgrade to the true latest 22274 for starters; I won't really spend time troubleshooting on anything but the current (latest development build) version (i.e. if you're having a problem, make sure you test on the latest version before seeking help -- see the posting guidelines).

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      B 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        I'm seeing a lot of conflicting information in your report. 22203 is not latest, it's the older stable (and your log entries confirm this as well). Your office light being turned off in the SET reaction you show is on Hass, not on Vera.

        I would upgrade to the true latest 22274 for starters; I won't really spend time troubleshooting on anything but the current (latest development build) version (i.e. if you're having a problem, make sure you test on the latest version before seeking help -- see the posting guidelines).

        B Offline
        B Offline
        basai
        wrote on last edited by
        #3

        @toggledbits

        Apologies for the confusion.

        I was trying to indicate, although poorly, that I did install 'latest' at first which didn't correct the problem and then opted to go with 'stable' thinking that was the better choice.

        As far as the MSR Set Reaction using haas vs vera per my report, I was testing both and neither worked when the rule is triggered, however the light does turn off when I manually select the play button next to the Set Reaction Rule for either the set haas or vera case. Unfortunately I neglected to reflect that correctly in my report and hence the mismatch / confusion

        HTH
        -bh

        1 Reply Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #4

          There are quite a few people on latest, including myself on three systems. If there was a problem with reactions, I think there would be more than one report. Please try reinstalling latest, restart, and then confirm in the log entries that you have the correct version running (as of this weekend that would be latest-22274). I suspect your attempted upgrade didn't go as planned.

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          1 Reply Last reply
          0
          • B Offline
            B Offline
            basai
            wrote on last edited by
            #5

            Howdy, Honestly I didn’t really think this was an MSR Set Reaction pandemic and was more than likely a locally induced error of some sort.

            This is fixed now based on something you said in your last reply suspecting an update problem which pulled me out of a loop and put me on the right path.

            Summary: Upgrading to latest-22274 fixed the problem but QNAP’s Container Station using the Docker Hub Tab would only download and install latest-22179. Not sure if this is a QNAP bug or feature.

            Detail: For the benefit of any QNAP NAS users out there I’ll explain.

            Using QNAP NAS’s Container Station, searching for “reactor” in the “Docker Hub” tab I would select "latest-amd64”, but it would only install latest-22179 and not the actual latest-22274. Picking up the NAS and shaking it a few times, turning it off and on again, or putting more quarters in it didn't help.

            In the past I didn’t find a need to do the following since I believe Container Station should be doing this all by self, and if not, user error on my part.

            So to fix this I ssh’d to the QNAP NAS CLI and ran.

            docker pull toggledbits/reactor:latest-amd64
            

            Which returned the following, I was feeling optimistic seeing the "pull completes' "

            [basai@basai ~]$ docker pull toggledbits/reactor:latest-amd64
            latest-amd64: Pulling from toggledbits/reactor
            8663204ce13b: Already exists 
            8c392e9e905c: Already exists 
            36ce72f2f129: Already exists 
            2e8529c47e46: Already exists 
            26c2865d7fe4: Pull complete 
            b45a2cf2a065: Pull complete 
            ac02d13d40de: Pull complete 
            2bd82a6d3d8c: Pull complete 
            Digest: sha256:a192e403200a62664cec40f40f61499218ac9a0cae3b8ed8390f87679505105d
            Status: Downloaded newer image for toggledbits/reactor:latest-amd64
            docker.io/toggledbits/reactor:latest-amd64
            [basai@basai ~]$
            

            After this completed, now when I went to create a new docker by going into container station, searching for “reactor” in the “Docker Hub Tab” and selected “latest-amd64” it correctly installed latest-22274 and also pre-populated the NODE_PATH variable correctly which wasn’t happening before.

            Problem solved and MSR is working as expected again.

            Thanks you for your help, MSR Rocks!
            -bh

            toggledbitsT 1 Reply Last reply
            0
            • B basai

              Howdy, Honestly I didn’t really think this was an MSR Set Reaction pandemic and was more than likely a locally induced error of some sort.

              This is fixed now based on something you said in your last reply suspecting an update problem which pulled me out of a loop and put me on the right path.

              Summary: Upgrading to latest-22274 fixed the problem but QNAP’s Container Station using the Docker Hub Tab would only download and install latest-22179. Not sure if this is a QNAP bug or feature.

              Detail: For the benefit of any QNAP NAS users out there I’ll explain.

              Using QNAP NAS’s Container Station, searching for “reactor” in the “Docker Hub” tab I would select "latest-amd64”, but it would only install latest-22179 and not the actual latest-22274. Picking up the NAS and shaking it a few times, turning it off and on again, or putting more quarters in it didn't help.

              In the past I didn’t find a need to do the following since I believe Container Station should be doing this all by self, and if not, user error on my part.

              So to fix this I ssh’d to the QNAP NAS CLI and ran.

              docker pull toggledbits/reactor:latest-amd64
              

              Which returned the following, I was feeling optimistic seeing the "pull completes' "

              [basai@basai ~]$ docker pull toggledbits/reactor:latest-amd64
              latest-amd64: Pulling from toggledbits/reactor
              8663204ce13b: Already exists 
              8c392e9e905c: Already exists 
              36ce72f2f129: Already exists 
              2e8529c47e46: Already exists 
              26c2865d7fe4: Pull complete 
              b45a2cf2a065: Pull complete 
              ac02d13d40de: Pull complete 
              2bd82a6d3d8c: Pull complete 
              Digest: sha256:a192e403200a62664cec40f40f61499218ac9a0cae3b8ed8390f87679505105d
              Status: Downloaded newer image for toggledbits/reactor:latest-amd64
              docker.io/toggledbits/reactor:latest-amd64
              [basai@basai ~]$
              

              After this completed, now when I went to create a new docker by going into container station, searching for “reactor” in the “Docker Hub Tab” and selected “latest-amd64” it correctly installed latest-22274 and also pre-populated the NODE_PATH variable correctly which wasn’t happening before.

              Problem solved and MSR is working as expected again.

              Thanks you for your help, MSR Rocks!
              -bh

              toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by
              #6

              @basai said in MSR Set Reaction not working anymore:

              putting more quarters in it didn't help

              LOL! That inflation is hitting everything, isn't it?

              Glad it worked out!

              Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

              1 Reply Last reply
              1
              • toggledbitsT toggledbits locked this topic on
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              Recent Topics

              • Caution: zwave-js-ui docker 11.4.0 is broken
                toggledbitsT
                toggledbits
                0
                2
                32

              • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                toggledbitsT
                toggledbits
                0
                68
                4.8k

              • Shelly Wall Display XL
                therealdbT
                therealdb
                2
                6
                94

              • Handling Dead Entities and Renamed Entities
                PablaP
                Pabla
                0
                5
                84

              • Strange behavior for MQTT templates using payload and attributes
                toggledbitsT
                toggledbits
                0
                6
                133

              • [MSR] reactor-mqtt-contrib package for additional MQTT templates
                therealdbT
                therealdb
                1
                46
                8.2k

              • HA 2025.9.4 Supported Yet?
                toggledbitsT
                toggledbits
                0
                2
                87

              • The reaction stopped working (Google Nest max playing a video)
                toggledbitsT
                toggledbits
                0
                7
                356

              • Rule Set UI bug - RESOLVED
                toggledbitsT
                toggledbits
                1
                2
                234

              • [Reactor] Copy&Paste of Rules
                therealdbT
                therealdb
                0
                1
                301

              • [Reactor] Help with screne controller cycling logic
                toggledbitsT
                toggledbits
                0
                5
                404

              • Stop the MSR by an external switch on Hubitat.
                Tom_DT
                Tom_D
                0
                6
                739
              Powered by NodeBB | Contributors
              Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
              • Login

              • Don't have an account? Register

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