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. Release 1.0.0
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

Release 1.0.0

Scheduled Pinned Locked Moved Multi-System Reactor
9 Posts 6 Posters 859 Views 6 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 toggledbits
    #1

    Well, it's July 19th, and as previously advertised, Reactor (Multi-System, aka MSR) has been published at release 1.0.0.

    Docker images are on DockerHub, and download package for bare-metal installs is available at https://reactor.toggledbits.com/download/

    Those of you with access to the Mantis Bug Tracker for the project, please continue to use it, particularly if you stick with the "latest" docker image tag (which will continue to be updated periodically, as will the bare-metal tarball). Feel free to open issues there on behalf of other users who do not have accounts if it seems appropriate.

    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
    11
    • PerHP Offline
      PerHP Offline
      PerH
      wrote on last edited by
      #2

      Haven't been able to do much helping on this for a while, but after installing the release docker, and moving the rest my automation to MSR i feel the need to say:
      GOOD JOB!
      Especially to Patrick, but also to all contributors.

      Automation is now very fast and intuitive to set up, and I still havent found anything i can't do with this. No bugs as far as i've seen yet either!

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

        Thanks, @PerH , and indeed, a lot of effort by many went to get it this far. And miles to go before (we) sleep...

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

        G B 2 Replies Last reply
        1
        • toggledbitsT toggledbits

          Thanks, @PerH , and indeed, a lot of effort by many went to get it this far. And miles to go before (we) sleep...

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

          @toggledbits +1 for the Robert Frost reference.

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

          *HASS 2025.6.0
          w/ ZST10-700 fw 7.18.3

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

          1 Reply Last reply
          1
          • toggledbitsT toggledbits

            Thanks, @PerH , and indeed, a lot of effort by many went to get it this far. And miles to go before (we) sleep...

            B Offline
            B Offline
            Buxton
            wrote on last edited by
            #5

            @toggledbits I was able to install the container through compose, however, I had to make some changes to get it working. See below for my compose file:

             MSR:
              container_name: reactor
              image: toggledbits/reactor:latest-generic-amd64
              restart: "on-failure"
              environment:
               REACTOR_DATA_PREFIX: /var/reactor
               TZ: America/Los_Angeles
              expose:
               - 8111
              ports:
               - 8111:8111
              volumes:
               - /home/username/reactor:/var/reactor
               - /etc/localtime:/etc/localtime:ro
              tmpfs: /tmp
            #  logging:
            #   driver: "json-file"
            #   options:
            #    max-file: 5
            #    max-size: 2m
            

            The changes I made are:
            1.) substitute "MSR" for "web" for the service name. This was just a precaution against a generic service name interfering with container management programs I use, and was not a needed/critical change to get things working.
            2.) simplify the volume syntax for binding a data volume. The syntax you have on your website caused a yaml compile error with version: '3.7' compose.
            3.) comment out the logging options. These options compiled, but threw a runtime JSON error that stopped the container from coming up:

            ERROR: for MSR  Cannot create container for service MSR: json: cannot unmarshal number into Go struct field LogConfig.HostConfig.LogConfig.Config of type string
            ERROR: Encountered errors while bringing up the project.
            

            I hope to cut out some time next week to start forming some logic. The web UI looks great.

            B 1 Reply Last reply
            1
            • PerHP Offline
              PerHP Offline
              PerH
              wrote on last edited by
              #6

              There will be some syntax differences for different versions of compose, but I would suggest that you reinstate the logging options in order to control/restrict the storage space the container uses for logs. 🙂

              1 Reply Last reply
              0
              • tunnusT Offline
                tunnusT Offline
                tunnus
                wrote on last edited by tunnus
                #7

                Just installed 1.0.0 (21200), which seems to run fine on Debian chroot. Didn't find "reactor.service-example" file that was supposed to be included in the installation package?

                EDIT: found an example from documentation, but it turned out that you cannot run systemctl under chroot 😞

                @toggledbits or anyone, any advice on running sysinit style startup script?

                Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

                1 Reply Last reply
                0
                • N Offline
                  N Offline
                  noelab
                  wrote on last edited by
                  #8

                  Hi everybody!
                  I was following this web site as non-member. Finally I have a new Synology Nas to try the new @toggledbits 's reactor project and this post is first of all to thank @toggledbits for his effort and passion to share his projects and to make them accessible even for those who are not a programmer. I know many of you reading the posts from the vera community and would like to express my gratitude for the advice you give to understand things. So a big Thanks and congratulations to Patrick for this new project !!!
                  I just installed MSR and I am excited to try it out!

                  -Reactor (Multi-hub) 25082-3c348de6
                  -Docker on Synology NAS
                  -Ezlo firmware version 2.0.59.2471.8
                  -HASS Docker 2025.2.5
                  -ZWaveJSUI 10.1.3
                  -Update 30/03/2025

                  1 Reply Last reply
                  6
                  • B Buxton

                    @toggledbits I was able to install the container through compose, however, I had to make some changes to get it working. See below for my compose file:

                     MSR:
                      container_name: reactor
                      image: toggledbits/reactor:latest-generic-amd64
                      restart: "on-failure"
                      environment:
                       REACTOR_DATA_PREFIX: /var/reactor
                       TZ: America/Los_Angeles
                      expose:
                       - 8111
                      ports:
                       - 8111:8111
                      volumes:
                       - /home/username/reactor:/var/reactor
                       - /etc/localtime:/etc/localtime:ro
                      tmpfs: /tmp
                    #  logging:
                    #   driver: "json-file"
                    #   options:
                    #    max-file: 5
                    #    max-size: 2m
                    

                    The changes I made are:
                    1.) substitute "MSR" for "web" for the service name. This was just a precaution against a generic service name interfering with container management programs I use, and was not a needed/critical change to get things working.
                    2.) simplify the volume syntax for binding a data volume. The syntax you have on your website caused a yaml compile error with version: '3.7' compose.
                    3.) comment out the logging options. These options compiled, but threw a runtime JSON error that stopped the container from coming up:

                    ERROR: for MSR  Cannot create container for service MSR: json: cannot unmarshal number into Go struct field LogConfig.HostConfig.LogConfig.Config of type string
                    ERROR: Encountered errors while bringing up the project.
                    

                    I hope to cut out some time next week to start forming some logic. The web UI looks great.

                    B Offline
                    B Offline
                    Buxton
                    wrote on last edited by
                    #9

                    @buxton Just a follow-up to the docker compose file I listed above. The error I received for the logging option occurred because I used an integer for the "max-file" field. The proper notation should be:

                      logging:
                        driver: "json-file"
                        options:
                          max-file: "5"
                          max-size: 2m
                    

                    Also note that for the logging section only, there are two spaces for the indents instead of one . YAML is unforgiving with formatting, so this too was corrected in my YAML file

                    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

                    • Gradually turn on lights.
                      G
                      gwp1
                      0
                      4
                      135

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

                    • Error After Upgrade
                      G
                      gwp1
                      0
                      4
                      105

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

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

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

                    • Links to MSR from HA
                      Tom_DT
                      Tom_D
                      0
                      1
                      91

                    • Set Reaction > Script Action
                      wmarcolinW
                      wmarcolin
                      0
                      11
                      436

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

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

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

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