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. How to use the "latch" option/output mode
Hubitat upgrade 2.5.3.123 may have broken login
3
Topic thumbnail image
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 (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 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
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor

How to use the "latch" option/output mode

Scheduled Pinned Locked Moved Multi-System Reactor
6 Posts 5 Posters 2.2k Views 5 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.
  • R Offline
    R Offline
    RogerO
    wrote on last edited by toggledbits
    #1

    Hello,
    Likely a very obvious solution
    I need so help setting up logic. Monitoring 2 parameters A and B.

    If A and B go true, turn on switch
    I want it to remain true until both A and B go false.

    I think it should be done with latch but struggling with how to implement it in MSR.

    toggledbitsT 1 Reply Last reply
    1
    • A Offline
      A Offline
      Alan_F
      wrote on last edited by Alan_F
      #2

      There may be a more concise way to get there, but I think you can do this by nesting groups as follows:

      Outer group - "OR"
          --- Nested group 1: "AND"
                  > Condition 1 
                  > Condition 2
          --- Nested group 2: "AND"
               --- Nested group 2.1  "OR"
                      > Condition 1 
                      > Condition 2
               --- Nested group 2.2  "AND" **
                      > Switch is on
      Reaction:
           --- Turn on switch
      Reset Reaction:
           --- Turn off switch
      

      ** = This selection doesn't matter as there is only one condition in the group

      So when the switch is off and Condition 1 and 2 both go true, the first nested group goes true and turns on the switch. At this point the second nested group also goes true as you have C1 = true, C2 = true, and switch = on.

      Once the switch is on, if one of the conditions goes to false then nested group 1 will go false, but nested group 2 will stay true, since either C1 or C2 is true and the switch is on. When both C1 and C2 go false then nested group 2 goes false and the rule is reset.

      1 Reply Last reply
      0
      • R Offline
        R Offline
        RogerO
        wrote on last edited by
        #3

        Excellent. Thank you very much.

        1 Reply Last reply
        0
        • R RogerO

          Hello,
          Likely a very obvious solution
          I need so help setting up logic. Monitoring 2 parameters A and B.

          If A and B go true, turn on switch
          I want it to remain true until both A and B go false.

          I think it should be done with latch but struggling with how to implement it in MSR.

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

          @rogero Using a latch makes it a bit simpler:

          41e791a2-df9f-4fa2-a179-124cf6fec65f-image.png

          Theory of operation: the overall condition of the rule is AND: there are two groups, and for the rule to SET, both groups have to be true.

          The first group "Both On" is an AND and can therefore only be true if both switches are turned on at the same time. This group is latched (notice yellow highlight on Options button for the group).

          The second group "Either On" is an OR and will therefore be true when either switch is turned on.

          If one switch is turned on, "Either On" will go true, but not "Both On," so the rule remains reset. When the second switch is turned on, "Both On" then goes true, and when both groups are true, the rule sets.

          Now, the "Both On" is latched true. It cannot go false until its sibling condition "Either On" goes false, so while either switch is on, "Both On" remains latched true and the rule remains set. Only when both switches are turned off does "Either On" go false, which causes the latch to release on "Both On", and the rule resets.

          This is a textbook example of latching.

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

          G 1 Reply Last reply
          1
          • toggledbitsT toggledbits

            @rogero Using a latch makes it a bit simpler:

            41e791a2-df9f-4fa2-a179-124cf6fec65f-image.png

            Theory of operation: the overall condition of the rule is AND: there are two groups, and for the rule to SET, both groups have to be true.

            The first group "Both On" is an AND and can therefore only be true if both switches are turned on at the same time. This group is latched (notice yellow highlight on Options button for the group).

            The second group "Either On" is an OR and will therefore be true when either switch is turned on.

            If one switch is turned on, "Either On" will go true, but not "Both On," so the rule remains reset. When the second switch is turned on, "Both On" then goes true, and when both groups are true, the rule sets.

            Now, the "Both On" is latched true. It cannot go false until its sibling condition "Either On" goes false, so while either switch is on, "Both On" remains latched true and the rule remains set. Only when both switches are turned off does "Either On" go false, which causes the latch to release on "Both On", and the rule resets.

            This is a textbook example of latching.

            G Offline
            G Offline
            gwp1
            wrote on last edited by
            #5

            @toggledbits And has been bookmarked as such!

            *Hubitat C-7 2.5.2.139
            *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

            *HAOS
            Core 2026.10.4
            w/ HA Connect ZWA-2 & ZBT-2
            FW: v1.1
            SDK: v7.23.1

            *Prod MSR in docker/portainer
            MSR: latest-26298-fbb75fb8
            MQTTController: 25139
            ZWave Controller: 25139

            1 Reply Last reply
            0
            • wmarcolinW Offline
              wmarcolinW Offline
              wmarcolin
              wrote on last edited by
              #6

              Each day that passes, I am amazed at the amount of resources available in MSR. This "latch" feature is very interesting, and certainly knowing this facility, I will soon find a way to use it.

              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

              • Hubitat upgrade 2.5.3.123 may have broken login
                toggledbitsT
                toggledbits
                0
                5
                23

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

              • Reverse proxy & API ACL
                tunnusT
                tunnus
                0
                9
                417

              • MFA
                T
                tamorgen
                0
                28
                1.2k

              • Grouped devices
                G
                gwp1
                0
                3
                160

              • Login protections
                toggledbitsT
                toggledbits
                0
                2
                205

              • Reactor (Multi-System/Multi-Hub) Announcements
                toggledbitsT
                toggledbits
                5
                152
                160.3k

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

              • MSR with reverse proxy
                tunnusT
                tunnus
                0
                12
                861

              • Missing attribute after upgrade
                3
                3rdStng
                0
                3
                655

              • Use of Google Gemini as an MSR and Hubitat configuration aid
                therealdbT
                therealdb
                0
                2
                305

              • [MSR] Native fan capabilty
                therealdbT
                therealdb
                1
                3
                293
              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