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

Using Variables in notifications

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 5 Posters 527 Views 5 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.
  • C Offline
    C Offline
    Cadwizzard
    wrote on last edited by Cadwizzard
    #1

    I'm trying to insert variables into notifications. I've tried
    {
    "message": "Oil Level is {{Oil_Level_V_to_Percent}}"
    }

    Also prefixing {{ with $ and a few other things.
    I get the main body but the variable is missing, i.e "Oil Level Is"
    Could someone please help me send the variable (and to title the notification would be great too)
    Many thanks 🙂
    Apologies

    Hass: v2022.10.4
    MSR: latest-22274-24dfd72c

    The rule :
    heatingoilalert.png variable.png

    PablaP 1 Reply Last reply
    0
    • C Cadwizzard

      I'm trying to insert variables into notifications. I've tried
      {
      "message": "Oil Level is {{Oil_Level_V_to_Percent}}"
      }

      Also prefixing {{ with $ and a few other things.
      I get the main body but the variable is missing, i.e "Oil Level Is"
      Could someone please help me send the variable (and to title the notification would be great too)
      Many thanks 🙂
      Apologies

      Hass: v2022.10.4
      MSR: latest-22274-24dfd72c

      The rule :
      heatingoilalert.png variable.png

      PablaP Offline
      PablaP Offline
      Pabla
      wrote on last edited by
      #2

      @cadwizzard first we’d need to know what home controller you are using and what version of MSR.

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

        ...and if the variable and action is in a Rule (show it) or a Global Reaction (show it). And show the variable definition, be it rule-based or global.

        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
        • C Offline
          C Offline
          Cadwizzard
          wrote on last edited by
          #4

          Apologies
          Initial post updated

          1 Reply Last reply
          0
          • PablaP Offline
            PablaP Offline
            Pabla
            wrote on last edited by Pabla
            #5

            So when you are testing if the actions work using a variable you have to use the big play button that right under the "Set Reaction" title. As for using said variable you're going to want to use it in this form ${{<variable_name>}}. Since you were likely hitting the play button just for this action that is probably why you werent getting the variable value in your notification.

            As for adding a title it will look like this

            {
              "message": "${{Oil_Level_V_to_Percent}}",
              "title": "<insert title name>"
            }
            
            C 1 Reply Last reply
            1
            • PablaP Pabla

              So when you are testing if the actions work using a variable you have to use the big play button that right under the "Set Reaction" title. As for using said variable you're going to want to use it in this form ${{<variable_name>}}. Since you were likely hitting the play button just for this action that is probably why you werent getting the variable value in your notification.

              As for adding a title it will look like this

              {
                "message": "${{Oil_Level_V_to_Percent}}",
                "title": "<insert title name>"
              }
              
              C Offline
              C Offline
              Cadwizzard
              wrote on last edited by Cadwizzard
              #6

              @pabla Thank You!
              I was going wrong with the title by missing the comma in preceding line, I had the rest right and indented the same before I took the code out, as it wasn't working.

              And right again, I had tested the code with ${{content}} but it didn't work - most likely because I used the play button to the right and not above the reaction.

              Really appreciated, i've updated my template I copy from, so that should be notifications sorted for everything now.

              Seperate issue is the value on the sensor flaps up and down by 1% when its close to changing (temperature in the oil tank/expansion) and sends lots of notifications, just need to figure out how to address that. But off topic for this post 🙂

              PablaP 1 Reply Last reply
              1
              • C Cadwizzard

                @pabla Thank You!
                I was going wrong with the title by missing the comma in preceding line, I had the rest right and indented the same before I took the code out, as it wasn't working.

                And right again, I had tested the code with ${{content}} but it didn't work - most likely because I used the play button to the right and not above the reaction.

                Really appreciated, i've updated my template I copy from, so that should be notifications sorted for everything now.

                Seperate issue is the value on the sensor flaps up and down by 1% when its close to changing (temperature in the oil tank/expansion) and sends lots of notifications, just need to figure out how to address that. But off topic for this post 🙂

                PablaP Offline
                PablaP Offline
                Pabla
                wrote on last edited by
                #7

                @cadwizzard You can use the round function for your variable to round it to whatever decimal point you need. Have a look in reactor docs under expressions -> functions for more info

                C 1 Reply Last reply
                0
                • PablaP Pabla

                  @cadwizzard You can use the round function for your variable to round it to whatever decimal point you need. Have a look in reactor docs under expressions -> functions for more info

                  C Offline
                  C Offline
                  Cadwizzard
                  wrote on last edited by
                  #8

                  @pabla The issue isn't rounding, the sensor is in Volts, i multiply by 10 to get % for gauges etc, so it's always rounded.
                  The issue is due to temperature and the accuracy of the sensor (ultrasonic), when the oil level is very close to for example 55 and 56% (5.5v/5.6v) and the oil expands, the reading will go from 55 to 56 and then 55 and then 56 over and over due to the tiny variance between the two readings. If that makes sense.
                  I can't set a rule to only track decreasing changes as we also fill up the tank sometimes too 🙂

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

                    You might consider a bit of time-based hysteresis by using the "sustain for" option in your rule/condition(s). I do this with various things around the house... if the attic humidity is above X% for more than YY minutes, start the dehumidifier, etc. This removes the short-cycling that can occur when a measurement is unstable around a critical point.

                    Also, there are ways previously documented in Reactor for Vera to do things like one-hour averages and moving averages, which can dampen those bounces/drifts. I'm not sure if anyone has done an MSR version of those, but the general approach is the same.

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

                    therealdbT MikeReadingtonM 2 Replies Last reply
                    1
                    • toggledbitsT toggledbits

                      You might consider a bit of time-based hysteresis by using the "sustain for" option in your rule/condition(s). I do this with various things around the house... if the attic humidity is above X% for more than YY minutes, start the dehumidifier, etc. This removes the short-cycling that can occur when a measurement is unstable around a critical point.

                      Also, there are ways previously documented in Reactor for Vera to do things like one-hour averages and moving averages, which can dampen those bounces/drifts. I'm not sure if anyone has done an MSR version of those, but the general approach is the same.

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

                      @toggledbits said in Using Variables in notifications:

                      Also, there are ways previously documented in Reactor for Vera to do things like one-hour averages and moving averages, which can dampen those bounces/drifts. I'm not sure if anyone has done an MSR version of those, but the general approach is the same.

                      Speaking of this, I'll surely welcome some recipes somewhere. I'll think a curated list will definitely benefit the community. I think it's fair to link reactor ones as well, since expressions are almost similar.

                      --
                      On a mission to automate everything.

                      My MS Reactor contrib
                      My Luup Plug-ins

                      1 Reply Last reply
                      1
                      • toggledbitsT toggledbits

                        You might consider a bit of time-based hysteresis by using the "sustain for" option in your rule/condition(s). I do this with various things around the house... if the attic humidity is above X% for more than YY minutes, start the dehumidifier, etc. This removes the short-cycling that can occur when a measurement is unstable around a critical point.

                        Also, there are ways previously documented in Reactor for Vera to do things like one-hour averages and moving averages, which can dampen those bounces/drifts. I'm not sure if anyone has done an MSR version of those, but the general approach is the same.

                        MikeReadingtonM Offline
                        MikeReadingtonM Offline
                        MikeReadington
                        wrote on last edited by
                        #11

                        @toggledbits I used something like that to dampen solar panel logic. I am not "legally" allowed to hook up, but I still wanted to play with them. I still have a dumb meter and it's easily possible to end up negative for the month. I used a couple of RIB relays to turn panel groups off if the consumption target for the month was trending under what would be considered believable.

                        (I also turn them off by the driveway entrance sensor logic on the days that I know the meter reader will show up. I don't particularly need an observant reader seeing the meter flying around backward)

                        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

                        • Set Reaction > Script Action
                          therealdbT
                          therealdb
                          0
                          6
                          109

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

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

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

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

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

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

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

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

                        • Disaster recovery and virtualisation
                          CatmanV2C
                          CatmanV2
                          0
                          5
                          727

                        • Remote access of Zwave stick from Z-wave server
                          CatmanV2C
                          CatmanV2
                          0
                          3
                          444
                        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