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. Set Entity value in expression?
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[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
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
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
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. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
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

Set Entity value in expression?

Scheduled Pinned Locked Moved Multi-System Reactor
20 Posts 4 Posters 1.5k Views 4 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.
  • toggledbitsT Away
    toggledbitsT Away
    toggledbits
    wrote on last edited by
    #6

    Generally speaking, you should use the power_switch service instead of the x_vera_svc... extension service whenever possible. The extension services are meant to be used only when the general services don't provide the function you need.

    I still can't read your screen shot. When you make the screen shots, try copying only the area with the data fields on the left, and leave off the buttons on the right. This will exclude a lot of unnecessary pixels from the screen shot and improve the overall resolution (reduce downsampling), and make is smaller to post, which is friendlier for the forums as well.

    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
    • S Offline
      S Offline
      sebby
      wrote on last edited by
      #7

      I get that, but the power_switch service only has on or off. I am trying to set it from a stored variable, so i don't know if it is on or off to begin, hence my attempt to set it via the SwitchPower1.SetTarget.

      toggledbitsT 1 Reply Last reply
      0
      • S sebby

        I get that, but the power_switch service only has on or off. I am trying to set it from a stored variable, so i don't know if it is on or off to begin, hence my attempt to set it via the SwitchPower1.SetTarget.

        toggledbitsT Away
        toggledbitsT Away
        toggledbits
        wrote on last edited by toggledbits
        #8

        @sebby I'm adding set to power_switch as we speak. Will be in the next build.

        To set from a stored variable, use a substitution in the variable value: ${{ expression-or-variable-name }}

        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
        • 3 Offline
          3 Offline
          3rdStng
          wrote on last edited by 3rdStng
          #9

          I did this exact same thing within Reactor and it became more trouble than it was worth and ultimately removed that rule. A very quick recap of the way I had it was:

          Conditions (now triggers):
          -- AC is ON
          (AND)
          -- Motion sensor tripped
          Activity (now Reaction):
          IF TRUE:
          -- GetLoadState of device (entity) and set that to a non-defined variable.
          -- Turn the fan on to XX%.
          IF FALSE:
          -- Turn fan to {variable}%

          Now how it became more trouble than it was worth probably could have been solved my adding an additional condition/trigger. If I walked into a room and then back out, but the AC was on, the fan would turn on. No sense in having the fan on if nobody was in the room. Thinking back, I would add that Motion has been detected and needs to remain detected/tripped for 120 seconds. (Assuming that your motion sensors reset in less than 120 seconds)

          1 Reply Last reply
          0
          • S Offline
            S Offline
            sebby
            wrote on last edited by sebby
            #10

            Thanks guys, my problem seems to be even more basic than all of that. what i cannot figure out is the "service" variable to use for the specific actions. I hope this image works, have tried everything i can think of to make it readable to all.

            Screen Shot 2021-08-06 at 4.24.56 PM.png

            1 Reply Last reply
            0
            • toggledbitsT Away
              toggledbitsT Away
              toggledbits
              wrote on last edited by
              #11

              The x_vera_device.set_variable action is the same as luup.variable_set() on Vera -- it sets the value of a state variable on the device. The service would be a Vera service ID. This is not what you want for turning a switch on or off. You cannot, in MSR or on Vera/Luup, turn a switch on or off by setting a state variable. You have to use an on/off action.

              I just uploaded the new build to latest (21218). This has a power_switch.set action that takes a boolean, as you are trying to do here. Update to the new latest build, then in your screen shot above, where you have x_vera_device.set_variable, you will select power_switch.set. It will give you a single parameter in which you can specify a boolean value (e.g. true or false), or use a variable substitution as I posted earlier.

              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
              1
              • S Offline
                S Offline
                sebby
                wrote on last edited by
                #12

                wow, thank you so much for that, as always greatly appreciated.

                1 Reply Last reply
                1
                • S Offline
                  S Offline
                  sebby
                  wrote on last edited by
                  #13

                  Hi Rigpapa, I updated the build, the variable is a drop-down with only the true/false option and not a variable that can be substituted. do i need to do something else to make it a string entry?

                  S 1 Reply Last reply
                  0
                  • toggledbitsT Away
                    toggledbitsT Away
                    toggledbits
                    wrote on last edited by
                    #14

                    https://smarthome.community/post/9103

                    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
                    1
                    • S sebby

                      Hi Rigpapa, I updated the build, the variable is a drop-down with only the true/false option and not a variable that can be substituted. do i need to do something else to make it a string entry?

                      S Offline
                      S Offline
                      sebby
                      wrote on last edited by
                      #15

                      @sebby Screen Shot 2021-08-06 at 8.59.30 PM.png

                      LibraSunL 1 Reply Last reply
                      0
                      • S sebby

                        @sebby Screen Shot 2021-08-06 at 8.59.30 PM.png

                        LibraSunL Offline
                        LibraSunL Offline
                        LibraSun
                        wrote on last edited by LibraSun
                        #16

                        @sebby said... (see above screenshot)

                        Based on your screenshot, it kinda looks like you can't (yet) override the two preset drop-down choices in that menu, in order to insert your own ${{ }} expression? (I'm not using 'Latest' so haven't tested myself.)

                        1 Reply Last reply
                        0
                        • toggledbitsT Away
                          toggledbitsT Away
                          toggledbits
                          wrote on last edited by toggledbits
                          #17

                          Whoops! Forgot about that (booleans use a fixed list rather than the generic multi-value path/datalist control)... fix coming...

                          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
                          1
                          • S Offline
                            S Offline
                            sebby
                            wrote on last edited by
                            #18

                            no rush, i was able to work around it by inserting the status of the fans as a number:

                            {
                            "Livingroom Fan" : getEntity("vera>Livingroom Fan").attributes.power_switch.state == false ? 0 : 1, 
                            "Loft Fan" : getEntity("vera>Loft Fan").attributes.power_switch.state == false ? 0 : 1, 
                            "Office Fan" : getEntity("vera>Office Fan").attributes.power_switch.state == false ? 0 : 1
                            }
                            

                            then used the SetTarget entity action to turn them on or off.

                            1 Reply Last reply
                            0
                            • toggledbitsT Away
                              toggledbitsT Away
                              toggledbits
                              wrote on last edited by
                              #19

                              OK. Build 21219 is up, allows expression substitution in boolean.

                              A couple of other things...

                              • ...attributes.power_switch.state == false ? 0 : 1 can be more succinctly written as attributes.power_switch.state ? 1 : 0
                              • The performAction() expression function will perform an action from an expression. If you have an object stored in a variable old_status that contains data like this: [ { id: "vera>Livingroom Fan", status: true }, { id: "vera>Loft Fan", status: false }, { id: "vera>Office Fan", status: true } ], then you can set those statuses in one expression: each d in old_status: performAction( d.id, "power_switch.set", d.status )

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

                              S 1 Reply Last reply
                              2
                              • toggledbitsT toggledbits

                                OK. Build 21219 is up, allows expression substitution in boolean.

                                A couple of other things...

                                • ...attributes.power_switch.state == false ? 0 : 1 can be more succinctly written as attributes.power_switch.state ? 1 : 0
                                • The performAction() expression function will perform an action from an expression. If you have an object stored in a variable old_status that contains data like this: [ { id: "vera>Livingroom Fan", status: true }, { id: "vera>Loft Fan", status: false }, { id: "vera>Office Fan", status: true } ], then you can set those statuses in one expression: each d in old_status: performAction( d.id, "power_switch.set", d.status )
                                S Offline
                                S Offline
                                sebby
                                wrote on last edited by
                                #20
                                • The performAction() expression function will perform an action from an expression. If you have an object stored in a variable old_status that contains data like this: [ { id: "vera>Livingroom Fan", status: true }, { id: "vera>Loft Fan", status: false }, { id: "vera>Office Fan", status: true } ], then you can set those statuses in one expression: each d in old_status: performAction( d.id, "power_switch.set", d.status )

                                This is exactly what i was looking for! thank you!!!!!! i was looking at the docs and completely glossed over that section...

                                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

                                • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                                  toggledbitsT
                                  toggledbits
                                  0
                                  68
                                  4.7k

                                • Shelly Wall Display XL
                                  therealdbT
                                  therealdb
                                  2
                                  6
                                  73

                                • Handling Dead Entities and Renamed Entities
                                  PablaP
                                  Pabla
                                  0
                                  5
                                  60

                                • Strange behavior for MQTT templates using payload and attributes
                                  toggledbitsT
                                  toggledbits
                                  0
                                  6
                                  122

                                • [MSR] reactor-mqtt-contrib package for additional MQTT templates
                                  therealdbT
                                  therealdb
                                  1
                                  46
                                  8.1k

                                • HA 2025.9.4 Supported Yet?
                                  toggledbitsT
                                  toggledbits
                                  0
                                  2
                                  83

                                • The reaction stopped working (Google Nest max playing a video)
                                  toggledbitsT
                                  toggledbits
                                  0
                                  7
                                  347

                                • Rule Set UI bug - RESOLVED
                                  toggledbitsT
                                  toggledbits
                                  1
                                  2
                                  226

                                • [Reactor] Copy&Paste of Rules
                                  therealdbT
                                  therealdb
                                  0
                                  1
                                  299

                                • [Reactor] Help with screne controller cycling logic
                                  toggledbitsT
                                  toggledbits
                                  0
                                  5
                                  400

                                • Stop the MSR by an external switch on Hubitat.
                                  Tom_DT
                                  Tom_D
                                  0
                                  6
                                  724

                                • Expose MSR entities
                                  CatmanV2C
                                  CatmanV2
                                  0
                                  11
                                  860
                                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