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. Expressions and LuaXP Functions
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

Expressions and LuaXP Functions

Scheduled Pinned Locked Moved Multi-System Reactor
126 Posts 5 Posters 36.5k Views 5 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
    #1

    Knowing that MSR Preview may not yet fully implement LuaXP (CORRECTION: MSR uses a different language lexpjs), I could not resist whipping up some text expressions for fun. Whereupon two things popped out at me:

    1. The new scaling (0.00 - 1.00) of Dimming Level will require a rewrite of certain Expressions that I use to balance my light levels. For example, it was my custom to monitor one lamp's brightness (0 - 100) with Reactor Luup, then set another lamp to 93% of that level, using this Expression:
    floor(getstate( 9, "urn:upnp-org:serviceId:Dimming1", "LoadLevelTarget" ) * 0.93)
    

    Now, in MSR, it will become necessary to modify that to read:

    floor ((getEntity( "vera>device_9" ).attributes.dimming.level * 0.93)*100)/100
    

    which effectively scales the value up x 100 (so that floor() can act upon it correctly), then downscale it / 100. Just an FYI to ponder.

    1. I'm noticing that every edit, however minor, of an Expression in MSR requires an immediate SAVE click before the 'Run' button will become active. That is to say, I cannot repeatedly evaluate the Expression during editing, without clicking SAVE first.

    Only mentioning this latter behavior since it departs so dramatically from Reactor Luup's paradigm.

    toggledbitsT 1 Reply Last reply
    0
    • LibraSunL LibraSun

      Knowing that MSR Preview may not yet fully implement LuaXP (CORRECTION: MSR uses a different language lexpjs), I could not resist whipping up some text expressions for fun. Whereupon two things popped out at me:

      1. The new scaling (0.00 - 1.00) of Dimming Level will require a rewrite of certain Expressions that I use to balance my light levels. For example, it was my custom to monitor one lamp's brightness (0 - 100) with Reactor Luup, then set another lamp to 93% of that level, using this Expression:
      floor(getstate( 9, "urn:upnp-org:serviceId:Dimming1", "LoadLevelTarget" ) * 0.93)
      

      Now, in MSR, it will become necessary to modify that to read:

      floor ((getEntity( "vera>device_9" ).attributes.dimming.level * 0.93)*100)/100
      

      which effectively scales the value up x 100 (so that floor() can act upon it correctly), then downscale it / 100. Just an FYI to ponder.

      1. I'm noticing that every edit, however minor, of an Expression in MSR requires an immediate SAVE click before the 'Run' button will become active. That is to say, I cannot repeatedly evaluate the Expression during editing, without clicking SAVE first.

      Only mentioning this latter behavior since it departs so dramatically from Reactor Luup's paradigm.

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

      @librasun There's going to be a lot to digest on all sides of the expression discussion, as expressions are one of the most-changed parts of MSR from Reactor for Vera/openLuup. A few days ago, I made another pass at the documentation for Expressions, to at least get most of the syntax and function changes out, if not the operational specifics.

      Not really related to expressions, strictly speaking, The 0-1 issue is going to keep coming up, I realize. The original thinking was to allow more resolution, as the 0-100 mapping is actually lower res than the 0-255 or 0-65535 that many devices support at their closer-to-physical layers. To make that easier, I can take the HomeAssistant approach and have a mirrored set of values in another scale, like level_percent, and name the actions accordingly, like dimming.set_percent. So I'll throw that on the list, and it should make a little less work. That said, ...

      @librasun said in Expressions and LuaXP Functions:

      then set another lamp to 93% of that level, using this Expression

      I'm not really understanding the problem here, and I'll frame my confusion with an example, and perhaps you can tell me where you see a problem I've missed... you've got a lamp that you set to 40% on Vera, or 0.40 as reported in MSR, and you want a second lamp set at 93% of that, so the second lamp would be set to 0.372. It's not a problem to store that value in MSR, and nor is it a problem to set that value using dimming.set, as MSR will convert it back to units of the system when it sends the action to it. So on Vera with a 0-100 scale, it would send 37, and if the host system accepted 0-255, it would send 94. You don't really need to round the numbers. Does it have to do with comparisons in conditions? If you're willing to floor() to two digits so you can do a comparison like <= 0.93, then the equivalent without the rounding step is < 0.94.

      There's no LuaXP in MSR. MSR uses lexpjs, which I also wrote, so of course there will be similarities for that reason alone, but also because basic infix expression syntax doesn't wander far from common ground. But there are changes, and lexpjs is a much more robust module, built on a proper grammar into a proper parser. This has enabled me to add a lot of flexibility into the language that didn't exist in LuaXP, and would have been a real pain to not have available in MSR. And I can also more easily evolve it. For the most basic usage, there's not much difference, but the expressions are used extensively in the device mappings, and so many of the "tweaks" applied are specifically to keep those expressions short and readable.

      The biggest changes with regard to expressions are context and timing.

      Rule-based expressions, the expressions that live within a rule, operate much like they did in ReactorSensors: they are evaluated prior to the evaluation of conditions; and they are evaluated in the order in which they are listed. A big difference is that rule-based expressions are not available outside their parent rule. There is no way to "export" them.

      Global expressions are entirely new. Global expressions are accessible to all rules, both in rule-based expressions (referred to by name), and in Set Variable actions. They are primarily meant to be common-use data containers. They are only evaluated when they are referred to in an expression that is itself being evaluated; they do not evaluate continuously or on event. So for example, if you created a global expression getEntity( "vera>device_9" ).attributes.dimming.level, and that global expression was not used by any rule-based expression, it would not update when the dimming level changes and you would see no change in its value in the UI (and that is all expected). It will just sit there. If, however, you refer to it in a rule-based expression, that then becomes a driver, the rule's dependency on the device recognized, and both the expression and the rule using it would be evaluated when the dependent device changes.

      The disabling of the "Run" button on expressions when unsaved is a temporary simplification. Right now, there's no way to run an arbitrary expression. Any expression that is run is presumed to require its full state to run. That is, an expression inside a rule could refer to any other expression value in the rule, so all of the expression values in the rule are part of the execution context of every expression. Rules know how to build the context and run their stored expressions, but they don't know how to run a one-off expression within their context: there's no API to say "just run this arbitrary expression with your usual context as if it was part of the rule." All of that needs to be built. It will get done, but for the moment, you'll have to tolerate the inconvenience of having to save the rule/expressions first. Expressions didn't work completely and couldn't be used at all in actions until yesterday's build. One step at a time. 🙂


      Note: In the process of writing this I did notice that the and, or and not operators from Lua/LuaXP are not present in lexpjs currently as these keywords. They are directly equivalent to &&, || and ! respectively that are native to lexpjs, so I'll go ahead and add the syntactic sugar to the grammar so that the Lua keywords work, to reduce the load on Reactor users coming over from Vera.

      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
        #3

        Excellent explanations, thank you! I will adapt my own uses to the new scaled dimming levels instead of trying to deal with them as integers like the old days. For the moment I cannot think of a pressing case in which integers would be required, but I dare say someone else will come up with one soon, so your idea of implementing set_percent might make sense in the long run.

        I look forward to your full documentation of the "new" lexpjs language. Just let me know when you are ready for me to hammer very hard on that and assist with updating any documentation.

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

          Every build includes the day's doc updates, if any. Get to that from the "Manual" link in the left nav.

          Work in progress on the docs is often visible at https://reactor.toggledbits.com/docs/

          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
            #5

            Roger that. Meanwhile, out here in the weeds responding to your earlier interest why I'd want to keep something like dimming values granular/integer... it's because I sometimes base triggers off of a device's exact brightness level (e.g. when dim = 50). So I'll have to modify my thinking for when dim = 0.50. Trivial.

            Having digested the docs for LEXPJS (https://github.com/toggledbits/lexpjs/blob/master/lexp.js), I can simply rely on the 2-argument ROUND instead of the 1-argument FLOOR and be done with it.

            I'll keep an eye on those Docs as you suggest. Thanks again.

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

              If you're looking at lexpjs on Github, better to look at the develop branch these days... master has not been updated in quite a while.

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

              1 Reply Last reply
              1
              • MatohlM Offline
                MatohlM Offline
                Matohl
                wrote on last edited by Matohl
                #7

                Started to play around with expressions in the MSR. Comparing two temperatur sensor and passing the lowest into a virtual sensor in Vera. It seems that the value in not passed to the virtual sensor or most probably I do something wrong. I have two similar rules, if Temp1<=Temp2 (shown below) and one if the Temp2<Temp1. I am not sure about the "Set Reaction"

                Skärmbild från 2021-03-08 22-18-55.png Skärmbild från 2021-03-08 22-19-22.png

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

                  The MSR variable/expression replacement is ${{ expression or variable name }}. Try that. I fixed at least one substitution bug today, but I'm not sure if it would intersect your use in the reaction. You've got a device type in your service field for the set variable action, and I'm not sure what your conditions are meant to do. I think what you mean to do is something more like this:

                  Expressions:

                  • Temp1: getEntity( "vera>device_86" ).attributes.value_sensor.value
                  • Temp2: getEntity( "vera>device_88" ).attributes.value_sensor.value
                  • MinTemp: min( Temp1, Temp2 )

                  Condition:

                  • Expression Value: MinTemp changes

                  Set Reaction:

                  • Set Variable: service=urn:upnp-org:serviceId:TemperatureSensor1, variable=CurrentTemperature, value = ${{MinTemp}}

                  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
                    #9

                    Gotta ask: What precisely causes the field(s) background under 'Set Reaction' to turn yellow? For example, if I wrote {levelLamp} it's not yellow, but if I type ${levelLamp} or ${{levelLamp}} (as I knew the proper syntax to be) it turns yellow.

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

                      Yellow means it will accept the value but it may be out of range for the field. I suspect that's a side-effect of the bug I fixed. You'll need to wait for today's build before playing more (at least, if you want it to work 🙂 )

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

                      MatohlM 1 Reply Last reply
                      1
                      • toggledbitsT toggledbits

                        Yellow means it will accept the value but it may be out of range for the field. I suspect that's a side-effect of the bug I fixed. You'll need to wait for today's build before playing more (at least, if you want it to work 🙂 )

                        MatohlM Offline
                        MatohlM Offline
                        Matohl
                        wrote on last edited by Matohl
                        #11

                        @toggledbits Thanks, I missed that the variable expression has been changed.

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

                          Ah-ha, I see that you went with zero-based array indexing in LEXPJS, versus the ol' one-based indexing enjoyed back in LuaXP. Gonna make my transition to MSR a bit more challenging as I transcribe my umpteen array-centric Reactor routines, but c'est la vie. 🙂

                          Glad I noticed this before getting to use the Backup/Restore approach, since I doubt it does (or can or even should) attempt an auto-translation of such things. In my case, being one-off on my table lookups could have meant setting the wrong House Mode, etc. Fun! LOL

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

                            Also, I'm noticing that if you define in Expressions:

                            obj = {ani:bird, typ:bard}
                            

                            that, in order to access the value of "bard", instead of obj.typ (which returns {name:bard}), one must instead construct:

                            type = obj.typ.name // returns "bard"
                            

                            Maybe that's normal? I had to really think about it as a non-programmer.

                            NOTE: In the process I also learned that the 'keys' of an object cannot be numbers; they must begin with a letter.

                            More importantly, I am already missing the array function CHOOSE -- can it be imported into LEXPJS?

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

                              I REALLY LOVE how you can now do the following array index references with minimal effort (and that this probably obviates the need for the CHOOSE function I mentioned above):

                              Expressions

                              idx = 2
                              
                              listN = ["red","green","blue"]
                              
                              findIt = listN[idx]  // returns "blue"
                              
                              1 Reply Last reply
                              0
                              • LibraSunL Offline
                                LibraSunL Offline
                                LibraSun
                                wrote on last edited by LibraSun
                                #15

                                Even with the release of 21072, it seems we are still waiting for "substitutions" to become allowable within Expressions. Is this correct?

                                For example, rather than this disallowed comparison in Triggers:

                                [Expression Value]  [acMode]  [ <> ]  [ ${{houseMode}} ]
                                

                                where acMode and houseMode are both defined expressions within that Rule...

                                I'm using this workaround:

                                [Expression Value] [ modesMatch ] [ is FALSE ]
                                

                                for which I created the Boolean expression

                                modesMatch := ( acMode == houseMode )
                                

                                Gets me where I need to be, just slightly less elegant. (For now.)

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

                                  Correct. Not yet in conditions.

                                  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 LibraSun
                                    #17

                                    Good to know. Meanwhile, I'm profiting from variable substitutions working awesomely down in Reactions!

                                    Although I bumped into a case you may not have fully considered? Namely, in a Rule designed to alter House Mode to match the current mode of my ecobee Thermostat, I cannot use substitution with your "House Mode" plug-in, since it only permits any of four preset options from a pick list.

                                    That is to say:

                                    [Entity Action]  [ House Mode ]  [ x_vera_housemode.set ]  [ <mode> ]
                                    

                                    does not let me select the mode dynamically, based on a variable; it's hard-wired.

                                    Instead, I'm forced (as I always was in RFL) to execute Lua code against Vera herself:

                                    [Entity Action]  [ Vera Plus ]  [ x_vera_sys.runlua ]  [ luup.call_action( "urn:micasaverde-com:serviceId:HomeAutomationGateway1", "SetHouseMode", { Mode = ${{acModeNum}} }, 0 ) ]
                                    

                                    I thought this would work, but it does not appear to be substituting for acModeNum in place, the way RFL used to do for, say. Reactor.Variables.acModeNum.

                                    P.S. Alternatively, if you could surface Vera's and/or Reactor's "House Mode" action in the following manner, I could use it in the reaction:

                                    [ Entity Action ] [ Vera | Reactor ] [ ...setHouseMode ] [ ${{acModeNum}} ]

                                    Standing by for guidance, and hope you find this food for thought in later MSR revisions.

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

                                      That's a datalist control. You don't have to pick what's on the list. You can enter whatever you want.

                                      1cc94e04-6ff6-4a5c-9efc-a70853b57123-image.png

                                      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
                                        #19

                                        Thanks, my bad! Didn't even think to try that. Would have saved me like 45 minutes of poking around, lol. 🙂

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

                                          Meanwhile, I seem to have dug another small hole in the VARIABLE SUBSTITUTION workflow, and it's been vexing me for over an hour. This action
                                          var_sub_fail.png keeps sending a literal

                                          ${{houseModeTxt}}
                                          

                                          to its target, instead of the substituted value:

                                          houseModeTxt := away (string)
                                          

                                          Did not want to post this as a PR, since I think it's unique to me. Took me a while to even notice that Vera was throwing a bright blue error on her Dashboard, with the ecobee plugin complaining of being sent an out-of-range parameter (expects one of "home", "away", "sleep" or "smart1").

                                          Thoughts? Am I having a fatal stroke here?

                                          1 Reply Last reply
                                          0
                                          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
                                            131

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

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            103

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

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

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

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            90

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            433

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

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

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

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            260
                                          Powered by NodeBB | Contributors
                                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Unsolved