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] Modes race condition upon docker restart returns
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

[SOLVED] Modes race condition upon docker restart returns

Scheduled Pinned Locked Moved Multi-System Reactor
5 Posts 3 Posters 257 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.
  • 3 Offline
    3 Offline
    3rdStng
    wrote on last edited by 3rdStng
    #1

    Hi @toggledbits. It appears that the race condition from this post has returned. Or maybe it's a sibling race condition?

    MSR latest-21360-315df22 in docker on unRAID server for Hubitat C7 running 2.30.0.121

    EDIT: I may see the cause of the issue- More below in my EDIT section. And please let me know if this is TOO much information and screenshots. Trying to make it easier for you. Thx.

    I have a contact sensor report over my Echo devices when it is opened/closed, but only when the Hubitat is in it's Home state. Every once in a while this contact sensor get's stuck in the open state, as it is right now. A quick open and close resets the state, but that's a different issue.

    The issue, similar to the last race condition, upon my docker restart, the Reset Reaction is announced followed by the Set Reaction. If I remove the Mode entity and restart the docker, no announcements are made.

    Copy of the rule prior to docker restart (Copied to only notify on one Echo vs spam the family.)
    532ae3ae-a3a7-4c71-ba86-dd8c1dc17552-image.png

    Docker restarted - SET times changed.
    955539ae-ea7c-4a0a-8991-59f96a159be1-image.png

    Removed Mode entity and restarted Docker - Contact sensor and SET times remained.
    e4af0934-c0dc-4cdd-8a3d-4d9801d3ecd1-image.png

    Added Mode back in and restarted again. SET time and Home True value are set to the same time.
    14bae763-76f7-40c1-86cc-c13526d6d3c2-image.png

    EDIT: I was grabbing my entire rule to show the work. No Constraints, No Local Expressions. Upon doing this, I noticed that the Mode entity has a Null value. I checked another one of my rules that uses my Mode state and that rule is also Null. As if this value is not being stored. The overview/summary page shows the value as Home, but when I edit the rule, it shows Null.
    23d8c56d-87cf-4b2e-b2f9-9d48d38c338c-image.png

    A completely different rule, not touched, yet. Showing the null value differences.
    270f6639-9326-4724-9782-61128c858759-image.png

    3 1 Reply Last reply
    0
    • 3 3rdStng

      Hi @toggledbits. It appears that the race condition from this post has returned. Or maybe it's a sibling race condition?

      MSR latest-21360-315df22 in docker on unRAID server for Hubitat C7 running 2.30.0.121

      EDIT: I may see the cause of the issue- More below in my EDIT section. And please let me know if this is TOO much information and screenshots. Trying to make it easier for you. Thx.

      I have a contact sensor report over my Echo devices when it is opened/closed, but only when the Hubitat is in it's Home state. Every once in a while this contact sensor get's stuck in the open state, as it is right now. A quick open and close resets the state, but that's a different issue.

      The issue, similar to the last race condition, upon my docker restart, the Reset Reaction is announced followed by the Set Reaction. If I remove the Mode entity and restart the docker, no announcements are made.

      Copy of the rule prior to docker restart (Copied to only notify on one Echo vs spam the family.)
      532ae3ae-a3a7-4c71-ba86-dd8c1dc17552-image.png

      Docker restarted - SET times changed.
      955539ae-ea7c-4a0a-8991-59f96a159be1-image.png

      Removed Mode entity and restarted Docker - Contact sensor and SET times remained.
      e4af0934-c0dc-4cdd-8a3d-4d9801d3ecd1-image.png

      Added Mode back in and restarted again. SET time and Home True value are set to the same time.
      14bae763-76f7-40c1-86cc-c13526d6d3c2-image.png

      EDIT: I was grabbing my entire rule to show the work. No Constraints, No Local Expressions. Upon doing this, I noticed that the Mode entity has a Null value. I checked another one of my rules that uses my Mode state and that rule is also Null. As if this value is not being stored. The overview/summary page shows the value as Home, but when I edit the rule, it shows Null.
      23d8c56d-87cf-4b2e-b2f9-9d48d38c338c-image.png

      A completely different rule, not touched, yet. Showing the null value differences.
      270f6639-9326-4724-9782-61128c858759-image.png

      3 Offline
      3 Offline
      3rdStng
      wrote on last edited by
      #2

      If I restart my Hubitat controller, the Entity value when editing the rule will show the current value. But if I restart my docker, it will then show a null value.

      Value after HE hub reboot but before docker restart
      16f78441-3fae-43e9-8b60-4c1cdc7d85d8-image.png

      wmarcolinW 1 Reply Last reply
      0
      • 3 Offline
        3 Offline
        3rdStng
        wrote on last edited by 3rdStng
        #3

        @toggledbits posted a new blind docker build 21362 which has resolved the Mode issue. He wasn't able to test this build, but I wanted to get this update on here in case others come across it. I will mark this as SOLVED for now, even though this build was not tested by him.

        1 Reply Last reply
        0
        • 3 3rdStng

          If I restart my Hubitat controller, the Entity value when editing the rule will show the current value. But if I restart my docker, it will then show a null value.

          Value after HE hub reboot but before docker restart
          16f78441-3fae-43e9-8b60-4c1cdc7d85d8-image.png

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

          @3rdstng

          Allow me my two cents, in the third situation when you return to the Hubitat mode evaluation, it is written home with the "h" in lowercase, and remember that this is a case sensitive comparison that is valid, i.e., see that in the Currente Value status the Home is with the H in uppercase, that would make your rule unfeasible.

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

            He's got a case-insensitive test going; it'll be fine. The problem arises mostly when you send a new mode to Hubitat... that's where you need to be careful and get the case correct.

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

            1 Reply Last reply
            0
            • toggledbitsT toggledbits locked this topic on
            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
              43
            • 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
              339
            • 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