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. Error importing backup from vera
UI not loading after upgrading to 26318
tunnusT
Sorry for a hasty post, will update some details later, but the scenario is that I managed to type a wrong password for too many times and had the following users.yaml section: authtrack: max_attempts: 4 within_minutes: 180 # 180 minutes = 3 hrs block_expiration_minutes: 10080 # 7 days At this time I used build 26298. Then noticed there's a new build with a bypass blocking feature (and yes, it said it won't remove existing block). Anyway, went ahead and upgraded to 26318, but the problem now is that UI is not loading at all (page does not answer). This also means that I cannot use "http://reactor_host:port/diag/clear_authtrack?askauth" command to clear the block (or use any other source IP for login). Docker container stays up & running and does not exit. I'll try to dig up some logs, but anything that I could immediately try out (could I delete a particular file for example)? EDIT: some logs [latest-26318]2026-11-17T20:42:32.337Z <Rule:INFO> MSR startup (rule-lculfnhm in Miscellaneous) started [latest-26318]2026-11-17T20:42:32.343Z <httpapi:NOTICE> httpapi#1 HTTP server listening on :::8111 [latest-26318]2026-11-17T20:42:32.347Z <httpapi:INFO> httpapi#1 local docs found in /opt/reactor/docs/html; setting up static service [latest-26318]2026-11-17T20:42:32.354Z <app:NOTICE> Starting WSAPI... [latest-26318]2026-11-17T20:42:32.355Z <wsapi:NOTICE> wsapi: starting version 26298 protocol [latest-26318]2026-11-17T20:42:32.523Z <Engine:INFO> Engine#1 master timer tick, local time "17/11/2026 22:42:32" (TZ offset 120 mins from UTC) [latest-26318]2026-11-17T20:42:32.542Z <Engine:NOTICE> Starting reaction MSR startup<SET> (rule-lculfnhm:S) [latest-26318]2026-11-17T20:42:32.545Z <Notifier:null> Module Notifier v26186 [latest-26318]2026-11-17T20:42:32.545Z <Engine:INFO> MSR startup<SET> all actions completed. [latest-26318]2026-11-17T20:42:32.557Z <Rule:INFO> Rule#rule-lculfnhm reaction rule-lculfnhm:S completed [latest-26318]2026-11-17T20:42:32.558Z <default:null> Module NotifyTelegram v26177
Multi-System Reactor
[Resolved] Hubitat upgrade 2.5.3.123 may have broken login
3
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
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
MFA
T
Topic thumbnail image
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
Login protections
tunnusT
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

Error importing backup from vera

