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. Cheapest platform on which to run MSR
Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
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
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor

Cheapest platform on which to run MSR

Scheduled Pinned Locked Moved Multi-System Reactor
27 Posts 7 Posters 5.8k 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.
  • Black CatB Black Cat

    With the new Raspberry Pi Imager you can configure the boot sequence and user when you download (format) the card or SSD.
    Click on the settings Icon (lower righthand side) that will give you access to setting User Names, SSH and more..
    Make sure you use the Rasp Pi downloader for this and its a breeze.

    I suggest you just throw caution to the wind and buy a SSD, they aren't that much more expensive than a SD Card.
    The Pi4 makes it all worth while

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

    @black-cat TOTALLY agree on the SSD. I found a three-pack on AMZ for a very reasonable cost and haven't looked back. Everything runs much smoother/faster than on the SD card (for obvious reasons) and the knowledge that I'm not facing a SD card failure is reassuring.

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

    *HASS 2025.11.1
    w/ ZST10-700 fw 7.18.3

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

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

      Thanks for all the suggestions and support. I have a 16 GB SSD coming (based on advice given). I was hoping to install the OS directly as I don't have a SD Card. Still, it's a small problem if that all that is stopping me. I was thinking of using (installing?) a Docker so that I can install other applications too, but would this be too much to bite off for a beginner?

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

      toggledbitsT 1 Reply Last reply
      0
      • T Talisker

        Thanks for all the suggestions and support. I have a 16 GB SSD coming (based on advice given). I was hoping to install the OS directly as I don't have a SD Card. Still, it's a small problem if that all that is stopping me. I was thinking of using (installing?) a Docker so that I can install other applications too, but would this be too much to bite off for a beginner?

        toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by toggledbits
        #14

        @talisker said in Cheapest platform on which to run MSR:

        I was thinking of using (installing?) a Docker so that I can install other applications too, but would this be too much to bite off for a beginner?

        I recommend it. It takes away a lot of details. Install docker and docker-compose on the RPi like this:

        sudo apt-get install docker docker-compose
        

        I recommend using docker-compose to manage the container from the command line. The installation instructions (for Reactor on docker) give you a template docker-compose configuration file you can just copy-paste. It makes starting the Reactor container much less verbose, and it basically manages itself once started (including restarting at boot). Upgrades are this easy:

        docker-compose down     # stop Reactor
        docker-compose pull     # pull updated Reactor image
        docker-compose up -d    # restart Reactor on new image
        

        I guess you could also install Portainer for a GUI to manage docker, but I think that's more complicated. Put the three lines above in a script file and run it whenever you need to.

        I would also recommend installing Geany if you plan on using the desktop GUI. It's a very easy programmer's text editor that does syntax highlighting, so it will help you make correct changes to Reactor's YAML configuration files, shell scripts, etc.

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

          No, a Pi 2 won't do it. Well, you probably could, but I don't recommend it and I haven't tried it. A 3B+ is workable. I've tested that, so that's the safest minimum I can recommend.

          I've had trouble getting Pis as well for multiple projects, but I recently found rpilocator.com and I can highly recommend it. If you follow them on Twitter you can basically get alerts from them and it helps. You need to be quick. Yesterday they reported over 100 units available from a popular US seller, and today that seller is reported out of stock.

          I recently managed to get a Compute Module 4 with 8GB EMMC (built-in Flash storage like an SSD). That ran me US$45 for the CM4, and another $40 for the I/O board on which you mount it. I am testing that right now, and will likely use it as my build system for 64-bit Raspbian Bullseye releases (coming soon). It's much tidier than fussing with the USB-SATA adapter. That is all equivalent to a 4B+ in power, and may be equivalent or even a little lower in price -- by the time you've purchased a Pi 4B+ with 2GB RAM, an 8GB or larger SSD, and the USB 3.1 to SATA interface, you're in the same price range. Either way you go, the investment is a computing platform you can use for a long time; they've got good power, are well-built little boards (all), etc.

          Also, for any configuration with less than 2GB RAM, I recommend using the "Lite" version of the OS install (no desktop/GUI, command line only). That would include the 3B+.

          toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #15

          I want to add that I've been using a (Raspberry Pi) Compute Module 4 with 8GB EMMC on board (and no Wi-Fi), mounted on the RPi CM4 I/O Board, and it's a great combination and alternative. I mentioned that earlier in this thread when I first got it, and now it's been about six weeks and I've got some experience with it. The overall cost was comparable to the RPi 4B+ maker/consumer board with an added SSD and USB3.1 interface (around $45 for the CM4 and $40 for the I/O board, so US$85). The CM4's are more available right now (still hard to get, but much easier than the maker board) because RPi is giving manufacturing priority to CM4 to support industry. The I/O boards are easy to get and always have been. The I/O board offers two on-board HDMI interfaces, a PCIe (x1) ssocket (for many things, like another way to get storage), a gigabit Ethernet port, two USB 2.0 connectors (hmmmph, rather see 3.x), microSD socket (for non-EMMC models), two camera connectors, two display connectors, 28 x GPIO, and a battery-backed real time clock. You can power it with a 12VDC power supply (2.1mm positive tip barrel connector), so it's easy to get the power in that the board really needs, and on a connector I regard as more stable and durable for that purpose than USB micro. It also offers a Berg-style power connector for use with, for example, a small (MeanWell) switching PSU. It has a USB micro connector for connecting to a PC, where the system then looks like a Flash drive so you can do updates or make filesystem changes on a cold system.

          Below are a couple of photos of my rig in a case I designed in Fusion 360 and 3D printed.

          20220609_130143.jpg 20220609_130155.jpg

          It's a bit (1-2cm) smaller than a Vera Plus in every dimension; for non-Vera readers, that's about the size of many 4-port Ethernet switches and small routers. It's fanless, and so far, I haven't seen the need for anything other than passive/convective cooling. But I will be adding heat sinks to the CM4, just for more headroom. The I/O board has a standard four-pin fan connector that works from the 12VDC supply.

          What I especially like is that the eMMC storage is bus-connected to the CPU on the same card, so it's much faster than either MicroSD or SSD-over-USB. I haven't tested PCIe storage yet. The CM4 configuration is also much less fragile. I find the USB interface cable necessary for the SSD on the maker board setup to be unwieldy to cable manage, and I've learned not to move it at all when running or I'll cause disk faults and a kernel crash (i.e. it looks and acts like cobbled together bits, where the CM4+I/O looks purpose-built). The real time clock is also great to have; many of you may remember from Those Other Forums that I am firmly of the opinion that no serious IoT platform can be built without one (so that the time is very close to correct when the system cold boots after a power loss and network time is not yet available, and thus time-bsed automations don't go crazy due to a reset/default clock).

          I highly recommend this approach to anyone. For CM4 configuration, I think the 2GB RAM/8GB eMMC (MSRP US$40 without Wi-Fi, US$45 with) is good for just a basic Reactor host, but the filesystem may end up a little tight if you also want to run Hass, InfluxDB, etc. (the OS itself takes almost half of my 8GB with the desktop GUI installed). I would go up to 16GB or 32GB eMMC for those, and 4GB RAM. The maximum manufactured configuration is 8GB RAM and 32GB eMMC, with an MSRP of US$90/95 without/with Wi-Fi. Run it on the 64-bit version of Raspbian Bullseye. Unless you have some reason to want Wi-Fi, I'd save the US$5 — running your IoT automations on Wi-Fi as primary network interface is not a good idea (IMO); the I/O board's gigabit Ethernet port is The Way. Full specs for the CM4 are here, and for the I/O board here.

          Just so I've said it, I don't think the maker board configuration is bad at all, it's just in a close second place for me right now (because of the form factor issues and the real time clock). Six weeks ago I didn't have enough experience with the CM4 to declare it my favorite, but as of right now, that's where it is. But I would in no way shy away from the maker board or recommend against it. I've seen some tidy rigs put together with easily-printed cases for the maker board with an SSD, and some clever right-angle USB connectors to ease the USB cabling issue. But if you're comparing cost and convenience of the two configurations, I now think the CM4+I/O configuration edges out the maker board. The best configuration for you is the one you find most agreeable, always.

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

            @talisker said in Cheapest platform on which to run MSR:

            I was thinking of using (installing?) a Docker so that I can install other applications too, but would this be too much to bite off for a beginner?

            I recommend it. It takes away a lot of details. Install docker and docker-compose on the RPi like this:

            sudo apt-get install docker docker-compose
            

            I recommend using docker-compose to manage the container from the command line. The installation instructions (for Reactor on docker) give you a template docker-compose configuration file you can just copy-paste. It makes starting the Reactor container much less verbose, and it basically manages itself once started (including restarting at boot). Upgrades are this easy:

            docker-compose down     # stop Reactor
            docker-compose pull     # pull updated Reactor image
            docker-compose up -d    # restart Reactor on new image
            

            I guess you could also install Portainer for a GUI to manage docker, but I think that's more complicated. Put the three lines above in a script file and run it whenever you need to.

            I would also recommend installing Geany if you plan on using the desktop GUI. It's a very easy programmer's text editor that does syntax highlighting, so it will help you make correct changes to Reactor's YAML configuration files, shell scripts, etc.

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

            @toggledbits said in Cheapest platform on which to run MSR:

            I guess you could also install Portainer for a GUI to manage docker, but I think that's more complicated

            @toggledbits, more complicated is an understatement.
            I'd like to hear from anyone who has done this and not experienced difficulties, I've been able to run either (Reactor or Portainer) but not both in Portainer Container. Over to the experts.....

            aka Zedrally

            1 Reply Last reply
            0
            • toggledbitsT toggledbits

              I want to add that I've been using a (Raspberry Pi) Compute Module 4 with 8GB EMMC on board (and no Wi-Fi), mounted on the RPi CM4 I/O Board, and it's a great combination and alternative. I mentioned that earlier in this thread when I first got it, and now it's been about six weeks and I've got some experience with it. The overall cost was comparable to the RPi 4B+ maker/consumer board with an added SSD and USB3.1 interface (around $45 for the CM4 and $40 for the I/O board, so US$85). The CM4's are more available right now (still hard to get, but much easier than the maker board) because RPi is giving manufacturing priority to CM4 to support industry. The I/O boards are easy to get and always have been. The I/O board offers two on-board HDMI interfaces, a PCIe (x1) ssocket (for many things, like another way to get storage), a gigabit Ethernet port, two USB 2.0 connectors (hmmmph, rather see 3.x), microSD socket (for non-EMMC models), two camera connectors, two display connectors, 28 x GPIO, and a battery-backed real time clock. You can power it with a 12VDC power supply (2.1mm positive tip barrel connector), so it's easy to get the power in that the board really needs, and on a connector I regard as more stable and durable for that purpose than USB micro. It also offers a Berg-style power connector for use with, for example, a small (MeanWell) switching PSU. It has a USB micro connector for connecting to a PC, where the system then looks like a Flash drive so you can do updates or make filesystem changes on a cold system.

              Below are a couple of photos of my rig in a case I designed in Fusion 360 and 3D printed.

              20220609_130143.jpg 20220609_130155.jpg

              It's a bit (1-2cm) smaller than a Vera Plus in every dimension; for non-Vera readers, that's about the size of many 4-port Ethernet switches and small routers. It's fanless, and so far, I haven't seen the need for anything other than passive/convective cooling. But I will be adding heat sinks to the CM4, just for more headroom. The I/O board has a standard four-pin fan connector that works from the 12VDC supply.

              What I especially like is that the eMMC storage is bus-connected to the CPU on the same card, so it's much faster than either MicroSD or SSD-over-USB. I haven't tested PCIe storage yet. The CM4 configuration is also much less fragile. I find the USB interface cable necessary for the SSD on the maker board setup to be unwieldy to cable manage, and I've learned not to move it at all when running or I'll cause disk faults and a kernel crash (i.e. it looks and acts like cobbled together bits, where the CM4+I/O looks purpose-built). The real time clock is also great to have; many of you may remember from Those Other Forums that I am firmly of the opinion that no serious IoT platform can be built without one (so that the time is very close to correct when the system cold boots after a power loss and network time is not yet available, and thus time-bsed automations don't go crazy due to a reset/default clock).

              I highly recommend this approach to anyone. For CM4 configuration, I think the 2GB RAM/8GB eMMC (MSRP US$40 without Wi-Fi, US$45 with) is good for just a basic Reactor host, but the filesystem may end up a little tight if you also want to run Hass, InfluxDB, etc. (the OS itself takes almost half of my 8GB with the desktop GUI installed). I would go up to 16GB or 32GB eMMC for those, and 4GB RAM. The maximum manufactured configuration is 8GB RAM and 32GB eMMC, with an MSRP of US$90/95 without/with Wi-Fi. Run it on the 64-bit version of Raspbian Bullseye. Unless you have some reason to want Wi-Fi, I'd save the US$5 — running your IoT automations on Wi-Fi as primary network interface is not a good idea (IMO); the I/O board's gigabit Ethernet port is The Way. Full specs for the CM4 are here, and for the I/O board here.

              Just so I've said it, I don't think the maker board configuration is bad at all, it's just in a close second place for me right now (because of the form factor issues and the real time clock). Six weeks ago I didn't have enough experience with the CM4 to declare it my favorite, but as of right now, that's where it is. But I would in no way shy away from the maker board or recommend against it. I've seen some tidy rigs put together with easily-printed cases for the maker board with an SSD, and some clever right-angle USB connectors to ease the USB cabling issue. But if you're comparing cost and convenience of the two configurations, I now think the CM4+I/O configuration edges out the maker board. The best configuration for you is the one you find most agreeable, always.

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

              @toggledbits said in Cheapest platform on which to run MSR:

              I want to add that I've been using a (Raspberry Pi) Compute Module 4 with 8GB EMMC on board

              Way to go, unfortunately for me, the CM4 I/O board is the only part available. The Compute Module 4 is OOS (all versions), sigh.....
              BTW, I love the case.....makes it all look very professional.

              aka Zedrally

              toggledbitsT 1 Reply Last reply
              1
              • Black CatB Black Cat

                @toggledbits said in Cheapest platform on which to run MSR:

                I want to add that I've been using a (Raspberry Pi) Compute Module 4 with 8GB EMMC on board

                Way to go, unfortunately for me, the CM4 I/O board is the only part available. The Compute Module 4 is OOS (all versions), sigh.....
                BTW, I love the case.....makes it all look very professional.

                toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by toggledbits
                #18

                @black-cat said in Cheapest platform on which to run MSR:

                The Compute Module 4 is OOS

                It's terrible right now, for sure. Just a reminder, rpilocator.com may be helpful. I'm asking him if he can add AU/NZ vendors, but I see PiAustralia has starter kits available (not just board, but a kit with a board). Pricey, but if you must have, maybe worth the premium.

                For anyone it helps, it appears Semaf in Austria has stock of RPI 4B 2GB at the moment, and has since last night.

                Update: Core Electronics (AU) also has the starter kit and the desktop kit in stock, and both come with a Pi 4 board.

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

                  If anyone is interested, I've published my model for the Compute Module 4 case on printables.com.

                  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
                  • A Offline
                    A Offline
                    Alan_F
                    wrote on last edited by
                    #20

                    @black-cat I run Reactor and Portainer on a Pi4 without any issues.

                    The Pi is running Node-Red (bare metal), and in Docker: Teslamate (includes Teslamate, Grafana, Traefik, PostgreSQL, MQTT), Reactor (includes InfluxDB for Reactor, Chronograf, Telegraf), Gotify (a self-hosted notification platform), and a Tesla Powerwall integration (includes 2nd instances of Telegraf and InfluxDB, Grafana, and pypowerwall). Fifteen containers when you add Portainer itself. The Portainer GUI makes this all much easier to manage.

                    1 Reply Last reply
                    0
                    • Black CatB Offline
                      Black CatB Offline
                      Black Cat
                      wrote on last edited by
                      #21

                      @Alan_F , thanks for the reply.
                      The difficulty I have is not running it but setting MSR configuration.
                      I haven't been able to locate where the config files reside. @toggledbits, could MSR have a goto button for setting the configs in the Tools page?
                      That would make setting configs extremely easy.

                      aka Zedrally

                      toggledbitsT 1 Reply Last reply
                      0
                      • Black CatB Black Cat

                        @Alan_F , thanks for the reply.
                        The difficulty I have is not running it but setting MSR configuration.
                        I haven't been able to locate where the config files reside. @toggledbits, could MSR have a goto button for setting the configs in the Tools page?
                        That would make setting configs extremely easy.

                        toggledbitsT Offline
                        toggledbitsT Offline
                        toggledbits
                        wrote on last edited by
                        #22

                        @black-cat said in Cheapest platform on which to run MSR:

                        I haven't been able to locate where the config files reside.

                        They live in the config subdirectory of the directory you created. You're using Portainer? Should be in the configuration of the existing container (it's a binding to /var/reactor inside the container).

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

                        R 1 Reply Last reply
                        0
                        • R Offline
                          R Offline
                          retireditguy
                          wrote on last edited by
                          #23

                          Love your printed case, but it is not tall or deep enough to add the PCIE adapter for an m2 SSD. Have you come across any oversized cases for the CM4 IO boards that would accommodate use of the PCI slot.

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

                            If you tell me how much more clearance you need, I'd be happy to model a roomier version.

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

                            R 1 Reply Last reply
                            0
                            • toggledbitsT toggledbits

                              If you tell me how much more clearance you need, I'd be happy to model a roomier version.

                              R Offline
                              R Offline
                              retireditguy
                              wrote on last edited by
                              #25

                              @toggledbits I have the CM4IO currently installed in a Waveshare CM4-IO-Board- Case-A metal case. The board is mounted to standoffs inside the case. I was able to remove enough of the front rim of the case to be able to mount the board without the cover, so depth is no longer an issue (There was already a small cutout area in the rim.) Overall the case is 6 7/8" wide x 4 1/8" deep x 1 1/8" high. It needs about another 1 1/2" in height, making the total height 2 1/2". I appreciate your offer to model a roomier case, but I don't have a 3D printer so it would be of little use to me. I guess that I will have to run it without a cover until the market catches up, assuming that the CM4 on CM4 IO is selling well.

                              1 Reply Last reply
                              0
                              • toggledbitsT toggledbits

                                @black-cat said in Cheapest platform on which to run MSR:

                                I haven't been able to locate where the config files reside.

                                They live in the config subdirectory of the directory you created. You're using Portainer? Should be in the configuration of the existing container (it's a binding to /var/reactor inside the container).

                                R Offline
                                R Offline
                                retireditguy
                                wrote on last edited by
                                #26
                                This post is deleted!
                                toggledbitsT 1 Reply Last reply
                                0
                                • R retireditguy

                                  This post is deleted!

                                  toggledbitsT Offline
                                  toggledbitsT Offline
                                  toggledbits
                                  wrote on last edited by
                                  #27

                                  @retireditguy your question is OT for this thread and belongs in its own topic. Please start a new topic for your question. Also, please refer to the posting guidelines before (re)asking your question.

                                  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 locked this topic on
                                  Reply
                                  • Reply as topic
                                  Log in to reply
                                  • Oldest to Newest
                                  • Newest to Oldest
                                  • Most Votes


                                  Recent Topics

                                  • Local expression in Rule does not evaluate as they used to do
                                    CrilleC
                                    Crille
                                    0
                                    1
                                    16

                                  • Home Assistant 2025.11.2 and latest-25315
                                    G
                                    gwp1
                                    0
                                    6
                                    59

                                  • Reactor (Multi-System/Multi-Hub) Announcements
                                    toggledbitsT
                                    toggledbits
                                    5
                                    129
                                    73.6k

                                  • Notice to Docker + ARM Users (RPi 3/4/5 and others)
                                    toggledbitsT
                                    toggledbits
                                    1
                                    1
                                    45

                                  • Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
                                    M
                                    mgvra
                                    1
                                    3
                                    110

                                  • Script action and custom timers
                                    toggledbitsT
                                    toggledbits
                                    0
                                    4
                                    129

                                  • Help resolve change in behaviour post update
                                    CatmanV2C
                                    CatmanV2
                                    0
                                    12
                                    347

                                  • There is an alternative to homebridge-mqttthing
                                    akbooerA
                                    akbooer
                                    1
                                    2
                                    106

                                  • Reactor w/HA 2025.11 error on set_datetime service call setting only time
                                    CrilleC
                                    Crille
                                    0
                                    6
                                    141

                                  • Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
                                    toggledbitsT
                                    toggledbits
                                    0
                                    17
                                    421

                                  • Shelly Wall Display XL
                                    akbooerA
                                    akbooer
                                    2
                                    9
                                    775

                                  • [Solved] alarm() in global expression throws error in log.
                                    toggledbitsT
                                    toggledbits
                                    0
                                    26
                                    774
                                  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