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)
[MSR] Native fan capabilty
therealdbT
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable. I have a couple of them. ie, this is from ESPHome via HASS. x_hass.domain="fan" x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan" x_hass.floor_id=null x_hass.services=["fan","esphome"] x_hass.source="esphome" x_hass.state="off" x_hass_attr.friendly_name="Seashell Hood Ventilation Fan" x_hass_attr.percentage=50 x_hass_attr.percentage_step=25 x_hass_attr.preset_mode="" x_hass_attr.preset_modes=[] x_hass_attr.supported_features=49 Thanks.
Multi-System Reactor
[MSR] Rule do not fire
therealdbT
Topic thumbnail image
Multi-System Reactor
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
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
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
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor

Reactor Ex Machina II (2023-July Update)

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

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

      *Prod MSR in docker/portainer
      MSR: latest-26193-8dd8f854
      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

        • [MSR] Native fan capabilty
          therealdbT
          therealdb
          1
          3
          119

        • [MSR] Rule do not fire
          therealdbT
          therealdb
          0
          4
          148

        • Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
          N
          noelab
          0
          8
          226

        • DynamicGroupController and attributes
          toggledbitsT
          toggledbits
          1
          9
          318

        • Reactor (Multi-System/Multi-Hub) Announcements
          toggledbitsT
          toggledbits
          5
          149
          139.6k

        • Unofficial thread for compatibility
          tunnusT
          tunnus
          2
          2
          757

        • Ooops - Deleted Reactor Ex Machina II
          toggledbitsT
          toggledbits
          0
          2
          96

        • Bail out of failed reaction?
          T
          tamorgen
          0
          3
          169

        • Arming Envisalink panel from MSR
          T
          tamorgen
          0
          7
          394

        • [Solved] DynamicGroupController updating members issue
          CrilleC
          Crille
          0
          5
          284

        • Upgrade Issues
          T
          tbully
          0
          9
          421

        • [SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
          toggledbitsT
          toggledbits
          0
          10
          543
        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