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. MSR thinks all my Ezlo Controller devices no longer exist, they do !
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
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
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 Inspect - a small read-only helper panel for MSR
wmarcolinW
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
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor

MSR thinks all my Ezlo Controller devices no longer exist, they do !

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 5 Posters 1.5k 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.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by cw-kid
    #1

    Hi

    Today in MSR alerts I see 100 alerts saying that the devices on my Ezlo controllers no longer exist.

    They do still exist. I checked some of these devices in the Ezlo Online API Tool doing a hub.devices.list query.

    I then checked that the ID numbers were the same for the devices and they are the same device ID's still.

    So my devices do still exist with the same device ID's it seems.

    So not sure why MSR has over 100 alerts saying otherwise.

    9d7c4732-40f3-4551-b8d4-e24e0e8dda10-image.png

    I then looked in Entities selected my Ezlo Plus controller and it listed all my devices OK I think and nothing looked out of place.

    Thanks

    1 Reply Last reply
    0
    • CatmanV2C Offline
      CatmanV2C Offline
      CatmanV2
      wrote on last edited by CatmanV2
      #2

      Have you made any changes to MSR or your Ezlo config?

      <edit> I missed the bit where they were all back!

      C

      The Ex-Vera abuser know as CatmanV2.....

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

        It's Ezlo. Anything is possible. Most likely, a momentary hiccup in either the hub (did it self-update?) or their cloud caused the inventory report to come back empty, maybe the hub (or their cloud) wasn't fully ready at the moment of the query. In fact, this kind of behavior is one of reasons MSR doesn't instantly delete a device that is no longer reported in the hub's inventory — all interfaces now have a grace period wherein a device can be restored. Anyway, if the Entities list shows all the devices now, clear the warnings and soldier on.

        Also please make sure you've looked at (and preferably captured/saved) the log files when asking questions like this (and of course, posting any potentially relevant findings). IMO, any post that doesn't say you've looked at the logs isn't meeting the posting guidelines/doing the homework.

        Oh, and I'll take this moment to acknowledge that in a couple of days the Vera community will mark five years since Ezlo announced that it acquired Vera.

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

        PablaP 1 Reply Last reply
        2
        • CatmanV2C Offline
          CatmanV2C Offline
          CatmanV2
          wrote on last edited by
          #4

          Are they out of beta, yet?

          C

          The Ex-Vera abuser know as CatmanV2.....

          1 Reply Last reply
          1
          • toggledbitsT toggledbits

            It's Ezlo. Anything is possible. Most likely, a momentary hiccup in either the hub (did it self-update?) or their cloud caused the inventory report to come back empty, maybe the hub (or their cloud) wasn't fully ready at the moment of the query. In fact, this kind of behavior is one of reasons MSR doesn't instantly delete a device that is no longer reported in the hub's inventory — all interfaces now have a grace period wherein a device can be restored. Anyway, if the Entities list shows all the devices now, clear the warnings and soldier on.

            Also please make sure you've looked at (and preferably captured/saved) the log files when asking questions like this (and of course, posting any potentially relevant findings). IMO, any post that doesn't say you've looked at the logs isn't meeting the posting guidelines/doing the homework.

            Oh, and I'll take this moment to acknowledge that in a couple of days the Vera community will mark five years since Ezlo announced that it acquired Vera.

            PablaP Offline
            PablaP Offline
            Pabla
            wrote on last edited by
            #5

            @toggledbits said in MSR thinks all my Ezlo Controller devices no longer exist, they do !:

            Oh, and I'll take this moment to acknowledge that in a couple of days the Vera community will mark five years since Ezlo announced that it acquired Vera.

            I am so happy I jumped ship from Ezlo/Vera to Home Assistant. Ezlo is soooooo many years behind its an absolute joke

            1 Reply Last reply
            1
            • CatmanV2C Offline
              CatmanV2C Offline
              CatmanV2
              wrote on last edited by
              #6

              I am quite amazed by HA. Although in some measure disturbed that my printer is broadcasting ink levels (for example). Plus there are some odd things that it detects (Linn Home) where I have no Linn gear at all.
              But otherwise loving it! Especially with MSR

              The Ex-Vera abuser know as CatmanV2.....

              G 1 Reply Last reply
              2
              • CatmanV2C CatmanV2

                I am quite amazed by HA. Although in some measure disturbed that my printer is broadcasting ink levels (for example). Plus there are some odd things that it detects (Linn Home) where I have no Linn gear at all.
                But otherwise loving it! Especially with MSR

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

                @CatmanV2 HA has matured nicely over the past couple years.

                *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
                2
                • toggledbitsT toggledbits locked this topic on
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                Recent Topics

                • Grouped devices
                  G
                  gwp1
                  0
                  3
                  61

                • Reverse proxy & API ACL
                  tunnusT
                  tunnus
                  0
                  3
                  56

                • MFA
                  toggledbitsT
                  toggledbits
                  0
                  17
                  382

                • Login protections
                  toggledbitsT
                  toggledbits
                  0
                  2
                  123

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

                • Reactor Inspect - a small read-only helper panel for MSR
                  G
                  gwp1
                  2
                  6
                  375

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

                • MSR with reverse proxy
                  tunnusT
                  tunnus
                  0
                  12
                  725

                • Missing attribute after upgrade
                  3
                  3rdStng
                  0
                  3
                  421

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

                • [MSR] Native fan capabilty
                  therealdbT
                  therealdb
                  1
                  3
                  244

                • [MSR] Rule do not fire
                  therealdbT
                  therealdb
                  0
                  4
                  351
                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