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. [Solved] Expressions - predefining a variable type
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

[Solved] Expressions - predefining a variable type

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 3 Posters 658 Views 3 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.
  • PerHP Offline
    PerHP Offline
    PerH
    wrote on last edited by PerH
    #1

    I have a use case where I need to have a boolean variable that will be set to true/false by reactions.

    I see that i can define a local variable by giving it a name and leaving the definition empty. This leaves it at state "null" until a reaction tells it that its a boolean.

    Is there a way to tell it that it should start out as "false" (i.e when reactor has restarted), and not null?

    Am i going about this the wrong way?

    -- The use case is that I have a sensor on my fireplace, and the following logic is for notifying when its time to get up en refill with firewood.. I also want to reset the MaxInInterval to CurrentTemp when notification is sent..

    1fd2951f-cb6b-4a2f-b957-1e0698171f4d-image.png dd99634e-f0ad-4878-bb87-0284c2df5535-image.png

    Edit: better screenhots. Reactor version 23010-7dd2c9e9

    1 Reply Last reply
    0
    • PerHP Offline
      PerHP Offline
      PerH
      wrote on last edited by
      #2

      BTW, in the screenshots we see that the NotificationSent has fired, and is now interpreted as a string..

      1 Reply Last reply
      0
      • PerHP Offline
        PerHP Offline
        PerH
        wrote on last edited by PerH
        #3

        The rule is corrected and works well:
        35bcdc03-5131-419d-95b4-68b00a675fec-image.png

        It notifies once for each time the temperature has increased, only with temperatures above 100°C, and when i'm home..

        The NotificationSent value wasn't nessecary here, But i'm still wondering if one can define a variable type and set the start value, and later manupulate that value by a reaction?

        1 Reply Last reply
        1
        • therealdbT Offline
          therealdbT Offline
          therealdb
          wrote on last edited by
          #4

          It depends on the use case, but I usually set them via a group in the reaction. Just be sure to se to ${{bool(false)}}
          Depending on the use case, I have a couple resetting (or setting for the first time) in a reaction watching for MSR start.

          --
          On a mission to automate everything.

          My MS Reactor contrib
          My Luup Plug-ins

          toggledbitsT 1 Reply Last reply
          2
          • therealdbT therealdb

            It depends on the use case, but I usually set them via a group in the reaction. Just be sure to se to ${{bool(false)}}
            Depending on the use case, I have a couple resetting (or setting for the first time) in a reaction watching for MSR start.

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

            @therealdb said in Expressions - predefining a variable type:

            Just be sure to se to ${{bool(false)}}

            That's redundant. false is a reserved word that means boolean false, so you don't need to put it through bool()

            @PerH

            4249770b-225b-45f6-a011-4a7abb908f5c-image.png

            This Set Variable action is setting the variable to the string value "true". The operand/parameter of the action is a string. In order to get a boolean, you have to use the expression substitution form as @therealdb suggests, but you only need ${{ true }} -- the interior of the substitution is an expression, and the result of the expression is whatever type the expression result is... in this case, the keyword true simply evaluates to boolean true (the result is boolean).

            To answer your original question, you can initially set the expression for the variable to false in the Expressions editor at the time you create the variable (or any time after), save changes, force and evaluation, and then once the initial false value is bound to the variable, just remove the expression (make it an expressionless variable) and save changes again.

            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
            2
            • PerHP Offline
              PerHP Offline
              PerH
              wrote on last edited by
              #6

              Considering this solved, but would like to add that its a bit important to mark "true" and "false" as depicted above here, and not using them in string form.
              Using "true" in string form in the condition like in "MaxInInterval" in the initial post didn't work, the condition didn't flip when the state changed.
              I guess this is because of how these reserved words are interpreted, so tagging them as boolean is important.

              toggledbitsT 1 Reply Last reply
              0
              • PerHP PerH

                Considering this solved, but would like to add that its a bit important to mark "true" and "false" as depicted above here, and not using them in string form.
                Using "true" in string form in the condition like in "MaxInInterval" in the initial post didn't work, the condition didn't flip when the state changed.
                I guess this is because of how these reserved words are interpreted, so tagging them as boolean is important.

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

                @PerH I'm finding this entire statement to be a bit cryptic. Can you elaborate on what you are saying here, how you now think it works?

                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
                • PerHP Offline
                  PerHP Offline
                  PerH
                  wrote on last edited by
                  #8

                  I'd be happy to!

                  in the original post you see my expression: if NotificationSent != "true" then, which is supposed to reset the maximum reading when notification is sent, and prepare for a new increase when more wood is applied.

                  This never fired when the condition was met, but when I changed it to if NotificationSent != "1" then, (with the same change in the reactions) it worked as intended. The variable was still interpreted as a string.

                  My theory was that this was caused by the special considerations for the word "true" in the interpreter somehow, and that the ${{ true }} in the reaction would solve the problem.

                  That may offcourse be wrong? I admit that the imperical basis is rather thin. 😉

                  I should be able to reproduce this if needed.

                  therealdbT 1 Reply Last reply
                  0
                  • PerHP PerH

                    I'd be happy to!

                    in the original post you see my expression: if NotificationSent != "true" then, which is supposed to reset the maximum reading when notification is sent, and prepare for a new increase when more wood is applied.

                    This never fired when the condition was met, but when I changed it to if NotificationSent != "1" then, (with the same change in the reactions) it worked as intended. The variable was still interpreted as a string.

                    My theory was that this was caused by the special considerations for the word "true" in the interpreter somehow, and that the ${{ true }} in the reaction would solve the problem.

                    That may offcourse be wrong? I admit that the imperical basis is rather thin. 😉

                    I should be able to reproduce this if needed.

                    therealdbT Offline
                    therealdbT Offline
                    therealdb
                    wrote on last edited by
                    #9

                    @PerH I’ve been in the same boat and, yes, the problem is in the underlying type. The same applies to int/float, if you have an increment somewhere.

                    Apologies for the bool() part, I was on my phone and I wrote the first thing that came to my mind, but @toggledbits is in fact right.

                    --
                    On a mission to automate everything.

                    My MS Reactor contrib
                    My Luup Plug-ins

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

                      Yes, the rules of comparisons of different types for Expressions are different from the rules in Conditions. In a Condition, the comparison of the string "true" to a boolean attribute with value true will succeed. In Expressions, the JavaScript rules are followed so the equivalent expression's (e.g. "true" == true) result is false (the string is not equal to the boolean because the word contained in the string isn't magical). But in a Condition, the comparison of a non-zero operand to a boolean attribute having value true will be true, and in Expressions following the JavaScript rules will also be true (because in JavaScript and therefore the expression language, non-zero values are equivalent to true, and 0 is equivalent to false). Basically, in Expressions the strings are treated more strictly by their type, as in JavaScript, and there are no "magic values" (like the word "true") that are understood to mean something else. In Conditions, because all operands are strings, some back office magic happens to try to interpret what to do, otherwise no comparison to anything other than a string could work at all.

                      This may seem inconsistent across the product but it's something I'm unlikely to change as (a) relaxing it in Expressions promotes sloppy construction of expressions, and (b) Expressions are and always have been (even in R4V) an advanced user feature and it is my expectation that advanced users learn the rules of the language, as they would for any language (e.g. Lua). In Conditions and Actions (of Reactions), all operands and parameters are always strings; they need to be manipulated for Conditions to do comparisons, or for Actions to produce the right parameters for the target device or hub. In Expressions, the values are determined by the subexpression that produces them (e.g. "1" produces a string type result, where 1 produces a numeric result, [1] produces an array containing a numeric, and ["1"] produces an array containing a string).

                      I also note your expression if MaxInterval-CurrentTemp > 15 then true else false end, is a bit redundant from a programmer's perspective. In this construction, MaxInterval -CurrentTemp > 15 on its own produces true or false (the > operator always produces a boolean result), so you don't need the branches of the if...else..end construction here, the greater-than test itself can be the entire expression: MaxInterval-CurrentTemp > 15 alone will work the same and be more efficient. Adding the if block just makes extra work.

                      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
                      2
                      • PerHP Offline
                        PerHP Offline
                        PerH
                        wrote on last edited by
                        #11

                        I appreciate both the strictness regarding code and the lesson in javascript. Thanks!

                        I've found out why my "MaxInInterval" didn't work in the original post, and what that "Force re-evaluation..." tickbox on the reactions does!

                        42141f14-385f-429d-a8b9-4358b1074800-image.png

                        (to type it out, I changed the variable in reaction, and naturally, the only variable being updated was the one called out..)

                        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
                          77

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

                        • Error After Upgrade
                          G
                          gwp1
                          0
                          4
                          78

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

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

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

                        • Links to MSR from HA
                          Tom_DT
                          Tom_D
                          0
                          1
                          72

                        • Set Reaction > Script Action
                          wmarcolinW
                          wmarcolin
                          0
                          11
                          401

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

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

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

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