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. How to auto start on Rpi reboot ?
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
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor

How to auto start on Rpi reboot ?

Scheduled Pinned Locked Moved Multi-System Reactor
26 Posts 6 Posters 1.7k Views 7 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
    #7

    This was the contents of the msr.service file.

    I had to change the path slightly.

    [Unit]
    Description=Multi System Reactor
    After=network.target
    
    [Service]
    Type=simple
    ExecStart=nohup /home/pi/Documents/reactor/app.sh
    Restart=on-failure
    RestartSec=5s
    
    [Install]
    WantedBy=multi-user.target
    
    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #8

      I would add User=pi at a minimum to the service section.

      I have concerns about the stop action. Investigating...

      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
        #9

        Thanks, I did miss the sudo for the nano command to create the file.

        The path does look suspicious too in addition to @toggledbits input. There may be other specificities about raspbian I may be missing.

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

          I made a mistake in the msr.service file. Corrected and now the "sudo systemctl enable msr" command runs with no error.

          I then rebooted the Pi but some time later I still cannot load MSR in the browser.

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

            This is the contents of the msr.service file now

            [Unit]
            Description=Multi System Reactor
            After=network.target
            
            [Service]
            User=pi
            Type=simple
            ExecStart=nohup /home/pi/Documents/reactor/app.sh
            Restart=on-failure
            RestartSec=5s
            
            [Install]
            WantedBy=multi-user.target
            
            1 Reply Last reply
            0
            • rafale77R Offline
              rafale77R Offline
              rafale77
              wrote on last edited by rafale77
              #12

              can you show the error by posting the output of

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

                There are several things to indicate that the process is not ready for this at this point. Among them is that the nodejs installation done by the installer is local to the pi user. There are also issues with the home directory, and the search paths for modules and data relative to the current working directory vs the path of the application.

                Too soon. Not ready yet. Not going to fix it tonight. This is prelease software. It isn't mean to run like production software at this point.

                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
                  #14

                  Think I have it working now and MSR is auto starting after a reboot

                  I placed my msr.service file in this directory:

                  /home/pi/Documents/reactor

                  Using WinSCP, on the msr.service file properties, I made its Group and Owner to be pi rather than root.

                  This is the files contents:

                  [Unit]
                  Description=Multi System Reactor
                  After=network.target
                  
                  [Service]
                  Type=simple
                  ExecStart=nohup ./app.sh &
                  WorkingDirectory=/home/pi/Documents/reactor
                  Restart=on-failure
                  RestartSec=5s
                  
                  [Install]
                  WantedBy=multi-user.target
                  

                  I then ran these commands in the terminal in Putty:

                  sudo systemctl enable /home/pi/Documents/reactor/msr.service
                  
                  sudo systemctl start msr
                  

                  And I can check its status with this command:

                  sudo systemctl status msr
                  

                  It says its active and running.

                  If I reboot the Pi now after the reboot the MSR web page is then available and can be accessed.

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

                    Yeah, but running the shell script is not correct. You're basically having systemd do what the shell script is also doing (restarting when stopped), and it's going to cause problems. Your exec is also forking, so adding yet another layer of indirection that all but guarantees that systemd is going to be looking at the wrong process ID for what it thinks is a running Reactor. That could lead to problems stopping and restarting, and with the possible effect that an incorrect stop causes data loss.

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

                      Didn't think I'd set it up correctly 😕 More of a hack to get it auto started.

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

                        You're not far off, really, but the devilish details require some internal knowledge of how Reactor starts and organizes itself, and it's made a bit more complicated by the necessity to locate things "off shore" for docker containers and make sure that stays working as well. There's a bit of a balancing act there. As I'm sure you know well, features are not strictly governed by their ability to be implemented; they are also very much a function of what it takes to support them. I'd rather there be an "official" way that I know people use, because if ten people do it their own way, I'll have ten different ways I need to figure out any time there's a problem.

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

                          Can I ask what data one could loose in a power outage? I presume that any setup (rules/expressions) change is written to persistent files on "save"?

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

                            Right now, all data is written when modified, but that may not always be the case, and there's a high likelihood it will be user-configurable, even.

                            One of the things designed in is that MSR is "crappy-storage-ready". @rafale77 can tell you at length about the merits and woes of various storage technologies, and an SD card in a Raspberry Pi is no exception (in fact, probably both a good example and a dire warning). MSR has a storage architecture for its data that allows "pluggable" storage disciplines, so you could, for example, choose a cached-with-delayed-write-back mechanism to reduce wear, and you could choose that for everything, or just states, or states and logs, etc. So in that case, as the system shuts down, it is necessary for the cache to write back any "dirty" (modified but unsaved as yet) data, or the modifications would be lost.

                            That said, you should be thinking about getting your Pi off an SD card if that's what you're running, if you intend to run it full-time with MSR and depend on it. There are only two types of SD cards: those that have failed, and those that are about to. I have my Pi running on a cheap 2.5" SSD, and it's also a good bit faster, although there is some alchemy to getting that working, and while it's much better than it was, it involves some pretty magical incantations still today and can be a bit angst-inducing.

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

                            Black CatB 1 Reply Last reply
                            1
                            • MatohlM Offline
                              MatohlM Offline
                              Matohl
                              wrote on last edited by
                              #20

                              With the newer firmwares to the RPi it is fairly straight forward to use a SSD since it has native support now. Not that much alchemy anymore.

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

                                Getting the firmware onto the Pi is a series of commands rarely used, so that's part of it. The other part is that your choice of interfaces is critical, as some are supported and some are not.

                                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
                                  #22

                                  I had no problems with the interfaces, I guess I was lucky. I bought an ordinary SATA to USB3 cable and a standard Samsung 250G disc and plugged it in.
                                  For the commands and if anyone is interested I used the following guide:

                                  Jul 24, 2021  /  Raspberry Pi

                                  How to Boot Raspberry Pi 4 / 400 From a USB SSD or Flash Drive

                                  How to Boot Raspberry Pi 4 / 400 From a USB SSD or Flash Drive

                                  A firmware update lets you use any USB device to boot a Pi 4 / 400.

                                  The only problem with the guide was that boot-option in raspi-config had been moved to another menu location since the guide was written

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

                                    The guide is OK, but it contains two omissions that I think are pretty important for the average user:

                                    1. The first is the interface issue. Only certain interfaces work, and some definitely do not. I first purchased the Sabrent 3.0 to SSD model EC-SSHD. Doesn't work. Found in another guide (linked below) what does work. Thankfully, I had on hand a bigger 3.1 dual-drive powered USB 3.1 interface I use for doing backups and other evil deeds around the house, so I got that Frankensteined on until the working Sabrent 3.1 to SSD model EC-SS31 arrived. Notice the subtle but important difference. Sad but true.
                                    2. In Tom's Guide, in the SD Card Copier, the "New Partition UUIDs" checkbox must be off. They neglect to say this (it's shown off in the screen shot, but it's worth using words). If it's on, the boot will fail because the boot script and fstab will have the old IDs rather than the new. This is easily fixed if you know where and how to do it, but I think most users would find it frustrating if they don't realize what they've done.

                                    Link with supported interfaces below. Don't use these older instructions, just use the list of supported devices it offers:

                                    Jun 29, 2019

                                    Raspberry Pi 4 USB Boot Config Guide for SSD / Flash Drives

                                    Raspberry Pi 4 USB Boot Config Guide for SSD / Flash Drives

                                    The Raspberry Pi 4 is finally here and has a lot of exciting changes. One very major downside is that it doesn’t support true USB booting yet out of the box (like the 3 series did).

                                    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

                                      Right now, all data is written when modified, but that may not always be the case, and there's a high likelihood it will be user-configurable, even.

                                      One of the things designed in is that MSR is "crappy-storage-ready". @rafale77 can tell you at length about the merits and woes of various storage technologies, and an SD card in a Raspberry Pi is no exception (in fact, probably both a good example and a dire warning). MSR has a storage architecture for its data that allows "pluggable" storage disciplines, so you could, for example, choose a cached-with-delayed-write-back mechanism to reduce wear, and you could choose that for everything, or just states, or states and logs, etc. So in that case, as the system shuts down, it is necessary for the cache to write back any "dirty" (modified but unsaved as yet) data, or the modifications would be lost.

                                      That said, you should be thinking about getting your Pi off an SD card if that's what you're running, if you intend to run it full-time with MSR and depend on it. There are only two types of SD cards: those that have failed, and those that are about to. I have my Pi running on a cheap 2.5" SSD, and it's also a good bit faster, although there is some alchemy to getting that working, and while it's much better than it was, it involves some pretty magical incantations still today and can be a bit angst-inducing.

                                      Black CatB Offline
                                      Black CatB Offline
                                      Black Cat
                                      wrote on last edited by Black Cat
                                      #24

                                      @toggledbits said in How to auto start on Rpi reboot ?:

                                      although there is some alchemy to getting that working, and while it's much better than it was, it involves some pretty magical incantations still today and can be a bit angst-inducing.

                                      ha......truer words have never been spoken.
                                      I just spent the last weekend trying to get a Pi4 booting from a SSD, followed every "how to" I could find and just can't get the bootloader to set to 0xf41, it remains stuck on 0xf14.
                                      I might have to wait for a Pi5 to achieve my dream or borrow your magical incantations.....

                                      edit: now after reading the How to patrick refers to, it confuses me even more. It appears every time there is a FW update the goal posts change and Boot Order becomes something else. 0x1 , 0x4, OMG Maybe a Windows install is easier?

                                      aka Zedrally

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

                                        OK. Build 21074 has some necessary changes to support running as a system daemon under systemd on RPi4. As seen earlier in this thread, a service file is needed that needs to be placed in (typically) /etc/systemd/system. The easiest way to get the correct service file for your current install is to run the tools/rpi-install.sh install script. On an installed system, it will not do much of anything, but it will create a file called reactor.service in the tools subdirectory. From there:

                                        1. Make sure any other Reactor processes are stopped (e.g. pkill -QUIT node)
                                        2. Use sudo cp tools/reactor.service /etc/systemd/system/ to copy the file to /etc;
                                        3. Run sudo systemctl daemon-reload
                                        4. If you want Reactor to start automatically at boot: sudo systemctl enable reactor
                                        5. Start Reactor now: sudo systemctl start reactor

                                        You should now be able to see your log file recording the startup. You may also observe the log messages rolling in /var/log/syslog. The running Reactor instance will also leave a reactor.pid file in the reactor install directory (it will remove it when it shuts down, so its absence is a good indication that it is not running under systemd).

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

                                          @toggledbits said in How to auto start on Rpi reboot ?:

                                          rpi-install.sh

                                          9f322ffb-ca93-464b-9c47-fbec7c7e12b4-image.png

                                          This is the reactor.service file it created:

                                          # This file allows you to run your Reactor installation under systemd,
                                          # so it can be started at boot. Copy this file (as root or under sudo)
                                          # to /etc/systemd/system, and then run "systemctl daemon-reload". You
                                          # can then able Reactor to start at boot "systemctl enable reactor".
                                          # The usual systemctl subcommands can also be used to start, stop, and
                                          # restart reactor at will (e.g. "systemctl restart reactor").
                                          
                                          [Unit]
                                          Description=Multi System Reactor
                                          After=network.target
                                          
                                          [Service]
                                          Type=simple
                                          User=pi
                                          WorkingDirectory=/home/pi/Documents/reactor
                                          ExecStart=/usr/bin/node app -p
                                          Restart=on-failure
                                          RestartSec=5s
                                          
                                          [Install]
                                          WantedBy=multi-user.target
                                          
                                          

                                          I followed the rest of the instructions and I could see a reactor.pid file had been created and reactor was running again.

                                          I then rebooted my Pi and after it rebooted MSR is running again.

                                          So everything appears to have worked OK.

                                          Thanks

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


                                          Recent Topics

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            43

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            122
                                            35.4k

                                          • Z-Wave Future....
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            131

                                          • Can´t restart or upgrade/deploy MSR
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            86

                                          • [Solved] Limit HA Entity in MSR
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            7
                                            191

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            662

                                          • Remote access of Zwave stick from Z-wave server
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            384

                                          • Organizing/ structuring rule sets and rules
                                            G
                                            gwp1
                                            0
                                            5
                                            374

                                          • Moving MSR from a QNAP container to RP 5 - some issues
                                            G
                                            gwp1
                                            0
                                            5
                                            346

                                          • Widget deletion does not work and landing page (status) is empy
                                            G
                                            gwp1
                                            0
                                            4
                                            340

                                          • Need help reducing false positive notifications
                                            T
                                            tamorgen
                                            0
                                            7
                                            520
                                          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