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. Global Reactions - Constraints ?
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

Global Reactions - Constraints ?

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

    Hi

    Will Global Reaction rules have Constraints added at some point?

    And maybe the other functions like Reset Reaction and Expressions.

    Thanks

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

      Global reactions are reactions, not rules. Rules have constraints. Reactions do not. I don't know what "other functions like reset reaction and expressions" means in this context, either. Maybe an example?

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

      cw-kidC 2 Replies Last reply
      1
      • toggledbitsT toggledbits

        Global reactions are reactions, not rules. Rules have constraints. Reactions do not. I don't know what "other functions like reset reaction and expressions" means in this context, either. Maybe an example?

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

        @toggledbits

        Can I change my question.

        Can I trigger a rule set via a http request in to MSR?

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

          If you can't use the HTTP request to trip a virtual switch....

          C

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

          1 Reply Last reply
          0
          • cw-kidC cw-kid

            @toggledbits

            Can I change my question.

            Can I trigger a rule set via a http request in to MSR?

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

            @cw-kid said in Global Reactions - Constraints ?:

            Can I trigger a rule set via a http request in to MSR?

            I can't make sense of why one would want to do this. In my view, the only reason to trigger a rule is to get it to run its reaction. You can, instead, just run a global reaction with an HTTP request.

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

            cw-kidC 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              @cw-kid said in Global Reactions - Constraints ?:

              Can I trigger a rule set via a http request in to MSR?

              I can't make sense of why one would want to do this. In my view, the only reason to trigger a rule is to get it to run its reaction. You can, instead, just run a global reaction with an HTTP request.

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

              @toggledbits

              I know I can run a Global Reaction via a http request.

              I am wondering about replacing Vera scenes with either global reactions which I can do for none conditional things.

              Or by being able to trigger a rule set via a http command.

              These Vera scenes are generally manually triggered.

              1 Reply Last reply
              0
              • toggledbitsT toggledbits

                Global reactions are reactions, not rules. Rules have constraints. Reactions do not. I don't know what "other functions like reset reaction and expressions" means in this context, either. Maybe an example?

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

                @toggledbits said in Global Reactions - Constraints ?:

                Maybe an example?

                I have some scenes in Vera that switch my house modes and do other stuff also. These scenes have no trigger, they are manual and I can run them when I either press a button in the Home Remote dashboard app or when I ask Google Home to run the scene etc.

                The Vera scenes just have LUA code in them, no actions under their "Advanced Editor" section.

                This is a portion of the LUA code for my Away scene. It just checks if a virtual switch is turned on or not? If its on it does not put Vera in to Away mode, if its off then it does put Vera in to Away mode and the HTTP Requests are just for TTS announcements and alert messages to Telegram.

                local status = luup.variable_get("urn:upnp-org:serviceId:SwitchPower1", "Status", 419) --Status of Safe to Arm virtual switch
                if status == "0" then --Safe to Arm
                  luup.inet.wget("http://SOME-HTTP-REQUEST")
                  luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","SetHouseMode", {Mode = 2}, 0) --Set House Mode to Away
                  luup.inet.wget('SOME-HTTP-REQUEST' ,5);
                 
                else --Not Safe to Arm
                  luup.inet.wget("SOME-HTTP-REQUEST")
                 luup.inet.wget('SOME-HTTP-REQUEST' ,5);
                end
                

                My actual LUA code for this "Away" scene is a bit longer and has some function delays in it and it also puts all my Android tablets to sleep, however I cannot currently do that either, by using the VeraScenes.lua file and the Vera startup library, problems are here.

                I do not know how to replicate this manually triggered "scene" in MSR.

                Only way I have tried so far is to create a Global Reaction and to use the same LUA code in the Reaction. However that is not currently working and the LUA code never runs, which is this thread here.

                I could potentially replicate the functionality of this LUA code in a Rule Set but then I cannot manually initiate a Rule Set and its actions via a HTTP Request sent in to MSR like I can with a Global Reaction.

                So currently I cannot move this "Away" scene to MSR and delete it off Vera.

                I would like to reduce the number of Vera scenes I have and use MSR instead, I want to get to the point where the Vera hub is pretty much just a Z-Wave radio and all logic is done in MSR etc.

                For more simple manually triggered scenes, where they just turn something on or off or whatever, I can easily recreate those scenes in MSR as Global Reactions and I have done some already for my LED colour lighting scenes.

                However for some scenes like this "Away" one that have some conditional things in them, I cannot currently use Global Reactions or Rule Sets.

                1 Reply Last reply
                0
                • LibraSunL Offline
                  LibraSunL Offline
                  LibraSun
                  wrote on last edited by
                  #8

                  While I'm not completely certain that this addresses the core of your question, please know that I activate many of my "manual" routines as follows:
                  (a) On Vera, I establish a virtual switch (e.g. VS named "Lights Out");
                  (b) In house, I have a 4-button remote control ("Nodon") with multi-press capabilities;
                  (c) On MSR, I create a Rule that watches for "Nodon" sl_CentralScene == 3 (button #1 pushed and held);
                  (d) All that rule does is turn on "Lights Out" VS (which is set to auto-reset after 2 seconds by Switchboard plug-in);
                  (e) On MSR, I have a second Rule which watches for VS "Lights Out" to become TRUE;
                  (f) That 2nd rule does all the things I want done for my "Lights Out" routine.

                  The reason I do it this way is that the intermediate VS becomes a handy entry point for both the Dashboard, the Vera UI, any Lua code or related plug-ins running on Vera, as well as a visual cue in the app UI to know that the "Lights Out" routine has been triggered.

                  So few things appear in all those places (VS and Virtual Dimmers being two of them) as well as themselves are controllable by Alexa. If I say "Lights Out" to my virtual assistant, all she does is turn on the VS "Lights Out" and we're off and running!

                  cw-kidC 1 Reply Last reply
                  0
                  • LibraSunL LibraSun

                    While I'm not completely certain that this addresses the core of your question, please know that I activate many of my "manual" routines as follows:
                    (a) On Vera, I establish a virtual switch (e.g. VS named "Lights Out");
                    (b) In house, I have a 4-button remote control ("Nodon") with multi-press capabilities;
                    (c) On MSR, I create a Rule that watches for "Nodon" sl_CentralScene == 3 (button #1 pushed and held);
                    (d) All that rule does is turn on "Lights Out" VS (which is set to auto-reset after 2 seconds by Switchboard plug-in);
                    (e) On MSR, I have a second Rule which watches for VS "Lights Out" to become TRUE;
                    (f) That 2nd rule does all the things I want done for my "Lights Out" routine.

                    The reason I do it this way is that the intermediate VS becomes a handy entry point for both the Dashboard, the Vera UI, any Lua code or related plug-ins running on Vera, as well as a visual cue in the app UI to know that the "Lights Out" routine has been triggered.

                    So few things appear in all those places (VS and Virtual Dimmers being two of them) as well as themselves are controllable by Alexa. If I say "Lights Out" to my virtual assistant, all she does is turn on the VS "Lights Out" and we're off and running!

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

                    @LibraSun

                    I can see how virtual switches could be used to trigger MSR rule sets and I do that for some things already.

                    However my remaining Vera scenes are really just scenes that are manually initiated and I'd like to be able to do the same thing in MSR, without having to create a bunch of new and unwanted virtual devices.

                    1 Reply Last reply
                    1
                    • LibraSunL Offline
                      LibraSunL Offline
                      LibraSun
                      wrote on last edited by
                      #10

                      If I could make one small suggestion, which may not fit your use case... namely, creating a single(!) virtual dimmer -- or even just pinpointing an otherwise unused Variable on an existing Vera device -- which MSR can watch for changes?

                      Then, (a) you trigger your Vera Scene (manually), (b) the Scene sets the value (of the Dimmer or Variable), (c) MSR detects the change (automatically), and (d) MSR runs the associated Rule (whose trigger is literally "Dimmer" == X or "Variable" == Y). For this setup to work reliably, I'd take it a step further with (e) MSR immediately resets "Dimmer" or "Variable" to 0.

                      You can tell I'm trying to get things up and running without the need for an as-yet-uncoded "Incoming HTTP Request". 🙂

                      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
                        144

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

                      • Error After Upgrade
                        G
                        gwp1
                        0
                        4
                        106

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

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

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

                      • Links to MSR from HA
                        Tom_DT
                        Tom_D
                        0
                        1
                        93

                      • Set Reaction > Script Action
                        wmarcolinW
                        wmarcolin
                        0
                        11
                        439

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

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

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

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