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. Is it possible to use a single reaction for multiple entities as variables?
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
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
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
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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 restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

Is it possible to use a single reaction for multiple entities as variables?

Scheduled Pinned Locked Moved Multi-System Reactor
30 Posts 4 Posters 3.1k Views 4 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 toggledbits

    Go to your Entities list, and find the window_sensors group entity, look at its attributes while you open and close a listed sensor. If it's not changing, then you either have an error in your DGC configuration, or the device(s) aren't responding as expected.

    Remember also your basic troubleshooting steps: any time something doesn't work the way you expect it to, go look in the log files for messages. DGC configures groups at startup, so look at the messages logged for DynamicGroupController during startup.

    T Offline
    T Offline
    tamorgen
    wrote on last edited by tamorgen
    #17

    @toggledbits
    I was just going around the hosue and testing different windows.

    Some of the windows seem to work. When I use sys_group.empty (primary), the value when all the windows are closed is True: The windows that are working, the boolean changes to false and the Local Expression value (window_names) changes to that window. I'm going to have to pinpoint which windows aren't working correctly. It could be an issue in the HA configuration.yaml for the DSC/Envisalink entries. That's for me to figure out.

    The only other issue is the message. It's not sending the value of the string. I'm receiving $ Opened!

    message: ${{ window_names }} Opened!
    

    Edit: The one I had been testing with, right next to my office desk, does change in the entities tab.

    Office Windows
    hass>binary_sensor_office_windows
    true
    1:38:38 PM

    Edit 2: I copied and pasted from the Entities tab the Office Windows Canoncial ID into the reactor.yaml config. Even though they looked identical, once I restarted reactor, that window is now responding properly. I suspect I may have hidden characters in the ones that aren't functioning.

    1 Reply Last reply
    0
    • T tamorgen

      @toggledbits said in Is it possible to use a single reaction for multiple entities as variables?:

      Seems OK

      It's still not tripping in MSR when I open a window.

      This is what is being shown when all the windows are closed. I'm not really paying atention to the comparssion value, jsut the current value it's displaying. That value isn't changing.

      589719a4-62af-420a-aefe-83ceb44a5801-image.png

      I tried it with sys_group.members as well.

      87f1c786-11f3-475c-9e3e-99adf122f89e-image.png

      None of the comparisons seem to make any difference. Current value: array:0) "" remains the same in any state of the windows.

      T Offline
      T Offline
      tamorgen
      wrote on last edited by
      #18

      @tamorgen said in Is it possible to use a single reaction for multiple entities as variables?:

      @toggledbits said in Is it possible to use a single reaction for multiple entities as variables?:

      Seems OK

      It's still not tripping in MSR when I open a window.

      This is what is being shown when all the windows are closed. I'm not really paying atention to the comparssion value, jsut the current value it's displaying. That value isn't changing.

      589719a4-62af-420a-aefe-83ceb44a5801-image.png

      I tried it with sys_group.members as well.

      87f1c786-11f3-475c-9e3e-99adf122f89e-image.png

      None of the comparisons seem to make any difference. Current value: array:0) "" remains the same in any state of the windows.

      I went back to all the windows in the reactor.yaml file and copied the values directly from the Entities tab. They are all now working.

      The only thing not working is the notification. Any ideas what the cause could be?

      toggledbitsT 1 Reply Last reply
      0
      • T tamorgen

        @tamorgen said in Is it possible to use a single reaction for multiple entities as variables?:

        @toggledbits said in Is it possible to use a single reaction for multiple entities as variables?:

        Seems OK

        It's still not tripping in MSR when I open a window.

        This is what is being shown when all the windows are closed. I'm not really paying atention to the comparssion value, jsut the current value it's displaying. That value isn't changing.

        589719a4-62af-420a-aefe-83ceb44a5801-image.png

        I tried it with sys_group.members as well.

        87f1c786-11f3-475c-9e3e-99adf122f89e-image.png

        None of the comparisons seem to make any difference. Current value: array:0) "" remains the same in any state of the windows.

        I went back to all the windows in the reactor.yaml file and copied the values directly from the Entities tab. They are all now working.

        The only thing not working is the notification. Any ideas what the cause could be?

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

        @tamorgen said in Is it possible to use a single reaction for multiple entities as variables?:

        The only thing not working is the notification. Any ideas what the cause could be?

        You have:

        message: ${{ window_names }} Opened!
        

        That stands out because it's not valid YAML. Missing quotes.

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

        T 1 Reply Last reply
        0
        • toggledbitsT toggledbits

          @tamorgen said in Is it possible to use a single reaction for multiple entities as variables?:

          The only thing not working is the notification. Any ideas what the cause could be?

          You have:

          message: ${{ window_names }} Opened!
          

          That stands out because it's not valid YAML. Missing quotes.

          T Offline
          T Offline
          tamorgen
          wrote on last edited by tamorgen
          #20

          @toggledbits, how should the quotes work for a MSR variable in yaml? I copied your example in the second post, but you aren’t calling a HA function. I’ve been playing around with it, but I’m not getting the variable in the system call.

          I’m looking at this documentation for HA.

          Home Assistant

          Script Syntax

          Script Syntax

          Documentation for the Home Assistant Script Syntax.

          They show an example

          
          data: 
              message: "{{ blind_state_message }}"
          
          

          So, in theory,

              message: "{{ window_names }}" opened.
          

          should be valid. The difference here is that window_names is coming from the local expression.

          However, MSR throws an error, telling me that I have invalid service data.

          1 Reply Last reply
          0
          • CrilleC Offline
            CrilleC Offline
            Crille
            wrote on last edited by Crille
            #21

            @tamorgen You need MSR to evaluate the whole data being sent

            ${{ { “message”: window_names + “ opened!” } }}
            
            T 1 Reply Last reply
            0
            • CrilleC Crille

              @tamorgen You need MSR to evaluate the whole data being sent

              ${{ { “message”: window_names + “ opened!” } }}
              
              T Offline
              T Offline
              tamorgen
              wrote on last edited by tamorgen
              #22

              @Crille said in Is it possible to use a single reaction for multiple entities as variables?:

              @tamorgen You need MSR to evaluate the whole data being sent

              ${{ { “message”: window_names + “ opened!” } }}
              

              That's not working either. It actually disables the Play button at he end of Entity Action.

              This is a system call on home assistant (call_service) to send a notification via the HA companion app. The message: text isn't part of the message to be sent, it's yaml code that is part of the data field.

              For example, I have another reaction that sends a message to my phone when my washing machine has completed a cycle.

              Screen Shot 2023-02-23 at 5.56.40 PM.png

              The word message doesn't appear on my phone, just the data after it.

              Here is my current rule:

              Screen Shot 2023-02-23 at 5.59.30 PM.png

              In the Local Expressions, you can see Last value: (string) "Office Windows", so that value should be returned for window_names in the system call.

              1 Reply Last reply
              0
              • PablaP Offline
                PablaP Offline
                Pabla
                wrote on last edited by Pabla
                #23

                Try without the spaces so it looks like this message: ${{window_names}} Open. MSR supports both JSON and Yaml, but you just gotta make sure theres no errors. Usually online validators help with this

                T 2 Replies Last reply
                0
                • CrilleC Offline
                  CrilleC Offline
                  Crille
                  wrote on last edited by
                  #24

                  Try my example by hitting the general play button for Reaction.

                  1 Reply Last reply
                  0
                  • PablaP Pabla

                    Try without the spaces so it looks like this message: ${{window_names}} Open. MSR supports both JSON and Yaml, but you just gotta make sure theres no errors. Usually online validators help with this

                    T Offline
                    T Offline
                    tamorgen
                    wrote on last edited by
                    #25

                    @Pabla said in Is it possible to use a single reaction for multiple entities as variables?:

                    Try without the spaces so it looks like this message: ${{window_names}} Open. MSR supports both JSON and Yaml, but you just gotta make sure theres no errors. Usually online validators help with this

                    Doesn't work. MSR throws this error.

                    Screen Shot 2023-02-23 at 6.10.33 PM.png

                    1 Reply Last reply
                    0
                    • PablaP Offline
                      PablaP Offline
                      Pabla
                      wrote on last edited by
                      #26

                      I don't think you have it written correctly here's an example of how I have it used in one of my own notifications
                      image.png

                      1 Reply Last reply
                      0
                      • PablaP Pabla

                        Try without the spaces so it looks like this message: ${{window_names}} Open. MSR supports both JSON and Yaml, but you just gotta make sure theres no errors. Usually online validators help with this

                        T Offline
                        T Offline
                        tamorgen
                        wrote on last edited by
                        #27

                        @Pabla said in Is it possible to use a single reaction for multiple entities as variables?:

                        Try without the spaces so it looks like this message: ${{window_names}} Open. MSR supports both JSON and Yaml, but you just gotta make sure theres no errors. Usually online validators help with this

                        That triggers the notification, but the value isn't returned.

                        IMG_B67DDA55F775-1.jpeg

                        1 Reply Last reply
                        0
                        • PablaP Offline
                          PablaP Offline
                          Pabla
                          wrote on last edited by
                          #28

                          Don't use the play button next to the action, use the play button right under set reaction

                          T 1 Reply Last reply
                          0
                          • PablaP Pabla

                            Don't use the play button next to the action, use the play button right under set reaction

                            T Offline
                            T Offline
                            tamorgen
                            wrote on last edited by
                            #29

                            @Pabla said in Is it possible to use a single reaction for multiple entities as variables?:

                            Don't use the play button next to the action, use the play button right under set reaction

                            Well that makes a difference! This has been driving me nuts all afternoon. Thanks for cluing me in!

                            IMG_F4FBD5E781DD-1.jpeg

                            1 Reply Last reply
                            2
                            • toggledbitsT Offline
                              toggledbitsT Offline
                              toggledbits
                              wrote on last edited by
                              #30

                              It should look like this:

                              message: "${{window_names}} Open"
                              

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


                              Recent Topics

                              • Gradually turn on lights.
                                G
                                gwp1
                                0
                                4
                                132

                              • Stop the MSR by an external switch on Hubitat.
                                wmarcolinW
                                wmarcolin
                                0
                                1
                                31

                              • Error After Upgrade
                                G
                                gwp1
                                0
                                4
                                104

                              • Reset attribute value of entity in event handler
                                R
                                RHCPNG
                                0
                                5
                                203

                              • Need help figuring out how to delay a reset on reaction
                                G
                                gwp1
                                0
                                22
                                926

                              • Way to search for rules (rule state) in other rules
                                T
                                tamorgen
                                0
                                3
                                99

                              • Links to MSR from HA
                                Tom_DT
                                Tom_D
                                0
                                1
                                90

                              • Set Reaction > Script Action
                                wmarcolinW
                                wmarcolin
                                0
                                11
                                433

                              • Wiring Samotech SM308-S into light fitting
                                akbooerA
                                akbooer
                                0
                                2
                                147

                              • Errors after updating to MQTTController build 25139
                                toggledbitsT
                                toggledbits
                                0
                                6
                                238

                              • 🎉 My very first MSR controller: OpenSprinkler
                                therealdbT
                                therealdb
                                5
                                13
                                918

                              • Advice reqeusted to migrate MSR from Bare Metal to Container
                                T
                                tamorgen
                                0
                                5
                                260
                              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