Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Multi-System Reactor Developer Preview AVAILABLE
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

Multi-System Reactor Developer Preview AVAILABLE

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

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

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

    1 Reply Last reply
    0
    • rafale77R Offline
      rafale77R Offline
      rafale77
      wrote on last edited by
      #39

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

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

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

        This build also includes:

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

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

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

          And 21051 is now available.

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

          1 Reply Last reply
          0
          • rafale77R Offline
            rafale77R Offline
            rafale77
            wrote on last edited by
            #42

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

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

              I will look into that!


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

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

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

              1 Reply Last reply
              0
              • toggledbitsT toggledbits

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

                This build also includes:

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

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

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

                This build also includes:

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

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

                1 Reply Last reply
                0
                • MatohlM Offline
                  MatohlM Offline
                  Matohl
                  wrote on last edited by Matohl
                  #45

                  For being a "Developer preview" it is quite solid. After some minor issues yesterday and have been solved with 21051, I have re-built most of my Reactor-sensors in Vera in the MSR and it is working fine. They are now disabled in the Vera and let's see how it goes in the coming days 🙂

                  1 Reply Last reply
                  2
                  • A Offline
                    A Offline
                    Andr
                    wrote on last edited by
                    #46

                    Hi! I have really looking forward to this, MSR is the sole reason I have been trying to wrap my head around Home Assistant.

                    For now I am running Hassio on a VM at my Win10 "home server"
                    If I read the information right, I can't run MSR on Windows at the moment?

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

                      I'm close. I think by tomorrow or Wednesday I'll have the cross-platform issues nailed down.

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

                        OK, people, here we go! At long last, Multi-System Reactor developer preview is available!

                        The package can be downloaded from the Reactor bug tracker, a MantisBT system (at https://reactor.toggledbits.com/mantisbt/). There is a download button in the left margin, as well as links to the documentation, which you will need for installation.

                        UPDATE 2021-02-24 -- To keep spammers off, I've locked down registration on the Bug Tracker. To get access to the Bug Tracker and preview downloads, please PM me (not reply here) your full name and email address and I will set up an account for you.

                        This version of MSR will run on Linux systems, including RPi's under Raspios Buster, running node.js version 12.10 or higher (v14.15.1). For RPi users, there is an installation script that will install a local copy of node.js (for the logged-in user).

                        Bugs reports will be handled through the bug tracker only. Discussion and questions in this forum are fine, though (if that leads to a bug report, we'll transition).

                        This version supports Vera (and openLuup to the degree it's compatible with Vera Luup), Hubitat, and Home Assistant. Some of the device support on the H platforms is still a bit basic, but it is largely controlled by configuration and progress can be made quickly.

                        The documentation beyond installation is a mess. Of course, I started with the existing documentation and have been massaging into MSR's particulars, but it still has a long way to go on the detail.

                        I know I don't have to say this, but I will anyway... let me know how it goes!

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

                        Version 21054 now available.

                        • Fix 0000020: Play button doesn't run cover action (Fibaro-specific issue)
                        • Fix 0000034: Sunrise/sunset conditions over midnight don't trigger in the morning
                        • Fix 0000041: VeraController has no thermostat mapping (generic done; specific versions will almost surely be needed)
                        • Fix 0000044: Time conditions spanning midnight don't trigger in the morning
                        • Fix 0000045: Importer brings root group with options in, but root group options are not editable in MSR
                        • Fix 0000046: Hubitat configuration for URL needs to go deeper (IP and access token insufficient)
                        • Fix 0000047: VeraController rgb_color capability has attributes but no actions
                        • Fix 0000048: VeraController has no mapping for Harmony plugin

                        A couple of side notes:

                        1. The API functions mentioned here are integrated in this version;
                        2. This version runs on Windows, and there are draft instructions for how to get it installed.

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

                        K cw-kidC A 4 Replies Last reply
                        1
                        • toggledbitsT toggledbits

                          Version 21054 now available.

                          • Fix 0000020: Play button doesn't run cover action (Fibaro-specific issue)
                          • Fix 0000034: Sunrise/sunset conditions over midnight don't trigger in the morning
                          • Fix 0000041: VeraController has no thermostat mapping (generic done; specific versions will almost surely be needed)
                          • Fix 0000044: Time conditions spanning midnight don't trigger in the morning
                          • Fix 0000045: Importer brings root group with options in, but root group options are not editable in MSR
                          • Fix 0000046: Hubitat configuration for URL needs to go deeper (IP and access token insufficient)
                          • Fix 0000047: VeraController rgb_color capability has attributes but no actions
                          • Fix 0000048: VeraController has no mapping for Harmony plugin

                          A couple of side notes:

                          1. The API functions mentioned here are integrated in this version;
                          2. This version runs on Windows, and there are draft instructions for how to get it installed.
                          K Offline
                          K Offline
                          kfxo
                          wrote on last edited by
                          #49

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

                          • Fix 0000041: VeraController has no thermostat mapping (generic done; specific versions will almost surely be needed)

                          Is it possible to get thermostat (climate) mappings for HassController?

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

                            Version 21055 now available

                            • 0000048 - No support for Harmony plugin or devices (basic support); related PR 0000053 still open (details).
                            • 0000049 - Version 21054 missing SMTP
                            • 0000051 - Show reaction ID on (Global) Reactions detail card
                            • 0000054 - ALTHUE Vera plugin mapping (basic support); please comment on this PR with issues
                            • 0000055 - Telegram plugin mapping; please comment on this PR with issues

                            Resolved, but left open for confirmation/feedback (comment on PR as needed; will be closed if not further comments):

                            • 0000053 - Harmony device details
                            • 0000052 - Thermostat attributes and actions for Horstmann thermostat
                            • 0000045 - Importer will bring in options on trigger (root) group, but you can't edit them
                            • 0000005 - Set Variable action not yet implemented; now has completely untested implementation.

                            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
                            • Black CatB Offline
                              Black CatB Offline
                              Black Cat
                              wrote on last edited by
                              #51

                              Pi4 (2GB RAM) arrived today. can't wait to join in the action.
                              Some advice please from the knowledgeable ones if I can.
                              I had intended to use a SATA HD instead of the SD Card, perhaps this isn't necessary and may be an overkill?
                              What does the collective think?

                              aka Zedrally

                              1 Reply Last reply
                              0
                              • rafale77R Offline
                                rafale77R Offline
                                rafale77
                                wrote on last edited by rafale77
                                #52

                                No it’s not overkill. If you look at the HA forum, you will see legions of people migrating away from the rPI to intel NUC because of the SD card issue. These are very cheap, controller less (therefore cache less, garbage collection less, wear leveling less) NAND flash which have a relatively short lifetime (similar to what Ezio embedded in their updated/downgraded version of the vera). The rPi4 is a bit tricky to boot from SATA but it can be done and if you want a reliable system, you should definitely go down that route.

                                A big part of it of course will depend on how much storage writing you will be doing but regardless, mid-long term it’s a bit of a waste. The SSD cards are really designed for digital cameras where pictures are taken until the card is full, transferred and then erased again on a low frequency basis. They are not very good for computing storage use.

                                MatohlM 1 Reply Last reply
                                0
                                • ElcidE Offline
                                  ElcidE Offline
                                  Elcid
                                  wrote on last edited by
                                  #53

                                  In fact its a good idea, those sd cards can fail all to easily, with all the reading and writing.

                                  1 Reply Last reply
                                  0
                                  • therealdbT Online
                                    therealdbT Online
                                    therealdb
                                    wrote on last edited by
                                    #54

                                    I'm on my second NUC. The first one was a Celeron, now on an i3 I found getting dust in our offices (it was used as front desk PC before the pandemic). This to say that probably eBay is your friend, and Amazon too. You could find a lot of deals (well under 100 USD/EUR) for used/reconditioned NUCs.

                                    Mine with i3, 16GB ram (I added more) and 256 GB SSD is heavily used (openLuup, my own software, cams processing, mqtt server, a lot of mqtt clients, bluetooth for MiFlora and SwitchBot) and barely consuming more than 5% CPU.

                                    --
                                    On a mission to automate everything.

                                    My MS Reactor contrib
                                    My Luup Plug-ins

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

                                      They're good little boxes, although I wish they were a bit cheaper. My Hass runs on a NUC, and I also use a NUC as my on-LAN secondary DNS/NTP and a few other things (like Unifi management). I'm a big fan of the Jetson Nano, too. I think this board needs more attention.

                                      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 rafale77
                                        #56

                                        Alternative here in the US: I just got an HP T640 for $90. It's a little big physically but all the memory is replaceable: 2 sodimm slots, one 16gb mmc which I replaced with an SSD and boom, that's my MSR box. CPU is a ryzen equivalent of the i3 8145U in the NUC. Runs circles around any rpi for a lot less when you add up all the storage and peripheral cost. Heck it adds up to be even cheaper than my mini pc celeron box I posted in this forum before and is 3x faster. (or 8-10x faster than any rpi)

                                        More info here: https://forums.servethehome.com/index.php?threads/new-hp-t640-thin-client-ryzen-r1505g-4gb-16gf-no-kb-mouse-no-os-installed-109.31544/

                                        Edit:
                                        Added for reference comparison to rpi4... pretty hard to justify buying a raspberry honestly when they end up costing the same.

                                        https://www.cpu-monkey.com/en/compare_cpu-raspberry_pi_4_b_broadcom_bcm2711-1796-vs-amd_ryzen_embedded_r1505g-1197

                                        or here

                                        1 Reply Last reply
                                        2
                                        • rafale77R Offline
                                          rafale77R Offline
                                          rafale77
                                          wrote on last edited by rafale77
                                          #57

                                          In the same tone of what I posted before but with an older slower 6W CPU if you want to dirt cheap, these are very good (as in more reliable, upgradable, cheaper) than rPIs
                                          in the UK: https://www.ebay.com/itm/HP-Flexible-T520-Thin-Client/265062105722?
                                          in the US: https://www.ebay.com/itm/HP-T520-Flexible-Thin-Client-4GB-DDR3-V2V45UA-ABA-No-Stand-SSD/313404749197?

                                          You just need to find an old HP laptop power supply for it. That won't break your scotch budget... and amazingly they come with a windows10 pro license in the BIOS.

                                          cw-kidC 1 Reply Last reply
                                          1
                                          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
                                            5

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

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

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

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

                                          • Script action and custom timers
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            119

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

                                          • 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
                                            135

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

                                          • Shelly Wall Display XL
                                            akbooerA
                                            akbooer
                                            2
                                            9
                                            756

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