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. Dynamic Groups Controller - Filter Expressions
[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

Dynamic Groups Controller - Filter Expressions

Scheduled Pinned Locked Moved Multi-System Reactor
5 Posts 2 Posters 570 Views 2 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.
  • PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by
    #1

    Diving into Dynamic Groups and I am trying to create a filter expression for grouping battery devices that have a battery charge of between 11% and 35%. Thought this would be easy by setting my config to the following

        enabled: true
        name: "Dynamic Group Controller"
        implementation: DynamicGroupController
        config:
          groups:
            "low_battery_35":
              select:
                - include_capability: battery_power
              filter_expression:
                entity.attributes.battery_power.level 0.11 < 0.35
    

    However that didn't do the trick, I tried this as well no luck

      - id: groups
        enabled: true
        name: "Dynamic Group Controller"
        implementation: DynamicGroupController
        config:
          groups:
            "low_battery_35":
              select:
                - include_capability: battery_power
              filter_expression:
                entity.attributes.battery_power.level < 0.35
                entity.attributes.battery_power.level > 0.11
    

    Is it even possible to have two filters for one group? I am trying to create 3 groups total one would notify me if a device falls below 35%, then another notification if it falls below 10%, then a final notification if the battery is dead. If I just leave the filter expression at < 0.35 that device shows up in the 10% and 0% groups as well causing the device to show up multiple times in other groups.

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

      If only there was a file where the system left clues... 🙂

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

      PablaP 1 Reply Last reply
      1
      • toggledbitsT toggledbits

        If only there was a file where the system left clues... 🙂

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

        @toggledbits oops yes should've checked the logs first for some clues. Using this config below, there are no errors in the logs. However the group now shows devices that are below 35% battery and all devices above 11% battery, not inbetween 11% and 35% like I intend. Would I have to create a secondary group that filters the "low_battery_35" group and have the filter be for devices above 11% or is there a way to set the filter_expression to only show a the devices with a charge between 11% and 35% without needing to create a second group?

                "low_battery_35":
                  select:
                    - include_capability: battery_power
                  filter_expression:
                    entity.attributes.battery_power.level < 0.35,
                    entity.attributes.battery_power.level > 0.11
        
        1 Reply Last reply
        0
        • toggledbitsT Away
          toggledbitsT Away
          toggledbits
          wrote on last edited by toggledbits
          #4

          Actually, the fact that there's no error is a great surprise to me. It looks like you've walked into a YAML ambiguity. Half the online validators I throw your config into choke on it, and half don't. And it turns out, the YAML parser package I'm using in Reactor doesn't.

          The problems in your config are two:

          1. If you look carefully at the multi-line filter example in the docs, it begins filter_expression: >... and that > is important. It's missing in your config. It tells YAML that a multi-line string follows, and it should be there to remove the aforementioned ambiguity in YAML syntax.

          2. If you fix #1, the expression you have then isn't going to do what you want it to do. You have given an expression list (two or more expressions separated by commas), and in that case, the result of the expression is the result of the last expression (only). That's defined by the expression parser library, and it's an important aspect of the syntax that allows complex expressions to be written. What you really want is to and these two expressions together using the && operator. That would be:

             entity.attributes.battery_power.level < 0.35 &&
             entity.attributes.battery_power.level > 0.11
            

            You could also write that on one line. You could also use a temporary variable to make the expression run a little faster:

             level = entity.attributes.battery_power.level, level < 0.35 && level > 0.11
            

            That again is an expression list, and the result is that of the second expression (only) — boolean true if the level is between 0.11 and 0.35, and false otherwise.

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

          PablaP 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            Actually, the fact that there's no error is a great surprise to me. It looks like you've walked into a YAML ambiguity. Half the online validators I throw your config into choke on it, and half don't. And it turns out, the YAML parser package I'm using in Reactor doesn't.

            The problems in your config are two:

            1. If you look carefully at the multi-line filter example in the docs, it begins filter_expression: >... and that > is important. It's missing in your config. It tells YAML that a multi-line string follows, and it should be there to remove the aforementioned ambiguity in YAML syntax.

            2. If you fix #1, the expression you have then isn't going to do what you want it to do. You have given an expression list (two or more expressions separated by commas), and in that case, the result of the expression is the result of the last expression (only). That's defined by the expression parser library, and it's an important aspect of the syntax that allows complex expressions to be written. What you really want is to and these two expressions together using the && operator. That would be:

               entity.attributes.battery_power.level < 0.35 &&
               entity.attributes.battery_power.level > 0.11
              

              You could also write that on one line. You could also use a temporary variable to make the expression run a little faster:

               level = entity.attributes.battery_power.level, level < 0.35 && level > 0.11
              

              That again is an expression list, and the result is that of the second expression (only) — boolean true if the level is between 0.11 and 0.35, and false otherwise.

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

            @toggledbits That seems to have done the trick! I originally removed the > because I thought without out Reactor would treat each new line as a new entry but I see that it is the total opposite. Thanks for the help!

            1 Reply Last reply
            0
            • toggledbitsT toggledbits locked this topic on
            • toggledbitsT toggledbits referenced 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
              78
              5.5k

            • Do you Matter?
              CatmanV2C
              CatmanV2
              0
              2
              64

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

            • Shelly Wall Display XL
              therealdbT
              therealdb
              2
              6
              162

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

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

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

            • HA 2025.9.4 Supported Yet?
              toggledbitsT
              toggledbits
              0
              2
              110

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

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

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

            • [Reactor] Help with screne controller cycling logic
              toggledbitsT
              toggledbits
              0
              5
              423
            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