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

Rule for devices battery level ?

Scheduled Pinned Locked Moved Multi-System Reactor
43 Posts 6 Posters 4.5k Views 7 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 cw-kid
    #7

    I seem to have a problem with my trigger however

    905686d6-d0dc-4f28-ae27-37fb5b167683-image.png

    Its triggering the reaction when I don't want it to do so.

    I need to make the value of the expression "battery_low_names" null when no devices are below the battery level of 10% etc.

    I've tried adding in a ? in to the expression but it doesn't seem to be working

    join( each id in battery_low_list: getEntity(id)?.name, ', ')
    

    EDIT:

    This seems to work instead adding "? id: null" to the end of the expression.

    join( each id in battery_low_list: getEntity(id).name, ', ') ? id: null
    

    6f03c823-ba5f-4ea4-b794-313bdfe2f7b9-image.png

    EDIT 2:

    Maybe it doesn't work because now its not putting in the devices name in the expression value

    8ff5e855-5f1d-470f-8ca7-d4542728abf5-image.png

    EDIT 3:

    I then tried changing the trigger altogether to this, but it doesn't work and becomes true anyway.

    7ac8c487-52db-4907-b06c-99ccc293f6f7-image.png

    Likewise with this one:

    f9835abb-2cec-4b65-ab01-58acea857711-image.png

    Maybe there is a bug? All of these are going true and running the reaction when I expect them not to do that

    a3821660-9193-4725-845f-ea83766162a0-image.png

    IanI 1 Reply Last reply
    0
    • cw-kidC cw-kid

      I seem to have a problem with my trigger however

      905686d6-d0dc-4f28-ae27-37fb5b167683-image.png

      Its triggering the reaction when I don't want it to do so.

      I need to make the value of the expression "battery_low_names" null when no devices are below the battery level of 10% etc.

      I've tried adding in a ? in to the expression but it doesn't seem to be working

      join( each id in battery_low_list: getEntity(id)?.name, ', ')
      

      EDIT:

      This seems to work instead adding "? id: null" to the end of the expression.

      join( each id in battery_low_list: getEntity(id).name, ', ') ? id: null
      

      6f03c823-ba5f-4ea4-b794-313bdfe2f7b9-image.png

      EDIT 2:

      Maybe it doesn't work because now its not putting in the devices name in the expression value

      8ff5e855-5f1d-470f-8ca7-d4542728abf5-image.png

      EDIT 3:

      I then tried changing the trigger altogether to this, but it doesn't work and becomes true anyway.

      7ac8c487-52db-4907-b06c-99ccc293f6f7-image.png

      Likewise with this one:

      f9835abb-2cec-4b65-ab01-58acea857711-image.png

      Maybe there is a bug? All of these are going true and running the reaction when I expect them not to do that

      a3821660-9193-4725-845f-ea83766162a0-image.png

      IanI Offline
      IanI Offline
      Ian
      wrote on last edited by
      #8

      @cw-kid

      I'm using this.

      7a996464-1926-424b-800c-7358045bc946-image.png

      This goes true when battery_low_names is populated with the names of the devices with low battery levels.

      cw-kidC 1 Reply Last reply
      0
      • IanI Ian

        @cw-kid

        I'm using this.

        7a996464-1926-424b-800c-7358045bc946-image.png

        This goes true when battery_low_names is populated with the names of the devices with low battery levels.

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

        @ian

        That works !

        Easy when you know how..

        The trigger is now going false when no devices are in the battery_low_names expression results.

        b398a767-2130-47b6-bca1-bdcd3346f965-image.png

        1 Reply Last reply
        0
        • toggledbitsT toggledbits

          @cw-kid One of my to-do list tasks for expressions is to be able to create a list of devices that match a test. Until that comes, you can just build your own array of battery-operated devices like this (lets call this battery_device_list) :

          35882eb5-310f-41b1-a95e-eaf52dbc0bb8-image.png

          Then, you can reduce that list to all of the devices that have battery < 10%:

          c108f634-1ad1-4156-9e47-777c98c9d69b-image.png

          That leaves you with an array of the entities that have low battery. Use another expression to convert that into a comma-separated list of entity names:

          30ca5615-71c3-431e-b83f-d0aeff6144e4-image.png

          Your rule just checks to see if that battery_low_names (a string now) expression is not empty, and runs whatever notifications you want to run if it is not. You can include the battery_low_names variable in the text of your email or other notification, too.

          1bfd5d0f-1313-4613-ac2b-5731ddf5c594-image.png

          toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by toggledbits
          #10

          @toggledbits said in Rule for devices battery level ?:

          (a string now) expression is not empty,

          Details.

          Also these can be rule expressions, they do not need to be global.

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

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

            Thanks I've changed the expressions to local rule ones instead and its all still working.

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

              How can I make this rule re-trigger ?

              Say I don't immediate go replace the battery on the device mentioned, can I have the rule run the alerts / notifications each day or week until I have done it and changed the batteries ?

              Also can the alerts also state what the battery level percentage actually is ?

              Thanks

              toggledbitsT IanI 2 Replies Last reply
              0
              • cw-kidC cw-kid

                How can I make this rule re-trigger ?

                Say I don't immediate go replace the battery on the device mentioned, can I have the rule run the alerts / notifications each day or week until I have done it and changed the batteries ?

                Also can the alerts also state what the battery level percentage actually is ?

                Thanks

                toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #13

                @cw-kid said in Rule for devices battery level ?:

                How can I make this rule re-trigger ?

                Wrap the condition in a group and put the group in "pulse" output mode with the timing you want.

                @cw-kid said in Rule for devices battery level ?:

                Also can the alerts also state what the battery level percentage actually is ?

                Yes, but I'm going to leave it as an exercise for the reader. Level of difficulty: moderate.

                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
                0
                • cw-kidC cw-kid

                  How can I make this rule re-trigger ?

                  Say I don't immediate go replace the battery on the device mentioned, can I have the rule run the alerts / notifications each day or week until I have done it and changed the batteries ?

                  Also can the alerts also state what the battery level percentage actually is ?

                  Thanks

                  IanI Offline
                  IanI Offline
                  Ian
                  wrote on last edited by
                  #14

                  @cw-kid

                  Try this.

                  16c0d434-95ea-453d-b06e-e9a68663fbe5-image.png

                  cw-kidC 1 Reply Last reply
                  0
                  • IanI Ian

                    @cw-kid

                    Try this.

                    16c0d434-95ea-453d-b06e-e9a68663fbe5-image.png

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

                    @ian

                    Thanks Ian that works, my Telegram text message now has the number% at the end of the message now.

                    However this messes up the Google Home TTS announcement sent via node-red, if I have a "%" in the expression. So I had to change it to the word "percent" instead and now the TTS sounds correct when spoken.

                    join( each id in battery_low_list: getEntity(id).name + " " + "at" + " " + int(getEntity(id).attributes.battery_power.level * 100) + " percent", ', ')
                    
                    1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      @cw-kid said in Rule for devices battery level ?:

                      How can I make this rule re-trigger ?

                      Wrap the condition in a group and put the group in "pulse" output mode with the timing you want.

                      @cw-kid said in Rule for devices battery level ?:

                      Also can the alerts also state what the battery level percentage actually is ?

                      Yes, but I'm going to leave it as an exercise for the reader. Level of difficulty: moderate.

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

                      @toggledbits said in Rule for devices battery level ?:

                      Wrap the condition in a group and put the group in "pulse" output mode with the timing you want.

                      Like this?

                      146e1b92-875d-4a6e-8619-e555c355fbce-image.png

                      5eed7d9c-43ab-4a1e-8505-c0679f0ce401-image.png

                      Seems to be working and the alerts are repeating every 60 seconds now. I will just set this to 24hrs I think.

                      1 Reply Last reply
                      1
                      • toggledbitsT toggledbits

                        @cw-kid One of my to-do list tasks for expressions is to be able to create a list of devices that match a test. Until that comes, you can just build your own array of battery-operated devices like this (lets call this battery_device_list) :

                        35882eb5-310f-41b1-a95e-eaf52dbc0bb8-image.png

                        Then, you can reduce that list to all of the devices that have battery < 10%:

                        c108f634-1ad1-4156-9e47-777c98c9d69b-image.png

                        That leaves you with an array of the entities that have low battery. Use another expression to convert that into a comma-separated list of entity names:

                        30ca5615-71c3-431e-b83f-d0aeff6144e4-image.png

                        Your rule just checks to see if that battery_low_names (a string now) expression is not empty, and runs whatever notifications you want to run if it is not. You can include the battery_low_names variable in the text of your email or other notification, too.

                        1bfd5d0f-1313-4613-ac2b-5731ddf5c594-image.png

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

                        @toggledbits said in Rule for devices battery level ?:

                        One of my to-do list tasks for expressions is to be able to create a list of devices that match a test.

                        This is very useful, is it released yet or still on the to-do list?

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

                          Still on the to-do list, but I think I'm close to figuring out what I want it to do. These things get harder with time: the more people use them, the more etched in stone they become, so making a "first guess" and completely changing things later isn't really something I want to do a lot of. If I can get something good on the first try, that's the way...

                          Here's what I'm thinking...

                          First, the matchEntities() function would quickly narrow down the set, in a manner similar to the filters on the Entities page and the Entity Picker:

                              living_room_sensors = matchEntities( { controller: 'vera', capability: [ 'binary_sensor', 'value_sensor'' ], group: 'Living Room' } )
                          

                          This would return an array of entities. From here, you could use an each statement to further filter any deep refinements. This expression would take the above array of sensors in the Living Room and pick out those that are battery powered and have battery level under 50%:

                              low_battery_living_room = each e in living_room_sensors: e.attributes.battery_power?.level <= 0.5 ? e : null
                          

                          I'm liking this approach because the function could do the bulk reduction of potential hundreds of entities down to a manageable list, and then the final filtering of the list can be done with expressions for maximum flexibility.

                          Any thoughts about that?

                          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

                            Still on the to-do list, but I think I'm close to figuring out what I want it to do. These things get harder with time: the more people use them, the more etched in stone they become, so making a "first guess" and completely changing things later isn't really something I want to do a lot of. If I can get something good on the first try, that's the way...

                            Here's what I'm thinking...

                            First, the matchEntities() function would quickly narrow down the set, in a manner similar to the filters on the Entities page and the Entity Picker:

                                living_room_sensors = matchEntities( { controller: 'vera', capability: [ 'binary_sensor', 'value_sensor'' ], group: 'Living Room' } )
                            

                            This would return an array of entities. From here, you could use an each statement to further filter any deep refinements. This expression would take the above array of sensors in the Living Room and pick out those that are battery powered and have battery level under 50%:

                                low_battery_living_room = each e in living_room_sensors: e.attributes.battery_power?.level <= 0.5 ? e : null
                            

                            I'm liking this approach because the function could do the bulk reduction of potential hundreds of entities down to a manageable list, and then the final filtering of the list can be done with expressions for maximum flexibility.

                            Any thoughts about that?

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

                            @toggledbits That would do it for me, is the matchEntities() function already available in Expressions? I get no error but no matter what I do the Expression always returns an empty array.
                            I'd expect this to contain at least something:

                            matchEntities( { controller: 'vera', capability: 'humidity_sensor' } )
                            
                            1 Reply Last reply
                            0
                            • toggledbitsT Offline
                              toggledbitsT Offline
                              toggledbits
                              wrote on last edited by
                              #20

                              No, it's not yet available.

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

                              CrilleC tunnusT 2 Replies Last reply
                              0
                              • CrilleC Offline
                                CrilleC Offline
                                Crille
                                wrote on last edited by
                                #21

                                Ah, that explains a lot 🙂 I like the idea, it seems very flexible.

                                1 Reply Last reply
                                0
                                • toggledbitsT toggledbits

                                  No, it's not yet available.

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

                                  @toggledbits Thanks, the new matchEntities() is brilliant. Now we can have dynamic arrays of devices.

                                  toggledbitsT 1 Reply Last reply
                                  0
                                  • CrilleC Crille

                                    @toggledbits Thanks, the new matchEntities() is brilliant. Now we can have dynamic arrays of devices.

                                    toggledbitsT Offline
                                    toggledbitsT Offline
                                    toggledbits
                                    wrote on last edited by
                                    #23

                                    @crille said in Rule for devices battery level ?:

                                    Now we can have dynamic arrays of devices.

                                    Tell me about that...

                                    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

                                      @crille said in Rule for devices battery level ?:

                                      Now we can have dynamic arrays of devices.

                                      Tell me about that...

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

                                      @toggledbits Inspired by this topic I created a rule with similar expressions to monitor/notify x_ezlo_device.reachable for all my Ezlo devices. Instead of managing a static array, like the battery_device_list in this topic, the expression matchEntities( {capability: 'x_ezlo_device'} ) generates a list of devices that is dynamically updated if devices are added or removed from the controller.

                                      1 Reply Last reply
                                      1
                                      • toggledbitsT toggledbits

                                        No, it's not yet available.

                                        tunnusT Offline
                                        tunnusT Offline
                                        tunnus
                                        wrote on last edited by
                                        #25

                                        @toggledbits I'm testing this new function, but somehow it does not show all the devices I'm expecting it to show. See examples below

                                        Screenshot 2021-09-30 at 17.34.23.png

                                        Array is empty, although it should contain one device:

                                        Screenshot 2021-09-30 at 17.41.02.png

                                        Strange, as device 216 definitely has capability "x_vera_device"

                                        Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

                                          One of the issues I see in matchEntities() as it currently works is that it returns an array of entity objects with attribute values, but it does not update that array when any of the returned entities' attributes or other values changes. So it's certain, then, that the attributes will go stale in the result array.

                                          For the next build, I will change the definition of this function to return canonical entity IDs only, rather than entity objects, so you will have to use getEntity() in your each over the results, as you did with your test_array example, and this will ensure that you are always looking at the latest attributes. You can test this theory now by modifying your each for d_failure_list to use getEntity( id.canonical_id ).

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

                                          tunnusT 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

                                          • Gradually turn on lights.
                                            G
                                            gwp1
                                            0
                                            4
                                            132

                                          • Stop the MSR by an external switch on Hubitat.
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            1
                                            31

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            103

                                          • Reset attribute value of entity in event handler
                                            R
                                            RHCPNG
                                            0
                                            5
                                            202

                                          • Need help figuring out how to delay a reset on reaction
                                            G
                                            gwp1
                                            0
                                            22
                                            925

                                          • Way to search for rules (rule state) in other rules
                                            T
                                            tamorgen
                                            0
                                            3
                                            99

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            90

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            433

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

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

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

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            260
                                          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