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. Multi-System Reactor Developer Preview AVAILABLE
Can you run MSR on Home Assistant OS ?
cw-kidC
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC. Sounds like Home Assistant OS is linux based using Docker for HA etc. Would I also be able to install things like MSR as well on their OS ? On the same box? Thanks.
Multi-System Reactor
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
This trigger no longer working - complaining about the operator needing changing
cw-kidC
Topic thumbnail image
Multi-System Reactor
Self test
CatmanV2C
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something? Cheers C
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

Multi-System Reactor Developer Preview AVAILABLE

Scheduled Pinned Locked Moved Multi-System Reactor
124 Posts 12 Posters 58.0k Views 14 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.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #25

    On my list of hubs/controllers to tackle next are Homey and OpenHAB, but I am also interested in MQTT, so I'm hearing a bump in priority coming, at least for investigation.

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

    rafale77R 1 Reply Last reply
    1
    • LibraSunL Offline
      LibraSunL Offline
      LibraSun
      wrote on last edited by
      #26

      I'm enjoying this thread as it develops, but will stand by until someone wraps MSR into a Docker package that I can install/run on my Docker-enabled Synology NAS.

      Like everyone else, "I'm at full candy corn" (so the Stewie Griffith saying goes) on this project and can't wait to give it a whirl!

      • LS
      1 Reply Last reply
      3
      • toggledbitsT toggledbits

        On my list of hubs/controllers to tackle next are Homey and OpenHAB, but I am also interested in MQTT, so I'm hearing a bump in priority coming, at least for investigation.

        rafale77R Offline
        rafale77R Offline
        rafale77
        wrote on last edited by rafale77
        #27

        @toggledbits

        Definitely a vote for MQTT here though it does require setup on both MSR and the "children" controllers, it reduces the I/O traffic dramatically compared to the polling approaches. In my personal case, since I am a bit bored like @therealdb, and don't have much to add or improve to my home automation, my interest is on improving efficiencies. I find satisfaction even when decreasing CPU utilization by decimal points.

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

          I realise that I have to re-think my rules from Vera since I can only have one set of reaction to a rule. In Vera you could have different reaction to different rules within one sensor. I have to look at Rule Set's

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

            The importer will automatically split out any group that has activities (from Vera) to a Rule in MSR, and leave a "rule" condition in the parent to preserve the logic. I think it's wayyyy more convenient, but I've also had a few months of working on it to get used to it.

            You can also create global reactions that can be run from any other reaction.

            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
            • MatohlM Offline
              MatohlM Offline
              Matohl
              wrote on last edited by Matohl
              #30

              I realise that but I was so into the "old" Reactor I had to re-think a little bit. I want to build my logic without importing the old mistakes from the beginning. Suggestion for improvement: To set dimming level you have yellow background and white text which is very difficult to read, at least for my eyes 🙂
              Edit: Wrong I was using the app "Dark Reader" on my RPi witch confused the colours. Turning it off it is black on yellow

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

                FYI, the yellow indicator means it's going to let you do what you are asking, but the value you are giving is out of range. Dimming values in MSR are real numbers between 0 and 1 inclusive.

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

                  Release 21050 just published; use the "Download" button in the bug tracker.

                  Upgrade instructions

                  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
                  • G Offline
                    G Offline
                    gwp1
                    wrote on last edited by
                    #33

                    how does one obtain creds to the MantisBT?

                    *Hubitat C-7 2.4.3.177
                    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                    *HAOS
                    Core 2026.1.1
                    w/ HA Connect ZWA-2
                    FW: v1.1
                    SDK: v7.23.1

                    *Prod MSR in docker/portainer
                    MSR: latest-26011-c621bbc7
                    MQTTController: 25139
                    ZWave Controller: 25139

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

                      Send me a PM with your email address and full name; I'll set up your account and the site will email you.

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

                      G 1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        Send me a PM with your email address and full name; I'll set up your account and the site will email you.

                        G Offline
                        G Offline
                        gwp1
                        wrote on last edited by
                        #35

                        @toggledbits Done. Thanks!

                        *Hubitat C-7 2.4.3.177
                        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                        *HAOS
                        Core 2026.1.1
                        w/ HA Connect ZWA-2
                        FW: v1.1
                        SDK: v7.23.1

                        *Prod MSR in docker/portainer
                        MSR: latest-26011-c621bbc7
                        MQTTController: 25139
                        ZWave Controller: 25139

                        1 Reply Last reply
                        0
                        • rafale77R rafale77

                          @toggledbits

                          Definitely a vote for MQTT here though it does require setup on both MSR and the "children" controllers, it reduces the I/O traffic dramatically compared to the polling approaches. In my personal case, since I am a bit bored like @therealdb, and don't have much to add or improve to my home automation, my interest is on improving efficiencies. I find satisfaction even when decreasing CPU utilization by decimal points.

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

                          Since we’re at it, I think the mqtt gateway should support announcements, lwt and so on.

                          This will make very easy to integrate things like Shelly, tasmota, and so on.

                          --
                          On a mission to automate everything.

                          My MS Reactor contrib
                          My Luup Plug-ins

                          1 Reply Last reply
                          0
                          • PerHP Offline
                            PerHP Offline
                            PerH
                            wrote on last edited by
                            #37
                            This post is deleted!
                            1 Reply Last reply
                            0
                            • toggledbitsT Offline
                              toggledbitsT Offline
                              toggledbits
                              wrote on last edited by
                              #38

                              I had an issue with an account on the bug tracker (already?) so I locked it down. PM me your full name and email address and I'll set up your account. It will email you an access link.

                              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
                              • rafale77R Offline
                                rafale77R Offline
                                rafale77
                                wrote on last edited by
                                #39

                                Got my instance going with Home Assistant. I am finding it brilliant as it is connecting to it through websocket. I am seeing the potential now to have reactor act as a bridge, detecting events happening on Home Assistant and forwarding them to openLuup and vice versa, eliminating the need for configuring additional scenes on openLuup and automation on home assistant!

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

                                  I'm getting ready to assemble today's build (21051). I think I have everything urgent covered, with some PRs left open for confirmation. There's one more I want to try to address before I roll it up and out for the day.

                                  This build also includes:

                                  • Fix for condition trigger repeating when a sustained-for delay applies (#30);
                                  • Fix an error on import (#29);
                                  • Fix an error on Hass caused by an unhandled attribute (#27);
                                  • New units configuration value "uk" (#31), as well as more granular control over units (if imperial, metric, or uk isn't enough, you can now set units by use class; per device/attribute is planned and part of the architecture as well);
                                  • Fix elevation computation problem in sunrise/set data (mangles angles if elev configured <> 0) (#34);
                                  • Now with working SMTP, Prowl, Pushover and Syslog notifications;
                                  • Notification forwarding for Hubitat (see docs for configuration details);
                                  • many documentation fixes and upgrades.

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

                                  K 1 Reply Last reply
                                  2
                                  • toggledbitsT Offline
                                    toggledbitsT Offline
                                    toggledbits
                                    wrote on last edited by
                                    #41

                                    And 21051 is now available.

                                    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
                                    • rafale77R Offline
                                      rafale77R Offline
                                      rafale77
                                      wrote on last edited by
                                      #42

                                      Updated and now added openLuup. Doesn't seem to be a problem but why do openLuup scenes and room entities keep flashing green even without seemingly any updates?

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

                                        I will look into that!


                                        Edit: It looks like the jobs object is dropped on Vera Luup when it's empty, but is always present on openLuup. Since the comparison to see if a value changes doesn't "go deep" on objects and arrays, it sees two empty objects as different every time they are presented (using JS's comparison operator), and the scene is being presented on each update even though outwardly there don't appear to be any changes. So two small diffs between Vera Luup and openLuup contributing.

                                        I'm just going to suppress anything that isn't a primitive and leave it at that. Deep inspection of objects and arrays isn't likely to be valuable or necessary.

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

                                          I'm getting ready to assemble today's build (21051). I think I have everything urgent covered, with some PRs left open for confirmation. There's one more I want to try to address before I roll it up and out for the day.

                                          This build also includes:

                                          • Fix for condition trigger repeating when a sustained-for delay applies (#30);
                                          • Fix an error on import (#29);
                                          • Fix an error on Hass caused by an unhandled attribute (#27);
                                          • New units configuration value "uk" (#31), as well as more granular control over units (if imperial, metric, or uk isn't enough, you can now set units by use class; per device/attribute is planned and part of the architecture as well);
                                          • Fix elevation computation problem in sunrise/set data (mangles angles if elev configured <> 0) (#34);
                                          • Now with working SMTP, Prowl, Pushover and Syslog notifications;
                                          • Notification forwarding for Hubitat (see docs for configuration details);
                                          • many documentation fixes and upgrades.
                                          K Offline
                                          K Offline
                                          kfxo
                                          wrote on last edited by
                                          #44

                                          @toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:

                                          I'm getting ready to assemble today's build (21051). I think I have everything urgent covered, with some PRs left open for confirmation. There's one more I want to try to address before I roll it up and out for the day.

                                          This build also includes:

                                          • Fix for condition trigger repeating when a sustained-for delay applies (#30);
                                          • Fix an error on import (#29);
                                          • Fix an error on Hass caused by an unhandled attribute (#27);
                                          • New units configuration value "uk" (#31), as well as more granular control over units (if imperial, metric, or uk isn't enough, you can now set units by use class; per device/attribute is planned and part of the architecture as well);
                                          • Fix elevation computation problem in sunrise/set data (mangles angles if elev configured <> 0) (#34);
                                          • Now with working SMTP, Prowl, Pushover and Syslog notifications;
                                          • Notification forwarding for Hubitat (see docs for configuration details);
                                          • many documentation fixes and upgrades.

                                          Looking good, squashing those bugs. I will keep reporting anything I find. Just set up SMTP. Works great!

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


                                          Recent Topics

                                          • Can you run MSR on Home Assistant OS ?
                                            toggledbitsT
                                            toggledbits
                                            0
                                            5
                                            49

                                          • HA and AI
                                            therealdbT
                                            therealdb
                                            0
                                            4
                                            129

                                          • How to upgrade from an old version of MSR?
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            26
                                            332

                                          • This trigger no longer working - complaining about the operator needing changing
                                            toggledbitsT
                                            toggledbits
                                            0
                                            18
                                            79

                                          • Self test
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            102

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

                                          • VEC Virtual Switch Auto Off
                                            S
                                            SweetGenius
                                            1
                                            1
                                            83

                                          • Upcoming Storage Change -- Got Back-ups?
                                            toggledbitsT
                                            toggledbits
                                            3
                                            1
                                            80

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

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

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

                                          • Possible feature request 2?
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            151
                                          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