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. The x_vera_state capability is gone
[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

The x_vera_state capability is gone

Scheduled Pinned Locked Moved Multi-System Reactor
22 Posts 5 Posters 2.4k 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.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #8

    OK after restarting MSR for a second time I can now see all the new svc stuff.

    Side note, I can see a SubMasters1 service ID listed. I uninstalled that plugin ages ago, looks like some traces have been left behind.

    Screenshot_20210314_152101_com.android.chrome.jpg

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

      Vera's implementation of services is very "loosey goosey". If any device has a state variable in a service, Vera considers that service "supported" by the device (even if the device doesn't actually implement any of its actions or manage that state variable). It has the advantage of not being overly strict, so that you can set variables that (a) aren't declared in a service that a device is declared to support; (b) are (declared or not) in a service the device does not explicitly support; and (c) have nothing to do with any defined service at all. This is useful, but also leaves Vera with a tendancy to accumulate a lot of garbage state variables that can't be easily cleaned out as your configuration changes over time. Vera themselves use this flexibility extensively, and it is available to plugins as well. Complicating matters, plugins are not notified when they are uninstalled, so there is no opportunity for a plugin to clean up after itself before heading out the door.

      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
      • LibraSunL Offline
        LibraSunL Offline
        LibraSun
        wrote on last edited by
        #10

        I used to take pains to remove (by setting to a null value using Luup, I believe) any extraneous device parameters I had introduced due to typos, etc. Now, I'm much less fussy about them and tend to leave bogus variables in place.

        As @kfxo had worried (above), I thought my couple of dozen or so Rules in MSR would require major editing with the changes introduced in rev. 21072, but happily found only TWO occurrences of x_vera_state in my workflow. Lucky!

        K cw-kidC 2 Replies Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by
          #11

          You will only find them in rules and getEntity expressions, too. There were no actions in x_vera_state, so no need to worry about reactions.

          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
          • LibraSunL LibraSun

            I used to take pains to remove (by setting to a null value using Luup, I believe) any extraneous device parameters I had introduced due to typos, etc. Now, I'm much less fussy about them and tend to leave bogus variables in place.

            As @kfxo had worried (above), I thought my couple of dozen or so Rules in MSR would require major editing with the changes introduced in rev. 21072, but happily found only TWO occurrences of x_vera_state in my workflow. Lucky!

            K Offline
            K Offline
            kfxo
            wrote on last edited by
            #12

            @librasun said in The x_vera_state capability is gone:

            As @kfxo had worried (above), I thought my couple of dozen or so Rules in MSR would require major editing with the changes introduced in rev. 21072, but happily found only TWO occurrences of x_vera_state in my workflow. Lucky!

            Ended up not being too bad but I had to click through like 300 rules just to make sure I did not miss anything.

            This release is top notch. I had a list of Hass mappings I wanted to start requesting @toggledbits and now they are all there.

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

              It should still be the case that the most frequently-used device types should get mappings with their most-frequently-used attributes, but now we can take our time about it. The Reactor system capabilities are just simpler wrappers for the native controller ones. Eventually, they will also facilitate moving a device from one controller type to another. If, for example, you are using the Reactor binary_sensor capability in a Rule, and you move that device to another controller, it should still work as a binary_sensor on the new controller. On the other hand, if you've decided to use x_vera_svc_micasaverde-com_SecuritySensor1.Tripped in your rule and you move the device to HomeAssistant or Hubitat, you won't get that benefit.

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

              cw-kidC 1 Reply Last reply
              1
              • toggledbitsT toggledbits

                It should still be the case that the most frequently-used device types should get mappings with their most-frequently-used attributes, but now we can take our time about it. The Reactor system capabilities are just simpler wrappers for the native controller ones. Eventually, they will also facilitate moving a device from one controller type to another. If, for example, you are using the Reactor binary_sensor capability in a Rule, and you move that device to another controller, it should still work as a binary_sensor on the new controller. On the other hand, if you've decided to use x_vera_svc_micasaverde-com_SecuritySensor1.Tripped in your rule and you move the device to HomeAssistant or Hubitat, you won't get that benefit.

                cw-kidC Offline
                cw-kidC Offline
                cw-kid
                wrote on last edited by
                #14

                @toggledbits said in The x_vera_state capability is gone:

                for example, you are using the Reactor binary_sensor capability in a Rule, and you move that device to another controller, it should still work as a binary_sensor on the new controller.

                Genius !

                I am keeping all mine as the Reactor System ones then.

                Unless there is some specific requirement where I can only use x_vera_svc_

                1 Reply Last reply
                1
                • LibraSunL LibraSun

                  I used to take pains to remove (by setting to a null value using Luup, I believe) any extraneous device parameters I had introduced due to typos, etc. Now, I'm much less fussy about them and tend to leave bogus variables in place.

                  As @kfxo had worried (above), I thought my couple of dozen or so Rules in MSR would require major editing with the changes introduced in rev. 21072, but happily found only TWO occurrences of x_vera_state in my workflow. Lucky!

                  cw-kidC Offline
                  cw-kidC Offline
                  cw-kid
                  wrote on last edited by
                  #15

                  @librasun said in The x_vera_state capability is gone:

                  I used to take pains to remove (by setting to a null value using Luup, I believe) any extraneous device parameters

                  So how can I manually remove this SubMasters1 Service ID ?

                  Looking in the list in the Entities area of MSR, that SubMasters is the only Vera plugin that I have uninstalled but a Service ID for it remains.

                  When I select it, it lists these devices:

                  efa7dfc8-b508-4c48-86c7-d90df59c6c3e-image.png

                  Looking at those devices Variables in Vera I cannot see any Variables related to SubMasters I don't think.

                  Thanks

                  1 Reply Last reply
                  0
                  • LibraSunL Offline
                    LibraSunL Offline
                    LibraSun
                    wrote on last edited by
                    #16
                    This post is deleted!
                    1 Reply Last reply
                    0
                    • toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by
                      #17

                      If you expand those entities and look at their attributes, you will likely find x_vera_svc_toggledbits_com_Submasters1.xxxx where xxxx is some name. The variables on Vera will have the same xxxx 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
                      • cw-kidC Offline
                        cw-kidC Offline
                        cw-kid
                        wrote on last edited by
                        #18

                        x_vera_svc_toggledbits_com_Submasters1.Random="0.5573104607556194"

                        So the variable is called "Random" it appears. I can see that in Vera on the Variables tab of the device.

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

                          It's living up to its name! Run this on your Vera, putting in the device number where indicated:

                          luup.variable_set( "urn:toggledbits-com:serviceId:Submasters1", "Random", nil, DEVNUM )
                          luup.reload()
                          

                          You'll also need to restart MSR, since there's no indication from the Vera when a state variable is deleted, it can't know.

                          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
                          • LibraSunL Offline
                            LibraSunL Offline
                            LibraSun
                            wrote on last edited by
                            #20

                            I vote that the above -- namely, Vera Variable Zapper -- be included among the Tools planned for MSR. Or is that too purpose-specific?
                            I've always hoped for a programmatic/UI means of pruning unwanted Variables from my Devices without resorting to Luup code on Vera.

                            CrilleC 1 Reply Last reply
                            0
                            • cw-kidC Offline
                              cw-kidC Offline
                              cw-kid
                              wrote on last edited by
                              #21

                              I have run that command against each device number and now all those affected devices no longer have a "Random" variable.
                              After restarting MSR I can now no longer see the SubMasters1 service ID so its all gone now.

                              Thank you.

                              1 Reply Last reply
                              0
                              • LibraSunL LibraSun

                                I vote that the above -- namely, Vera Variable Zapper -- be included among the Tools planned for MSR. Or is that too purpose-specific?
                                I've always hoped for a programmatic/UI means of pruning unwanted Variables from my Devices without resorting to Luup code on Vera.

                                CrilleC Offline
                                CrilleC Offline
                                Crille
                                wrote on last edited by
                                #22

                                @librasun I believe that is fixed in Vera fw 7.32
                                "12. Fixed the issues with not being able to remove or set an attribute or variable to the empty value".

                                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

                                • Caution: zwave-js-ui docker 11.4.0 is broken
                                  toggledbitsT
                                  toggledbits
                                  0
                                  2
                                  37

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

                                • Shelly Wall Display XL
                                  therealdbT
                                  therealdb
                                  2
                                  6
                                  98

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

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

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

                                • HA 2025.9.4 Supported Yet?
                                  toggledbitsT
                                  toggledbits
                                  0
                                  2
                                  91

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

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

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

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

                                • Stop the MSR by an external switch on Hubitat.
                                  Tom_DT
                                  Tom_D
                                  0
                                  6
                                  740
                                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