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. Installing MSR on Windows
[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
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

Installing MSR on Windows

Scheduled Pinned Locked Moved Multi-System Reactor
13 Posts 3 Posters 1.4k 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.
  • 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.
    A Offline
    A Offline
    Andr
    wrote on last edited by
    #1

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

    Version 21054 now available.
    ...
    2. This version runs on Windows, and there are draft instructions for how to get it installed.

    I am so excited!

    Sorry that I need to bother with a noob question at the first step😂
    Does this box need to be checked for MSR to run nicley?
    7bc519af-f0e4-46af-a040-0ce261d08a8f-image.png

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

      I split this off to its own thread...

      You know, I don't know. I just checked it and rolled on. I may have to uninstall/reinstall later and see if it makes a difference. But I went with it on to start.

      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
      1
      • A Offline
        A Offline
        Andr
        wrote on last edited by
        #3

        Well. Now I have looked, read, re-read and looked again. So now I am ready to get an surely obvious answer smashed in my face.

        How do I download the Reactor package??
        The link reactor.toggledbits.com/mantisbt leads to a login page, but no way to register, no link in the left margin...

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

          Did you PM me your full name and email? I don't think you did, but then, I've been a bit distracted today...

          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

            Did you PM me your full name and email? I don't think you did, but then, I've been a bit distracted today...

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

            @toggledbits

            Nope, have not done that. Coming right up!

            I don't know were that information is, but you maybe can add it in your first post in this thread to help others in the future?
            Multi-System Reactor Developer Preview AVAILABLE:

            1 Reply Last reply
            1
            • toggledbitsT toggledbits

              I split this off to its own thread...

              You know, I don't know. I just checked it and rolled on. I may have to uninstall/reinstall later and see if it makes a difference. But I went with it on to start.

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

              @toggledbits said in Installing MSR on Windows:

              I split this off to its own thread...

              You know, I don't know. I just checked it and rolled on. I may have to uninstall/reinstall later and see if it makes a difference. But I went with it on to start.

              So now MSR is up and running ✌

              I start without adding the extra "Chocolatey" stuff in the Node.js install, so we will see if this comes back and bite me later on.
              But I try to have a little stuff on the system as possible.

              Rest of installation went as expected.
              When extracting using 7-zip there was some error messages, but I don't what that means or if it have anything to do with MSR.
              9e2d6b13-f204-4c9d-a261-ac7a51dbb6ed-image.png

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

                OK. I'll look into those. If it interferes with anything, it will be the dashboard, not Reactor itself, it looks like.

                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
                • LibraSunL Offline
                  LibraSunL Offline
                  LibraSun
                  wrote on last edited by LibraSun
                  #8

                  Yay, proud of myself getting MSR v.21068 installed and running on a clean Windows 10 machine, just for fun.

                  My next plan, if it's possible, is to configure MSR to work with the ezlo Plus I have running at that location.

                  Will check the YAML files...

                  EDIT: Nope, not yet implemented. Still can play with the UI and do bug reports in the meantime!

                  1 Reply Last reply
                  0
                  • LibraSunL Offline
                    LibraSunL Offline
                    LibraSun
                    wrote on last edited by LibraSun
                    #9

                    LOL, even dug up my ol' trusty Vera 1 and am putting it through its initial Setup paces (not going smoothly -- "Update" fails, it wants to run Adobe Flash, which has since been discontinued, etc.). We'll see what MSR has to make of this dinosaur.

                    EDIT: Quite shockingly, even my old Z-Wave dongle, which I thought had bitten the dust, appears to be working!?!? Also managed to log into extremely old MIOS1 servers with un/pw.

                    EDIT 2: MSR no likey! When I enabled the Vera controller IP in reactor.yaml, and restarted MSR, it just kinda hung. Had to CTRL-C my way out. Oh, well! 😞

                    EDIT 3: Nope, I spoke too soon. Even with Vera > enable: false, MSR seems to hang about 3 minutes on startup, then magically pops up with 21068 in the upper right corner. Will continue exploring what else may be hanging MSR up.

                    EDIT 4: Reactor's fully up and running, connected to my Vera 1. A quick reboot of the host PC seemed to help!

                    1 Reply Last reply
                    0
                    • A Offline
                      A Offline
                      Andr
                      wrote on last edited by Andr
                      #10

                      Hi

                      Life has kept me busy this year so I haven't had time to tinker with any fun smarthome stuff for a long while.

                      So I was set to upgrade to latest version 21275 and install MSR as a service.
                      It have not gone well 😞

                      The service stops directly.
                      Info from daemon\reactor.err.log

                      Logging stream path spec may be using pre-21075 form; please remove ./logs/ from the path!
                      internal/modules/cjs/loader.js:883
                        throw err;
                        ^
                      
                      Error: Cannot find module 'ws'
                      Require stack:
                      - C:\reactor\server\wsapi\wsapi.js
                      - C:\reactor\app.js
                          at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
                          at Function.Module._load (internal/modules/cjs/loader.js:725:27)
                          at Module.require (internal/modules/cjs/loader.js:952:19)
                          at require (internal/modules/cjs/helpers.js:88:18)
                          at Object.<anonymous> (C:\reactor\server\wsapi\wsapi.js:239:30)
                          at Module._compile (internal/modules/cjs/loader.js:1063:30)
                          at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
                          at Module.load (internal/modules/cjs/loader.js:928:32)
                          at Function.Module._load (internal/modules/cjs/loader.js:769:14)
                          at Module.require (internal/modules/cjs/loader.js:952:19) {
                        code: 'MODULE_NOT_FOUND',
                        requireStack: [ 'C:\\reactor\\server\\wsapi\\wsapi.js', 'C:\\reactor\\app.js' ]
                      }
                      

                      When I tries to start MSR normally i get a "NODE_PATH is missing" but I have set this, and with correct casing.

                      ||PS C:\reactor> set NODE_PATH=C:\reactor
                      PS C:\reactor> node app.js
                      basedir C:\reactor
                      confdir C:\reactor\config
                      datadir C:\reactor\storage
                      logsdir C:\reactor\logs
                      plugindir C:\reactor\ext
                      module.paths [ 'C:\reactor\node_modules', 'C:\node_modules' ]
                      NODE_PATH undefined
                      Required environment variable NODE_PATH is missing; can't continue.
                      Logging stream path spec may be using pre-21075 form; please remove ./logs/ from the path!
                      2021-10-03T21:55:13.989Z app:null Reactor latest-21275-df3d784 starting on v14.16.0
                      2021-10-03T21:55:13.990Z app:INFO Process ID 8800; platform win32/x64 Windows 10 Education; locale (undefined)
                      2021-10-03T21:55:13.990Z app:INFO Basedir C:\reactor; data in C:\reactor\storage
                      2021-10-03T21:55:13.990Z app:INFO NODE_PATH (undefined)
                      C:\reactor\app.js:233
                      throw new Error(a0_0x52b285(0x1c5));
                      ^

                      Error: Required environment variable NODE_PATH is not set
                      at Object.<anonymous> (C:\reactor\app.js:233:11)
                      at Module._compile (internal/modules/cjs/loader.js:1063:30)
                      at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
                      at Module.load (internal/modules/cjs/loader.js:928:32)
                      at Function.Module._load (internal/modules/cjs/loader.js:769:14)
                      at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
                      at internal/main/run_main_module.js:17:47||

                      Please help 🙂

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

                        Logging stream path spec may be using pre-21075 form; please remove ./logs/ from the path!

                        Tells me you have a really old configuration that needs to be updated. At least copy the dist-config/logging.yaml file to the config directory to start over with that part of your config. The other parts of your config are likely OK.

                        Error: Cannot find module 'ws'

                        Tells me that you haven't installed the prerequisite dependencies, which is part of the installation instructions. Did you follow the installation instructions for Windows?

                        When I tries to start MSR normally i get a "NODE_PATH is missing" but I have set this, and with correct casing.

                        If you think you set it, and it says you didn't, then most likely you didn't use the correct command for the shell you are in. The instructions are different for CMD.EXE vs Windows PowerShell. The installation instructions cover that, too.

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

                          Solved it! ✌

                          After updating config files i got a new error message that told me what dependencies that was missing. Some Popper thing...
                          So for now it is up and running again 🙂

                          1 Reply Last reply
                          0
                          • toggledbitsT toggledbits

                            Logging stream path spec may be using pre-21075 form; please remove ./logs/ from the path!

                            Tells me you have a really old configuration that needs to be updated. At least copy the dist-config/logging.yaml file to the config directory to start over with that part of your config. The other parts of your config are likely OK.

                            Error: Cannot find module 'ws'

                            Tells me that you haven't installed the prerequisite dependencies, which is part of the installation instructions. Did you follow the installation instructions for Windows?

                            When I tries to start MSR normally i get a "NODE_PATH is missing" but I have set this, and with correct casing.

                            If you think you set it, and it says you didn't, then most likely you didn't use the correct command for the shell you are in. The instructions are different for CMD.EXE vs Windows PowerShell. The installation instructions cover that, too.

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

                            @toggledbits said in Installing MSR on Windows:

                            Tells me that you haven't installed the prerequisite dependencies, which is part of the installation instructions. Did you follow the installation instructions for Windows?

                            Well, i did not download the node.js install package since I did that when i installed one of the first MSR-previews.
                            Otherwise i followd all steps.
                            (Except that i miss the config files because i was only updating in my mind and had no idea that CMD & PS makes a difference - You learn every day)

                            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

                            • Home Assistant Connect ZWA-2 & ZBT-2
                              tunnusT
                              tunnus
                              3
                              9
                              283

                            • [MSR] Feature request: For Each action on arrays/groups
                              therealdbT
                              therealdb
                              0
                              7
                              93

                            • [Solved] Error: Command timeout
                              toggledbitsT
                              toggledbits
                              0
                              10
                              330

                            • Issue with MSR UI becoming unresponsive
                              S
                              sethlampman
                              0
                              7
                              133

                            • Date/time condition
                              tunnusT
                              tunnus
                              0
                              3
                              107

                            • Is there a way to turn this section (image in post) off?
                              toggledbitsT
                              toggledbits
                              0
                              1
                              78

                            • Device log?
                              toggledbitsT
                              toggledbits
                              0
                              2
                              102

                            • Midnight crossing not working in date/time condition (build 25325)
                              tunnusT
                              tunnus
                              0
                              3
                              128

                            • Reactor (Multi-System/Multi-Hub) Announcements
                              toggledbitsT
                              toggledbits
                              5
                              131
                              75.9k

                            • [Solved] Local expression in Rule does not evaluate as they used to do
                              CrilleC
                              Crille
                              0
                              5
                              343

                            • Home Assistant 2025.11.2 and latest-25315
                              G
                              gwp1
                              0
                              6
                              328
                            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