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. Expression to randomly run Global Reactions ?
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

Expression to randomly run Global Reactions ?

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

    @toggledbits @LibraSun

    Thanks guys. OK I have removed the interval and just have the trigger that the virtual switch must be true and I have a pulse for 1 second and to repeat every 60 seconds, just for testing, I'll set this to a longer time later.

    I have also updated the expression with the new one to get rid of 0.

    I have also changed the Reactions to directly set the colours of the light rather than calling the Global Reactions to do it.

    It seems to be working, however there seem to be something strange going on with pulses and repeats ?

    When the break count reaches zero the random number in the expression is changing quickly through 3 different numbers, which is weird.

    Also if you set the pulse to say 15 seconds and the repeat to 60 seconds it's not behaving as I would expect ?

    In this case when the break counter reaches zero the expression number changes to a different number, it then changes to a pulse counter for 15 seconds and when that reaches zero the expression number changes again.

    I only expected it to change the expression number when the repeat count down from 60 seconds reaches zero not also when the pulse counter reaches zero.

    Is this a bug or am I not understanding things correctly?

    Thanks

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

      Each change in the edge of the pulse necessarily causes a re-evaluation of the rule because the condition state may change, which in turn may change the state of the parent groups/containers. So the sequence of what you will see is: pulse true -> reevaluation -> rule set -> pulse delay -> pulse false/break start -> reevaluation -> rule reset -> break delay -> break end/pulse true -> reevaluation -> rule set ... etc...

      Since your actions only run when the rule sets, you still only get one set per pulse; the change in the random value has no effect in any other evaluation.

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

        ...and I believe the only way to alter that arrangement (not that there's anything WRONG with how it's currently operating!), would be to affirmatively evaluate the random number using an expression tucked into the first step of your Set Reaction:

        [Set Variable] [chooseColor] [ ${{ floor ( random ( ) * 6 + 0.5 ) + 1 }} ]
        

        Of course, for this setup to work, your chooseColor expression would have to be blank (otherwise, assignment doesn't work). I'm 99% confident that assigning the variable value at the outset of Set Reaction would indeed get it there in time for the subsequent case-by-case Group Constraints to utilize it as desired, but honestly I have not tested such a scenario. Worth trying, if your OCD doesn't like all those "extra" random values happening, LOL!

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

          This is also correct (a Set Variable can be used, and will evaluate/set before the groups -- in order shown, basically). In fact, this is the way I would do it for myself, for the very reason @LibraSun recommends: it stabilizes the value, and would do so in circumstances where the usage is more complex and the debugging would be made more difficult by the rapid changes otherwise.

          EDIT/NOTA BENE: A bit of a trap here was discovered later. Be sure to read this later post. The recommended action for this purpose/implementation is to not use a Set Variable action to choose a random value. The linked post explains why.

          Not that it much matters, but the random expression can also just be written as floor( random() * 6 + 1 ) (ever so slightly optimized).

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

          cw-kidC 1 Reply Last reply
          1
          • toggledbitsT toggledbits

            This is also correct (a Set Variable can be used, and will evaluate/set before the groups -- in order shown, basically). In fact, this is the way I would do it for myself, for the very reason @LibraSun recommends: it stabilizes the value, and would do so in circumstances where the usage is more complex and the debugging would be made more difficult by the rapid changes otherwise.

            EDIT/NOTA BENE: A bit of a trap here was discovered later. Be sure to read this later post. The recommended action for this purpose/implementation is to not use a Set Variable action to choose a random value. The linked post explains why.

            Not that it much matters, but the random expression can also just be written as floor( random() * 6 + 1 ) (ever so slightly optimized).

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

            @toggledbits @LibraSun

            Thanks for the further suggestions.

            I have made the "ChooseColour" expression empty and at the top of the Set Reactions I now have this:

            af827001-5b6c-4b19-8c9f-eac7128d7150-image.png

            The random number now only changes the once upon each repeat count down and the rule summary card now looks like this:

            fd720374-8147-4230-81ad-a11a1ff935df-image.png

            Its working but not reliably as the colour does not change on the light after every repeat count down. Sometimes it just stays on the previous colour that it was.

            I have checked each Group Constraint action for each of the different colours and when pressing the Play button on each of them the LED strip does change to that correct colour.

            And at other times the light seems to get stuck on one colour for a long time and many cycles, even though the rule is still generating numbers and then after a while it starts changing colours again, so it seems laggy.

            Here is an example of how each Group Constraint looks:

            cf18f604-c615-4bbb-8cdc-9f657ae17d20-image.png

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

              As of this stage, there's nothing to prevent the same color from repeating 2, 3, ... infinite times. Such is the nature of random numbers. Was it one of your prerequisites that the color always change from what it was the previous cycle? Of course, that could occasionally lead to a ping-pong of %(#fb1004)[red], %(#0bf913)[green], %(#fb1004)[red], %(#0bf913)[green], %(#fb1004)[red], %(#0bf913)[green], .... which you may also find objectionable.

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

                Also turn off the "Force re-evaluation of expressions" checkbox. You don't need that in this circumstance (since the use of the variable comes after the set explicitly), and it may even get in the way.

                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
                • toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by toggledbits
                  #15

                  OK... wait up... apology here. Since conditions in reactions are a new feature, even I am not completely steeped in their particular behaviors, and limitations, and I just had a "but wait..." moment.

                  All conditions are evaluated at the same time. The group constraints are evaluated at the same time as the triggers. So, while the reaction's groups will run in sequence, the constraint result is determined before the reaction is run, and therefore doing the Set Variable action in the reaction has no effect on the then-current run of the reaction. That is, even though the reaction may Set Variable to a new random number, the constraints have already been evaluated using the previous value of the variable (what is was before the Set Variable action). So this would definitely account for the "lag" that @cw-kid is observing, because the value set by Set Variable on one run of the set reaction won't be used until the next time the set reaction runs.

                  And it's still the case that random numbers are not guaranteed to repeat or even be uniformly distributed over a small (less than several million, perhaps?) sample

                  So... setting your random number in the "Expressions" section of the rule, rather than by using a Set Variable action, is probably a better implementation for this purpose (at least, will be easier to follow/debug).

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

                    Glad you explained all that, because I had a sneaking suspicion that the timing (and not just the order) of the [Set Variable] was important here. Kinda hard sometimes to keep it all straight, insofar as the human is not the most "logic"-al of engines!

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

                      OK understood I will change the expression back to how it was and remove the set variable in the set reaction area.

                      I will increase the trigger repeat to 5 minutes and test it one evening when its dark outside.

                      Ideally I'd like for a different colour each time to be selected, but I guess the expression for the random numbers could select the same number again and therefore the colour would not change for that cycle.

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

                        Alternatively, you could randomize the color selection itself (not just limited to the 4-5 RGB choices you have now). More variety at the expense of slightly more complicated MSR expressions... but with a net savings in the number of Group Constraints required (just one instead of N for N colors).

                        cw-kidC 1 Reply Last reply
                        0
                        • LibraSunL LibraSun

                          Alternatively, you could randomize the color selection itself (not just limited to the 4-5 RGB choices you have now). More variety at the expense of slightly more complicated MSR expressions... but with a net savings in the number of Group Constraints required (just one instead of N for N colors).

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

                          @librasun

                          Sounds great but I don't know how to do it LOL.

                          As is I have 7 predefined colours which are the primary hex codes for those colours, red, green, blue, purple, orange, pink, yellow.

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

                            You've got me curious now: What make/model of garden lights do you have? And what is their ultimate color palette? Have you tried setting them to intermediate colors using the [Set_Color_RGB] action in MSR, for instance?

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

                              OK understood I will change the expression back to how it was and remove the set variable in the set reaction area.

                              I will increase the trigger repeat to 5 minutes and test it one evening when its dark outside.

                              Ideally I'd like for a different colour each time to be selected, but I guess the expression for the random numbers could select the same number again and therefore the colour would not change for that cycle.

                              ElcidE Offline
                              ElcidE Offline
                              Elcid
                              wrote on last edited by Elcid
                              #21

                              @cw-kid said in Expression to randomly run Global Reactions ?:

                              Ideally I'd like for a different colour each time to be selected, but I guess the expression for the random numbers could select the same number again and therefore the colour would not change for that cycle.

                              I use this to generate a random number that has not been used last time. In the reaction use express variable randomVal, once the reaction is over set randomVal to
                              ${{int(split(join(split("1234567", randomVal || 0),""),"")[floor(random()*6)])}}
                              Then every time you get a different number.

                              cw-kidC 1 Reply Last reply
                              2
                              • LibraSunL LibraSun

                                You've got me curious now: What make/model of garden lights do you have? And what is their ultimate color palette? Have you tried setting them to intermediate colors using the [Set_Color_RGB] action in MSR, for instance?

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

                                @librasun

                                It's a Fibaro RGBW module v1

                                1 Reply Last reply
                                0
                                • ElcidE Elcid

                                  @cw-kid said in Expression to randomly run Global Reactions ?:

                                  Ideally I'd like for a different colour each time to be selected, but I guess the expression for the random numbers could select the same number again and therefore the colour would not change for that cycle.

                                  I use this to generate a random number that has not been used last time. In the reaction use express variable randomVal, once the reaction is over set randomVal to
                                  ${{int(split(join(split("1234567", randomVal || 0),""),"")[floor(random()*6)])}}
                                  Then every time you get a different number.

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

                                  @elcid said in Expression to randomly run Global Reactions ?:

                                  I use this to generate a random number that has not been used last time

                                  That's what I needed!

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

                                    @elcid said in Expression to randomly run Global Reactions ?:

                                    I use this to generate a random number that has not been used last time

                                    That's what I needed!

                                    ElcidE Offline
                                    ElcidE Offline
                                    Elcid
                                    wrote on last edited by Elcid
                                    #24

                                    @cw-kid This is probably more efficient

                                    ${{int(substr(replace("1234567", randomVal || 0,""),floor(random()*6),1))}}
                                    

                                    Then I looked at moving this to MSR as I have it in Reactor, . I found the remove function and this is now easily expanded to larger number and you can easily set a range

                                    ${{remove( 1..7, randomVal - 1)[floor(random()*6)]}}
                                    

                                    @toggledbits , possible bug
                                    list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
                                    Is that expected.

                                    toggledbitsT LibraSunL cw-kidC 3 Replies Last reply
                                    2
                                    • ElcidE Elcid

                                      @cw-kid This is probably more efficient

                                      ${{int(substr(replace("1234567", randomVal || 0,""),floor(random()*6),1))}}
                                      

                                      Then I looked at moving this to MSR as I have it in Reactor, . I found the remove function and this is now easily expanded to larger number and you can easily set a range

                                      ${{remove( 1..7, randomVal - 1)[floor(random()*6)]}}
                                      

                                      @toggledbits , possible bug
                                      list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
                                      Is that expected.

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

                                      @elcid said in Expression to randomly run Global Reactions ?:

                                      @toggledbits , possible bug
                                      list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
                                      Is that expected.

                                      Yes, because 1..7 on its own produces an array. So wrapping it in list() gives you an array containing an array.

                                      FWIW, list() is basically deprecated, because lexpjs lets you use common array notation (e.g. [1,2,3,4,5,6,7]) to define an array.

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

                                      ElcidE 1 Reply Last reply
                                      0
                                      • ElcidE Elcid

                                        @cw-kid This is probably more efficient

                                        ${{int(substr(replace("1234567", randomVal || 0,""),floor(random()*6),1))}}
                                        

                                        Then I looked at moving this to MSR as I have it in Reactor, . I found the remove function and this is now easily expanded to larger number and you can easily set a range

                                        ${{remove( 1..7, randomVal - 1)[floor(random()*6)]}}
                                        

                                        @toggledbits , possible bug
                                        list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
                                        Is that expected.

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

                                        @elcid said in Expression to randomly run Global Reactions ?:

                                        @cw-kid This is probably more efficient

                                        ${{int(substr(replace("1234567", randomVal || 0,""),floor(random()*6),1))}}
                                        

                                        Then I looked at moving this to MSR as I have it in Reactor, . I found the remove function and this is now easily expanded to larger number and you can easily set a range

                                        ${{remove( list(1..7)[0], randomVal - 1)[floor(random()*6)]}}
                                        

                                        GENIUS! Gonna borrow this.

                                        @toggledbits , possible bug
                                        list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
                                        Is that expected.

                                        Yes, that's expected, since 1..7 itself creates an array – namely, [1,2,3,4,5,6,7] – while list() (now deprecated = avoid in MSR) also turns its argument into an array. I suggest omit list and see if things improve.

                                        1 Reply Last reply
                                        0
                                        • toggledbitsT toggledbits

                                          @elcid said in Expression to randomly run Global Reactions ?:

                                          @toggledbits , possible bug
                                          list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
                                          Is that expected.

                                          Yes, because 1..7 on its own produces an array. So wrapping it in list() gives you an array containing an array.

                                          FWIW, list() is basically deprecated, because lexpjs lets you use common array notation (e.g. [1,2,3,4,5,6,7]) to define an array.

                                          ElcidE Offline
                                          ElcidE Offline
                                          Elcid
                                          wrote on last edited by
                                          #27

                                          @toggledbits just discovered that as you posted, is it mentioned in the docs, as I had not come acreoss it?

                                          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
                                            59

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

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            64

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

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

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

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            65

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            396

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

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

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

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