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. Localization
[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

Localization

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 4 Posters 947 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.
  • CrilleC Offline
    CrilleC Offline
    Crille
    wrote on last edited by
    #1

    @toggledbits I've done a (test) Swedish translation for MSR, I don't want/need a translated version, but I had the time and perhaps some future users would find it useful 🙂
    I noticed it's a bit early in the process to go live with systemwide localizations so no github in place yet, do you want input on this now or should we wait a few releases? considering it may be low priority issues.
    If so, do you want feedback here or in mantis?

    CrilleC 1 Reply Last reply
    4
    • toggledbitsT Away
      toggledbitsT Away
      toggledbits
      wrote on last edited by
      #2

      Go ahead and put it in Mantis. That's exciting!

      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
      • CrilleC Crille

        @toggledbits I've done a (test) Swedish translation for MSR, I don't want/need a translated version, but I had the time and perhaps some future users would find it useful 🙂
        I noticed it's a bit early in the process to go live with systemwide localizations so no github in place yet, do you want input on this now or should we wait a few releases? considering it may be low priority issues.
        If so, do you want feedback here or in mantis?

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

        A little preview of the Swedish version of MSR 🙂
        preview.PNG

        F 1 Reply Last reply
        2
        • CrilleC Crille

          A little preview of the Swedish version of MSR 🙂
          preview.PNG

          F Offline
          F Offline
          Fanan
          wrote on last edited by
          #4

          @crille great job!! I was hoping for someone to do the translation into swedish. English works just fine, but I wouldn't mind having it in swedish. 🙂 (Gärna på bred småländska )

          1 Reply Last reply
          2
          • toggledbitsT Away
            toggledbitsT Away
            toggledbits
            wrote on last edited by
            #5

            This is so cool. I don't even have the words, honestly. There are very personal feelings at work here. I'll just say I come from a world family, so seeing Reactor in a language other than English adds a connection for me that I have long wanted to see. Thank you for taking the time to do this.

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

            CrilleC 2 Replies Last reply
            1
            • toggledbitsT toggledbits

              This is so cool. I don't even have the words, honestly. There are very personal feelings at work here. I'll just say I come from a world family, so seeing Reactor in a language other than English adds a connection for me that I have long wanted to see. Thank you for taking the time to do this.

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

              @toggledbits Well you made it fairly easy, all it needs is a little bit of time and correct wordings for the appropriate places, so thank you.

              1 Reply Last reply
              1
              • MatohlM Offline
                MatohlM Offline
                Matohl
                wrote on last edited by
                #7

                Good job. I will test it when it is available, and I am at home 🙂

                1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  This is so cool. I don't even have the words, honestly. There are very personal feelings at work here. I'll just say I come from a world family, so seeing Reactor in a language other than English adds a connection for me that I have long wanted to see. Thank you for taking the time to do this.

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

                  @toggledbits According to the documentation for localization:

                  "You may, at your option, contribute your language file to be included with future builds of Reactor as an add-on ... We will simply pull your latest language file from your Github repository directly when and as needed during builds..."

                  Will this hold back the release of a new build, waiting for translators to update their repos with new versions matching the new build?

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

                    This is all so new, I hadn't really thought about it, but here's my first reaction to it:

                    • I would not delay a latest build, as these are not scheduled, and sometimes have urgency.
                    • I would delay a numbered release (e.g. 1.0.1, etc.). But, my plan and practice so far has been to derive these from prior latest builds that have proven stable, so I can factor in the necessary changes at that point and wait for them. This may require a bit of additional configuration management on my part, but I can plan the timing of the release, and give everyone predictable schedules.

                    Going forward, I think there are two practices that we will need to follow to give the best/longest compatibility:

                    • Strings are not removed from the translation files when later versions disuse them, at least, not for a very long time. Rather, they can perhaps be moved to the bottom of the file under a comment # Strings not used as of 21267 (for example) to keep them organized but still present. In this way, a 22044 translation file would still work well for 21267 or versions prior, because it still contains the old strings. At some major revision (2.0) we can clean house and remove the old strings. We've removed a few already; I won't ask you to remove any more, I'll just call them out as "disused."
                    • Strings will not change their keys, use, or meaning. If a changes in these ways, a new string (or tag) will be created for the purpose, and the old version can go on the list of old/disused strings. This should help ensure that 21267 and 22044 use a string in the same way, and the translations are valid in both. So, for example, the 1:T change I just asked you to make will never be repeated; it was the first and last such request, and we'll do it by replacement going forward.

                    Any thoughts or recommendations you have about all this are more than welcome. I've done many product localizations from the original engineering side. What I haven't done is worked with language teams on localized builds thereafter -- that has always ended up going to other departments and other companies in other countries, and handled weeks or months after my work has been packaged and released in the US. So, I don't have any experience at policies and procedures that work in helping you maintain the work. I have a good imagination, but it's a bit of "the tail wagging the dog" as we say here, so I'm eager to have you tell me what you think should be done. What we're doing now is only my first guess to see what happens to get it rolling.

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

                    CrilleC 1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      This is all so new, I hadn't really thought about it, but here's my first reaction to it:

                      • I would not delay a latest build, as these are not scheduled, and sometimes have urgency.
                      • I would delay a numbered release (e.g. 1.0.1, etc.). But, my plan and practice so far has been to derive these from prior latest builds that have proven stable, so I can factor in the necessary changes at that point and wait for them. This may require a bit of additional configuration management on my part, but I can plan the timing of the release, and give everyone predictable schedules.

                      Going forward, I think there are two practices that we will need to follow to give the best/longest compatibility:

                      • Strings are not removed from the translation files when later versions disuse them, at least, not for a very long time. Rather, they can perhaps be moved to the bottom of the file under a comment # Strings not used as of 21267 (for example) to keep them organized but still present. In this way, a 22044 translation file would still work well for 21267 or versions prior, because it still contains the old strings. At some major revision (2.0) we can clean house and remove the old strings. We've removed a few already; I won't ask you to remove any more, I'll just call them out as "disused."
                      • Strings will not change their keys, use, or meaning. If a changes in these ways, a new string (or tag) will be created for the purpose, and the old version can go on the list of old/disused strings. This should help ensure that 21267 and 22044 use a string in the same way, and the translations are valid in both. So, for example, the 1:T change I just asked you to make will never be repeated; it was the first and last such request, and we'll do it by replacement going forward.

                      Any thoughts or recommendations you have about all this are more than welcome. I've done many product localizations from the original engineering side. What I haven't done is worked with language teams on localized builds thereafter -- that has always ended up going to other departments and other companies in other countries, and handled weeks or months after my work has been packaged and released in the US. So, I don't have any experience at policies and procedures that work in helping you maintain the work. I have a good imagination, but it's a bit of "the tail wagging the dog" as we say here, so I'm eager to have you tell me what you think should be done. What we're doing now is only my first guess to see what happens to get it rolling.

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

                      @toggledbits I believe your suggestions for long term compatibility is spot on.
                      Considering this is new and we are running "latest" there will be frequent acceptable changes that demand translators/user actions for keeping things up to date.
                      As you say numbered releases should probably already have an updated file for localization and I really like the implementation of disused strings for backward compatibility.

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

                        OK. I'm updating the docs with all of this. Keep the discoveries and suggestions 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
                        • 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
                          5

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

                        • Shelly Wall Display XL
                          therealdbT
                          therealdb
                          2
                          6
                          81

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

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

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

                        • HA 2025.9.4 Supported Yet?
                          toggledbitsT
                          toggledbits
                          0
                          2
                          84

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

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

                        • [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
                          735
                        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