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. Creating Rules with Conditional Logic
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

Creating Rules with Conditional Logic

Scheduled Pinned Locked Moved Multi-System Reactor
12 Posts 6 Posters 722 Views 6 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.
  • K Offline
    K Offline
    kidhasmoxy
    wrote on last edited by
    #1

    How are folks handling situations where they want to have Conditional Actions or Branching Logic in their Set Reactions for a rule? Are you creating Duplicating the same trigger and setting different conditions and Actions?

    Is there an approach where you combine a main rule with your entity triggers with sub rules that trigger off Expressions? You then could write your conditions as Set Variable actions in the Main Rule for the Expressions that evaluate to true or false. Each sub rule would trigger based on the expression changing to true and then could also change it back to false after.

    Not sure if that's worth the complexity for the reusability and control over duplicate triggers.

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

      Maybe an example? I'll try to offer one, and a solution.

      Motion controlled light. When there's motion during the day, light A on 100%, light B on 100%. When there's motion during the night, light A on 100%, light B on 50%. So you might think "if motion then do A=100 and then if day do B=100 otherwise do B=50"

      Rule "Motion":

      • Entity Attribute condition checks motion sensor is tripped.

      Rule "Day Motion":

      • Rule condition check "Motion" rule set/true
      • Entity Attribute condition checks reactor_system.suninfo.period == "day"
      • ACTION: Turn on light A 100%
      • ACTION: Turn on light B 100%

      Rule "Night Motion"

      • Rule condition check "Motion" rule set/true
      • Entity Attribute condition checks reactor_system.suninfo.period <> "day"
      • ACTION: Turn on light A 100%
      • ACTION: Turn on light B 50%

      The suninfo checks could also be seen as Constraints.

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

        This ties into (possibly) nicely to something I was just wondering about, having taking note of some of this thread:

        I have a security set up that we arm at night as part of our house shutdown process. When it arms it announces on all Alexas that this is happening. Likewise in the morning when we tell the house to wake up it announces on all Veras that the system is disarmed.
        So far so good
        However new behaviour from Mrs C's cat is to wake me up every 30 minutes from about 0130 until 0500 to be let out.
        This necessitated a new control for the security system (sans everything else that the wake up does) but of course that then screams from every Alexa both the arm and disarm.

        Soooo.
        I have changed things. Removed the announcement from the arm and disarm and use those to trigger 4 more rules:
        Armed in hours > loud Vera everywhere
        Armed OOH > very quiet Vera in the kitchen only
        Disarmed in hours > loud Vera everywhere
        Disarmed OOH > very quiet Vera in the kitchen only.

        All is well with the world but I now have 12 rules in Reactor (6 of which are unused being the 'false' sate)

        Is there a better way of doing this?

        Cheers

        C

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

        F K 2 Replies Last reply
        0
        • CatmanV2C CatmanV2

          This ties into (possibly) nicely to something I was just wondering about, having taking note of some of this thread:

          I have a security set up that we arm at night as part of our house shutdown process. When it arms it announces on all Alexas that this is happening. Likewise in the morning when we tell the house to wake up it announces on all Veras that the system is disarmed.
          So far so good
          However new behaviour from Mrs C's cat is to wake me up every 30 minutes from about 0130 until 0500 to be let out.
          This necessitated a new control for the security system (sans everything else that the wake up does) but of course that then screams from every Alexa both the arm and disarm.

          Soooo.
          I have changed things. Removed the announcement from the arm and disarm and use those to trigger 4 more rules:
          Armed in hours > loud Vera everywhere
          Armed OOH > very quiet Vera in the kitchen only
          Disarmed in hours > loud Vera everywhere
          Disarmed OOH > very quiet Vera in the kitchen only.

          All is well with the world but I now have 12 rules in Reactor (6 of which are unused being the 'false' sate)

          Is there a better way of doing this?

          Cheers

          C

          F Offline
          F Offline
          Fanan
          wrote on last edited by
          #4

          @catmanv2 . I have solved this by the color of a Hue lamp. If the house is armed, this light goes red, otherwise it´s bright white light. Then it only needs to be 1 rule; true/false = red/white light.
          The only trouble is where to put the light in the house... 🙂

          CatmanV2C 1 Reply Last reply
          0
          • CatmanV2C CatmanV2

            This ties into (possibly) nicely to something I was just wondering about, having taking note of some of this thread:

            I have a security set up that we arm at night as part of our house shutdown process. When it arms it announces on all Alexas that this is happening. Likewise in the morning when we tell the house to wake up it announces on all Veras that the system is disarmed.
            So far so good
            However new behaviour from Mrs C's cat is to wake me up every 30 minutes from about 0130 until 0500 to be let out.
            This necessitated a new control for the security system (sans everything else that the wake up does) but of course that then screams from every Alexa both the arm and disarm.

            Soooo.
            I have changed things. Removed the announcement from the arm and disarm and use those to trigger 4 more rules:
            Armed in hours > loud Vera everywhere
            Armed OOH > very quiet Vera in the kitchen only
            Disarmed in hours > loud Vera everywhere
            Disarmed OOH > very quiet Vera in the kitchen only.

            All is well with the world but I now have 12 rules in Reactor (6 of which are unused being the 'false' sate)

            Is there a better way of doing this?

            Cheers

            C

            K Offline
            K Offline
            kidhasmoxy
            wrote on last edited by
            #5

            @catmanv2 this is the exact type of situation that I’m thinking of. Also have an automation that alerts me when the power sensor for my washer goes between different ranges so I know what stage it’s in.

            @toggledbits are you thinking of making a native condition action? I don’t know about Vera, but the automation engines in Hubitat and Home Assistant both have this capability and it makes a big difference.

            cw-kidC toggledbitsT 2 Replies Last reply
            0
            • F Fanan

              @catmanv2 . I have solved this by the color of a Hue lamp. If the house is armed, this light goes red, otherwise it´s bright white light. Then it only needs to be 1 rule; true/false = red/white light.
              The only trouble is where to put the light in the house... 🙂

              CatmanV2C Offline
              CatmanV2C Offline
              CatmanV2
              wrote on last edited by
              #6

              @fanan said in Creating Rules with Conditional Logic:

              @catmanv2 . I have solved this by the color of a Hue lamp. If the house is armed, this light goes red, otherwise it´s bright white light. Then it only needs to be 1 rule; true/false = red/white light.
              The only trouble is where to put the light in the house... 🙂

              Thanks 🙂 Won't quite solve my issue though as armed is not the false of 'disarmed' There's some sensors to check and so on as well

              C

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

              1 Reply Last reply
              0
              • K kidhasmoxy

                @catmanv2 this is the exact type of situation that I’m thinking of. Also have an automation that alerts me when the power sensor for my washer goes between different ranges so I know what stage it’s in.

                @toggledbits are you thinking of making a native condition action? I don’t know about Vera, but the automation engines in Hubitat and Home Assistant both have this capability and it makes a big difference.

                cw-kidC Offline
                cw-kidC Offline
                cw-kid
                wrote on last edited by cw-kid
                #7

                @kidhasmoxy said in Creating Rules with Conditional Logic:

                making a native condition action

                Plus one here for this.

                Currently I've used LUA code called in the Reaction / action to then do further conditional checks of things.

                1 Reply Last reply
                0
                • K kidhasmoxy

                  @catmanv2 this is the exact type of situation that I’m thinking of. Also have an automation that alerts me when the power sensor for my washer goes between different ranges so I know what stage it’s in.

                  @toggledbits are you thinking of making a native condition action? I don’t know about Vera, but the automation engines in Hubitat and Home Assistant both have this capability and it makes a big difference.

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

                  @kidhasmoxy said in Creating Rules with Conditional Logic:

                  @toggledbits are you thinking of making a native condition action? I don’t know about Vera, but the automation engines in Hubitat and Home Assistant both have this capability and it makes a big difference.

                  I don't know what this means

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

                  K 1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    @kidhasmoxy said in Creating Rules with Conditional Logic:

                    @toggledbits are you thinking of making a native condition action? I don’t know about Vera, but the automation engines in Hubitat and Home Assistant both have this capability and it makes a big difference.

                    I don't know what this means

                    K Offline
                    K Offline
                    kidhasmoxy
                    wrote on last edited by
                    #9

                    @toggledbits The 3 graphical rules engines I've use the most are Home Assistant Automations, Hubitat Rule Machine, and webcore (supports SmartThings and Hubitat.)

                    All have the notion of using conditions to decide which actions execute after the rule is triggered. This allows you to reduce the number of rules you need and avoid dealing with managing rule dependencies.

                    Supporting this approach makes it easier to migrate from any one (or in this case, all) of those solutions.

                    Documentation from Hubitat:
                    https://docs.hubitat.com/index.php?title=Rule-4.0#Rule-4.0_Conditional_Actions_and_Logical_Expressions

                    Here's an example from Home Assistant:
                    a137a042-3607-4e93-8a75-b9703c996903-image.png

                    Example from Webcore
                    5eab2744-86ec-41ea-9bf8-378062c5f0bc-image.png

                    Example from Hubitat:
                    c0fe8962-deb2-42ec-a091-9dc7bb2e2a9e-image.png

                    1 Reply Last reply
                    0
                    • cw-kidC Offline
                      cw-kidC Offline
                      cw-kid
                      wrote on last edited by
                      #10

                      For me the Rule sets Contraints are the main conditions of the rule.

                      If those conditions are met then the Reaction / actions should be fired.

                      However within those actions there are some scenarios where further conditional checks need to be made.

                      Only way to do this currently in MSR is to create two or more rules or have LUA code on the single rules Reaction carry out those further conditions.

                      1 Reply Last reply
                      0
                      • LibraSunL Offline
                        LibraSunL Offline
                        LibraSun
                        wrote on last edited by
                        #11
                        This post is deleted!
                        1 Reply Last reply
                        0
                        • LibraSunL Offline
                          LibraSunL Offline
                          LibraSun
                          wrote on last edited by LibraSun
                          #12

                          I think this topic gets addressed nicely by the new CONSTRAINT GROUPS feature introduced back in rev. 21117.

                          1 Reply Last reply
                          0
                          • toggledbitsT toggledbits locked this topic on
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          Recent Topics

                          • Gradually turn on lights.
                            G
                            gwp1
                            0
                            4
                            147

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

                          • Error After Upgrade
                            G
                            gwp1
                            0
                            4
                            106

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

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

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

                          • Links to MSR from HA
                            Tom_DT
                            Tom_D
                            0
                            1
                            95

                          • Set Reaction > Script Action
                            wmarcolinW
                            wmarcolin
                            0
                            11
                            443

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

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

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

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