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 ?
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor

Expression to randomly run Global Reactions ?

Scheduled Pinned Locked Moved Multi-System Reactor
39 Posts 4 Posters 6.3k 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.
  • 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
      • toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by
        #28

        Yup. That's in the docs.

        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
        • toggledbitsT toggledbits

          Yup. That's in the docs.

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

          @toggledbits
          Its a bit confusing, i read this
          "[5,7,9], so this function is now obsolete and may be removed later)"
          and tried [1..7], when that failed, I assumed the only way to spread was list(1..7)
          May be add a note about 1..7 being the same as list(1..7). As I found it some what unclear.

          toggledbitsT 1 Reply Last reply
          1
          • ElcidE Elcid

            @toggledbits
            Its a bit confusing, i read this
            "[5,7,9], so this function is now obsolete and may be removed later)"
            and tried [1..7], when that failed, I assumed the only way to spread was list(1..7)
            May be add a note about 1..7 being the same as list(1..7). As I found it some what unclear.

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

            @elcid , it says:

            c4320d3a-82e9-463d-80f3-cf95bd0f4c34-image.png

            I think this is pretty clear. The range operator is documented separately.

            May be add a note about 1..7 being the same as list(1..7).

            But it's not. That's how we got started. 🙂

            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
            1
            • toggledbitsT toggledbits

              @elcid , it says:

              c4320d3a-82e9-463d-80f3-cf95bd0f4c34-image.png

              I think this is pretty clear. The range operator is documented separately.

              May be add a note about 1..7 being the same as list(1..7).

              But it's not. That's how we got started. 🙂

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

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

              May be add a note about 1..7 being the same as list(1..7).

              But it's not. That's how we got started.

              I mean 1..7 being what I assume list(1..7) would produce a single array. That's why I found it confusing, I think that I expected a array to have [ ] around them.
              Maybe add "also see range operator".

              LibraSunL 1 Reply Last reply
              0
              • ElcidE Elcid

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

                May be add a note about 1..7 being the same as list(1..7).

                But it's not. That's how we got started.

                I mean 1..7 being what I assume list(1..7) would produce a single array. That's why I found it confusing, I think that I expected a array to have [ ] around them.
                Maybe add "also see range operator".

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

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

                I mean 1..7 being what I assume list(1..7) would produce

                Funny you should mention this, since all yesterday, I grappled with the question, "How can I find the minimum of an array in MSR?" (Answer: Not easily at all!) Turns out the min() function only works on a list with 2 elements, not arrays of arbitrary length. In other words, min(1,2,3) yields 1 without a hitch, whereas min([1,2,3]) returns null (for good reason: There's no guarantee the argument will always be a 1-dimensional numeric array!). Same for max().

                Which led me to the realization that there's no direct way in MSR to "convert" an array into a list. Seems your brain encountered the same type of mental collision while trying to work out your imported expression. 🙂

                toggledbitsT 1 Reply Last reply
                0
                • LibraSunL LibraSun

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

                  I mean 1..7 being what I assume list(1..7) would produce

                  Funny you should mention this, since all yesterday, I grappled with the question, "How can I find the minimum of an array in MSR?" (Answer: Not easily at all!) Turns out the min() function only works on a list with 2 elements, not arrays of arbitrary length. In other words, min(1,2,3) yields 1 without a hitch, whereas min([1,2,3]) returns null (for good reason: There's no guarantee the argument will always be a 1-dimensional numeric array!). Same for max().

                  Which led me to the realization that there's no direct way in MSR to "convert" an array into a list. Seems your brain encountered the same type of mental collision while trying to work out your imported expression. 🙂

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

                  @librasun My notes in the code:

                  911a7b09-dc4b-4bd3-8cdf-ac8e14be82bf-image.png

                  Guess it's time to get to 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
                  1
                  • cw-kidC cw-kid

                    @librasun

                    What makes the expression run and generate a new number after a period of time?

                    This is what I have so far.

                    Trigger is the virtual switch in Vera.
                    Pulse every 1 seconds and repeat every 60 seconds.

                    40a55606-5dd6-4434-8131-03320411fb36-image.png

                    Set Reaction - Groups that look at the expression named "ChooseColour" and its current number value and then runs a Global Reaction now directly sets that colour on the LED strip.

                    c928ebf7-c1cf-4400-9230-0c3d15953375-image.png

                    The random number generator expression named "ChooseColour" this is a rule expression not a Global Expression.

                    b1a6ba74-2a13-40bc-b9f3-5cdebc0be840-image.png

                    I added an 1 minute interval to the triggers and the virtual switch is true trigger is also pulsing every minute.

                    The expression is now changing numbers every minute, but the reactions don't seem to be running as the colour is stuck and not changing.

                    Also I think this expression generates the number zero which I don't have assigned to any reaction.

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

                    @cw-kid Just so you know, I have a "Color Cycler" rule that uses the [Entity Action] [Set Color RGB] action with this expression inside each field ("R", "G" and "B"):

                    ${{ floor(random()*255) }}
                    

                    which makes the associated light (a Hue bulb) adopt a perfectly random color. Just something you might consider trying.

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

                      Thanks I will try the "Color Cycler" in a brand new rule to test it out.

                      I haven't as yet looked at updating my current rule with the new expression to always guarantee a new random number that hasn't been repeated etc.

                      I will have a look over the weekend. Sure I will have questions.

                      Cheers

                      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.

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

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

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

                        I've just tried using this in my rule set, I added it as the expression for the rule. When I press the play button next to it, it seems to work and changes to different numbers between 1 to 7 etc.

                        00c35ba9-2e00-4e8a-9466-a9bdcab01860-image.png

                        However when I restart Reactor it says it cannot find the Global Expression named "randomVal".

                        So I then created it as a Global Expression, the error has now gone away, but I don't understand what this Global Expression is for?

                        be503a5a-92f9-4a03-bc35-2a9061f6fc94-image.png

                        Thanks

                        1 Reply Last reply
                        0
                        • ElcidE Offline
                          ElcidE Offline
                          Elcid
                          wrote on last edited by Elcid
                          #37

                          That should be used in the reaction as image below
                          Screenshot_20210619-173952.png

                          The expression global or normal is left blank. so every time your rule reaction runs it sets a new unique random number, ready for next time

                          cw-kidC 1 Reply Last reply
                          1
                          • ElcidE Elcid

                            That should be used in the reaction as image below
                            Screenshot_20210619-173952.png

                            The expression global or normal is left blank. so every time your rule reaction runs it sets a new unique random number, ready for next time

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

                            @elcid

                            This look better now?

                            I have added the Set Variable in the Set Reaction and made the expression empty:

                            fec35140-bd79-4484-85e6-15ea34d22fe6-image.png

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

                              It looks to be working OK. Its changing the colours on the LED strip every 5 minutes currently. I'll leave it running for a while tonight.

                              Thanks.

                              1 Reply Last reply
                              0
                              • toggledbitsT toggledbits locked this topic on
                              Reply
                              • Reply as topic
                              Log in to reply
                              • Oldest to Newest
                              • Newest to Oldest
                              • Most Votes


                              Recent Topics

                              • Access control - allowing anonymous user to dashboard
                                toggledbitsT
                                toggledbits
                                0
                                2
                                44

                              • VEC Virtual Switch Auto Off
                                S
                                SweetGenius
                                1
                                1
                                34

                              • Upcoming Storage Change -- Got Back-ups?
                                toggledbitsT
                                toggledbits
                                2
                                1
                                30

                              • Oddness in Copy/Move of Reactions
                                G
                                gwp1
                                0
                                1
                                63

                              • [Solved] function isRuleEnabled() issue
                                CrilleC
                                Crille
                                0
                                4
                                92

                              • [Reactor] Problem with Global Reactions and groups
                                therealdbT
                                therealdb
                                0
                                3
                                106

                              • Possible feature request 2?
                                CatmanV2C
                                CatmanV2
                                0
                                3
                                78

                              • Reactor (Multi-System/Multi-Hub) Announcements
                                toggledbitsT
                                toggledbits
                                5
                                133
                                80.1k

                              • Genuinely impressed with Zigbee and HA / Reactor
                                CatmanV2C
                                CatmanV2
                                1
                                9
                                393

                              • Copying a global reaction
                                toggledbitsT
                                toggledbits
                                0
                                3
                                117

                              • [HowTo] Using HABridge with Reactor
                                CatmanV2C
                                CatmanV2
                                0
                                9
                                453

                              • [Reactor] Bug when sending MQTT boolean payloads
                                toggledbitsT
                                toggledbits
                                0
                                4
                                173
                              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