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 ?
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
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
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
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
Can't customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor

MQTT - add rules support ?

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 5 Posters 794 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 Away
    toggledbitsT Away
    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 Away
          toggledbitsT Away
          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 Away
                    toggledbitsT Away
                    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

                      • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                        toggledbitsT
                        toggledbits
                        0
                        68
                        4.7k

                      • Shelly Wall Display XL
                        therealdbT
                        therealdb
                        2
                        6
                        75

                      • Handling Dead Entities and Renamed Entities
                        PablaP
                        Pabla
                        0
                        5
                        61

                      • Strange behavior for MQTT templates using payload and attributes
                        toggledbitsT
                        toggledbits
                        0
                        6
                        122

                      • [MSR] reactor-mqtt-contrib package for additional MQTT templates
                        therealdbT
                        therealdb
                        1
                        46
                        8.1k

                      • HA 2025.9.4 Supported Yet?
                        toggledbitsT
                        toggledbits
                        0
                        2
                        83

                      • The reaction stopped working (Google Nest max playing a video)
                        toggledbitsT
                        toggledbits
                        0
                        7
                        348

                      • Rule Set UI bug - RESOLVED
                        toggledbitsT
                        toggledbits
                        1
                        2
                        226

                      • [Reactor] Copy&Paste of Rules
                        therealdbT
                        therealdb
                        0
                        1
                        299

                      • [Reactor] Help with screne controller cycling logic
                        toggledbitsT
                        toggledbits
                        0
                        5
                        400

                      • Stop the MSR by an external switch on Hubitat.
                        Tom_DT
                        Tom_D
                        0
                        6
                        731

                      • Expose MSR entities
                        CatmanV2C
                        CatmanV2
                        0
                        11
                        860
                      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