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. Copying configuraiton and rules from QNAP install to Raspberry PI 4 install
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

Copying configuraiton and rules from QNAP install to Raspberry PI 4 install

Scheduled Pinned Locked Moved Multi-System Reactor
13 Posts 3 Posters 731 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #3

    I suspect the files on the QNAP have root as the owner. That often happens with docker containers, and if you're just logged in as the pi user trying to copy the files, you'll get those messages. Drag and drop isn't going to get you there. I don't have a QNAP NAS, but if you can ssh into it, do that (log in as yourself). Then...

    • Bring yourself up to root sudo su -.
    • Navigate (using cd) to the directory above your config, storage, and logs on the QNAP NAS.
    • Make an archive file: tar cvf ../reactorconfig.tar .
      This will create the archive file in the directory above your current directory.
    • Copy the archive file to the Pi (e.g. into /home/pi)
    • Log in on the Pi as pi
    • Become root on the Pi: sudo su -
    • Go to the directory you created for the Reactor work files (using cd)
    • Untar the archive file: tar xvf /home/pi/reactorconfig.tar
    • Make your future life easier by making pi the owner of the files (esp. the config files): chown -R pi .
    • Exit the root privilege level: exit (you are now user pi again)
    • Try starting the docker container (using docker-compose is highly recommended, see install instructions).

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

    T 1 Reply Last reply
    1
    • T Offline
      T Offline
      Talisker
      wrote on last edited by
      #4

      Thanks for the prompt responses guys. I might have to concede on this one and start my reactions again!

      On another note. I have installed / configured docker-compose (or at least I thought I had). I don't seem to be able to use it to stop reactor:

      pi@raspberrypi:~ $ docker stop reactor
      Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/reactor/stop": dial unix /var/run/docker.sock: connect: permission denied
      pi@raspberrypi:~ $ cd reactor
      pi@raspberrypi:~/reactor $ docker stop reactor
      Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/reactor/stop": dial unix /var/run/docker.sock: connect: permission denied
      pi@raspberrypi:~/reactor $ dir
      config docker-compose.yml logs storage
      pi@raspberrypi:~/reactor $ ^C
      pi@raspberrypi:~/reactor $ sudo docker stop reactor
      reactor
      pi@raspberrypi:~/reactor $ docker-compose down
      ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?

      If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
      pi@raspberrypi:~/reactor $

      Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

      1 Reply Last reply
      0
      • CatmanV2C Offline
        CatmanV2C Offline
        CatmanV2
        wrote on last edited by
        #5

        I should probably leave this to @toggledbits but what does

        su docker stop reactor
        

        do?

        C

        The Ex-Vera abuser know as CatmanV2.....

        1 Reply Last reply
        0
        • T Offline
          T Offline
          Talisker
          wrote on last edited by
          #6

          pi@raspberrypi:~/reactor $ su docker stop reactor
          su: user docker does not exist or the user entry does not contain all the required fields

          Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

          1 Reply Last reply
          0
          • CatmanV2C Offline
            CatmanV2C Offline
            CatmanV2
            wrote on last edited by
            #7

            Oh sorry!

            sudo docker stop reactor
            

            DOH

            C

            The Ex-Vera abuser know as CatmanV2.....

            T 1 Reply Last reply
            0
            • CatmanV2C CatmanV2

              Oh sorry!

              sudo docker stop reactor
              

              DOH

              C

              T Offline
              T Offline
              Talisker
              wrote on last edited by
              #8

              @catmanv2 I tried that thanks and it works:

              sudo docker stop reactor #stops reactor
              sudo service docker restart #starts reactor

              Cheers!

              Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

              1 Reply Last reply
              1
              • toggledbitsT toggledbits

                I suspect the files on the QNAP have root as the owner. That often happens with docker containers, and if you're just logged in as the pi user trying to copy the files, you'll get those messages. Drag and drop isn't going to get you there. I don't have a QNAP NAS, but if you can ssh into it, do that (log in as yourself). Then...

                • Bring yourself up to root sudo su -.
                • Navigate (using cd) to the directory above your config, storage, and logs on the QNAP NAS.
                • Make an archive file: tar cvf ../reactorconfig.tar .
                  This will create the archive file in the directory above your current directory.
                • Copy the archive file to the Pi (e.g. into /home/pi)
                • Log in on the Pi as pi
                • Become root on the Pi: sudo su -
                • Go to the directory you created for the Reactor work files (using cd)
                • Untar the archive file: tar xvf /home/pi/reactorconfig.tar
                • Make your future life easier by making pi the owner of the files (esp. the config files): chown -R pi .
                • Exit the root privilege level: exit (you are now user pi again)
                • Try starting the docker container (using docker-compose is highly recommended, see install instructions).
                T Offline
                T Offline
                Talisker
                wrote on last edited by
                #9

                @toggledbits thanks for the methodology. I manged to copy the files from a usb stick to the relevant folders using the sudo cp command. Feeling pretty pleased as I am now up an running on my raspberry pi.

                Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

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

                  Just add the pi user to the docker group on the Pi, and you won't have to sudo to use the docker or docker-compose commands.

                  # Run this command as user `pi`:
                  sudo usermod -a -G docker pi
                  

                  Going forward, you should do everything related to the process (container) via docker-compose. You should rarely need or use the docker command itself.

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

                  T 1 Reply Last reply
                  1
                  • toggledbitsT toggledbits

                    Just add the pi user to the docker group on the Pi, and you won't have to sudo to use the docker or docker-compose commands.

                    # Run this command as user `pi`:
                    sudo usermod -a -G docker pi
                    

                    Going forward, you should do everything related to the process (container) via docker-compose. You should rarely need or use the docker command itself.

                    T Offline
                    T Offline
                    Talisker
                    wrote on last edited by
                    #11

                    @toggledbits something is not working quite right with my docker install (docker-compose). Not sure where to start!

                    815c9e37-4c43-42dc-b343-258a9016cff8-image.png

                    Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

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

                      Can you post your compose file? Also, I assume you ran the docker-compose command while in the same directory as the compose file? Did you start it with docker-compose? If not, you're probably going to get errors like this trying to stop it with docker-compose... the two commands are not interchangeable (for start/stop).

                      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
                      • T Offline
                        T Offline
                        Talisker
                        wrote on last edited by
                        #13

                        Sorry @toggledbits . I tied it again after a good break and it appears to work fine. I honestly don't know what was going wrong but things seem to now be in order:

                        pi@raspberrypi:~ $ cd reactor
                        pi@raspberrypi:~/reactor $ ls
                        config docker-compose.yml logs storage
                        pi@raspberrypi:~/reactor $ docker-compose down
                        Stopping reactor ... done
                        Removing reactor ... done
                        Removing network reactor_default
                        pi@raspberrypi:~/reactor $ docker-compose pull
                        Pulling reactor ... done
                        pi@raspberrypi:~/reactor $ docker-compose up -d
                        Creating network "reactor_default" with the default driver
                        Creating reactor ... done

                        docker-compose.yml below FYI:

                        Multi-System Reactor template docker-compose.yml (version 22160)

                        Change the lines indicated by "DO"...

                        version: '3'

                        services:
                        reactor:
                        container_name: reactor
                        environment:
                        # DO change the TZ: line to set your local time zone.
                        # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
                        TZ: GB
                        #
                        # DO NOT change this path. Your directory location is in "source" below.
                        REACTOR_DATA_PREFIX: /var/reactor

                        # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4)
                        image: toggledbits/reactor:latest-aarch64
                        
                        restart: "always"
                        expose:
                          - 8111
                        ports:
                          - 8111:8111
                        volumes:
                            # DO change the /home/username/reactor below to the directory you created for
                            # your local data; DO NOT change the /var/reactor part
                          - /home/pi/reactor:/var/reactor
                          - /etc/localtime:/etc/localtime:ro
                        tmpfs: /tmp
                        

                        Vera plus user. MSR user on Raspberry PI 4. Running MSR version 23049 in Docker

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


                        Recent Topics

                        • Gradually turn on lights.
                          G
                          gwp1
                          0
                          4
                          94

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

                        • Error After Upgrade
                          G
                          gwp1
                          0
                          4
                          86

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

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

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

                        • Links to MSR from HA
                          Tom_DT
                          Tom_D
                          0
                          1
                          78

                        • Set Reaction > Script Action
                          wmarcolinW
                          wmarcolin
                          0
                          11
                          416

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

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

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

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