Scheduled Pinned Locked Moved Multi-System Reactor
14 Posts 3 Posters 3.8k Views 3 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.
  • H Offline
    H Offline
    HansW
    wrote on last edited by
    #3

    Aha, thanks for your swift response! Any pointer to which file(s) to use? There are a few hundred of them and multiple with Reactor in the name..

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

      Ah. I was wondering... you have the wrong file(s), then. Reactor backups are one file with all ReactorSensors in the single file.

      Use the "Download" link on the Backup and Restore page of the Reactor master device (important: right-click the link and choose "Save As..." -- instructions are there with the link), and you will download a single JSON file. That's the input to the importer.

      Make sure the backup date being reported there is recent, also. If not, make a new backup first.

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

      1 Reply Last reply
      0
      • H Offline
        H Offline
        HansW
        wrote on last edited by
        #5

        Aha, I should have been able to figure that out myself but I had no idea that option existed. Thanks anyway, I just imported the file and it worked!

        Thanks for your excellent work, your software is very intuitive as compared to others.

        Is there any advice or good practice for replacing the vera house modes?

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

          Will you still be using your Vera? Are you moving to or adding another hub? If so, which?

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

          1 Reply Last reply
          0
          • H Offline
            H Offline
            HansW
            wrote on last edited by
            #7

            I am trying to get rid of my Vera and moving to HA on Qnap.

            It has been quite a challenge up to now especial since I have a NX584 so needed to set up a separate Pi for that but I keep on it.

            My NX584 used to set the house modes and your reactor took care of the lights and the heating.

            The house modes were nice although I would have preferred something more fancy like:

            At home daylight
            At home dark
            At home alarm on
            Away alarm on

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

              I just make rules for those things. I have a Rule Set called Dusk-Dawn, somewhat misnamed, and it has rules for Morning, Day, Evening, Night, and other time cycles. I then use Rule State conditions in other rules for each room to figure out what to do at those times in those rooms. There are also virtual switches for "Party Mode" (prevents lights from automatically being turned off at night, among other things); "Guest Mode" changes the light pattern on the main level/kitchen so guests don't have to walk around a dark house if they need a snack; etc.

              Following that model, you could make a Rule Set called "House Mode", and have rules or virtual switches for each mode accordingly. The trick is to set up your rules so that modes can't "overlap" -- get your rules right so that it's not possible to be in two modes at once (e.g. can't simultaneously be Day and Night).

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

              1 Reply Last reply
              1
              • H Offline
                H Offline
                HansW
                wrote on last edited by
                #9

                Thank, I will give it a spin and see where it leads me too!

                1 Reply Last reply
                0
                • W Offline
                  W Offline
                  whyfseeguy
                  wrote on last edited by
                  #10

                  Hi Patrick,

                  Running MSR on docker.

                  Trying to import the reactor config from Vera.

                  My workflow is:

                  1. docker exec -it reactor /bin/sh
                  2. /opt/reactor # node tools/import_reactor_backup.js /var/reactor/reactor-config-backup.json vera

                  Got the following error: (After restarting, no reactor config from Vera was imported)
                  Fetching current rulesets...
                  Pass 1: Translating...
                  ReactorSensor 134 Auto (un)lock doors
                  Creating ruleset for ReactorSensor 134 Auto (un)lock doors
                  Creating rule rule-134
                  ReactorSensor 139 Auto Lights
                  Creating ruleset for ReactorSensor 139 Auto Lights
                  Creating rule rule-139
                  ReactorSensor 143 Somfy Control
                  Creating ruleset for ReactorSensor 143 Somfy Control
                  Creating rule rule-143
                  ReactorSensor 167 Blue Iris Control
                  Creating ruleset for ReactorSensor 167 Blue Iris Control
                  Creating rule rule-167
                  ReactorSensor 183 Towel and Heater Sch
                  Creating ruleset for ReactorSensor 183 Towel and Heater Sch
                  Creating rule rule-183
                  ReactorSensor 208 Geofencing Action
                  Creating ruleset for ReactorSensor 208 Geofencing Action
                  Creating rule rule-208
                  (node:639) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'split' of undefined
                  at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:185:82)
                  at /opt/reactor/tools/import_reactor_backup.js:44:13
                  at Array.forEach (<anonymous>)
                  at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
                  at /opt/reactor/tools/import_reactor_backup.js:44:13
                  at Array.forEach (<anonymous>)
                  at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
                  at /opt/reactor/tools/import_reactor_backup.js:438:13
                  at Array.forEach (<anonymous>)
                  at /opt/reactor/tools/import_reactor_backup.js:402:34
                  (Use node --trace-warnings ... to show where the warning was created)
                  (node:639) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
                  (node:639) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

                  Any help will be appreciated. The worst case scenario is to re-do all the triggers and conditions in MSR from the ground up.

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

                    Are you using Vera's geofencing?

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

                    1 Reply Last reply
                    0
                    • W Offline
                      W Offline
                      whyfseeguy
                      wrote on last edited by
                      #12

                      Yes I am using Vera Geofencing.

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

                        OK. Pull the updated docker container and try again.

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

                        1 Reply Last reply
                        0
                        • W Offline
                          W Offline
                          whyfseeguy
                          wrote on last edited by
                          #14

                          I did a pull, now running 21257. Import seems to be working. The import tool created a bunch of rules from Vera Reactor. I will go through them 1 at a time to make the necessary changes. I will report back later if there are issues related to this.

                          Thanks again.

                          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

                          • UI not loading after upgrading to 26318
                            tunnusT
                            tunnus
                            0
                            3
                            77

                          • [Resolved] Hubitat upgrade 2.5.3.123 may have broken login
                            toggledbitsT
                            toggledbits
                            0
                            8
                            272

                          • Reactor (Multi-System/Multi-Hub) Announcements
                            toggledbitsT
                            toggledbits
                            5
                            153
                            163.0k

                          • Reactor Inspect - a small read-only helper panel for MSR
                            G
                            gwp1
                            2
                            8
                            599

                          • Reverse proxy & API ACL
                            tunnusT
                            tunnus
                            0
                            9
                            495

                          • MFA
                            T
                            tamorgen
                            0
                            28
                            1.4k

                          • Grouped devices
                            G
                            gwp1
                            0
                            3
                            194

                          • Login protections
                            toggledbitsT
                            toggledbits
                            0
                            2
                            236

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

                          • MSR with reverse proxy
                            tunnusT
                            tunnus
                            0
                            12
                            896

                          • Missing attribute after upgrade
                            3
                            3rdStng
                            0
                            3
                            692

                          • Use of Google Gemini as an MSR and Hubitat configuration aid
                            therealdbT
                            therealdb
                            0
                            2
                            326
                          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