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. First post
Reverse proxy & API ACL
tunnusT
I'm trying to allow anonymous access from a local network to /api/v1/log, but the problem now with the reverse proxy configuration is that this access is open via proxy to the internet. At least I wasn't able to configure ACL so that only an access from a local network would be permitted. reactor.yaml: baseurl: "http://192.168.1.12:8111" proxy_baseurl: "https://external.com:30000" trusted_proxy: "192.168.1.12" Local traffic would originate from 192.168.1.0/24 network. Synology is acting as a reverse proxy and hosting MSR as a docker container (which has its own network and IP 172.18.0.5). MSR build is latest-26298-fbb75fb8 users.yaml: - url: "/api/v1/log" method: "GET" source_ip: 172.18.0.0/24 allow: true Using the above ACL works, but it enables access via proxy also. If I use source_ip: 192.168.1.0/24, then it doesn't work either locally or remotely. So I'm kinda lost what should I use as source_ip in this case?
Multi-System Reactor
Grouped devices
G
I've seen many of you using Dynamic Group Controller. I'm using it myself for monitoring device battery levels. I've read and re-read the Dynamic Group Controller docs and still cannot come to an answer for my question so let me paint my scenario: I've migrated from EchoSpeaks in Hubitat ('cause borked and seemingly unmaintained) to Alexa Devices in Home Assistant ('cause not borked in 2026.11.0) to be able to send TTS to my Echo devices. In EchoSpeaks I could create groups. Sweet. In Alexa Devices I don't seem to be able to do so. As such, my thought was "wait - isn't there a way in MSR?" Is this an effective scenario that Dynamic Group Controller can be used for?
Multi-System Reactor
MFA
T
Topic thumbnail image
Multi-System Reactor
Login protections
tunnusT
Topic thumbnail image
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
Reactor Inspect - a small read-only helper panel for MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Reactor Build 26284 stuck at Loading Reactor UI
T
Topic thumbnail image
Multi-System Reactor
MSR with reverse proxy
tunnusT
I'm trying to use MSR via reserve proxy in Synology DSM, but MSR page does not load https://<public ip>:30000/reactor/en-US/ At the same time logging page loads normally https://<public ip>:30000/api/v1/log I thought maybe authentication was messing it up, but there was no deny entries in the log, and also disabling authentication did not make any difference. For this use case VPN is not an option (that works, but as said not an option for this particular use case). Any ideas what could cause this? MSR build latest-26242-28d69aa8, Chrome browser
Multi-System Reactor
Missing attribute after upgrade
3
Topic thumbnail image
Multi-System Reactor
[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
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

First post

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 2 Posters 2.5k 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.
  • T Offline
    T Offline
    tamorgen
    wrote on last edited by
    #1

    Good morning all,
    First, I just wanted to say hi and introduce myself. I've been using a Vera Plus for about 8 years now, and the luup based Reactor for two or three. Before that I used PLEG for my home logic on Vera.

    I've been monitoring the evolution of Ezlo, and I'm starting to consider making the jump to it. After discussing with others over on the Vera/Ezlo community, it seems that it's not an all or nothing switch, particularly with the Patrick's MSR, so I'm joining here today to start taking a look at it.

    Anyway, that's my basic post. Look forward to playing with MSR in the near future.

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

      Welcome. You'll find some differences between R4V (Reactor for Vera) and MSR, but also a lot of familiarity. Make sure to read the Concepts and Terminology section of the documentation for some background. The other parts of the docs will help you through the details.

      Also, if you have problems or questions, be sure you've read the posting guidelines beforehand. The goal is to give as much information up front as possible, and do your homework first. The post explains it.

      Have you decided on a platform to run MSR? Raspberry Pi? VM? Other small host? Are you familiar/comfortable with docker, or are you more likely to install Reactor directly (aka bare-metal)?

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

      T 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        Welcome. You'll find some differences between R4V (Reactor for Vera) and MSR, but also a lot of familiarity. Make sure to read the Concepts and Terminology section of the documentation for some background. The other parts of the docs will help you through the details.

        Also, if you have problems or questions, be sure you've read the posting guidelines beforehand. The goal is to give as much information up front as possible, and do your homework first. The post explains it.

        Have you decided on a platform to run MSR? Raspberry Pi? VM? Other small host? Are you familiar/comfortable with docker, or are you more likely to install Reactor directly (aka bare-metal)?

        T Offline
        T Offline
        tamorgen
        wrote on last edited by
        #3

        @toggledbits said in First post:

        Welcome. You'll find some differences between R4V (Reactor for Vera) and MSR, but also a lot of familiarity. Make sure to read the Concepts and Terminology section of the documentation for some background. The other parts of the docs will help you through the details.

        Also, if you have problems or questions, be sure you've read the posting guidelines beforehand. The goal is to give as much information up front as possible, and do your homework first. The post explains it.

        Have you decided on a platform to run MSR? Raspberry Pi? VM? Other small host? Are you familiar/comfortable with docker, or are you more likely to install Reactor directly (aka bare-metal)?

        Hi Patrick,
        Thanks for the warm welcome!

        I've actually just installed Reactor on my home server. I have essentially a file server that I also use for various other tasks, such as Pihole, dhcp managment, PlexMediaSever, running Fedora Server 36. I installed using the bare metal method

        From what I've read, MSR will give me an easier upgrade to Ezlo path than anything else. Ezlo is still missing too many things that I'm dependent on Vera to make a complete switch. I have a working Vera, so MSR should allow me to slowly transition at my own pace, until Ezlo can do it all, and eventually retire Vera.

        1 Reply Last reply
        0
        • T Offline
          T Offline
          tamorgen
          wrote on last edited by tamorgen
          #4

          @toggledbits
          Well, like I said, I got it installed, but it would appear there is an environmental variable that isn't correct.

          reactor.service: Failed at step EXEC spawning /usr/local/lib/nodejs/bin/node: No such file or directory

          It worked when I ran NODE_PATH=$(pwd) node app.js, but after I installed it as a service, it did not.

          Any advice on how I can find the correct path?

          Note: I used the following command to install:

          sudo dnf install nodejs-1:16:140.-2.fc36

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

            The pwd command returns the path of the current directory, which in that command is the directory where app.js lives and you have Reactor installed. Just make sure your Environment line in your service file contains that fully-qualified path.

            Here's the sample service file that you can modify. I'm not sure how you generated yours. You can also find this file in the tools directory in your Reactor install.

            # THIS IS A SAMPLE SYSTEMD SERVICE CONFIGURATION FILE FOR REACTOR.
            # Modify the WorkingDirectory, Environment, and User values below
            # to suit your system configuration. Also modify ExecStart with
            # the correct path to the "node" executable, if it has not been
            # installed in the system binary directories.
            # Then place the file in /etc/systemd/system or whatever other 
            # directory is normal for your system (remove the -example) from
            # the end of the name. You will need root privilegess to do this.
            # Then run:
            #     sudo systemctl daemon-reload
            #     sudo systemctl start reactor
            #
            [Unit]
            Description=Multi System Reactor
            After=network.target
            
            [Service]
            Type=simple
            User=myuser
            WorkingDirectory=/home/myuser/reactor
            Environment=NODE_PATH=/home/myuser/reactor
            ExecStart=/usr/local/lib/nodejs/bin/node app -p
            Restart=on-failure
            RestartSec=5s
            
            [Install]
            WantedBy=multi-user.target
            

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

            T 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              The pwd command returns the path of the current directory, which in that command is the directory where app.js lives and you have Reactor installed. Just make sure your Environment line in your service file contains that fully-qualified path.

              Here's the sample service file that you can modify. I'm not sure how you generated yours. You can also find this file in the tools directory in your Reactor install.

              # THIS IS A SAMPLE SYSTEMD SERVICE CONFIGURATION FILE FOR REACTOR.
              # Modify the WorkingDirectory, Environment, and User values below
              # to suit your system configuration. Also modify ExecStart with
              # the correct path to the "node" executable, if it has not been
              # installed in the system binary directories.
              # Then place the file in /etc/systemd/system or whatever other 
              # directory is normal for your system (remove the -example) from
              # the end of the name. You will need root privilegess to do this.
              # Then run:
              #     sudo systemctl daemon-reload
              #     sudo systemctl start reactor
              #
              [Unit]
              Description=Multi System Reactor
              After=network.target
              
              [Service]
              Type=simple
              User=myuser
              WorkingDirectory=/home/myuser/reactor
              Environment=NODE_PATH=/home/myuser/reactor
              ExecStart=/usr/local/lib/nodejs/bin/node app -p
              Restart=on-failure
              RestartSec=5s
              
              [Install]
              WantedBy=multi-user.target
              
              T Offline
              T Offline
              tamorgen
              wrote on last edited by
              #6

              @toggledbits

              Patrick,
              I had already updated the reactor.service file that you are referring to, but it seems to be that the path to nodejs is incorrect. What I'm trying to figure out is where Fedora would have installed that, so I can update the correct path.

              [Service]
              Type=simple
              User=tmorgenthaler
              WorkingDirectory=/home/tmorgenthaler/reactor
              Environment=NODE_PATH=/tmorgenthaler/myuser/reactor
              ExecStart=/usr/local/lib/nodejs/bin/node app -p
              Restart=on-failure
              RestartSec=5s

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

                Haven't used Fedora in a good while (although I'm a Berkeley guy), but most *nix has the which command you can use to find the path that a command lives in: which node

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

                T 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  Haven't used Fedora in a good while (although I'm a Berkeley guy), but most *nix has the which command you can use to find the path that a command lives in: which node

                  T Offline
                  T Offline
                  tamorgen
                  wrote on last edited by
                  #8

                  @toggledbits said in First post:

                  Haven't used Fedora in a good while (although I'm a Berkeley guy), but most *nix has the which command you can use to find the path that a command lives in: which node

                  That did it. I always forget that command!

                  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

                  • Reverse proxy & API ACL
                    tunnusT
                    tunnus
                    0
                    3
                    24

                  • Grouped devices
                    G
                    gwp1
                    0
                    1
                    14

                  • MFA
                    toggledbitsT
                    toggledbits
                    0
                    17
                    308

                  • Login protections
                    toggledbitsT
                    toggledbits
                    0
                    2
                    108

                  • Reactor (Multi-System/Multi-Hub) Announcements
                    toggledbitsT
                    toggledbits
                    5
                    152
                    150.9k

                  • Reactor Inspect - a small read-only helper panel for MSR
                    G
                    gwp1
                    2
                    6
                    358

                  • Reactor Build 26284 stuck at Loading Reactor UI
                    T
                    tamorgen
                    0
                    16
                    1.4k

                  • MSR with reverse proxy
                    tunnusT
                    tunnus
                    0
                    12
                    702

                  • Missing attribute after upgrade
                    3
                    3rdStng
                    0
                    3
                    409

                  • Use of Google Gemini as an MSR and Hubitat configuration aid
                    therealdbT
                    therealdb
                    0
                    2
                    235

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

                  • [MSR] Rule do not fire
                    therealdbT
                    therealdb
                    0
                    4
                    340
                  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