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. Reactor Ex Machina II (2023-July Update)
[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

Reactor Ex Machina II (2023-July Update)

Scheduled Pinned Locked Moved Multi-System Reactor
3 Posts 3 Posters 404 Views 4 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.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #1

    Here is an updated Reactor Ex Machina that works with new features of Reactor that have been added since the earlier post. It now can be done a single rule, thanks to the Repeat...While action in reactions.

    The easiest way to get this new version is to grab the rule data (bottom of this post) and save it with the name rule-reactorexmachina.json (exactly this; no changes) in your storage/rules/ subdirectory. Then restart Reactor. After restart, you will find the Reactor Ex Machina II rule in a Recovered Rules rule set. You can move it to whatever other rule set you like. You may see an error for the REM_lights variable (global) missing; don't worry about that right now, we'll handle that in a moment.

    To configure it, you need to do two things (and maybe a third optional thing):

    1. Create a global variable/expression called REM_lights that defines an array containing the canonical IDs of the lights you want it to manipulate. This is as it was for the previous version of REM, so you may already have that, and what you have is probably fine. If you don't have it, your expression should look like this to define the array of lights:

    195928f1-cc52-4b93-987a-afc2f7e0650b-image.png

    1. You need to configure the conditions in the Triggers of the new rule to be true when you want lights to randomly cycle. This is called the active period, and the default configuration is from 30 minutes before sunset to 23:30 (just as a placeholder).

    2. (OPTIONAL) Change the timing by modifying the two Delay actions. The Delay action in the Set Reaction is for when lights are being toggled while in the active period. In the Reset Reaction, the delay controls the timing of lights shutting off at the end of the active period (i.e. to simulate going to bed, which may be more rapid). The formula for computing the delay is random()*range + minimum (seconds). As an example, random()*840 + 60 would give a random delay of 60 to 900 (840+60=900) seconds (which is 1 to 15 minutes) between actions.

    Operation is pretty straightforward and greatly simplified by the new Reactor features. When the rule is SET (i.e. triggers true, in the active period), the Set Reaction starts an infinite loop that picks a random light from REM_lights and toggles it, then delays a random amount of time. That continues until the triggers are no longer true and the rule RESETs. The Reset Reaction then runs (automatically cancelling the Set Reaction task), turning off a light that is currently on (from among those in REM_lights again) and then delaying, repeating until all lights are off.

    Here's the rule JSON data:

    {
        "id": "rule-reactorexmachina",
        "container": "rules",
        "value": {
            "id": "rule-reactorexmachina",
            "serial": 44,
            "triggers": {
                "type": "group",
                "id": "trig",
                "op": "or",
                "conditions": [
                    {
                        "type": "group",
                        "id": "grp13uaq1lz",
                        "op": "and",
                        "conditions": [
                            {
                                "id": "cond13uaq1m0",
                                "type": "comment",
                                "data": {
                                    "comment": "Here, put in the rules for when random lights should cycle... time of day, house mode, virtual switch/input boolean state, etc."
                                }
                            },
                            {
                                "id": "cond13uaq1m2",
                                "type": "sun",
                                "data": {
                                    "tzo": 240,
                                    "op": "after",
                                    "start": "sunset",
                                    "start_offset": -30
                                }
                            },
                            {
                                "id": "cond13uaq1m3",
                                "type": "trange",
                                "data": {
                                    "op": "before",
                                    "start": {
                                        "hr": 18,
                                        "min": 45
                                    },
                                    "tzo": 240,
                                    "end": {}
                                }
                            }
                        ],
                        "editor_version": 23130,
                        "name": "Active Period"
                    }
                ],
                "editor_version": 23130,
                "disabled": true
            },
            "constraints": {
                "type": "group",
                "id": "cons",
                "op": "and",
                "conditions": []
            },
            "expressions": {
                "dummy": {
                    "name": "dummy",
                    "expr": "",
                    "index": 0
                },
                "lights_on": {
                    "name": "lights_on",
                    "expr": "each light in REM_lights: do e=getEntity( light ), e.attributes.power_switch.state ? e.canonical_id : null done",
                    "index": 1
                }
            },
            "name": "Reactor Ex Machina II",
            "react_set": {
                "id": "rule-reactorexmachina:S",
                "actions": [
                    {
                        "id": "rule-reactorexmachina:S-13ua1p95",
                        "type": "while",
                        "actions": [
                            {
                                "id": "13u9qo3b",
                                "type": "comment",
                                "data": {
                                    "comment": "Toggle a random light in the list of lights"
                                }
                            },
                            {
                                "id": "8wul3as",
                                "type": "setvar",
                                "data": {
                                    "var": "dummy",
                                    "rule": "rule-reactorexmachina",
                                    "value": "${{ performAction( REM_lights[ floor( random() * len( REM_lights ) ) ], 'toggle.toggle', {} ) }}",
                                    "reeval": false
                                }
                            },
                            {
                                "id": "13u9py8u",
                                "type": "comment",
                                "data": {
                                    "comment": "Delay random to next light toggle"
                                }
                            },
                            {
                                "id": "8wul3ew",
                                "type": "delay",
                                "data": {
                                    "delay": "${{ random()*840 + 60 }}"
                                }
                            }
                        ],
                        "constraints": {
                            "id": "13ua1p95-cons",
                            "name": "Active",
                            "type": "group",
                            "op": "and",
                            "conditions": [
                                {
                                    "id": "cond13uaycbu",
                                    "type": "comment",
                                    "data": {
                                        "comment": "The below is a dummy condition that's always true if your REM is configured (i.e. it has lights to operate on)"
                                    }
                                },
                                {
                                    "id": "cond13ua1smv",
                                    "type": "var",
                                    "data": {
                                        "var": "REM_lights",
                                        "op": "notempty"
                                    }
                                }
                            ],
                            "editor_version": 23130
                        }
                    }
                ],
                "rule": "rule-reactorexmachina",
                "editor_version": 23130
            },
            "react_reset": {
                "id": "rule-reactorexmachina:R",
                "actions": [
                    {
                        "id": "rule-reactorexmachina:R-13uagam7",
                        "type": "while",
                        "actions": [
                            {
                                "id": "13uagcg8",
                                "type": "comment",
                                "data": {
                                    "comment": "Turn off a light that's on. Then delay random to next light off. This continues until all lights are off (condition above)."
                                }
                            },
                            {
                                "id": "13uagut5",
                                "type": "setvar",
                                "data": {
                                    "var": "dummy",
                                    "rule": "rule-reactorexmachina",
                                    "value": "${{ performAction( lights_on[0], \"power_switch.off\" ) }}",
                                    "reeval": false
                                }
                            },
                            {
                                "id": "13uah4lh",
                                "type": "delay",
                                "data": {
                                    "delay": "${{ random()*270 + 30 }}"
                                }
                            }
                        ],
                        "constraints": {
                            "id": "13uagam7-cons",
                            "name": "Shutdown",
                            "type": "group",
                            "op": "and",
                            "conditions": [
                                {
                                    "id": "cond13uagex0",
                                    "type": "var",
                                    "data": {
                                        "rule": "rule-reactorexmachina",
                                        "var": "lights_on",
                                        "op": "notempty"
                                    }
                                }
                            ],
                            "editor_version": 23130
                        }
                    }
                ],
                "rule": "rule-reactorexmachina",
                "editor_version": 23130
            },
            "ruleset": "rs-remII"
        },
        "tss": 1689548165797,
        "tsc": 1689548165797
    }
    

    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
    3
    • G Offline
      G Offline
      gwp1
      wrote on last edited by
      #2

      @toggledbits Being the impetus for recreating this from the old days of Vera I love this "REM: TNG".

      *Hubitat C-7 2.4.3.123
      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

      *HASS 2025.9.4
      w/ ZST10-700 fw 7.18.3

      *Prod MSR in docker/portainer
      MSR: latest-25264-2fbe9217
      MQTTController: 25139
      ZWave Controller: 25139

      1 Reply Last reply
      0
      • therealdbT Offline
        therealdbT Offline
        therealdb
        wrote on last edited by
        #3

        very cool. any plans for an import/export feature in the UI?

        --
        On a mission to automate everything.

        My MS Reactor contrib
        My Luup Plug-ins

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


        Recent Topics

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

        • Do you Matter?
          CatmanV2C
          CatmanV2
          0
          2
          62

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

        • Shelly Wall Display XL
          therealdbT
          therealdb
          2
          6
          160

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

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

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

        • HA 2025.9.4 Supported Yet?
          toggledbitsT
          toggledbits
          0
          2
          108

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

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

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

        • [Reactor] Help with screne controller cycling logic
          toggledbitsT
          toggledbits
          0
          5
          422
        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