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. Release 22021 Windows Bare-metal won't load
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
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
[Solved] 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

Release 22021 Windows Bare-metal won't load

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 2 Posters 756 Views 2 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.
  • wmarcolinW Offline
    wmarcolinW Offline
    wmarcolin
    wrote on last edited by
    #1

    Hi

    I have the same situation as the Reactor interface wouldn't load in the browser, I use Windows bare-metal installation.

    Unlike the previous comment, looking at the log file I have no error, everything is loaded, and I see that the Reactor is operating, the actions are happening, only the interface in the browser that does not open.

    Thanks

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

      @wmarcolin did you run npm to update the dependencies for this release? Documented here.

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

      wmarcolinW 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        @wmarcolin did you run npm to update the dependencies for this release? Documented here.

        wmarcolinW Offline
        wmarcolinW Offline
        wmarcolin
        wrote on last edited by
        #3

        @toggledbits yes, I even saw in the manual that in the installation process you updated the command to Windows bare-metal.

        The first attempt was to follow the procedure of overwriting files from the current installation with the new version, and run the NPM process as you put in the update note. I noticed that the MSR ran, there was no error in the log, but the browse would not open.

        The second attempt, was a fresh installation, just copying from the old installation the config and storage directory, again browse did not open.

        The third action was then to do a completely new installation, copy the new config files from dist-config, update the IP and remove the Dynamic Group block because I did not put any controllers.

        83a4de66-8009-47a6-9f3b-81a0d42a17a3-image.png

        IT WORKED PERFECTLY! I see the new About page and the new Status with the new Widget, new toy 🙂

        97a7cb9b-0aa0-4bef-9f3b-9e5c3a58c2ba-image.png

        I stopped the MSR, and then copied the config and storage directories from the old version (22004), and it booted up again.

        I am no expert, but it seems to me that something in the old version might be blocking the browse from working. I have several copies of each attempt, if you want me to send you some log, or information, or make new attempts please send me a message and I will pass you the materials.

        Sorry for the boldness, but I would like to make a suggestion for the Widgets, would it be possible to remove the technical name of the rule from the logs (rule-kxhekauro)? I believe that everyone puts a name on their actions and this information may not be very useful).

        NOW IT IS VERY GOOD! One less item on the wishlist

        Once again thank you very much for all your dedication!

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

          If MSR starts but the browser won't open, that's often just one of the controllers being slow to start for some reason (usually communication with the hub). You have to wait over 60 seconds before declaring a problem, because that's how long it takes for the controller to time out. All controllers have to start up or time out before the HTTP API starts and the UI can come up. This is described in the Troubleshooting section of the docs.

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

          wmarcolinW 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            If MSR starts but the browser won't open, that's often just one of the controllers being slow to start for some reason (usually communication with the hub). You have to wait over 60 seconds before declaring a problem, because that's how long it takes for the controller to time out. All controllers have to start up or time out before the HTTP API starts and the UI can come up. This is described in the Troubleshooting section of the docs.

            wmarcolinW Offline
            wmarcolinW Offline
            wmarcolin
            wrote on last edited by
            #5

            @toggledbits

            Yes, I know this instruction, I even increased the time to 90 seconds two versions ago, so I wait.

            Well it is working now, but I started from a new installation, and only then copied the directories as I described above.

            I have another lab machine and will try to reproduce the problem. I remember some post that you comment on where we can see better the boot log, with more details, can you remind me where you have this information? Thanks.

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

              On Windows, I don't know where it logs. That may be a good exploration for you... I would think the Windows Event Log would be the right place to start. Not sure what section, though...

              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
              • wmarcolinW wmarcolin

                @toggledbits yes, I even saw in the manual that in the installation process you updated the command to Windows bare-metal.

                The first attempt was to follow the procedure of overwriting files from the current installation with the new version, and run the NPM process as you put in the update note. I noticed that the MSR ran, there was no error in the log, but the browse would not open.

                The second attempt, was a fresh installation, just copying from the old installation the config and storage directory, again browse did not open.

                The third action was then to do a completely new installation, copy the new config files from dist-config, update the IP and remove the Dynamic Group block because I did not put any controllers.

                83a4de66-8009-47a6-9f3b-81a0d42a17a3-image.png

                IT WORKED PERFECTLY! I see the new About page and the new Status with the new Widget, new toy 🙂

                97a7cb9b-0aa0-4bef-9f3b-9e5c3a58c2ba-image.png

                I stopped the MSR, and then copied the config and storage directories from the old version (22004), and it booted up again.

                I am no expert, but it seems to me that something in the old version might be blocking the browse from working. I have several copies of each attempt, if you want me to send you some log, or information, or make new attempts please send me a message and I will pass you the materials.

                Sorry for the boldness, but I would like to make a suggestion for the Widgets, would it be possible to remove the technical name of the rule from the logs (rule-kxhekauro)? I believe that everyone puts a name on their actions and this information may not be very useful).

                NOW IT IS VERY GOOD! One less item on the wishlist

                Once again thank you very much for all your dedication!

                wmarcolinW Offline
                wmarcolinW Offline
                wmarcolin
                wrote on last edited by
                #7

                @wmarcolin said in Release 22021 Windows Bare-metal won't load:

                Sorry for the boldness, but I would like to make a suggestion for the Widgets, would it be possible to remove the technical name of the rule from the logs (rule-kxhekauro)? I believe that everyone puts a name on their actions and this information may not be very useful).

                THANKS BOSS!! New version 22022 worked!!

                e2406bb2-f36b-4f4c-a201-a40da587d23a-image.png

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


                Recent Topics

                • Copying a global reaction
                  toggledbitsT
                  toggledbits
                  0
                  3
                  80

                • [HowTo] Using HABridge with Reactor
                  CatmanV2C
                  CatmanV2
                  0
                  9
                  389

                • [Reactor] Bug when sending MQTT boolean payloads
                  toggledbitsT
                  toggledbits
                  0
                  4
                  134

                • Genuinely impressed with Zigbee and HA / Reactor
                  therealdbT
                  therealdb
                  1
                  8
                  304

                • Difficulty defining repeating annual period
                  G
                  gwp1
                  0
                  5
                  98

                • Need help with sequence
                  therealdbT
                  therealdb
                  0
                  3
                  61

                • Possible feature request?
                  therealdbT
                  therealdb
                  0
                  5
                  162

                • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
                  CatmanV2C
                  CatmanV2
                  0
                  11
                  338

                • Time series documentation
                  tunnusT
                  tunnus
                  0
                  11
                  389

                • MQTT templates for ZIgbee scene controller, or a better way?
                  CatmanV2C
                  CatmanV2
                  0
                  3
                  158

                • Reset a delay
                  CatmanV2C
                  CatmanV2
                  0
                  8
                  221
                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