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. Update from 22240 to 22310 failed. New Install also failed. (Windows)
[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
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can't customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor

Update from 22240 to 22310 failed. New Install also failed. (Windows)

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

    So it was time to update MSR (and then HA but I got stuck here)
    Can't figure out what I have missed.

    My installed version of MSR was 22240.
    Node.js is version 16.15.1

    First I tried to update, following online manual.

    ||Download a Reactor distribution ZIP from https://reactor.toggledbits.com/download/ and place it in the folder above your existing reactor (runtime) directory.
    Stop and remove any existing Reactor service:

    cd \path\to\reactor
    node tools\install_reactor_windows_service.js -u .
    Remove any existing package-lock.json file from your Reactor directory.

    Unzip the archive file and copy its contents over the contents of your existing Reactor install directory.
    From the Reactor install directory, re-install/upgrade all package dependencies:

    npm install --no-save --omit dev
    If you are running Reactor as a Windows service, repeat those steps above.

    Restart Reactor (restart the service).
    Hard-refresh all browsers that are displaying Reactor content.||

    I found several (maybe it was 3) package-lock.json and I deleted all I could search in reactor folder.
    Unzip the new version and replaced old existing files.

    Install the reactor service again by instructions.

    ||In a command prompt window, running as Administrator, change directory to your Reactor install directory.
    Install the node-windows package as a global package (it must be global or the service will not work, and you must install the specific version provided by the command below):

    npm uninstall node-windows
    npm uninstall -g node-windows
    npm install -g node-windows@1.0.0-beta.6
    npm link node-windows
    Run the script to install:

    node tools\install_reactor_windows_service.js -i .||

    So this failed. Service wont start.

    Tried again.

    Then deleted everything exept my config folder and did a new install.
    Also downloaded 22310 again, but from "latest" build instead of "stable"
    When running node app.js in command promt i get some kind of error message:

    c:\reactor>node app.js
Reactor latest-22310-a6da8097 app 22310 configuration from c:\reactor\config
NODE_PATH C:\reactor
[latest-22310]2022-11-23T22:18:43.030Z <app:null> Reactor build latest-22310-a6da8097 starting on v16.15.1
c:\reactor\app.js:277
log['always'](a0_0x3d42be(0x26a), BUILD_VERSION, process['version']), log['always']('Process\x20ID\x20%1\x20user/group\x20%2/%3;\x20%4;\x20platform\x20%5/%6\x20%7;\x20locale\x20%8', process['pid'], process[a0_0x3d42be(0x269)](), process[a0_0x3d42be(0x278)](), is_docker ? 'docker' : a0_0x3d42be(0x288), process[a0_0x3d42be(0x287)], process['arch'], os[a0_0x3d42be(0x263)](), sys_locale), log[a0_0x3d42be(0x28c)]('Basedir\x20%1;\x20data\x20in\x20%2', c[a0_0x3d42be(0x1f8)], c[a0_0x3d42be(0x27b)]), log[a0_0x3d42be(0x28c)](a0_0x3d42be(0x21b), process['env'][a0_0x3d42be(0x291)]);
                                                                                                                                                                                                                                 ^

TypeError: process[a0_0x3d42be(...)] is not a function
    at Object.<anonymous> (c:\reactor\app.js:277:226)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47

    But I can't figure out what TypeError means?

    Also, before I tried a new install, there apperd an warning when installing reactor service.

    c:\reactor>npm install -g node-windows@1.0.0-beta.6
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

added 5 packages, and audited 6 packages in 3s

2 vulnerabilities (1 moderate, 1 critical)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

    Running npm audit fix --force seems to broke something, because I could not install service after that.

    c:\reactor>npm audit fix --force
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN using --force Recommended protections disabled.

up to date, audited 89 packages in 826ms

12 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

c:\reactor>node tools\install_reactor_windows_service.js -i .
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'node-windows'
Require stack:
- c:\reactor\tools\install_reactor_windows_service.js
←[90m    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m
←[90m    at Module.require (node:internal/modules/cjs/loader:1005:19)←[39m
←[90m    at require (node:internal/modules/cjs/helpers:102:18)←[39m
    at Object.<anonymous> (c:\reactor\tools\install_reactor_windows_service.js:102:15)
←[90m    at Module._compile (node:internal/modules/cjs/loader:1105:14)←[39m
←[90m    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)←[39m
←[90m    at Module.load (node:internal/modules/cjs/loader:981:32)←[39m
←[90m    at Function.Module._load (node:internal/modules/cjs/loader:822:12)←[39m
←[90m    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m {
  code: ←[32m'MODULE_NOT_FOUND'←[39m,
  requireStack: [ ←[32m'c:\\reactor\\tools\\install_reactor_windows_service.js'←[39m ]
}
    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #2

      I built a bare-metal only build 22238; download that and try it. Follow the instructions exactly. Do not run npm audit on Windows, you'll break the node-windows package and the service will not be installed. You must use exactly the version specified in the installation instructions right now.

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

      A 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        I built a bare-metal only build 22238; download that and try it. Follow the instructions exactly. Do not run npm audit on Windows, you'll break the node-windows package and the service will not be installed. You must use exactly the version specified in the installation instructions right now.

        A Offline
        A Offline
        Andr
        wrote on last edited by Andr
        #3

        @toggledbits said in Update from 22240 to 22310 failed. New Install also failed. (Windows):

        I built a bare-metal only build 22238; download that and try it. Follow the instructions exactly. Do not run npm audit on Windows, you'll break the node-windows package and the service will not be installed. You must use exactly the version specified in the installation instructions right now.

        Yes, that fixed it!
        Awesome support as always!

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

          @toggledbits, 22310 release notes are missing from the announcements?

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

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

          Recent Topics

          • [Reactor] Variables not updating correctly in latest-25201-2aa18550
            tunnusT
            tunnus
            0
            94
            7.8k
          • The reaction stopped working (Google Nest max playing a video)
            F
            Fanan
            0
            8
            570
          • Do you Matter?
            akbooerA
            akbooer
            0
            3
            192
          • Caution: zwave-js-ui docker 11.4.0 is broken
            toggledbitsT
            toggledbits
            0
            2
            127
          • Shelly Wall Display XL
            therealdbT
            therealdb
            2
            6
            337
          • Handling Dead Entities and Renamed Entities
            PablaP
            Pabla
            0
            5
            226
          • Strange behavior for MQTT templates using payload and attributes
            toggledbitsT
            toggledbits
            0
            6
            273
          • [MSR] reactor-mqtt-contrib package for additional MQTT templates
            therealdbT
            therealdb
            1
            46
            9.1k
          • HA 2025.9.4 Supported Yet?
            toggledbitsT
            toggledbits
            0
            2
            160
          • Rule Set UI bug - RESOLVED
            toggledbitsT
            toggledbits
            1
            2
            310
          • [Reactor] Copy&Paste of Rules
            therealdbT
            therealdb
            0
            1
            330
          • [Reactor] Help with screne controller cycling logic
            toggledbitsT
            toggledbits
            0
            5
            490
          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