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. MSR Upgrade from 22119 to 22136 fails, service wont start
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
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
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
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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 restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

MSR Upgrade from 22119 to 22136 fails, service wont start

Scheduled Pinned Locked Moved Multi-System Reactor
6 Posts 2 Posters 436 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.
  • W Offline
    W Offline
    wokwon
    wrote on last edited by
    #1

    Windows Server 2022 Build 20348
    Nodejs v16.14.0
    Currently running Reactor (Multi-hub) stable-22119-ae7212f
    Linked to Hass 2022.0.5.4 (on a different box)
    Windows server is dedicated to MSR and doesn't do anything else.

    I'd like to upgrade to 22136 to take advantage of the SSL feature added recently, and also to bring my current version of Hass into the 'supported' column with MSR.

    Following the instructions here: link text, section "Upgrade Windows Bare Metal"

    • Stop Reactor Service
    • Extract the zip, overwriting the reactor folder in c:\reactor\reactor
    • There is no package-lock.json file so I skip that.
    • Run "npm install --no-save --omit dev"

    Next step is to start the service. I start the service and it immediately stops. "Windows could not start the Reactor service on Local Computer. Error 1067: The process terminated unexpectedly".

    Tried rebooting, service won't stay running.

    I suspect I'm missing something, it's probably obvious but I've not been able to figure it out.

    I rolled back the reactor folder version (Windows Shadow copies) and then the service starts fine.

    Anyone else running Windows and know what I'm missing?

    • Tail of log file from running OK version, before upgrade attempt
    [stable-22119]2022-06-01T22:20:19.081Z <Rule:INFO> Lounge Billy Ambient Lighting - Turn On (Rule#rule-l0ki453b) evaluation complete
    [stable-22119]2022-06-01T22:20:19.082Z <httpapi:NOTICE> HTTP API v1 22021 base URL http://172.16.128.6:8111; listening
    [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> HTTP server running; registering proxy endpoints.
    [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> Starting WSAPI...
    [stable-22119]2022-06-01T22:20:19.229Z <wsapi:NOTICE> wsapi: starting version 21334
    [stable-22119]2022-06-01T22:20:19.656Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "6/2/2022, 8:20:19 AM" (TZ offset 600 mins from UTC)
    [stable-22119]2022-06-01T22:27:54.788Z <wsapi:INFO> wsapi: connection from ::ffff:172.16.128.5
    
    • Tail of log file from failed to start after upgrade (is identical, ii.e. nothing has been appended to it)
    [stable-22119]2022-06-01T22:20:19.081Z <Rule:INFO> Lounge Billy Ambient Lighting - Turn On (Rule#rule-l0ki453b) evaluation complete
    [stable-22119]2022-06-01T22:20:19.082Z <httpapi:NOTICE> HTTP API v1 22021 base URL http://172.16.128.6:8111; listening
    [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> HTTP server running; registering proxy endpoints.
    [stable-22119]2022-06-01T22:20:19.228Z <app:NOTICE> Starting WSAPI...
    [stable-22119]2022-06-01T22:20:19.229Z <wsapi:NOTICE> wsapi: starting version 21334
    [stable-22119]2022-06-01T22:20:19.656Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "6/2/2022, 8:20:19 AM" (TZ offset 600 mins from UTC)
    [stable-22119]2022-06-01T22:27:54.788Z <wsapi:INFO> wsapi: connection from ::ffff:172.16.128.5
    
    • reactor.wrapper.log (log file the failed to start event points to)
    2022-06-02 08:19:23 - Stopping reactor.exe
    2022-06-02 08:19:23 - ProcessKill 3628
    2022-06-02 08:19:25 - Shutdown exception
    Message:A system shutdown is in progress.
    
    Stacktrace:   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at System.Management.ManagementScope.InitializeGuts(Object o)
       at System.Management.ManagementScope.Initialize()
       at System.Management.ManagementObjectSearcher.Initialize()
       at System.Management.ManagementObjectSearcher.Get()
       at winsw.WrapperService.GetChildPids(Int32 pid)
       at winsw.WrapperService.StopProcessAndChildren(Int32 pid)
       at winsw.WrapperService.StopIt()
       at winsw.WrapperService.OnShutdown()
    2022-06-02 08:20:11 - Starting C:\Program Files\nodejs\node.exe  C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined
    2022-06-02 08:20:11 - Started 3272
    2022-06-02 08:30:54 - Stopping reactor.exe
    2022-06-02 08:30:54 - ProcessKill 3272
    2022-06-02 08:30:54 - Found child process: 3280 Name: conhost.exe
    2022-06-02 08:30:54 - Found child process: 3504 Name: node.exe
    2022-06-02 08:30:54 - Stopping process 3280
    2022-06-02 08:30:54 - Send SIGINT 3280
    2022-06-02 08:30:54 - SIGINT to 3280 failed - Killing as fallback
    2022-06-02 08:30:54 - Stopping process 3504
    2022-06-02 08:30:54 - Send SIGINT 3504
    2022-06-02 08:30:54 - SIGINT to 3504 failed - Killing as fallback
    2022-06-02 08:30:54 - Stopping process 3272
    2022-06-02 08:30:54 - Send SIGINT 3272
    2022-06-02 08:30:54 - SIGINT to 3272 failed - Killing as fallback
    2022-06-02 08:30:54 - Finished reactor.exe
    2022-06-02 08:33:41 - Starting C:\Program Files\nodejs\node.exe  C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined
    2022-06-02 08:33:41 - Started 4184
    2022-06-02 08:36:57 - Starting C:\Program Files\nodejs\node.exe  C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined
    2022-06-02 08:36:57 - Started 3100
    
    • Windows event log event:
    Child process [4184 - C:\Program Files\nodejs\node.exe  C:\reactor\reactor\node_modules\node-windows\lib\wrapper.js --file C:\reactor\reactor\app.js --scriptoptions= --log "Reactor wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n --stopparentfirst undefined] finished with 1
    
    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #2

      In your Reactor directory, please do npm ls and post the results.

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

      W 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        In your Reactor directory, please do npm ls and post the results.

        W Offline
        W Offline
        wokwon
        wrote on last edited by
        #3

        Note this is in the 'rolled back' state, not the 'wont start' state:

        PS C:\reactor\reactor> npm ls
        reactor-multi-system@1.0.3-22041 C:\reactor\reactor
        +-- @influxdata/influxdb-client@1.23.0
        +-- @mdi/font@5.9.55
        +-- @popperjs/core@2.11.2
        +-- body-parser@1.19.2
        +-- bootstrap-icons@1.5.0
        +-- bootstrap@4.6.1
        +-- cookie@0.4.2
        +-- digest-fetch@1.2.1
        +-- diskusage-ng@1.0.2
        +-- express@4.17.3
        +-- feather-icons@4.28.0
        +-- font-awesome@4.7.0
        +-- gridstack@5.0.0
        +-- jquery-ui-dist@1.13.1
        +-- jquery@3.6.0
        +-- js-yaml@3.14.1
        +-- minimist@0.0.10 extraneous
        +-- node-fetch@2.6.7
        +-- node-stream-zip@1.15.0 extraneous
        +-- node-windows@1.0.0-beta.6 extraneous
        +-- nodemailer@6.7.2
        +-- optimist@0.6.1 extraneous
        +-- qs@6.10.3
        +-- serve-static@1.14.2
        +-- uuid@8.3.2
        +-- wordwrap@0.0.3 extraneous
        +-- ws@7.5.7
        `-- xml@0.0.12 extraneous
        
        PS C:\reactor\reactor>
        
        1 Reply Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by toggledbits
          #4

          That is the correct list. From what you posted, it looks like you are somehow installing the wrong version of node-windows. The latest version is known not to work, and the developer is too busy to fix it, so the beta.6 is the required version. Make sure you are following the installation instructions to the letter (which do specify that particular beta6 version). This is all confirmed to work, I believe @wmarcolin can confirm, as I went through this with him a couple of weeks ago when we discovered the deficiency in node-windows.

          To make sure everything is well and truly cleared out before doing the upgrade, make sure you uninstall any existing Reactor service, then remove completely the package dependencies directory, and then make sure there is no global version of node-windows installed:

          cd \path\to\reactor
          node tools\install_reactor_windows_service.js -u .
          del /s /f node_modules
          npm rm -g node-windows
          

          Then do the full upgrade install.

          node-windows also creates a daemon directory in the Reactor directory when it attempts to start the service, and places its startup log files there. That would be another place to check for useful messages (particularly the .wrapper.log file).

          I've enhanced the upgrade instructions for Windows to more thoroughly document the steps needed while node-windows needs to be installed in a downgraded state.

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

          W 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            That is the correct list. From what you posted, it looks like you are somehow installing the wrong version of node-windows. The latest version is known not to work, and the developer is too busy to fix it, so the beta.6 is the required version. Make sure you are following the installation instructions to the letter (which do specify that particular beta6 version). This is all confirmed to work, I believe @wmarcolin can confirm, as I went through this with him a couple of weeks ago when we discovered the deficiency in node-windows.

            To make sure everything is well and truly cleared out before doing the upgrade, make sure you uninstall any existing Reactor service, then remove completely the package dependencies directory, and then make sure there is no global version of node-windows installed:

            cd \path\to\reactor
            node tools\install_reactor_windows_service.js -u .
            del /s /f node_modules
            npm rm -g node-windows
            

            Then do the full upgrade install.

            node-windows also creates a daemon directory in the Reactor directory when it attempts to start the service, and places its startup log files there. That would be another place to check for useful messages (particularly the .wrapper.log file).

            I've enhanced the upgrade instructions for Windows to more thoroughly document the steps needed while node-windows needs to be installed in a downgraded state.

            W Offline
            W Offline
            wokwon
            wrote on last edited by
            #5

            @toggledbits Thank you for the info and I'll try this later on and report back.

            1 Reply Last reply
            0
            • W Offline
              W Offline
              wokwon
              wrote on last edited by
              #6

              So, following:

              cd \path\to\reactor
              node tools\install_reactor_windows_service.js -u .
              del /s /f node_modules
              npm rm -g node-windows
              
              npm uninstall node-windows
              npm uninstall -g node-windows
              npm install -g node-windows@1.0.0-beta.6
              npm link node-windows
              

              ...extract the Reactor.zip over the old directory...

              node tools\install_reactor_windows_service.js -i .
              

              I'm now running fine with Reactor (Multi-hub) stable-22136.

              Thank you @toggledbits for your support and amazing product.

              Bonus is the SSL now works too (CertifytheWeb with LetsEncrypt will renew it and drop the key files in the correct location). That means I can have Reactor as a tab in the Hass sidebar (previously https Hass --> http reactor would not work).
              bdb4b2e7-f193-4fe1-9012-fdba37630a3e-image.png

              Ractor.yaml:
              99a5f802-c3e4-4bfa-9a29-975de1da4d28-image.png CertifyTheWeb:
              621270ab-242f-47c4-a7ee-d547ce9eb4cf-image.png Browser:
              0f4ac4f9-f330-4186-bb30-fd9cd559da39-image.png

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


              Recent Topics

              • Gradually turn on lights.
                G
                gwp1
                0
                4
                94

              • Stop the MSR by an external switch on Hubitat.
                wmarcolinW
                wmarcolin
                0
                1
                16

              • Error After Upgrade
                G
                gwp1
                0
                4
                86

              • Reset attribute value of entity in event handler
                R
                RHCPNG
                0
                5
                170

              • Need help figuring out how to delay a reset on reaction
                G
                gwp1
                0
                22
                860

              • Way to search for rules (rule state) in other rules
                T
                tamorgen
                0
                3
                92

              • Links to MSR from HA
                Tom_DT
                Tom_D
                0
                1
                78

              • Set Reaction > Script Action
                wmarcolinW
                wmarcolin
                0
                11
                417

              • Wiring Samotech SM308-S into light fitting
                akbooerA
                akbooer
                0
                2
                136

              • Errors after updating to MQTTController build 25139
                toggledbitsT
                toggledbits
                0
                6
                232

              • 🎉 My very first MSR controller: OpenSprinkler
                therealdbT
                therealdb
                5
                13
                898

              • Advice reqeusted to migrate MSR from Bare Metal to Container
                T
                tamorgen
                0
                5
                246
              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