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. localization settings
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

localization settings

Scheduled Pinned Locked Moved Multi-System Reactor
17 Posts 4 Posters 4.8k 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.
  • tunnusT tunnus

    @toggledbits wasn't expecting language localization, but date & time. From the manual:

    "You can override the locale Reactor uses for both browser and host display by setting the locale key in the reactor section of reactor.yaml"
    ...
    "By default, dates and times are displayed in the settings determined by the locale (including the order of month, day and year in date displays, and 12/24 time display)"

    So by setting locale in reactor.yaml I was expecting to see e.g. 24 h time format. That didn't happen and then I added time_format and date_format, but still no change?

    toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #4

    @tunnus The time_format and date_format are no longer used, since the locale configuration now determines the date and time format.

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

    tunnusT 1 Reply Last reply
    0
    • toggledbitsT toggledbits

      @tunnus The time_format and date_format are no longer used, since the locale configuration now determines the date and time format.

      tunnusT Offline
      tunnusT Offline
      tunnus
      wrote on last edited by
      #5

      @toggledbits okay, but any idea why using "locale: fi-FI" in reactor.yaml does not change date & time format in UI? Or should it?

      FWIW, using Chrome with Finnish as preferred language (but as said, not expecting to see language impact here, only date/time formatting)

      Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

      1 Reply Last reply
      0
      • tunnusT Offline
        tunnusT Offline
        tunnus
        wrote on last edited by
        #6

        ...I even tried adding LC_ALL variable to Docker with "fi_FI.UTF-8" as a value, but again no impact (for time formatting).

        Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

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

          At the moment it's an all or nothing deal... if there's a translation file, it will accept the locale; otherwise, it just sticks to default US English.

          Maybe you should write the fi-FI translation? 🙂

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

          tunnusT 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            At the moment it's an all or nothing deal... if there's a translation file, it will accept the locale; otherwise, it just sticks to default US English.

            Maybe you should write the fi-FI translation? 🙂

            tunnusT Offline
            tunnusT Offline
            tunnus
            wrote on last edited by
            #8

            @toggledbits said in localization settings:

            At the moment it's an all or nothing deal... if there's a translation file, it will accept the locale; otherwise, it just sticks to default US English.

            Maybe you should write the fi-FI translation? 🙂

            Might even do that 😁 But in the meanwhile wondering if nobody else is interested to get 24 hour time display. @therealdb & @Crille ?

            Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

            therealdbT 1 Reply Last reply
            0
            • CrilleC Offline
              CrilleC Offline
              Crille
              wrote on last edited by Crille
              #9

              The Swedish translation at http://[ip]:8111/reactor/sv-SE/ is in 24h format if the browsers locale setting is set to it.

              1 Reply Last reply
              1
              • tunnusT tunnus

                @toggledbits said in localization settings:

                At the moment it's an all or nothing deal... if there's a translation file, it will accept the locale; otherwise, it just sticks to default US English.

                Maybe you should write the fi-FI translation? 🙂

                Might even do that 😁 But in the meanwhile wondering if nobody else is interested to get 24 hour time display. @therealdb & @Crille ?

                therealdbT Offline
                therealdbT Offline
                therealdb
                wrote on last edited by
                #10

                @tunnus I have started Italian translation, but I'm busy with other things and I like American English anyway. But we could try to create an international English with 24h clock and right date formats, just in case 🤣

                --
                On a mission to automate everything.

                My MS Reactor contrib
                My Luup Plug-ins

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

                  I'm working on some changes, but it may be another week. I'm swamped right now.

                  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
                  2
                  • therealdbT Offline
                    therealdbT Offline
                    therealdb
                    wrote on last edited by
                    #12

                    For anyone here trying to get the 24H & right date format 🙂 just add this to your reactor config file (at least v 23063 required):

                    reactor:
                      ...
                      units: metric
                      date_format: "%d/%m/%Y"
                      time_format: "%H:%M:%S"
                    

                    Restart, hard refresh your browser and you're good to go. Thanks @toggledbits !

                    --
                    On a mission to automate everything.

                    My MS Reactor contrib
                    My Luup Plug-ins

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

                      Note: you only need to do this if your locale-defined time format isn't 24 hour.

                      Also, the format shown by @therealdb might be normal for his locale, but not yours specifically. This config will also override the locale-defined date format; if you don't want that, set time_format only.

                      Final note: Locale setting is determined by (both) the locale set for the host OS and the locale settings of your browser. This is the preferred way to set locale. Setting locale in Reactor's config is specifically not recommended.

                      Edit: to be clear, to get your language's preferred date and time formats, you should do the following, in the order listed:

                      1. Configure your host system (or the Reactor docker container) and your browser for the correct locale. This may be sufficient for most uses. Make sure to re-open browser windows from the "root" of the Reactor URL (e.g. click the Reactor logo in the upper-left corner of the page).
                      2. If the time or date format presented by correctly completing step 1 does not suit your preferences, then and only then set date_format and/or time_format in Reactor's config.
                      3. Never use the Reactor config locale setting; this is for developers only and is not a complete solution for getting the correct locale. Locale configuration is always inherited from (both) your host system and browser, and that is the only correct way to do it permanently.

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

                      tunnusT 1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        Note: you only need to do this if your locale-defined time format isn't 24 hour.

                        Also, the format shown by @therealdb might be normal for his locale, but not yours specifically. This config will also override the locale-defined date format; if you don't want that, set time_format only.

                        Final note: Locale setting is determined by (both) the locale set for the host OS and the locale settings of your browser. This is the preferred way to set locale. Setting locale in Reactor's config is specifically not recommended.

                        Edit: to be clear, to get your language's preferred date and time formats, you should do the following, in the order listed:

                        1. Configure your host system (or the Reactor docker container) and your browser for the correct locale. This may be sufficient for most uses. Make sure to re-open browser windows from the "root" of the Reactor URL (e.g. click the Reactor logo in the upper-left corner of the page).
                        2. If the time or date format presented by correctly completing step 1 does not suit your preferences, then and only then set date_format and/or time_format in Reactor's config.
                        3. Never use the Reactor config locale setting; this is for developers only and is not a complete solution for getting the correct locale. Locale configuration is always inherited from (both) your host system and browser, and that is the only correct way to do it permanently.
                        tunnusT Offline
                        tunnusT Offline
                        tunnus
                        wrote on last edited by tunnus
                        #14

                        @toggledbits so with build 23063 Docker environment variable LC_ALL should work (tried with build 23049, but no success)?

                        Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

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

                          That will change it on the host side. It has no effect on the browser settings (which are browser-dependent).

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

                          tunnusT 1 Reply Last reply
                          0
                          • toggledbitsT toggledbits

                            That will change it on the host side. It has no effect on the browser settings (which are browser-dependent).

                            tunnusT Offline
                            tunnusT Offline
                            tunnus
                            wrote on last edited by
                            #16

                            @toggledbits yes, just wanted to confirm that with earlier builds LC_ALL was essentially ignored

                            Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

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

                              Not ignored, just not used if there was no language file present for the selected language.

                              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
                              • 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
                                58

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

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

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

                              • Reverse proxy & API ACL
                                tunnusT
                                tunnus
                                0
                                9
                                492

                              • 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
                                894

                              • Missing attribute after upgrade
                                3
                                3rdStng
                                0
                                3
                                691

                              • 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