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
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
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor

MSR Upgrade from 22119 to 22136 fails, service wont start

Scheduled Pinned Locked Moved Multi-System Reactor
6 Posts 2 Posters 386 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

              • Advice reqeusted to migrate MSR from Bare Metal to Container
                T
                tamorgen
                0
                5
                38

              • Reactor (Multi-System/Multi-Hub) Announcements
                toggledbitsT
                toggledbits
                5
                122
                35.4k

              • Z-Wave Future....
                CatmanV2C
                CatmanV2
                0
                5
                131

              • Can´t restart or upgrade/deploy MSR
                toggledbitsT
                toggledbits
                0
                4
                86

              • [Solved] Limit HA Entity in MSR
                wmarcolinW
                wmarcolin
                0
                7
                191

              • Disaster recovery and virtualisation
                CatmanV2C
                CatmanV2
                0
                5
                662

              • Remote access of Zwave stick from Z-wave server
                CatmanV2C
                CatmanV2
                0
                3
                384

              • Organizing/ structuring rule sets and rules
                G
                gwp1
                0
                5
                374

              • Moving MSR from a QNAP container to RP 5 - some issues
                G
                gwp1
                0
                5
                346

              • Widget deletion does not work and landing page (status) is empy
                G
                gwp1
                0
                4
                338

              • Need help reducing false positive notifications
                T
                tamorgen
                0
                7
                520
              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