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. Feature request on reactions side.
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

Feature request on reactions side.

Scheduled Pinned Locked Moved Multi-System Reactor
37 Posts 4 Posters 3.0k 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.
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by LibraSun
    #23

    For starters, you've put spaces between buttonCodes and the [ which will not be interpreted correctly.
    Look above at my original example: the syntax is buttonCodes[index] with no spaces.
    (edit: extra spaces should be OK)

    Secondly, your definition of buttonCodes itself shows just a long comma-separated list, which cannot work as is. To make it an array, it must start with [ and end with ].

    Third, you reference buttonCodes in other variables, but named the expression ButtonCodes which is different. These things must match exactly.

    Fourth, some of your CharacterN definitions result in alphanumeric characters which are NOT "just 0 through 9" -- like "x" or "." -- hence they CANNOT serve as the index for an array lookup. Another approach is needed (example: use an Object, per the suggestion below).

    This is proving more challenging than expected -- even turning everything into an Object would pose its own hazards at this point -- but getting the syntax right is way more than half the battle!

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

      Also note that the data type of most of the index expressions is a string. Use int() to make sure it's a number: C1 = ButtonCodes[ int( Character1 ) ]

      Also, it may be useful to break everything out this way while you're testing and figuring it out, but ultimately, you may want to combine them: C1 = ButtonCodes[ int( substr( Channel, 0, 1 ) ) ]

      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
      • T Offline
        T Offline
        Tarkus
        wrote on last edited by
        #25

        The X's are just left over remnants of the lua process I was using. It was just padding and acted a indicator that the channel was at a end and stop the process. So channel 7.1 would come over as 7.1xx. I set 5 characters to accommodate a 5 digit channel i.e. 135.1 I will take a look at your suggestions.

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

          One technique I use involves setting up to "parallel" arrays, an example of which I'll outline here without explicit reference to the problem at hand. I hope to share the mechanics of it without clutter...

          value_I_have := getEntity(vera>source).parameter.i.want // result is "y"
          array_of_values := ["x","y","z"] // all possible  input values listed in some order
          array_of_codes := ["0123","2345","3456"] // desired converted output values for "x", "y" and "z"
          buttonPush := array_of_codes[ indexOf (array_of_values, value_I_have) ]
          

          Let that sink in a bit. In fact, if I were you @Tarkus , I'd mess around with abbreviated versions of this example in a throwaway Rule, just to get the feel for how each input affects the output.

          T 1 Reply Last reply
          0
          • LibraSunL LibraSun

            One technique I use involves setting up to "parallel" arrays, an example of which I'll outline here without explicit reference to the problem at hand. I hope to share the mechanics of it without clutter...

            value_I_have := getEntity(vera>source).parameter.i.want // result is "y"
            array_of_values := ["x","y","z"] // all possible  input values listed in some order
            array_of_codes := ["0123","2345","3456"] // desired converted output values for "x", "y" and "z"
            buttonPush := array_of_codes[ indexOf (array_of_values, value_I_have) ]
            

            Let that sink in a bit. In fact, if I were you @Tarkus , I'd mess around with abbreviated versions of this example in a throwaway Rule, just to get the feel for how each input affects the output.

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

            @librasun yes i do that often

            LibraSunL 1 Reply Last reply
            0
            • T Tarkus

              @librasun yes i do that often

              LibraSunL Offline
              LibraSunL Offline
              LibraSun
              wrote on last edited by
              #28

              @tarkus said in Feature request on reactions side.:

              @librasun yes i do that often

              That avoids the "trick" of trying to let Character1 stand in as a numeric value (i.e. serving as an index to an array), since we now know that it may be alphabetical.

              1 Reply Last reply
              0
              • T Offline
                T Offline
                Tarkus
                wrote on last edited by
                #29

                I thought a period was considered numeric in programing to accommodate decimals.

                LibraSunL 1 Reply Last reply
                0
                • T Tarkus

                  I thought a period was considered numeric in programing to accommodate decimals.

                  LibraSunL Offline
                  LibraSunL Offline
                  LibraSun
                  wrote on last edited by LibraSun
                  #30

                  @tarkus said in Feature request on reactions side.:

                  I thought a period was considered numeric in programing to accommodate decimals.

                  Your assumption is correct, however the intent was to let your deciphered "digits" (which I was misled to believe were strictly 0 through 9) stand as "numbers" in the expression buttonCodes[ ], whereas buttonCodes[ . ] and buttonCodes["x"] simply make no sense in that context.

                  Hence the need for parallel lookups.

                  toggledbitsT 1 Reply Last reply
                  0
                  • LibraSunL LibraSun

                    @tarkus said in Feature request on reactions side.:

                    I thought a period was considered numeric in programing to accommodate decimals.

                    Your assumption is correct, however the intent was to let your deciphered "digits" (which I was misled to believe were strictly 0 through 9) stand as "numbers" in the expression buttonCodes[ ], whereas buttonCodes[ . ] and buttonCodes["x"] simply make no sense in that context.

                    Hence the need for parallel lookups.

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

                    @librasun said in Feature request on reactions side.:

                    whereas buttonCodes[ . ] and buttonCodes["x"] simply make no sense.

                    These are actually OK if buttonCodes is an object, not an array. You can use the square-bracket notation same as dot member access, so buttonCodes[ "x" ] (note the quotes so it's a string) is the same as buttonCodes.x. Using the square bracket notation lets you use a variable for the member name. You don't need a second array, you just need to structure buttonCodes correctly...

                    buttonCodes = { '0': 'codes for 0', '1': 'codes for 1', '.': 'codes for dot' }
                    key_to_send = "."   # or whatever/however you get the key
                    send_data = buttonCodes[ key_to_send ]
                    

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

                    LibraSunL T 2 Replies Last reply
                    0
                    • toggledbitsT toggledbits

                      @librasun said in Feature request on reactions side.:

                      whereas buttonCodes[ . ] and buttonCodes["x"] simply make no sense.

                      These are actually OK if buttonCodes is an object, not an array. You can use the square-bracket notation same as dot member access, so buttonCodes[ "x" ] (note the quotes so it's a string) is the same as buttonCodes.x. Using the square bracket notation lets you use a variable for the member name. You don't need a second array, you just need to structure buttonCodes correctly...

                      buttonCodes = { '0': 'codes for 0', '1': 'codes for 1', '.': 'codes for dot' }
                      key_to_send = "."   # or whatever/however you get the key
                      send_data = buttonCodes[ key_to_send ]
                      
                      LibraSunL Offline
                      LibraSunL Offline
                      LibraSun
                      wrote on last edited by
                      #32

                      @toggledbits said in Feature request on reactions side.:

                      You don't need a second array, you just need to structure buttonCodes correctly...

                      I completely agree. If I could turn back time knowing what I know now about this scenario, I would definitely have chosen an Object. It's concise, easy to edit, employ, etc. I just didn't wanna yank @Tarkus around by the nose after we've come this far, lol.

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

                        @toggledbits , since we're on the topic of Objects, I've been meaning to ask:
                        Is there any chance you'd consider implementing a this self-reference for Objects, so I could in theory build:

                        obj := {'noun':'cat','verb':'plays','sentence':'The ' + this.noun + ' ' + this.verb}

                        Maybe that's cray-cray, but I've already bumped into a couple of occasions where it could be handy.

                        REFERENCE: https://www.w3schools.com/js/js_this.asp

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

                          That's not really the way this works for objects in any language I've ever seen or used. We keep using the term "object" here, because of JavaScript, but I really prefer the Python term "dictionary", and maybe I'm going to start using that instead (the grammar actually does, but somehow that didn't make the leap to the documentation and followed the JS nomenclature instead). It's not an object in the sense that there's class definition associated with it, it's just a collection of key/value pairs. Even in JavaScript for many versions, an "object" was really a fancy dictionary, and it is only the more recent versions where that is being formalized, but of course, for compatibility, they are forced to support the old model for some time.

                          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
                          • LibraSunL Offline
                            LibraSunL Offline
                            LibraSun
                            wrote on last edited by
                            #35

                            Typical me:
                            Princess_Bride_That_Word.jpg

                            1 Reply Last reply
                            1
                            • LibraSunL LibraSun

                              For starters, you've put spaces between buttonCodes and the [ which will not be interpreted correctly.
                              Look above at my original example: the syntax is buttonCodes[index] with no spaces.
                              (edit: extra spaces should be OK)

                              Secondly, your definition of buttonCodes itself shows just a long comma-separated list, which cannot work as is. To make it an array, it must start with [ and end with ].

                              Third, you reference buttonCodes in other variables, but named the expression ButtonCodes which is different. These things must match exactly.

                              Fourth, some of your CharacterN definitions result in alphanumeric characters which are NOT "just 0 through 9" -- like "x" or "." -- hence they CANNOT serve as the index for an array lookup. Another approach is needed (example: use an Object, per the suggestion below).

                              This is proving more challenging than expected -- even turning everything into an Object would pose its own hazards at this point -- but getting the syntax right is way more than half the battle!

                              T Offline
                              T Offline
                              Tarkus
                              wrote on last edited by
                              #36

                              @librasun said in Feature request on reactions side.:

                              Secondly, your definition of buttonCodes itself shows just a long comma-separated list, which cannot work as is. To make it an array, it must start with [ and end with ].

                              Yeah i had the brackets but it did not work so the absence of of them is just me trying different things and not knowing what I am doing. LOL

                              1 Reply Last reply
                              0
                              • toggledbitsT toggledbits

                                @librasun said in Feature request on reactions side.:

                                whereas buttonCodes[ . ] and buttonCodes["x"] simply make no sense.

                                These are actually OK if buttonCodes is an object, not an array. You can use the square-bracket notation same as dot member access, so buttonCodes[ "x" ] (note the quotes so it's a string) is the same as buttonCodes.x. Using the square bracket notation lets you use a variable for the member name. You don't need a second array, you just need to structure buttonCodes correctly...

                                buttonCodes = { '0': 'codes for 0', '1': 'codes for 1', '.': 'codes for dot' }
                                key_to_send = "."   # or whatever/however you get the key
                                send_data = buttonCodes[ key_to_send ]
                                
                                T Offline
                                T Offline
                                Tarkus
                                wrote on last edited by
                                #37

                                @toggledbits said in Feature request on reactions side.:

                                whereas buttonCodes[ . ] and buttonCodes["x"] simply make no sense.

                                These are actually OK if buttonCodes is an object, not an array. You can use the square-bracket notation same as dot member access, so buttonCodes[ "x" ] (note the quotes so it's a string) is the same as buttonCodes.x. Using the square bracket notation lets you use a variable for the member name. You don't need a second array, you just need to structure buttonCodes correctly...
                                buttonCodes = { '0': 'codes for 0', '1': 'codes for 1', '.': 'codes for dot' }
                                key_to_send = "." # or whatever/however you get the key
                                send_data = buttonCodes[ key_to_send ]

                                I ended up using this method and it works great!

                                Thanks for all the help.

                                1 Reply Last reply
                                2
                                • 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
                                  139

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

                                • Error After Upgrade
                                  G
                                  gwp1
                                  0
                                  4
                                  105

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

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

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

                                • Links to MSR from HA
                                  Tom_DT
                                  Tom_D
                                  0
                                  1
                                  91

                                • Set Reaction > Script Action
                                  wmarcolinW
                                  wmarcolin
                                  0
                                  11
                                  437

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

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

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

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