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] Expressions - predefining a variable type
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] Expressions - predefining a variable type

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

    I have a use case where I need to have a boolean variable that will be set to true/false by reactions.

    I see that i can define a local variable by giving it a name and leaving the definition empty. This leaves it at state "null" until a reaction tells it that its a boolean.

    Is there a way to tell it that it should start out as "false" (i.e when reactor has restarted), and not null?

    Am i going about this the wrong way?

    -- The use case is that I have a sensor on my fireplace, and the following logic is for notifying when its time to get up en refill with firewood.. I also want to reset the MaxInInterval to CurrentTemp when notification is sent..

    1fd2951f-cb6b-4a2f-b957-1e0698171f4d-image.png dd99634e-f0ad-4878-bb87-0284c2df5535-image.png

    Edit: better screenhots. Reactor version 23010-7dd2c9e9

    1 Reply Last reply
    0
    • PerHP Offline
      PerHP Offline
      PerH
      wrote on last edited by
      #2

      BTW, in the screenshots we see that the NotificationSent has fired, and is now interpreted as a string..

      1 Reply Last reply
      0
      • PerHP Offline
        PerHP Offline
        PerH
        wrote on last edited by PerH
        #3

        The rule is corrected and works well:
        35bcdc03-5131-419d-95b4-68b00a675fec-image.png

        It notifies once for each time the temperature has increased, only with temperatures above 100°C, and when i'm home..

        The NotificationSent value wasn't nessecary here, But i'm still wondering if one can define a variable type and set the start value, and later manupulate that value by a reaction?

        1 Reply Last reply
        1
        • therealdbT Offline
          therealdbT Offline
          therealdb
          wrote on last edited by
          #4

          It depends on the use case, but I usually set them via a group in the reaction. Just be sure to se to ${{bool(false)}}
          Depending on the use case, I have a couple resetting (or setting for the first time) in a reaction watching for MSR start.

          --
          On a mission to automate everything.

          My MS Reactor contrib
          My Luup Plug-ins

          toggledbitsT 1 Reply Last reply
          2
          • therealdbT therealdb

            It depends on the use case, but I usually set them via a group in the reaction. Just be sure to se to ${{bool(false)}}
            Depending on the use case, I have a couple resetting (or setting for the first time) in a reaction watching for MSR start.

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

            @therealdb said in Expressions - predefining a variable type:

            Just be sure to se to ${{bool(false)}}

            That's redundant. false is a reserved word that means boolean false, so you don't need to put it through bool()

            @PerH

            4249770b-225b-45f6-a011-4a7abb908f5c-image.png

            This Set Variable action is setting the variable to the string value "true". The operand/parameter of the action is a string. In order to get a boolean, you have to use the expression substitution form as @therealdb suggests, but you only need ${{ true }} -- the interior of the substitution is an expression, and the result of the expression is whatever type the expression result is... in this case, the keyword true simply evaluates to boolean true (the result is boolean).

            To answer your original question, you can initially set the expression for the variable to false in the Expressions editor at the time you create the variable (or any time after), save changes, force and evaluation, and then once the initial false value is bound to the variable, just remove the expression (make it an expressionless variable) and save changes again.

            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
            2
            • PerHP Offline
              PerHP Offline
              PerH
              wrote on last edited by
              #6

              Considering this solved, but would like to add that its a bit important to mark "true" and "false" as depicted above here, and not using them in string form.
              Using "true" in string form in the condition like in "MaxInInterval" in the initial post didn't work, the condition didn't flip when the state changed.
              I guess this is because of how these reserved words are interpreted, so tagging them as boolean is important.

              toggledbitsT 1 Reply Last reply
              0
              • PerHP PerH

                Considering this solved, but would like to add that its a bit important to mark "true" and "false" as depicted above here, and not using them in string form.
                Using "true" in string form in the condition like in "MaxInInterval" in the initial post didn't work, the condition didn't flip when the state changed.
                I guess this is because of how these reserved words are interpreted, so tagging them as boolean is important.

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

                @PerH I'm finding this entire statement to be a bit cryptic. Can you elaborate on what you are saying here, how you now think it works?

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

                  I'd be happy to!

                  in the original post you see my expression: if NotificationSent != "true" then, which is supposed to reset the maximum reading when notification is sent, and prepare for a new increase when more wood is applied.

                  This never fired when the condition was met, but when I changed it to if NotificationSent != "1" then, (with the same change in the reactions) it worked as intended. The variable was still interpreted as a string.

                  My theory was that this was caused by the special considerations for the word "true" in the interpreter somehow, and that the ${{ true }} in the reaction would solve the problem.

                  That may offcourse be wrong? I admit that the imperical basis is rather thin. 😉

                  I should be able to reproduce this if needed.

                  therealdbT 1 Reply Last reply
                  0
                  • PerHP PerH

                    I'd be happy to!

                    in the original post you see my expression: if NotificationSent != "true" then, which is supposed to reset the maximum reading when notification is sent, and prepare for a new increase when more wood is applied.

                    This never fired when the condition was met, but when I changed it to if NotificationSent != "1" then, (with the same change in the reactions) it worked as intended. The variable was still interpreted as a string.

                    My theory was that this was caused by the special considerations for the word "true" in the interpreter somehow, and that the ${{ true }} in the reaction would solve the problem.

                    That may offcourse be wrong? I admit that the imperical basis is rather thin. 😉

                    I should be able to reproduce this if needed.

                    therealdbT Offline
                    therealdbT Offline
                    therealdb
                    wrote on last edited by
                    #9

                    @PerH I’ve been in the same boat and, yes, the problem is in the underlying type. The same applies to int/float, if you have an increment somewhere.

                    Apologies for the bool() part, I was on my phone and I wrote the first thing that came to my mind, but @toggledbits is in fact right.

                    --
                    On a mission to automate everything.

                    My MS Reactor contrib
                    My Luup Plug-ins

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

                      Yes, the rules of comparisons of different types for Expressions are different from the rules in Conditions. In a Condition, the comparison of the string "true" to a boolean attribute with value true will succeed. In Expressions, the JavaScript rules are followed so the equivalent expression's (e.g. "true" == true) result is false (the string is not equal to the boolean because the word contained in the string isn't magical). But in a Condition, the comparison of a non-zero operand to a boolean attribute having value true will be true, and in Expressions following the JavaScript rules will also be true (because in JavaScript and therefore the expression language, non-zero values are equivalent to true, and 0 is equivalent to false). Basically, in Expressions the strings are treated more strictly by their type, as in JavaScript, and there are no "magic values" (like the word "true") that are understood to mean something else. In Conditions, because all operands are strings, some back office magic happens to try to interpret what to do, otherwise no comparison to anything other than a string could work at all.

                      This may seem inconsistent across the product but it's something I'm unlikely to change as (a) relaxing it in Expressions promotes sloppy construction of expressions, and (b) Expressions are and always have been (even in R4V) an advanced user feature and it is my expectation that advanced users learn the rules of the language, as they would for any language (e.g. Lua). In Conditions and Actions (of Reactions), all operands and parameters are always strings; they need to be manipulated for Conditions to do comparisons, or for Actions to produce the right parameters for the target device or hub. In Expressions, the values are determined by the subexpression that produces them (e.g. "1" produces a string type result, where 1 produces a numeric result, [1] produces an array containing a numeric, and ["1"] produces an array containing a string).

                      I also note your expression if MaxInterval-CurrentTemp > 15 then true else false end, is a bit redundant from a programmer's perspective. In this construction, MaxInterval -CurrentTemp > 15 on its own produces true or false (the > operator always produces a boolean result), so you don't need the branches of the if...else..end construction here, the greater-than test itself can be the entire expression: MaxInterval-CurrentTemp > 15 alone will work the same and be more efficient. Adding the if block just makes extra work.

                      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
                      2
                      • PerHP Offline
                        PerHP Offline
                        PerH
                        wrote on last edited by
                        #11

                        I appreciate both the strictness regarding code and the lesson in javascript. Thanks!

                        I've found out why my "MaxInInterval" didn't work in the original post, and what that "Force re-evaluation..." tickbox on the reactions does!

                        42141f14-385f-429d-a8b9-4358b1074800-image.png

                        (to type it out, I changed the variable in reaction, and naturally, the only variable being updated was the one called out..)

                        1 Reply Last reply
                        1
                        • 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
                          340

                        • 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