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. [Solved] Migrating MSR to Docker on Proxmox
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
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
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can't customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
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
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

[Solved] Migrating MSR to Docker on Proxmox

Scheduled Pinned Locked Moved Multi-System Reactor
12 Posts 2 Posters 980 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    gwp1
    wrote on last edited by gwp1
    #1
    • Zero issues installing Proxmox on a new MiniPC.
    • Zero issues migrating my HA instance over to the new hotness (I know, I was surprised, too!)

    And then MSR...

    My first issue: I'm logged into the msr CT as reactor (I used the suggested username just to keep things simple as this is new space for me and I was high off my success of migrating HA over).

    When I run

    docker pull toggledbits/reactor:latest-amd64
    

    ... it assigns the \reactor\ subdirectory where installed root ownership. I am absolutely logged in with the correct non-root user.
    1c58aead-85ca-4b2c-8f48-c3d1f57d7fe3-image.png

    Second issue: I copied over the following folders:
    67e7e4a5-cee8-4de1-90c7-1df35f1070b9-image.png When MSR loads, all of my Global Expressions are missing.

    Third issue:
    All controllers connect wonderfully (Hubitat, etc)... except HA.
    After changing ownership of the logs to reactor again I can see this when MSR calls HA:

    
    [latest-24366]2025-01-12T00:03:43.128Z <HubitatController:INFO> HubitatController#hubitat successful connection to ws://192.168.1.214/eventsocket
    [latest-24366]2025-01-12T00:03:43.151Z <HubitatController:NOTICE> HubitatController#hubitat current mode is Evening (2)
    [latest-24366]2025-01-12T00:03:43.212Z <HubitatController:NOTICE> HubitatController#hubitat HSM status is disarmed
    [latest-24366]2025-01-12T00:03:43.214Z <Controller:NOTICE> Controller HubitatController#hubitat is now online.
    [latest-24366]2025-01-12T00:03:43.255Z <MQTTController:INFO> MQTTController#mqtt2 connected; opening subscriptions
    [latest-24366]2025-01-12T00:03:43.371Z <MQTTController:INFO> MQTTController#mqtt2 sending inits and going online!
    [latest-24366]2025-01-12T00:03:43.373Z <Controller:NOTICE> Controller MQTTController#mqtt2 is now online.
    [latest-24366]2025-01-12T00:03:47.179Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.123:8123/api/websocket
    [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
    [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass ws error code ECONNREFUSED
    [latest-24366]2025-01-12T00:03:47.180Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.1.123:8123/api/websocket closed during open/negotiation
    [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
    [latest-24366]2025-01-12T00:03:52.181Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.123:8123/api/websocket
    [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
    [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass ws error code ECONNREFUSED
    [latest-24366]2025-01-12T00:03:52.183Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.1.123:8123/api/websocket closed during open/negotiation
    [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
    

    Yes, I created a fresh new long-lived access token for the MSR containerized install and updated the reactor.yaml config file correctly.

    Honestly, all-in-all, for my total lack of expertise here I'm very pleased that I only have these three issues. But they are def blockers atm.

    My RPi bare metal install of MSR hooked right up to the new HA and is humming along just fine (I used hostnames were possible and shuffled some IPs in other places so I wouldn't run into things later that were mapped incorrectly that I'd forgotten about.)

    • Proxmox 8.3.2
    • MSR lives in an Ubuntu 24.04 Proxmox container
    • MSR is latest docker version

    What else can I provide to those smarter than me here?

    *Hubitat C-7 2.4.2.129
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HASS 2025.7.2
    w/ ZST10-700 fw 7.18.3

    *Prod MSR in docker/portainer
    MSR: latest-25139-fbd67abc
    MQTTController: 25139
    ZWave Controller: 25139

    G toggledbitsT 2 Replies Last reply
    0
    • G gwp1
      • Zero issues installing Proxmox on a new MiniPC.
      • Zero issues migrating my HA instance over to the new hotness (I know, I was surprised, too!)

      And then MSR...

      My first issue: I'm logged into the msr CT as reactor (I used the suggested username just to keep things simple as this is new space for me and I was high off my success of migrating HA over).

      When I run

      docker pull toggledbits/reactor:latest-amd64
      

      ... it assigns the \reactor\ subdirectory where installed root ownership. I am absolutely logged in with the correct non-root user.
      1c58aead-85ca-4b2c-8f48-c3d1f57d7fe3-image.png

      Second issue: I copied over the following folders:
      67e7e4a5-cee8-4de1-90c7-1df35f1070b9-image.png When MSR loads, all of my Global Expressions are missing.

      Third issue:
      All controllers connect wonderfully (Hubitat, etc)... except HA.
      After changing ownership of the logs to reactor again I can see this when MSR calls HA:

      
      [latest-24366]2025-01-12T00:03:43.128Z <HubitatController:INFO> HubitatController#hubitat successful connection to ws://192.168.1.214/eventsocket
      [latest-24366]2025-01-12T00:03:43.151Z <HubitatController:NOTICE> HubitatController#hubitat current mode is Evening (2)
      [latest-24366]2025-01-12T00:03:43.212Z <HubitatController:NOTICE> HubitatController#hubitat HSM status is disarmed
      [latest-24366]2025-01-12T00:03:43.214Z <Controller:NOTICE> Controller HubitatController#hubitat is now online.
      [latest-24366]2025-01-12T00:03:43.255Z <MQTTController:INFO> MQTTController#mqtt2 connected; opening subscriptions
      [latest-24366]2025-01-12T00:03:43.371Z <MQTTController:INFO> MQTTController#mqtt2 sending inits and going online!
      [latest-24366]2025-01-12T00:03:43.373Z <Controller:NOTICE> Controller MQTTController#mqtt2 is now online.
      [latest-24366]2025-01-12T00:03:47.179Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.123:8123/api/websocket
      [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
      [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass ws error code ECONNREFUSED
      [latest-24366]2025-01-12T00:03:47.180Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.1.123:8123/api/websocket closed during open/negotiation
      [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
      [latest-24366]2025-01-12T00:03:52.181Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.123:8123/api/websocket
      [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
      [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass ws error code ECONNREFUSED
      [latest-24366]2025-01-12T00:03:52.183Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.1.123:8123/api/websocket closed during open/negotiation
      [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
      

      Yes, I created a fresh new long-lived access token for the MSR containerized install and updated the reactor.yaml config file correctly.

      Honestly, all-in-all, for my total lack of expertise here I'm very pleased that I only have these three issues. But they are def blockers atm.

      My RPi bare metal install of MSR hooked right up to the new HA and is humming along just fine (I used hostnames were possible and shuffled some IPs in other places so I wouldn't run into things later that were mapped incorrectly that I'd forgotten about.)

      • Proxmox 8.3.2
      • MSR lives in an Ubuntu 24.04 Proxmox container
      • MSR is latest docker version

      What else can I provide to those smarter than me here?

      G Offline
      G Offline
      gwp1
      wrote on last edited by
      #2

      So I searched this forum earlier but didn't find this thread. A generic global Internet search netted me this old nugget of info on exactly the first issue, the MSR>HA connectivity.

      Using @toggledbits one-liner

          curl -o - 'http://192.168.0.15:8123/api/config'
      

      returned just what I needed to determine it was an IP configuration error. I'd taken painstaking efforts to re-IP the new HA to the old HA's original IP... and then (for some inexplicable reason) updated the reactor.yaml with the new long-lived access token AND the temporary IP. Dunno what I was thinking... or if I was thinking... in that moment. But that's fixed now and MSR and HA are happily chatting away.

      So now I have the two issues remaining:

      My first issue: I'm logged into the msr CT as reactor (I used the suggested username just to keep things simple as this is new space for me and I was high off my success of migrating HA over).

      When I run

      docker pull toggledbits/reactor:latest-amd64
      ... it assigns the \reactor\ subdirectory where installed root ownership. I am absolutely logged in with the correct non-root user.
      

      a1810504-8d20-43ac-aa45-e34a4db3404b-image.png

      Second issue: I copied over the following folders:
      cd74d3a0-250c-41a6-aa6f-e05e6e9b5329-image.png

      When MSR loads, all of my Global Expressions are missing.

      *Hubitat C-7 2.4.2.129
      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

      *HASS 2025.7.2
      w/ ZST10-700 fw 7.18.3

      *Prod MSR in docker/portainer
      MSR: latest-25139-fbd67abc
      MQTTController: 25139
      ZWave Controller: 25139

      1 Reply Last reply
      0
      • G gwp1
        • Zero issues installing Proxmox on a new MiniPC.
        • Zero issues migrating my HA instance over to the new hotness (I know, I was surprised, too!)

        And then MSR...

        My first issue: I'm logged into the msr CT as reactor (I used the suggested username just to keep things simple as this is new space for me and I was high off my success of migrating HA over).

        When I run

        docker pull toggledbits/reactor:latest-amd64
        

        ... it assigns the \reactor\ subdirectory where installed root ownership. I am absolutely logged in with the correct non-root user.
        1c58aead-85ca-4b2c-8f48-c3d1f57d7fe3-image.png

        Second issue: I copied over the following folders:
        67e7e4a5-cee8-4de1-90c7-1df35f1070b9-image.png When MSR loads, all of my Global Expressions are missing.

        Third issue:
        All controllers connect wonderfully (Hubitat, etc)... except HA.
        After changing ownership of the logs to reactor again I can see this when MSR calls HA:

        
        [latest-24366]2025-01-12T00:03:43.128Z <HubitatController:INFO> HubitatController#hubitat successful connection to ws://192.168.1.214/eventsocket
        [latest-24366]2025-01-12T00:03:43.151Z <HubitatController:NOTICE> HubitatController#hubitat current mode is Evening (2)
        [latest-24366]2025-01-12T00:03:43.212Z <HubitatController:NOTICE> HubitatController#hubitat HSM status is disarmed
        [latest-24366]2025-01-12T00:03:43.214Z <Controller:NOTICE> Controller HubitatController#hubitat is now online.
        [latest-24366]2025-01-12T00:03:43.255Z <MQTTController:INFO> MQTTController#mqtt2 connected; opening subscriptions
        [latest-24366]2025-01-12T00:03:43.371Z <MQTTController:INFO> MQTTController#mqtt2 sending inits and going online!
        [latest-24366]2025-01-12T00:03:43.373Z <Controller:NOTICE> Controller MQTTController#mqtt2 is now online.
        [latest-24366]2025-01-12T00:03:47.179Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.123:8123/api/websocket
        [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
        [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass ws error code ECONNREFUSED
        [latest-24366]2025-01-12T00:03:47.180Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.1.123:8123/api/websocket closed during open/negotiation
        [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
        [latest-24366]2025-01-12T00:03:52.181Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.123:8123/api/websocket
        [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
        [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass ws error code ECONNREFUSED
        [latest-24366]2025-01-12T00:03:52.183Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.1.123:8123/api/websocket closed during open/negotiation
        [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]
        

        Yes, I created a fresh new long-lived access token for the MSR containerized install and updated the reactor.yaml config file correctly.

        Honestly, all-in-all, for my total lack of expertise here I'm very pleased that I only have these three issues. But they are def blockers atm.

        My RPi bare metal install of MSR hooked right up to the new HA and is humming along just fine (I used hostnames were possible and shuffled some IPs in other places so I wouldn't run into things later that were mapped incorrectly that I'd forgotten about.)

        • Proxmox 8.3.2
        • MSR lives in an Ubuntu 24.04 Proxmox container
        • MSR is latest docker version

        What else can I provide to those smarter than me here?

        toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by
        #3

        @gwp1 said in Migrating MSR to Docker on Proxmox:

        My first issue: ... it assigns the \reactor\ subdirectory where installed root ownership

        That would be correct. Reactor runs as root inside its docker container (very common with docker).

        @gwp1 said in Migrating MSR to Docker on Proxmox:

        Second issue: When MSR loads, all of my Global Expressions are missing.

        Always look at the logs. Something is probably in there. Your screen shot doesn't show permissions, but that's likely the issue. Reactor runs as root in the container, and will have rootish behavior in the config, logs, storage, etc.

        VMs often have virtual network switches/routers and virtual firewalls. That could be the issue. It could also be that filtering/firewall on the HA side doesn't like the IP address the Reactor VM is coming from. That seems more likely as other controller endpoints are connectable.

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

        G 1 Reply Last reply
        0
        • toggledbitsT toggledbits

          @gwp1 said in Migrating MSR to Docker on Proxmox:

          My first issue: ... it assigns the \reactor\ subdirectory where installed root ownership

          That would be correct. Reactor runs as root inside its docker container (very common with docker).

          @gwp1 said in Migrating MSR to Docker on Proxmox:

          Second issue: When MSR loads, all of my Global Expressions are missing.

          Always look at the logs. Something is probably in there. Your screen shot doesn't show permissions, but that's likely the issue. Reactor runs as root in the container, and will have rootish behavior in the config, logs, storage, etc.

          VMs often have virtual network switches/routers and virtual firewalls. That could be the issue. It could also be that filtering/firewall on the HA side doesn't like the IP address the Reactor VM is coming from. That seems more likely as other controller endpoints are connectable.

          G Offline
          G Offline
          gwp1
          wrote on last edited by gwp1
          #4

          @toggledbits very helpful on the docker explanation - this is my very first foray into docker (using it with MSR) so it's all fresh and new to me. Thank you.

          I resolved the HA <-> MSR issue - it was a bad IP in the reactor.yaml file.

          What file do Global Expressions live in? They are literally gone from the UI.

          50009eec-b417-49fc-a651-f5f3f58c5576-image.png

          And I have LOTS of them in production.
          eea488c3-264f-4fbe-ad94-0632049cbf76-image.png

          The log shows this, which is not surprising given none of them are there:

          [latest-24366]2025-01-12T16:58:29.554Z <Rule:ERR> Predicate#rule-m34m60yh/trig condition refers to undefined global `ambient_windspeed'
          

          *Hubitat C-7 2.4.2.129
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HASS 2025.7.2
          w/ ZST10-700 fw 7.18.3

          *Prod MSR in docker/portainer
          MSR: latest-25139-fbd67abc
          MQTTController: 25139
          ZWave Controller: 25139

          toggledbitsT 1 Reply Last reply
          0
          • G gwp1

            @toggledbits very helpful on the docker explanation - this is my very first foray into docker (using it with MSR) so it's all fresh and new to me. Thank you.

            I resolved the HA <-> MSR issue - it was a bad IP in the reactor.yaml file.

            What file do Global Expressions live in? They are literally gone from the UI.

            50009eec-b417-49fc-a651-f5f3f58c5576-image.png

            And I have LOTS of them in production.
            eea488c3-264f-4fbe-ad94-0632049cbf76-image.png

            The log shows this, which is not surprising given none of them are there:

            [latest-24366]2025-01-12T16:58:29.554Z <Rule:ERR> Predicate#rule-m34m60yh/trig condition refers to undefined global `ambient_windspeed'
            
            toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by toggledbits
            #5

            @gwp1 said in Migrating MSR to Docker on Proxmox:

            The log shows this,

            Look at the startup messages. Reactor loads the global expressions at startup. That's where the useful messages will be.

            @gwp1 said in Migrating MSR to Docker on Proxmox:

            What file do Global Expressions live in?

            They live in storage/expressions.json, but recent similar experience suggests that if one file has broken permissions, many do, so whatever you learn from that one file will likely need to be applied to many. Log in to your virtual machine, do ls -la from inside the storage subdirectory, and post the entire output. Also fetch http://reactor-ip-address:port/api/v1/system and post that output.

            By the way, it's also plausible that you haven't mapped your docker container to the right directory. Can you describe how you are launching the docker container, and post any commands you may have executed doing that?

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

            G 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              @gwp1 said in Migrating MSR to Docker on Proxmox:

              The log shows this,

              Look at the startup messages. Reactor loads the global expressions at startup. That's where the useful messages will be.

              @gwp1 said in Migrating MSR to Docker on Proxmox:

              What file do Global Expressions live in?

              They live in storage/expressions.json, but recent similar experience suggests that if one file has broken permissions, many do, so whatever you learn from that one file will likely need to be applied to many. Log in to your virtual machine, do ls -la from inside the storage subdirectory, and post the entire output. Also fetch http://reactor-ip-address:port/api/v1/system and post that output.

              By the way, it's also plausible that you haven't mapped your docker container to the right directory. Can you describe how you are launching the docker container, and post any commands you may have executed doing that?

              G Offline
              G Offline
              gwp1
              wrote on last edited by
              #6

              @toggledbits the link to @cw-kid's issue was the key: what he saw was exactly what I saw. 1kb file size, all of it.

              I did copy the entire storage folder (along with the rest) vs cherry-picking but somehow the file size thing he saw was replicated here. I recopied but checked <user> <group> the expressions.json file (after confirming both file size and contents) and started the new MSR and it's all there. I even did a test Rule Set > Rule create/del and all is well.

              I've shut down the RPi legacy system for now... gonna test run the new one.

              QQ... at the bottom of the rules now I see a history that I don't recall seeing in my legacy system (which is bare metal and current). I went back and it's in the legacy system - very nice. Shamefully going to ask when that was added.

              *Hubitat C-7 2.4.2.129
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HASS 2025.7.2
              w/ ZST10-700 fw 7.18.3

              *Prod MSR in docker/portainer
              MSR: latest-25139-fbd67abc
              MQTTController: 25139
              ZWave Controller: 25139

              toggledbitsT 1 Reply Last reply
              0
              • G gwp1

                @toggledbits the link to @cw-kid's issue was the key: what he saw was exactly what I saw. 1kb file size, all of it.

                I did copy the entire storage folder (along with the rest) vs cherry-picking but somehow the file size thing he saw was replicated here. I recopied but checked <user> <group> the expressions.json file (after confirming both file size and contents) and started the new MSR and it's all there. I even did a test Rule Set > Rule create/del and all is well.

                I've shut down the RPi legacy system for now... gonna test run the new one.

                QQ... at the bottom of the rules now I see a history that I don't recall seeing in my legacy system (which is bare metal and current). I went back and it's in the legacy system - very nice. Shamefully going to ask when that was added.

                toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by toggledbits
                #7

                @gwp1 said in Migrating MSR to Docker on Proxmox:

                Shamefully going to ask when that was added.

                Check the release notes.

                @gwp1 said in Migrating MSR to Docker on Proxmox:

                I even did a test Rule Set > Rule create/del and all is well.

                Make sure you restart Reactor after doing a create, and make sure the rule still exists, and then delete it, restart, and make sure it stays gone after the restart. If not, your storage permissions don't have sufficient write privileges. The reason for this particular sequence is that Reactor caches writes to reduce load on flash memories (like the MicroSD cards typical of Pi's), so it may be several minutes before stuff in memory is written to disk. Restarting Reactor forces the write during shudown.

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

                G 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  @gwp1 said in Migrating MSR to Docker on Proxmox:

                  Shamefully going to ask when that was added.

                  Check the release notes.

                  @gwp1 said in Migrating MSR to Docker on Proxmox:

                  I even did a test Rule Set > Rule create/del and all is well.

                  Make sure you restart Reactor after doing a create, and make sure the rule still exists, and then delete it, restart, and make sure it stays gone after the restart. If not, your storage permissions don't have sufficient write privileges. The reason for this particular sequence is that Reactor caches writes to reduce load on flash memories (like the MicroSD cards typical of Pi's), so it may be several minutes before stuff in memory is written to disk. Restarting Reactor forces the write during shudown.

                  G Offline
                  G Offline
                  gwp1
                  wrote on last edited by
                  #8

                  @toggledbits Fair enough 🙂

                  *Hubitat C-7 2.4.2.129
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HASS 2025.7.2
                  w/ ZST10-700 fw 7.18.3

                  *Prod MSR in docker/portainer
                  MSR: latest-25139-fbd67abc
                  MQTTController: 25139
                  ZWave Controller: 25139

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

                    Also see the edit I just made regarding your test. Apologies for brevity. I'm on the run today.

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

                    G 2 Replies Last reply
                    1
                    • toggledbitsT toggledbits

                      Also see the edit I just made regarding your test. Apologies for brevity. I'm on the run today.

                      G Offline
                      G Offline
                      gwp1
                      wrote on last edited by
                      #10

                      @toggledbits AH - will do that post-haste. Thanks. And fully appreciate the "on the run".

                      *Hubitat C-7 2.4.2.129
                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                      *HASS 2025.7.2
                      w/ ZST10-700 fw 7.18.3

                      *Prod MSR in docker/portainer
                      MSR: latest-25139-fbd67abc
                      MQTTController: 25139
                      ZWave Controller: 25139

                      1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        Also see the edit I just made regarding your test. Apologies for brevity. I'm on the run today.

                        G Offline
                        G Offline
                        gwp1
                        wrote on last edited by
                        #11

                        @toggledbits Confirmed. Added test Ruleset and Rule. Tools>Restart, they stuck. Deleted test Rule and Ruleset, Tools>Restart, they were still gone.

                        Next up: docker-compose

                        *Hubitat C-7 2.4.2.129
                        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                        *HASS 2025.7.2
                        w/ ZST10-700 fw 7.18.3

                        *Prod MSR in docker/portainer
                        MSR: latest-25139-fbd67abc
                        MQTTController: 25139
                        ZWave Controller: 25139

                        G 1 Reply Last reply
                        1
                        • G gwp1

                          @toggledbits Confirmed. Added test Ruleset and Rule. Tools>Restart, they stuck. Deleted test Rule and Ruleset, Tools>Restart, they were still gone.

                          Next up: docker-compose

                          G Offline
                          G Offline
                          gwp1
                          wrote on last edited by
                          #12

                          To bring this all full circle, I had installed Portainer just to see what it was/did. Rereading the manual for MSR I stumbled across Portainer-specific instructions.

                          Short story long, I deleted the original container and created a new one thru the Portainer path. Done in mere minutes, runs flawlessly and I don't need to worry about the docker-compose errors I was getting.

                          Going to mark this topic as solved as all of the three issues were addressed.

                          *Hubitat C-7 2.4.2.129
                          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                          *HASS 2025.7.2
                          w/ ZST10-700 fw 7.18.3

                          *Prod MSR in docker/portainer
                          MSR: latest-25139-fbd67abc
                          MQTTController: 25139
                          ZWave Controller: 25139

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


                          Recent Topics

                          • [Reactor] Help with screne controller cycling logic
                            CrilleC
                            Crille
                            0
                            2
                            22

                          • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                            tunnusT
                            tunnus
                            0
                            22
                            554

                          • Expose MSR entities
                            CatmanV2C
                            CatmanV2
                            0
                            11
                            104

                          • Comment in Globa Expressions
                            CrilleC
                            Crille
                            1
                            2
                            75

                          • Stop the MSR by an external switch on Hubitat.
                            toggledbitsT
                            toggledbits
                            0
                            3
                            163

                          • Little Bobby tables...
                            CatmanV2C
                            CatmanV2
                            0
                            3
                            95

                          • Home Assistant Voice TTS is Easy
                            CatmanV2C
                            CatmanV2
                            0
                            3
                            144

                          • Play Audio through Home Assistant Voice Unit
                            toggledbitsT
                            toggledbits
                            1
                            1
                            90

                          • Home Assistant Voice
                            CatmanV2C
                            CatmanV2
                            0
                            21
                            720

                          • Unofficial thread for compatibility
                            tunnusT
                            tunnus
                            2
                            1
                            100

                          • Gradually turn on lights.
                            toggledbitsT
                            toggledbits
                            0
                            21
                            961

                          • Reactor (Multi-System/Multi-Hub) Announcements
                            toggledbitsT
                            toggledbits
                            5
                            123
                            56.0k
                          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