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

Tarkus

@Tarkus
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
62
Topics
11
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial

  • Home Remote dashboard app and MSR HTTP API
    T Tarkus

    @librasun here is a demo I put together on Home Remote utilizing my personal project. I also use MSR for a majority of the conditional logic. The demo runs about 9 minutes.

    Home remote 3.0 Demo
    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    @toggledbits said in Feature request on reactions side.:

    whereas buttonCodes[ . ] and buttonCodes["x"] simply make no sense.

    These are actually OK if buttonCodes is an object, not an array. You can use the square-bracket notation same as dot member access, so buttonCodes[ "x" ] (note the quotes so it's a string) is the same as buttonCodes.x. Using the square bracket notation lets you use a variable for the member name. You don't need a second array, you just need to structure buttonCodes correctly...
    buttonCodes = { '0': 'codes for 0', '1': 'codes for 1', '.': 'codes for dot' }
    key_to_send = "." # or whatever/however you get the key
    send_data = buttonCodes[ key_to_send ]

    I ended up using this method and it works great!

    Thanks for all the help.

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    @librasun said in Feature request on reactions side.:

    Secondly, your definition of buttonCodes itself shows just a long comma-separated list, which cannot work as is. To make it an array, it must start with [ and end with ].

    Yeah i had the brackets but it did not work so the absence of of them is just me trying different things and not knowing what I am doing. LOL

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    I thought a period was considered numeric in programing to accommodate decimals.

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    @librasun yes i do that often

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    The X's are just left over remnants of the lua process I was using. It was just padding and acted a indicator that the channel was at a end and stop the process. So channel 7.1 would come over as 7.1xx. I set 5 characters to accommodate a 5 digit channel i.e. 135.1 I will take a look at your suggestions.

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    I also forgot to mention that I need to work a "." into the array

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    @LibraSun So this is where I am at and I am stuck. The variable Channel gets pulled in from veras multistring and it gets split into the Character variables. That part works, just trying to work thru the rest.

    Channel array.png

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    @librasun Ok the quotes did the trick! So I am assuming for

    "code0","code1","code2", ... ,"code9"

    I am assuming I am making 10 variables. i.e.

    code0="0000 0067 0000 000D 0060 0018 0030 0018 0018 0018 0018 0018 0030 0018 0018 0018 0018 0018 0018 0018 0030 0018 0018 0018 0018 0018 0018 0018 0018 0422"

    ect, ect....

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    @librasun Definitely did not use quotes, will try that.

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    Have not gotten that far. Just was playing around with this, this morning before my workday started. Will dig into logs when I get a chance.

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    yes, it just does not fire when putting the code into a variable.

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    @librasun

    Patrick did say the Plugin was really barebone's or something to that effect.

    IR.png-D5;,p-{in[ji1GS

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    I am afraid the Global Cache IR plugin that Patrick added support for does not seem to work with expressions in the send code field. I tried to add the hex code for a digit to a Global expression and put ${{Digit_1}} in the send code field but it did not work.

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    @librasun Sure I currently have lua that has multiple "if" conditions that is run on the reaction side. Consider these "if" conditions in the lua the secondary conditions.

    Usage senario:

    Say you have 3 separate expression / variables with varying values of 0-9 lets call them.

    Variable_1
    Variable_2
    Variable_3

    On the reaction side

    If variable_1 = 2

    Send TV IR code for digit 1

    If variable_1 = 2

    Send TV IR code for digit 2

    etc, etc

    delay 1 second

    If variable_2 = 1

    Send TV IR code for digit 1

    If variable_2 = 2

    Send TV IR code for digit 2

    etc, etc

    delay 1 second

    If variable_3 = 1

    Send TV IR code for digit 1

    If variable_3 = 2

    Send TV IR code for digit 2

    etc, etc

    Multi-System Reactor

  • Feature request on reactions side.
    T Tarkus

    Secondary conditional rules on reactions.

    Multi-System Reactor

  • Parsing an expression
    T Tarkus

    Thanks guys, this worked just like I needed it to.

    Multi-System Reactor

  • Parsing an expression
    T Tarkus

    It does not have to be on the Vera side. I can get the 3 digit variable into a MSR expression I just don't fully understand how to parse the characters into 3 separate entities for MSR to evaluate in a 3 seperare rules.i do follow what you suggested but just not sure how to implement it in MSR These are for TV channel.IR codes. I am using a lua routine on the Vera side for this and it often causes luup restarts. And I am just looking for a different approach.

    Multi-System Reactor

  • Parsing an expression
    T Tarkus

    So this would have to be lua on the vera side that populates the extract variable which I can then define as an expression in MSR? I am using the multi-string plugin which gets populated with a 3 digit string on multistrings variable1 and I want to perform 3 different reactions based on the varying values of characters 1 2 and 3. One reaction for each character. It sounds like I would need 3 variables extract1, extract2 and extract3.

    Multi-System Reactor

  • Parsing an expression
    T Tarkus

    If an expression value has a value of 789 can you isolate a character in the expression? i.e. If character 2 = 8 then perform a reaction. If not is this even possible to implement if I put in a feature request?

    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