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. MQTT - add rules support ?
[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
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor

MQTT - add rules support ?

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 5 Posters 3.1k 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.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #2

    I like the idea of publishing telemetry for rules. Unfortunately, the trigger state of a rule is (currently) not settable by anything other than the condition state that drives the triggers, and I think this is a vital consistency in the system, so I don't see that changing.

    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
    • A Offline
      A Offline
      Alan_F
      wrote on last edited by Alan_F
      #3

      Would it be an acceptable workaround to add the capability to set an expression to the value of an incoming MQTT payload? That way one could set up a rule set that goes true if:

      Group 1: AND   
         My condition 1
         My condition 2
      OR
      Group 2
         My expression changes from A to B
      

      So for a slightly more detailed example:

      My expression is named MQTT_Action_Switch1. It is set to the value of the payload of MQTT Topic "MSR/Action/Switch1"

      I make this rule:

      Group 1: AND
         Time is after 0800
         Motion sensor changes to true
      OR
      Group 2
         Expression MQTT_Action_Switch1 == true
      Set Action:
         Turn on switch1
         Set expression MQTT_Action_Switch1 == false
      

      So this rule goes true after 0800 when motion is sensed OR when the MQTT topic is received with a payload of True. It is self-resetting when set by MQTT, because the rule's set action resets the expression to false. Alternately if I leave off the last action, this rule would remain true until reset by something else setting MQTT_Action_Switch1 to false.

      1 Reply Last reply
      0
      • therealdbT Offline
        therealdbT Offline
        therealdb
        wrote on last edited by
        #4

        I already expressed the desire to have mqtt messages as triggers. This is more flexible imho and gives us the ability to capture a message and parse in one or more expressions.

        --
        On a mission to automate everything.

        My MS Reactor contrib
        My Luup Plug-ins

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

          Question: what should the topics for rules and global variables look like:

          reactor/mqtt/expr-somevariablename/value
          reactor/mqtt/expressions/somevariablename/value
          other?
          
          reactor/mqtt/rules/rule-948j23rj29/state
          reactor/mqtt/rule-398429223uf2/state
          other?
          

          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

            Question: what should the topics for rules and global variables look like:

            reactor/mqtt/expr-somevariablename/value
            reactor/mqtt/expressions/somevariablename/value
            other?
            
            reactor/mqtt/rules/rule-948j23rj29/state
            reactor/mqtt/rule-398429223uf2/state
            other?
            
            therealdbT Offline
            therealdbT Offline
            therealdb
            wrote on last edited by
            #6

            @toggledbits I prefer these:

            reactor/mqtt/expressions
            reactor/mqtt/rules
            

            because it's easier to subscribe with filters. The beauty of MQTT message structure is that it's hierarchical.

            --
            On a mission to automate everything.

            My MS Reactor contrib
            My Luup Plug-ins

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

              My original thought was that there would be a syntax in the expression definition that would allow an expression to be set to any MQTT topic. So "my_expression" = "^{{MQTT/topic/subtopic/etc/etc}}" where ^{{...}} is the syntax for an MQTT topic just like ${{...}} is the syntax for an expression anywhere in MSR... picking the ^ symbol at random just as an example.

              This would allow the capturing of topics that may already be defined. For example I use Teslamate to pull data from the Tesla API related to my cars. It stores the data in a psql database and also publishes everything to MQTT, with topics like "teslamate/cars/1/plugged_in" and a payload of true or false. If I could set an expression to ^{{teslamate/cars/1/plugged_in}} (meaning the payload value of that topic) then I would be able to create rules that would react when this changed to true or false.

              If I have to format the topics in a certain way to get MSR to recognize them, then I can't use it for anything in MQTT where I don't control the topics.

              I get that this wouldn't work for directly calling rule actions. For that one would have to format the topic to what MSR is looking for, like reactor/mqtt/rules/...

              CrilleC 1 Reply Last reply
              0
              • therealdbT Offline
                therealdbT Offline
                therealdb
                wrote on last edited by
                #8

                I’m ok to use an entity as trigger via mqtt. Something like we’re doing now for entities, but to intercept messages using wildcard.
                Then, pushing the value to an expression is an easy task.

                Right now I’m mostly using my own bridge to accomplish this via virtual devices, but I’ll be more than happy to further streamline this thing.

                --
                On a mission to automate everything.

                My MS Reactor contrib
                My Luup Plug-ins

                1 Reply Last reply
                0
                • A Alan_F

                  My original thought was that there would be a syntax in the expression definition that would allow an expression to be set to any MQTT topic. So "my_expression" = "^{{MQTT/topic/subtopic/etc/etc}}" where ^{{...}} is the syntax for an MQTT topic just like ${{...}} is the syntax for an expression anywhere in MSR... picking the ^ symbol at random just as an example.

                  This would allow the capturing of topics that may already be defined. For example I use Teslamate to pull data from the Tesla API related to my cars. It stores the data in a psql database and also publishes everything to MQTT, with topics like "teslamate/cars/1/plugged_in" and a payload of true or false. If I could set an expression to ^{{teslamate/cars/1/plugged_in}} (meaning the payload value of that topic) then I would be able to create rules that would react when this changed to true or false.

                  If I have to format the topics in a certain way to get MSR to recognize them, then I can't use it for anything in MQTT where I don't control the topics.

                  I get that this wouldn't work for directly calling rule actions. For that one would have to format the topic to what MSR is looking for, like reactor/mqtt/rules/...

                  CrilleC Offline
                  CrilleC Offline
                  Crille
                  wrote on last edited by
                  #9

                  @alan_f You could create your own MQTT Entity that could be used for trigger.
                  Just define the topics in local_mqtt_devices.yaml. You can change capability to Switch or any other that you prefer, this example is a Binary Sensor.

                  teslamate_sensor:
                    type: BinarySensor
                    capabilities: ['binary_sensor']
                    primary_attribute: binary_sensor.state
                    events:
                      "teslamate/cars/%topic%/plugged_in":
                        "binary_sensor.state":
                          expr: 'bool(payload)'
                  

                  and use that template for your MQTT entity in reactor.yaml.

                  "teslamate":
                    name: "Teslamate"
                    topic: "1"
                    uses_template: teslamate_sensor
                  

                  Your entity will now change state when something publishes true or false to the topics defined in your template.

                  teslamate.PNG

                  teslamate_trigger.PNG

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

                    @Alan_F The response by @Crille is correct... I was in mid-authoring of a similar post. You don't even need to make a template for it. Templates just make it easy to re-use topic/handling cross many entities, but if your topic is a one-off, you can do it all in line without a template as well:

                        entities:
                          teslamate_sensor:
                            type: BinarySensor
                            capabilities: ['binary_sensor']
                            primary_attribute: binary_sensor.state
                            events:
                              "teslamate/cars/1/plugged_in":
                                "binary_sensor.state":
                                  expr: 'bool(payload)'
                    

                    And here's the silly example I was writing, showing how you can capture a JSON payload (or any part of it):

                          entities:
                            my_received_data:
                              name: "Some Topic I Watch"
                              capabilities: 
                                - "value_sensor"
                              events:
                                "foo/bar/what/ever":
                                  "value_sensor.value":
                                    json_payload: true
                                    expr: payload
                    

                    In this case, the expression at the end just captures the entire payload, but you could also write payload.somemember.deepermember to pick just one value from within the passed object (if it is an object).

                    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
                    • A Offline
                      A Offline
                      Alan_F
                      wrote on last edited by Alan_F
                      #11

                      @Crille Thanks! I was a bit confused when I first read that section of the MQTT documentation but your example using the topics from my own system helped clear it up for me.

                      I made a slight change to the template to make it "teslamate/cars/%topic%" which allows me to re-use it for multiple binary entities for both cars by using for example "topic: "1/locked" and "topic: 2/locked" for two entities in reactor.yaml.

                      I also hit a snag where trying to directly copy:

                          entities:
                            teslamate_sensor:
                              type: BinarySensor
                              capabilities: ['binary_sensor']
                              primary_attribute: binary_sensor.state
                      

                      caused Reactor not to start with a yaml formatting error, but referring to the documentation I changed it to:

                          entities:
                            teslamate_sensor:
                              type: BinarySensor
                              capabilities: 
                                - binary_sensor
                              primary_attribute: binary_sensor.state
                      

                      moving the capability down one line with a leading "-" and it works.

                      Now I just have to find the time to write all the rules that are possible with the car information available in MSR... 👍

                      1 Reply Last reply
                      1
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      Recent Topics

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

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

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

                      • Reverse proxy & API ACL
                        tunnusT
                        tunnus
                        0
                        9
                        468

                      • MFA
                        T
                        tamorgen
                        0
                        28
                        1.3k

                      • Grouped devices
                        G
                        gwp1
                        0
                        3
                        177

                      • Login protections
                        toggledbitsT
                        toggledbits
                        0
                        2
                        224

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

                      • MSR with reverse proxy
                        tunnusT
                        tunnus
                        0
                        12
                        880

                      • Missing attribute after upgrade
                        3
                        3rdStng
                        0
                        3
                        680

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

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