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)
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor

Reactor Ex Machina II (2023-July Update)

Scheduled Pinned Locked Moved Multi-System Reactor
3 Posts 3 Posters 549 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.177
      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

      *HAOS
      Core 2026.1.1
      w/ HA Connect ZWA-2
      FW: v1.1
      SDK: v7.23.1

      *Prod MSR in docker/portainer
      MSR: latest-26011-c621bbc7
      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

        • Oddness in Copy/Move of Reactions
          G
          gwp1
          0
          1
          32

        • [Solved] function isRuleEnabled() issue
          CrilleC
          Crille
          0
          4
          49

        • [Reactor] Problem with Global Reactions and groups
          therealdbT
          therealdb
          0
          3
          69

        • Possible feature request 2?
          CatmanV2C
          CatmanV2
          0
          3
          49

        • Reactor (Multi-System/Multi-Hub) Announcements
          toggledbitsT
          toggledbits
          5
          133
          79.6k

        • Genuinely impressed with Zigbee and HA / Reactor
          CatmanV2C
          CatmanV2
          1
          9
          345

        • Copying a global reaction
          toggledbitsT
          toggledbits
          0
          3
          95

        • [HowTo] Using HABridge with Reactor
          CatmanV2C
          CatmanV2
          0
          9
          415

        • [Reactor] Bug when sending MQTT boolean payloads
          toggledbitsT
          toggledbits
          0
          4
          151

        • Difficulty defining repeating annual period
          G
          gwp1
          0
          5
          122

        • Need help with sequence
          therealdbT
          therealdb
          0
          3
          74

        • Possible feature request?
          therealdbT
          therealdb
          0
          5
          182
        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