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.
toggledbitsT

toggledbits

@toggledbits
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
Use of Google Gemini as an MSR and Hubitat configuration aid
R
I may be late to the AI party on this, but I recently ran into difficulty installing and configuring the Nexia Thermostat Manager on my Hubitat C8 Pro. Hoping for some immediate help I performed a Google search on my problem. I was a bit surprised to see Gemini jump into assist. Gemini walked me through the steps to clean up the failed install, followed by a script for successful installation and configuration. I would not have expected Gemini to "know" this much about Hubitat. Next I sought assistance MSR with the Entity Actions needed to set up the desired controls. I was unclear which of the attribute fields I should to set the cooling an heating temperatures. Once again, Gemini came back not with just a link to a possible explanation, but an easy to follow explanation instead. Once again, I did not expect Gemini to provide such detailed assistance with MSR. Gemini will be a key tool in my HA toolkit in the future.
How-To
[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
About
Posts
3.1k
Topics
49
Shares
0
Groups
1
Followers
18
Following
0

Posts

Recent Best Controversial

  • UI not loading after upgrading to 26318
    toggledbitsT toggledbits

    Stop Reactor, remove the auth.json and auth.dval files from the storage directory, restart Reactor.

    This will also invalidate all auths for all clients. Everyone will need to log in again.

    If you want something a little less dramatic, stop Reactor, edit auth.json and remove the contents of the value under authtrack (i.e. make it read value: {} with nothing between the curly braces). Then delete auth.dval and restart Reactor.

    Multi-System Reactor

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

    Forgot to mention, this version also supports HTTPS for the hub. Your hub username and password travel in cleartext if you don't use HTTPS in both your browser and Reactor, so it's worth considering turning it on in the hub and changing your source to https://... in your HubitatController configuration. If you use a self-signed certificate or use the hub's default certificate (i.e. you don't provide a signed certificate of your own), you must add ignore_certificates: true as well.

    Multi-System Reactor

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

    OK. Build 26318 supports the updated firmware (2.5.3).

    Multi-System Reactor

  • Reactor (Multi-System/Multi-Hub) Announcements
    toggledbitsT toggledbits

    Reactor build 26318

    • HubitatController: Fix hub login failure in hub firmware 2.5.3 and above.
    • Security: New Access Control configuration elements bypass_blocking and bypass_mfa. The former prevents IP addresses with multiple authentication failures from being blocked; the latter allows login without MFA when require_mfa: true is configured. Both expect an array of CIDR host or subnet addresses. See docs
    • DynamicGroupController: Prevent a group from having itself as a member.
    • HassController: Bless HA to 2026.11.1
    Multi-System Reactor announcements

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

    @3rdStng said in Hubitat upgrade 2.5.3.123 may have broken login:

    This error may be due to the container stopping?

    Correct assessment for the Engine not running messages.

    @3rdStng said in Hubitat upgrade 2.5.3.123 may have broken login:

    Disabling Hub Login Security, and commenting out my username and password in the config.yaml, allowed for the status updates to be sent/received by MSR. So this is a work around, but I would prefer to have a login enabled.

    That would be a correct workaround for the moment. When I get time this afternoon, I'll see what changed at the hub firmware and what I can do about it.

    Multi-System Reactor

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

    When hub login is enabled at the hub, events are not sent over the Websocket channel until HubitatController gets a successful login. I quickly reviewed the release notes for 2.5.3.123, and nothing jumped out at me, but I'm running to an event right now, and I'll be tied up in the morning tomorrow, so I won't get a chance to dig into this until tomorrow afternoon at the earliest.

    Do you know what version of firmware you were running prior to upgrade? It may be in messages in previous reactor.log files.

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    I'll take some responsibility here for not asking to see the entire file and just relying on snippets (hard to tell indent and relation to other data).

    BTW, the give-away was this:

    [latest-26298]2026-11-03T16:50:01.685Z <httpapi:null> httpapi#1 ACL no match: user tmorgenthaler to group:api_allowed
    

    It's saying that the user isn't in the group. But the group was in your config file... so this says it can't see your group... and the indenting explained why.

    Multi-System Reactor

  • Reverse proxy & API ACL
    toggledbitsT toggledbits

    The X-Forwarded-For header is only handled for the trusted_proxy list IPs.

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    The indenting of your groups section is very goofed up. api_allowed and everything below it should be outdented two spaces... same alignment as admin, not underneath it as you've shown. Also the two lines showing after applications under admin... no idea where that comes from or what it's supposed to do. Not sure what the intent was, but that's not anything Reactor will see or care about.

    proxy_baseurl and pass_all_proxy do not go in users.yaml.

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    As part of startup, you have two log messages: httpapi#1 ACLs and httpapi#1 ACL index, one after the other, both with additional data on the same line. Please post those. It looks like your custom ACL is not even being loaded. I would check your users.yaml file against yamllint.com or similar tool... I'm betting you have another error in the file and it's preventing the file from being loaded at all, so the last-known-good version of the configuration (without your ACL change) is being loaded.

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    Turn on ACL debug. The log will then show why your ACL isn't matched.

    Also look in your startup messages for any errors (specifically, search for "ignoring config").

    Multi-System Reactor

  • Reverse proxy & API ACL
    toggledbitsT toggledbits

    OK. I asked an AI friend if Synology works differently, and it reports that yes, indeed, Synology's Docker package does not handle network routing the same as the docker standard (Ubuntu, Debian, Raspberry Pi OS, etc.). It offered the following as a workaround:

    Yes. Synology’s Docker / Container Manager implementation has a well-known difference from standard Docker Engine on Linux.

    On a normal Docker install (Ubuntu, Debian, Raspberry Pi OS, etc.), published-port traffic that arrives via pure iptables DNAT usually preserves the original client source IP (or at least behaves in the ways we discussed earlier). On Synology DSM, the default setup for bridge-mode containers is different: inbound connections almost always appear inside the container as coming from the Docker bridge gateway (typically something like 172.17.0.1 or the gateway of whatever network the container is on).

    What people actually observe on Synology

    Multiple independent reports (Synology Community, Reddit, blogs about AdGuard Home, Pi-hole, Stalwart, etc.) describe the same behavior:

    • Client on the LAN connects to NAS-IP:published-port.
    • The application inside the container logs the source as 172.17.0.1 (or the equivalent gateway), not the real client IP and not the NAS’s LAN IP.

    Your customer describing it as “the container’s internal IP” is very likely referring to this same phenomenon (they may simply be seeing a 172.x address and calling it the container’s IP). It is extremely common on Synology and uncommon on vanilla Docker.

    Why Synology behaves differently

    Synology’s Docker package does not install (or does not keep) the same PREROUTING → DOCKER jump rules that stock Docker uses. As a result, traffic is handled more like a userland proxy that rewrites the source address to the bridge gateway before it reaches the container. Disabling IP masquerading alone does not fix it.

    The classic one-line workaround that many Synology users apply (via SSH) is:

    sudo iptables -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER
    sudo iptables -t nat -A PREROUTING -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER
    

    After adding these rules, the real client IP usually starts appearing. The change is not permanent across reboots, so people typically put it in a Task Scheduler script that runs at boot. Note that it can interact with DSM’s own firewall, so it must be tested carefully.

    Other Synology-specific factors

    • DSM’s built-in reverse proxy is frequently used in front of containers. In that case you also need to configure “Trusted Proxies” and ensure X-Forwarded-For / X-Real-IP are set, otherwise the container (or DSM itself) still sees the proxy’s IP.
    • Host network mode or a macvlan network bypasses the problem entirely (the container sees real client IPs), which is why many Synology users switch to those for apps that require accurate source IPs (DNS filters, rate-limiting, geolocation, etc.).

    In short: this is a known Synology Docker quirk caused by missing/different iptables handling of published ports. The customer’s observation matches the widely reported default behavior on DSM.

    -- end of response --

    Following the advice above is entirely at your own risk. I obviously can't vouch for the accuracy or effects (including undesirable side-effects) of what it suggests.

    Another approach here would be to use LLATs for your local access to the API, and write your ACLs accordingly.

    Multi-System Reactor

  • Reverse proxy & API ACL
    toggledbitsT toggledbits

    OK. Whatever the docker container on your NAS is doing is different from my test environment (Linux/Ubuntu). With the network set to bridge mode, the only time I see the container's internal address is when a request is made to 127.0.0.1 on the docker host into the Reactor container. Otherwise, I'm seeing real host addresses (LAN or external), not the container internal address.

    I assume 192.168.1.12 is your NAS host address, not some other assigned address?

    I would try reconfiguring your container's networking for host mode.

    Multi-System Reactor

  • Reverse proxy & API ACL
    toggledbitsT toggledbits

    Show me your request URL (local network)

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    @tamorgen said in MFA:

    • url: "/api/"

    Remove the trailing slash.

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    See edit above

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    Are you requesting from a browser or curl?

    Edit: also source_IP must be source_ip (all lower case).

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    The allowed list is separate from ACLs. It's just a first check. The ACLs are next. The former doesn't imply the latter, the latter having much more granularity/detail.

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    You don't need to run the commands from inside the container. You can add an ACL allowing the IP address of the host system or your LAN subnet (as source_ip). But in any case, once you add the user/group ACL entry to permit the endpoint as suggested above, as long as that entry also doesn't restrict IP (i.e. doesn't contain source_ip), any IP that can log in as that user (or a user in that group, if group), will be allowed from anywhere (i.e. authorized queries from outside the container will work).

    Multi-System Reactor

  • Login protections
    toggledbitsT toggledbits

    Interesting exercise. I decided that that alone wasn't sufficient, so I added MFA to the mix. I recommend using both with exposed Reactor systems, and in particular, enable required MFA for all users, so no accounts can accidentally be left open.

    Multi-System Reactor
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved