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. Does this rule look correct ?
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
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

Does this rule look correct ?

Scheduled Pinned Locked Moved Multi-System Reactor
24 Posts 4 Posters 4.8k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #1

    Schedule to turn on two side table lamps, 40 minutes before Sunset (everyday of the week) with some Constraints (Conditions) attached.

    Condition 1 = Both lamps have to be off in the first place

    AND

    Condition 2 = A virtual switch called “Dark Mode” should be off

    AND

    Condition 3 = Vera is NOT in either house mode “away” OR “vacation”

    I hope the screen shot is readable.

    1de0e3ca-0104-40b6-a3f3-0fbf2b33ea87-image.png

    I am a Reactor luddite and just want to make sure I am getting things in the right order / areas of the rule.

    Thanks

    1 Reply Last reply
    0
    • PablaP Offline
      PablaP Offline
      Pabla
      wrote on last edited by
      #2

      Were you able to snag my answer on the Vera forum and give that a try?

      cw-kidC 1 Reply Last reply
      0
      • MatohlM Offline
        MatohlM Offline
        Matohl
        wrote on last edited by
        #3

        Yes, in a quick look it seems ok

        1 Reply Last reply
        0
        • PablaP Pabla

          Were you able to snag my answer on the Vera forum and give that a try?

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

          @pabla said in Does this rule look correct ?:

          Were you able to snag my answer on the Vera forum and give that a try?

          I kinda missed it sorry.

          You are nesting different rules under one main sensor ?

          This rule just fired as per the sunset -40 time now and it did turn on the lamps OK.

          1 Reply Last reply
          0
          • PablaP Offline
            PablaP Offline
            Pabla
            wrote on last edited by
            #5

            Yes basically your set-up works fine. Was just recommending simplifying it down a bit for future scalability so you're not flooded with a bunch of different groups and activities.

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

              Please can you post your screen shot again so I can have a proper look at it.

              So the term "Sensor" in Reactor is the same as "Rule Set" in MSR ?

              1 Reply Last reply
              0
              • PablaP Pabla

                Yes basically your set-up works fine. Was just recommending simplifying it down a bit for future scalability so you're not flooded with a bunch of different groups and activities.

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

                @pabla said in Does this rule look correct ?:

                so you're not flooded with a bunch of different groups and activities.

                So can a Group created in one rule be used again in a different rule ?

                PablaP 1 Reply Last reply
                0
                • PablaP Offline
                  PablaP Offline
                  Pabla
                  wrote on last edited by Pabla
                  #8

                  I don't think I am at a trust level to attached a pic right now, I will try PMing you a pic on Vera forums on the mean time.

                  I believe a Sensor is the same as a rule set in MSR, I have not played with it yet. If you plan on using the sunset condition as a trigger for other activities, you can keep that in its' own rule set.

                  Edit: got the pic
                  757d5336-67c2-4cda-9ee3-f07416a52ffa-image.png

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

                    @pabla said in Does this rule look correct ?:

                    so you're not flooded with a bunch of different groups and activities.

                    So can a Group created in one rule be used again in a different rule ?

                    PablaP Offline
                    PablaP Offline
                    Pabla
                    wrote on last edited by
                    #9

                    @cw-kid said in Does this rule look correct ?:

                    @pabla said in Does this rule look correct ?:

                    so you're not flooded with a bunch of different groups and activities.

                    So can a Group created in one rule be used again in a different rule ?

                    If MSR is set-up similarily to Vera then yes you can reference another "Group" or "Rule Set" instead of having to create it again

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

                      I can't see a way to add a "Group" I already created in to a new Rule.

                      However I can see something called "Rule Result"

                      So I created a new Rule with just a trigger for Sunset -40 nothing else.

                      Then in my Lounge Lamps on rule I can select Rule Result and select the rule "Sunset -40" is True

                      5e7a828b-422a-4773-858e-9b37bd8b2555-image.png

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

                        I can't see a way to add a "Group" I already created in to a new Rule.

                        However I can see something called "Rule Result"

                        So I created a new Rule with just a trigger for Sunset -40 nothing else.

                        Then in my Lounge Lamps on rule I can select Rule Result and select the rule "Sunset -40" is True

                        5e7a828b-422a-4773-858e-9b37bd8b2555-image.png

                        PablaP Offline
                        PablaP Offline
                        Pabla
                        wrote on last edited by
                        #11

                        @cw-kid Ok then I guess Groups and Rule Sets arent exactly the same. You can still nestle all the other conditions into one Rule Set though for simplicity's sake.

                        Yes that is how I expect Rule Result to work. You can use this rule without having to re-create the same conditions every time.

                        cw-kidC 1 Reply Last reply
                        0
                        • PablaP Pabla

                          @cw-kid Ok then I guess Groups and Rule Sets arent exactly the same. You can still nestle all the other conditions into one Rule Set though for simplicity's sake.

                          Yes that is how I expect Rule Result to work. You can use this rule without having to re-create the same conditions every time.

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

                          @pabla said in Does this rule look correct ?:

                          Yes that is how I expect Rule Result to work. You can use this rule without having to re-create the same conditions every time

                          Yes that makes sense for Triggers.

                          @pabla said in Does this rule look correct ?:

                          You can still nestle all the other conditions into one Rule Set though for simplicity's sake

                          I'm not sure how to do that for constraints though.

                          If you look at my first screen shot above in the Constraints area, they are all my conditions.

                          So if those particular set of conditions I wanted to use again else where, your saying I could potentially create a new rule with just those conditions or constraints in that rule.

                          And then maybe reference them in another different new rule.

                          EDIT: Unless I made the primary template rule lets call it, if I put my constraints in to the triggers area of that rule instead.

                          I could then call that primary template rule from other rules using the "Rule Results" option.

                          If that makes sense, probably not LOL.

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

                            Please note that Pabla is making a recommendation for Vera Reactor, and cw-kid is asking a question about MSR.

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

                            PablaP 1 Reply Last reply
                            0
                            • toggledbitsT toggledbits

                              Please note that Pabla is making a recommendation for Vera Reactor, and cw-kid is asking a question about MSR.

                              PablaP Offline
                              PablaP Offline
                              Pabla
                              wrote on last edited by
                              #14

                              @toggledbits said in Does this rule look correct ?:

                              Please note that Pabla is making a recommendation for Vera Reactor, and cw-kid is asking a question about MSR.

                              Yes I think I am in over my head here, thought MSR was closer related to the Vera plugin.. I think you are on the right track though 😁

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

                                Yes I know he's talking about Reactor for Vera.

                                But I'm just looking around the MSR GUI to see if some of the concepts he is recommended are possible and available in MSR also.

                                1 Reply Last reply
                                0
                                • PablaP Offline
                                  PablaP Offline
                                  Pabla
                                  wrote on last edited by
                                  #16

                                  If I am understanding this correctly @toggledbits a Reactor Sensor = Rule Set, Group = Triggers and Constraints. Otherwise its very similar to the Vera Reactor? Sorry @cw-kid for high-jacking 🙂

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

                                    You can say anything you like on any of my threads mate.

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

                                      Pretty much all spot on. @Pabla I think there's enough of the Vera Reactor flavor for you to be comfortable once you start playing with it. The big differences are coming out in this thread. No ReactorSensors, but you can use Rule Sets to organize your rules. No activities (reactions in MSR) on groups, but you can make active groups into rules so they can have reactions. This is one of the big things the importer does... it scans through your ReactorSensor data finding groups that have activities and turns them into independent rules, leaving an MSR rule condition where the group was to preserve the logic (analogous to a Group State condition in Vera Reactor, as if you had moved the group elsewhere). The other big difference is the addition of Constraints as a passive filter. I say passive because changes in the conditions under Constraints can't initiate action in the rule; only a change in the state of Triggers does that. But all of the alternative tools one would use to get the same effect in Vera Reactor (e.g. sequencing option) are still there.

                                      @cw-kid, I definitely think you're getting the hang of it.

                                      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 Offline
                                        cw-kidC Offline
                                        cw-kid
                                        wrote on last edited by cw-kid
                                        #19

                                        Looks like you can do what I said.

                                        I have created some "Global Rules"

                                        One for "Night" which I've set as Civil Dusk till Civil Dawn

                                        02df96bb-388b-4c15-82d3-91cf88217e0b-image.png

                                        In another rule I can add it as a "Rule Result" within the Constrains (Conditions) area of that rule.

                                        887a1da1-53a8-4efe-b9e3-c95d9f73b993-image.png

                                        I think that should work then.

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

                                          Looks like you can do what I said.

                                          I have created some "Global Rules"

                                          One for "Night" which I've set as Civil Dusk till Civil Dawn

                                          02df96bb-388b-4c15-82d3-91cf88217e0b-image.png

                                          In another rule I can add it as a "Rule Result" within the Constrains (Conditions) area of that rule.

                                          887a1da1-53a8-4efe-b9e3-c95d9f73b993-image.png

                                          I think that should work then.

                                          PablaP Offline
                                          PablaP Offline
                                          Pabla
                                          wrote on last edited by
                                          #20

                                          @cw-kid Exactly! This way if you want to change Civil Dusk to be -30 mins or whatever it will update across all your Rule Sets!

                                          1 Reply Last reply
                                          1
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

                                          • How to upgrade from an old version of MSR?
                                            cw-kidC
                                            cw-kid
                                            0
                                            1
                                            12

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

                                          • VEC Virtual Switch Auto Off
                                            S
                                            SweetGenius
                                            1
                                            1
                                            48

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

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

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

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

                                          • Possible feature request 2?
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            91

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

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

                                          • Copying a global reaction
                                            toggledbitsT
                                            toggledbits
                                            0
                                            3
                                            124

                                          • [HowTo] Using HABridge with Reactor
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            9
                                            461
                                          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