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. Strange behavior for MQTT templates using payload and attributes
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

Strange behavior for MQTT templates using payload and attributes

Scheduled Pinned Locked Moved Multi-System Reactor
6 Posts 2 Posters 2.1k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • therealdbT Offline
    therealdbT Offline
    therealdb
    wrote on last edited by
    #1

    I'm re-writing my shelly_scenecontroller mqtt template because I added a new pushbutton and I had strange results. Basically, in the last couple of days, it fired itself, because of the way the logic works. Everytime I'm pushing a button, an "S" is sent as the event, so the button.state never changes. I'm looking for button.since to determine if the button is pressed again.
    That's good, but everytime a poll is done, the button.since attribute is updated, because it is tied to time().

    reactor-mqtt-contrib/shelly_gen1.yaml at 8bf5022f6b8ee80feed3d881befc119a1f58fcdc · dbochicchio/reactor-mqtt-contrib

    reactor-mqtt-contrib/shelly_gen1.yaml at 8bf5022f6b8ee80feed3d881befc119a1f58fcdc · dbochicchio/reactor-mqtt-contrib

    Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.

    So, I introduced the use of event_cnt from the payload, comparing the value to the stored one, in order to understand if it has been pushed again, or, in general, the number of times the button is pushed.
    Updated template:

        events:
          "shellies/%topic%/input_event/%channel%":
            - attribute: "value_sensor.value"
              json_payload: true
              expr: "float(payload?.event_cnt)"
            - attribute: "button.since"
              json_payload: true
              expr: >
                entity.attributes?.button?.since == null || 
                float(payload?.event_cnt) != entity.attributes?.value_sensor?.value
                  ? time() : entity.attributes.button.since
            - attribute: "scene_activation.since" # just copy button.since
              expr: "entity?.attributes?.button?.since"
            - attribute: "button.state"
              json_payload: true
              expr: >
                payload?.event == "S" ? "single" :
                payload?.event == "SS" ? "double" :
                payload?.event == "SSS" ? "triple" :
                payload?.event == "L" ? "long" :
                "unknown"
            - attribute: "scene_activation.scene_id"
              json_payload: true
              expr: "payload?.event"
            - attribute: "x_mqtt_device.online"
              expr: true
    

    This should work, but instead I have this value:

    20de8c3f-ad80-4c4a-9f4e-cb404f54553e-image.png

    and that's beyond strange and I can't honestly figure it out. @toggledbits any hint is appreciated. Thanks.

    --
    On a mission to automate everything.

    My MS Reactor contrib
    My Luup Plug-ins

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

      Debug level 5 for MQTTController and log files are your friend.

      That said, I'm suspicious of the operator precedence effect on your expression. Wrap a set of parens around the conditional of the ternary operator and try it 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
      • therealdbT Offline
        therealdbT Offline
        therealdb
        wrote on last edited by
        #3

        No joy from the logs. I added parens but no joy. The only thing that worked was a delete of the entity/restart of Reactor.

        [latest-25272]2025-09-30T14:49:47.414Z <MQTTController:5:MQTTController.js:599> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 associated with Array(1)[ "shelly_gatebutton" ]
        [latest-25272]2025-09-30T14:49:47.414Z <MQTTController:5:MQTTController.js:601> MQTTController#mqtt dispatching shellies/shelly-gatebutton/input_event/0 to shelly_gatebutton
        [latest-25272]2025-09-30T14:49:47.414Z <MQTTController:5:MQTTController.js:1152> MQTTController#mqtt handling shellies/shelly-gatebutton/input_event/0 (event shellies/shelly-gatebutton/input_event/0) for shelly_gatebutton: {"event":"","event_cnt":2}
        [latest-25272]2025-09-30T14:49:47.415Z <MQTTController:5:MQTTController.js:1168> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 affects entity shelly_gatebutton attributes value_sensor.value, button.since, scene_activation.since, button.state, scene_activation.scene_id, x_mqtt_device.online
        [latest-25272]2025-09-30T14:49:47.415Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton value_sensor.value=2
        [latest-25272]2025-09-30T14:49:47.415Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton button.since={"event":"","event_cnt":0}
        [latest-25272]2025-09-30T14:49:47.416Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton scene_activation.since={"event":"","event_cnt":0}
        [latest-25272]2025-09-30T14:49:47.416Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton button.state=unknown
        [latest-25272]2025-09-30T14:49:47.416Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton scene_activation.scene_id=
        [latest-25272]2025-09-30T14:49:47.417Z <MQTTController:5:MQTTController.js:1274> MQTTController#mqtt topic shellies/shelly-gatebutton/input_event/0 setting shelly_gatebutton x_mqtt_device.online=true
        [latest-25272]2025-09-30T14:49:47.417Z <MQTTController:5:MQTTController.js:1905> MQTTController#mqtt _handle_ext_event() shellies/shelly-gatebutton/input_event/0 matches 0 subscriptions
        

        Maybe it's something that when it's corrupted with json, doesn't work as expected. I'm reporting as an edge case, but it's very hard to reproduce. Thanks anyway. New build for my MQTT-contrib incoming.

        --
        On a mission to automate everything.

        My MS Reactor contrib
        My Luup Plug-ins

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

          Looking more deeply at your logic, I don't think it's going to work. Here's where I think you are:

          The current value of button.since is {"event":"", "event_cnt":0}. I assume it got set this way from prior effort leading up to this point. Now, based on what you currently have configured...

          When the topic shellies/shelly-gatebutton/input_event/0 arrives with event_cnt:2 in the payload, the first thing MQTTController is doing is setting value_sensor.value to 2. You can see that in the log snippet.

          The next thing is it attempts to set button.since, but since your expression is set up so that button.since is only changed if if the value of value_sensor.value is different from payload.event_cnt, which it won't be, because it just set them to the same value. So the expression simply returns the current value of button.since and thus changes nothing.

          See the problem now?

          You have control over the order in which the attributes are processed for the topic/event.

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

          therealdbT 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            Looking more deeply at your logic, I don't think it's going to work. Here's where I think you are:

            The current value of button.since is {"event":"", "event_cnt":0}. I assume it got set this way from prior effort leading up to this point. Now, based on what you currently have configured...

            When the topic shellies/shelly-gatebutton/input_event/0 arrives with event_cnt:2 in the payload, the first thing MQTTController is doing is setting value_sensor.value to 2. You can see that in the log snippet.

            The next thing is it attempts to set button.since, but since your expression is set up so that button.since is only changed if if the value of value_sensor.value is different from payload.event_cnt, which it won't be, because it just set them to the same value. So the expression simply returns the current value of button.since and thus changes nothing.

            See the problem now?

            You have control over the order in which the attributes are processed for the topic/event.

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

            @toggledbits said in Strange behavior for MQTT templates using payload and attributes:

            See the problem now?

            You have control over the order in which the attributes are processed for the topic/event.

            I see it! Thanks! (Never code in a hurry while doing 100 other things).

            --
            On a mission to automate everything.

            My MS Reactor contrib
            My Luup Plug-ins

            toggledbitsT 1 Reply Last reply
            1
            • therealdbT therealdb

              @toggledbits said in Strange behavior for MQTT templates using payload and attributes:

              See the problem now?

              You have control over the order in which the attributes are processed for the topic/event.

              I see it! Thanks! (Never code in a hurry while doing 100 other things).

              toggledbitsT Online
              toggledbitsT Online
              toggledbits
              wrote on last edited by
              #6

              @therealdb said in Strange behavior for MQTT templates using payload and attributes:

              Never code in a hurry while doing 100 other things

              Ummm... is there any other way? 🙂

              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
              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
                toggledbitsT
                toggledbits
                0
                6
                159

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

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

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

              • Reverse proxy & API ACL
                tunnusT
                tunnus
                0
                9
                539

              • MFA
                T
                tamorgen
                0
                28
                1.5k

              • Grouped devices
                G
                gwp1
                0
                3
                205

              • Login protections
                toggledbitsT
                toggledbits
                0
                2
                244

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

              • MSR with reverse proxy
                tunnusT
                tunnus
                0
                12
                915

              • Missing attribute after upgrade
                3
                3rdStng
                0
                3
                701

              • Use of Google Gemini as an MSR and Hubitat configuration aid
                therealdbT
                therealdb
                0
                2
                340
              Powered by NodeBB | Contributors
              Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
              • Login

              • Don't have an account? Register

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