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 ?
UI not loading after upgrading to 26318
tunnusT
Sorry for a hasty post, will update some details later, but the scenario is that I managed to type a wrong password for too many times and had the following users.yaml section: authtrack: max_attempts: 4 within_minutes: 180 # 180 minutes = 3 hrs block_expiration_minutes: 10080 # 7 days At this time I used build 26298. Then noticed there's a new build with a bypass blocking feature (and yes, it said it won't remove existing block). Anyway, went ahead and upgraded to 26318, but the problem now is that UI is not loading at all (page does not answer). This also means that I cannot use "http://reactor_host:port/diag/clear_authtrack?askauth" command to clear the block (or use any other source IP for login). Docker container stays up & running and does not exit. I'll try to dig up some logs, but anything that I could immediately try out (could I delete a particular file for example)? EDIT: some logs [latest-26318]2026-11-17T20:42:32.337Z <Rule:INFO> MSR startup (rule-lculfnhm in Miscellaneous) started [latest-26318]2026-11-17T20:42:32.343Z <httpapi:NOTICE> httpapi#1 HTTP server listening on :::8111 [latest-26318]2026-11-17T20:42:32.347Z <httpapi:INFO> httpapi#1 local docs found in /opt/reactor/docs/html; setting up static service [latest-26318]2026-11-17T20:42:32.354Z <app:NOTICE> Starting WSAPI... [latest-26318]2026-11-17T20:42:32.355Z <wsapi:NOTICE> wsapi: starting version 26298 protocol [latest-26318]2026-11-17T20:42:32.523Z <Engine:INFO> Engine#1 master timer tick, local time "17/11/2026 22:42:32" (TZ offset 120 mins from UTC) [latest-26318]2026-11-17T20:42:32.542Z <Engine:NOTICE> Starting reaction MSR startup<SET> (rule-lculfnhm:S) [latest-26318]2026-11-17T20:42:32.545Z <Notifier:null> Module Notifier v26186 [latest-26318]2026-11-17T20:42:32.545Z <Engine:INFO> MSR startup<SET> all actions completed. [latest-26318]2026-11-17T20:42:32.557Z <Rule:INFO> Rule#rule-lculfnhm reaction rule-lculfnhm:S completed [latest-26318]2026-11-17T20:42:32.558Z <default:null> Module NotifyTelegram v26177
Multi-System Reactor
[Resolved] Hubitat upgrade 2.5.3.123 may have broken login
3
Topic thumbnail image
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
Reactor Inspect - a small read-only helper panel for MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Reverse proxy & API ACL
tunnusT
I'm trying to allow anonymous access from a local network to /api/v1/log, but the problem now with the reverse proxy configuration is that this access is open via proxy to the internet. At least I wasn't able to configure ACL so that only an access from a local network would be permitted. reactor.yaml: baseurl: "http://192.168.1.12:8111" proxy_baseurl: "https://external.com:30000" trusted_proxy: "192.168.1.12" Local traffic would originate from 192.168.1.0/24 network. Synology is acting as a reverse proxy and hosting MSR as a docker container (which has its own network and IP 172.18.0.5). MSR build is latest-26298-fbb75fb8 users.yaml: - url: "/api/v1/log" method: "GET" source_ip: 172.18.0.0/24 allow: true Using the above ACL works, but it enables access via proxy also. If I use source_ip: 192.168.1.0/24, then it doesn't work either locally or remotely. So I'm kinda lost what should I use as source_ip in this case?
Multi-System Reactor
MFA
T
Topic thumbnail image
Multi-System Reactor
Grouped devices
G
I've seen many of you using Dynamic Group Controller. I'm using it myself for monitoring device battery levels. I've read and re-read the Dynamic Group Controller docs and still cannot come to an answer for my question so let me paint my scenario: I've migrated from EchoSpeaks in Hubitat ('cause borked and seemingly unmaintained) to Alexa Devices in Home Assistant ('cause not borked in 2026.11.0) to be able to send TTS to my Echo devices. In EchoSpeaks I could create groups. Sweet. In Alexa Devices I don't seem to be able to do so. As such, my thought was "wait - isn't there a way in MSR?" Is this an effective scenario that Dynamic Group Controller can be used for?
Multi-System Reactor
Login protections
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor Build 26284 stuck at Loading Reactor UI
T
Topic thumbnail image
Multi-System Reactor
MSR with reverse proxy
tunnusT
I'm trying to use MSR via reserve proxy in Synology DSM, but MSR page does not load https://<public ip>:30000/reactor/en-US/ At the same time logging page loads normally https://<public ip>:30000/api/v1/log I thought maybe authentication was messing it up, but there was no deny entries in the log, and also disabling authentication did not make any difference. For this use case VPN is not an option (that works, but as said not an option for this particular use case). Any ideas what could cause this? MSR build latest-26242-28d69aa8, Chrome browser
Multi-System Reactor
Missing attribute after upgrade
3
Topic thumbnail image
Multi-System Reactor
[MSR] Native fan capabilty
therealdbT
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable. I have a couple of them. ie, this is from ESPHome via HASS. x_hass.domain="fan" x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan" x_hass.floor_id=null x_hass.services=["fan","esphome"] x_hass.source="esphome" x_hass.state="off" x_hass_attr.friendly_name="Seashell Hood Ventilation Fan" x_hass_attr.percentage=50 x_hass_attr.percentage_step=25 x_hass_attr.preset_mode="" x_hass_attr.preset_modes=[] x_hass_attr.supported_features=49 Thanks.
Multi-System Reactor
[MSR] Rule do not fire
therealdbT
Topic thumbnail image
Multi-System Reactor
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
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
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor

Rule for devices battery level ?

Scheduled Pinned Locked Moved Multi-System Reactor
43 Posts 6 Posters 17.2k 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.
  • toggledbitsT toggledbits

    Can you show the entity detail for device 216 please?

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

    @toggledbits here you go:

    dimming.level=0
    dimming.step=null
    power_switch.state=false
    x_vera_device.configured=false
    x_vera_device.device_number=216
    x_vera_device.device_type="urn:schemas-upnp-org:device:DimmableLight:1"
    x_vera_device.failed=true
    x_vera_device.mapped_by="*;device_type=/urn:schemas-upnp-org:device:DimmableLight:/"
    x_vera_device.mapped_class="generic_dimmer"
    x_vera_device.parent_device=1
    x_vera_device.room_id="1"
    x_vera_energy.amps=null
    x_vera_energy.day_kwh=null
    x_vera_energy.kwh="6.7000"
    x_vera_energy.life_kwh=null
    x_vera_energy.month_kwh=null
    x_vera_energy.power_factor=null
    x_vera_energy.volts=null
    x_vera_energy.watts=""
    x_vera_energy.week_kwh=null
    x_vera_energy.year_kwh=null
    x_vera_svc_cd_jackson_com_DataMine1.errorStatus="true"
    x_vera_svc_micasaverde_com_EnergyMetering1.ActualUsage="1"
    x_vera_svc_micasaverde_com_EnergyMetering1.KWH="6.7000"
    x_vera_svc_micasaverde_com_EnergyMetering1.KWHReading="1597268716"
    x_vera_svc_micasaverde_com_EnergyMetering1.Log="0,0,0,1633073400,1"
    x_vera_svc_micasaverde_com_EnergyMetering1.Watts=""
    x_vera_svc_micasaverde_com_HaDevice1.AutoConfigure="0"
    x_vera_svc_micasaverde_com_HaDevice1.CommFailure="1"
    x_vera_svc_micasaverde_com_HaDevice1.CommFailureAlarm="1628783888,1"
    x_vera_svc_micasaverde_com_HaDevice1.CommFailureTime="1628780288"
    x_vera_svc_micasaverde_com_HaDevice1.Configured="0"
    x_vera_svc_micasaverde_com_HaDevice1.FirstConfigured="1526668133"
    x_vera_svc_micasaverde_com_HaDevice1.LastTimeCheck="1605041801"
    x_vera_svc_micasaverde_com_HaDevice1.LastTimeOffset="2"
    x_vera_svc_micasaverde_com_HaDevice1.LastUpdate="0"
    x_vera_svc_micasaverde_com_HaDevice1.ModeSetting="1:;2:;3:;4:"
    x_vera_svc_micasaverde_com_HaDevice1.PollRatings="0.20"
    x_vera_svc_micasaverde_com_ZWaveDevice1.AgiInfo="X"
    x_vera_svc_micasaverde_com_ZWaveDevice1.AlarmType="0x4,0x8,"
    x_vera_svc_micasaverde_com_ZWaveDevice1.AlarmVersion="0,2"
    x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationGroups="1"
    x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationNum="4"
    x_vera_svc_micasaverde_com_ZWaveDevice1.Capabilities="211,156,1,4,17,1,L,R,B,RS,|37S,38S:3,39S,43S,44S,50S:3,89S,90B,94,112S,113S:4,114,115S,122S,129S,133S,134,152,"
    x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredAssoc=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredVariable="80-Status notification type,1d,3,90- Enable or Disable energy reporting (0-1),1d,1,91-Minimum change in wattage for a REPORT (0-60000),2d,5,92-Minimum change in wattage percent for a REPORT,1d,5,120-Configure external switch mode for S1(0-3),1d,1,125,1d,1,128-Current working mode (0-2),1d,1,129-Dimming principle (0-2),1d,1,130-Dimmer load type connected(0-3),1d,1,131-Minimum brightness level,1d,20,132-Maximum brightness level,1d,90,249,1d,0"
    x_vera_svc_micasaverde_com_ZWaveDevice1.FirmwareInfo="134,111,41841"
    x_vera_svc_micasaverde_com_ZWaveDevice1.LastArr=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.LastNnu=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.LastReset="1526668110"
    x_vera_svc_micasaverde_com_ZWaveDevice1.LastRouteUpdate="1597229741"
    x_vera_svc_micasaverde_com_ZWaveDevice1.ManufacturerInfo="134,3,111"
    x_vera_svc_micasaverde_com_ZWaveDevice1.MeterScale="5"
    x_vera_svc_micasaverde_com_ZWaveDevice1.MeterType="1"
    x_vera_svc_micasaverde_com_ZWaveDevice1.NodeInfo="25S,26S,27S,2bS,2cS,32S,59S,5aB,5e,70S,71S,72,73S,7aS,81S,85S,86,98,"
    x_vera_svc_micasaverde_com_ZWaveDevice1.PlusInfo="1,5,0,6,0,6,0"
    x_vera_svc_micasaverde_com_ZWaveDevice1.PollNoReply="476"
    x_vera_svc_micasaverde_com_ZWaveDevice1.PollOk="37823"
    x_vera_svc_micasaverde_com_ZWaveDevice1.PollSettings="120"
    x_vera_svc_micasaverde_com_ZWaveDevice1.PollTxFail="1"
    x_vera_svc_micasaverde_com_ZWaveDevice1.SecurityFailed="0"
    x_vera_svc_micasaverde_com_ZWaveDevice1.SubscribedAlarms=",0x4,0x8,"
    x_vera_svc_micasaverde_com_ZWaveDevice1.SwitchMlSettings="2,0"
    x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesGet="80,3,90,1,91,5,92,5,120,1,125,1,128,1,129,1,130,1,131,20,132,90,249,0,"
    x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesSet="80-Status notification type,1d,3,90- Enable or Disable energy reporting (0-1),1d,1,91-Minimum change in wattage for a REPORT (0-60000),2d,5,92-Minimum change in wattage percent for a REPORT,1d,5,120-Configure external switch mode for S1(0-3),1d,1,125,1d,1,128-Current working mode (0-2),1d,1,129-Dimming principle (0-2),1d,1,130-Dimmer load type connected(0-3),1d,1,131-Minimum brightness level,1d,20,132-Maximum brightness level,1d,90,249,1d,0"
    x_vera_svc_micasaverde_com_ZWaveDevice1.VersionInfo="3,4,54,2,0"
    x_vera_svc_micasaverde_com_ZWaveNetwork1.ConsecutivePollFails="0"
    x_vera_svc_micasaverde_com_ZWaveNetwork1.LastPollSuccess="1597268720"
    x_vera_svc_upnp_org_Dimming1.LoadLevelLast="100"
    x_vera_svc_upnp_org_Dimming1.LoadLevelStatus="0"
    x_vera_svc_upnp_org_Dimming1.LoadLevelTarget="100"
    x_vera_svc_upnp_org_Dimming1.TurnOnBeforeDim="0"
    x_vera_svc_upnp_org_SwitchPower1.Status="0"
    zwave_device.capabilities="211,156,1,4,17,1,L,R,B,RS,|37S,38S:3,39S,43S,44S,50S:3,89S,90B,94,112S,113S:4,114,115S,122S,129S,133S,134,152,"
    zwave_device.failed=true
    zwave_device.manufacturer_info="134,3,111"
    zwave_device.node_id=53
    zwave_device.version_info="3,4,54,2,0"
    Capabilities: dimming, power_switch, toggle, x_vera_device, x_vera_energy, x_vera_svc_cd_jackson_com_DataMine1, x_vera_svc_micasaverde_com_Color1, x_vera_svc_micasaverde_com_EnergyMetering1, x_vera_svc_micasaverde_com_HaDevice1, x_vera_svc_micasaverde_com_ZWaveDevice1, x_vera_svc_micasaverde_com_ZWaveNetwork1, x_vera_svc_upnp_org_Dimming1, x_vera_svc_upnp_org_SwitchPower1, zwave_device
    Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, toggle.toggle, x_vera_device.set_variable, x_vera_energy.resetkwh, x_vera_svc_micasaverde_com_Color1.SetColor, x_vera_svc_micasaverde_com_Color1.SetColorRGB, x_vera_svc_micasaverde_com_Color1.SetColorTemp, x_vera_svc_micasaverde_com_EnergyMetering1.ResetKWH, x_vera_svc_micasaverde_com_HaDevice1.AllowPairing, x_vera_svc_micasaverde_com_HaDevice1.Poll, x_vera_svc_micasaverde_com_HaDevice1.Reconfigure, x_vera_svc_micasaverde_com_HaDevice1.Remove, x_vera_svc_micasaverde_com_HaDevice1.SetPollFrequency, x_vera_svc_micasaverde_com_HaDevice1.StressTest, x_vera_svc_micasaverde_com_HaDevice1.ToggleState, x_vera_svc_micasaverde_com_ZWaveNetwork1.AddNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.BackupDongle, x_vera_svc_micasaverde_com_ZWaveNetwork1.DownloadNetwork, x_vera_svc_micasaverde_com_ZWaveNetwork1.HealNetwork, x_vera_svc_micasaverde_com_ZWaveNetwork1.PollAllNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.PutByte, x_vera_svc_micasaverde_com_ZWaveNetwork1.ReconfigureAllNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.RemoveNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.SendData, x_vera_svc_micasaverde_com_ZWaveNetwork1.SetPolling, x_vera_svc_micasaverde_com_ZWaveNetwork1.SimulateIncomingData, x_vera_svc_micasaverde_com_ZWaveNetwork1.UpdateNeighbors, x_vera_svc_micasaverde_com_ZWaveNetwork1.UpdateNetwork, x_vera_svc_upnp_org_Dimming1.PauseRamp, x_vera_svc_upnp_org_Dimming1.ResumeRamp, x_vera_svc_upnp_org_Dimming1.SetLoadLevelTarget, x_vera_svc_upnp_org_Dimming1.SetOnEffect, x_vera_svc_upnp_org_Dimming1.SetOnEffectLevel, x_vera_svc_upnp_org_Dimming1.SetRampRate, x_vera_svc_upnp_org_Dimming1.SetStepDelta, x_vera_svc_upnp_org_Dimming1.StartRampDown, x_vera_svc_upnp_org_Dimming1.StartRampToLevel, x_vera_svc_upnp_org_Dimming1.StartRampUp, x_vera_svc_upnp_org_Dimming1.StepDown, x_vera_svc_upnp_org_Dimming1.StepUp, x_vera_svc_upnp_org_Dimming1.StopRamp, x_vera_svc_upnp_org_SwitchPower1.SetTarget, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config
    

    Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

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

      Perfect! Thank you. I think I see what's going on. New build coming later today...

      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
      1
      • toggledbitsT toggledbits

        Perfect! Thank you. I think I see what's going on. New build coming later today...

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

        @toggledbits thanks Patrick! Works nicely

        Screenshot 2021-10-05 at 16.40.49.png

        Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Zigbee2MQTT & ZWA-2

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

          How do I change my rule for devices with low batteries to use a dynamic array instead of the static manual array I am using currently ?

          battery_device_list:

          102246ea-adb8-40f8-a37b-e3283e6b6bf8-image.png

          Thanks

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

            How do I change my rule for devices with low batteries to use a dynamic array instead of the static manual array I am using currently ?

            battery_device_list:

            102246ea-adb8-40f8-a37b-e3283e6b6bf8-image.png

            Thanks

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

            @cw-kid
            45e80520-3d14-480f-bd11-c7de871c7719-image.png

            The first expression produces an array that includes all battery powered entities across all controllers.

            The second restricts the results to a specific controller.

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

              Ian thank you. I thought it would be the battery_power capability, but I didn't know how to write that in an expression. I will try it now.

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

                I think this may work then, I just need to edit my existing rule:

                60aa1069-d8de-4868-9ae0-213965417840-image.png

                matchEntities ({controller: 'vera', capability: ['battery_power']})
                

                EDITED rule:

                1355a3a7-ff45-438a-8e89-c06bb7071d96-image.png

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

                  I think this may work then, I just need to edit my existing rule:

                  60aa1069-d8de-4868-9ae0-213965417840-image.png

                  matchEntities ({controller: 'vera', capability: ['battery_power']})
                  

                  EDITED rule:

                  1355a3a7-ff45-438a-8e89-c06bb7071d96-image.png

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

                  @cw-kid You could also do all that in one expression if you prefer and are not using the other ones for anything else.

                  join( 
                    each id in matchEntities( { controller: 'vera', capability: 'battery_power' } ): do
                      device=getEntity( id ), 
                      device.attributes.battery_power.level > 0.1 ? null : device.name + " at " + device.attributes.battery_power.level * 100 + " percent"
                    done, ", " )
                  
                  cw-kidC 1 Reply Last reply
                  1
                  • CrilleC Crille

                    @cw-kid You could also do all that in one expression if you prefer and are not using the other ones for anything else.

                    join( 
                      each id in matchEntities( { controller: 'vera', capability: 'battery_power' } ): do
                        device=getEntity( id ), 
                        device.attributes.battery_power.level > 0.1 ? null : device.name + " at " + device.attributes.battery_power.level * 100 + " percent"
                      done, ", " )
                    
                    cw-kidC Offline
                    cw-kidC Offline
                    cw-kid
                    wrote on last edited by
                    #38

                    @crille

                    Great thank you, I will consider that.

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

                      Just a point here: why limit matchEntities() to one controller? Would you not perhaps want an alert for a device on any controller that has a low battery level?

                      Also, don't forget about the format() function, which is meant for things like this...

                          device.attributes.battery_power.level > 0.1 ? null : format( "{} at {:.1%}", device.name, device.attributes.battery_power.level )
                      

                      Oh, and in my home, any battery-operated device would be long dead if it was reporting 10% (0.1). Most of mine seem to start to malfunction below 50%.

                      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
                      1
                      • toggledbitsT toggledbits

                        Just a point here: why limit matchEntities() to one controller? Would you not perhaps want an alert for a device on any controller that has a low battery level?

                        Also, don't forget about the format() function, which is meant for things like this...

                            device.attributes.battery_power.level > 0.1 ? null : format( "{} at {:.1%}", device.name, device.attributes.battery_power.level )
                        

                        Oh, and in my home, any battery-operated device would be long dead if it was reporting 10% (0.1). Most of mine seem to start to malfunction below 50%.

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

                        @toggledbits I'm trying to understand the pros and cons of using this vs the new DynamicGroupController, could you give a short summation?

                        wmarcolinW 1 Reply Last reply
                        0
                        • CrilleC Crille

                          @toggledbits I'm trying to understand the pros and cons of using this vs the new DynamicGroupController, could you give a short summation?

                          wmarcolinW Offline
                          wmarcolinW Offline
                          wmarcolin
                          wrote on last edited by
                          #41

                          Hi @crille !

                          In this post we are having this discussion about Dynamic, I am having a hard time getting it to work, but it will be very good, the concept is great and this will make it much easier.

                          https://smarthome.community/topic/793/multidimensional-array/17?_=1638031443562&loggedin=true

                          CrilleC 1 Reply Last reply
                          0
                          • wmarcolinW wmarcolin

                            Hi @crille !

                            In this post we are having this discussion about Dynamic, I am having a hard time getting it to work, but it will be very good, the concept is great and this will make it much easier.

                            https://smarthome.community/topic/793/multidimensional-array/17?_=1638031443562&loggedin=true

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

                            @wmarcolin Yes, but the goal seems to be the same so what's the pros of doing it in the DynamicGroupController? More efficient, more dynamic, less complex etc, than a global expression like the one above?
                            I'm all up for new improved ways of doing things just need an explanation of why 🙂

                            wmarcolinW 1 Reply Last reply
                            0
                            • CrilleC Crille

                              @wmarcolin Yes, but the goal seems to be the same so what's the pros of doing it in the DynamicGroupController? More efficient, more dynamic, less complex etc, than a global expression like the one above?
                              I'm all up for new improved ways of doing things just need an explanation of why 🙂

                              wmarcolinW Offline
                              wmarcolinW Offline
                              wmarcolin
                              wrote on last edited by
                              #43

                              @crille

                              In my opinion, everything you put in: more efficient, more dynamic, less complex. Below is a screenshot of how I do it today, and it would be replaced only by the format expression already directly inside a message as per telegram.

                              77669a6a-5057-4bfc-9370-a32da5a597b3-image.png

                              I will also use it to easily know all the devices that will be tripped in the house, see the other post for what I am adding after the battery. Besides this, unifying devices that for example are triggered by a contact or movement and have different expressions, will help unify and set up the alarm trigger management.

                              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

                              • UI not loading after upgrading to 26318
                                tunnusT
                                tunnus
                                0
                                1
                                13

                              • [Resolved] Hubitat upgrade 2.5.3.123 may have broken login
                                toggledbitsT
                                toggledbits
                                0
                                8
                                214

                              • Reactor (Multi-System/Multi-Hub) Announcements
                                toggledbitsT
                                toggledbits
                                5
                                153
                                162.3k

                              • Reactor Inspect - a small read-only helper panel for MSR
                                G
                                gwp1
                                2
                                8
                                578

                              • Reverse proxy & API ACL
                                tunnusT
                                tunnus
                                0
                                9
                                472

                              • MFA
                                T
                                tamorgen
                                0
                                28
                                1.3k

                              • Grouped devices
                                G
                                gwp1
                                0
                                3
                                182

                              • Login protections
                                toggledbitsT
                                toggledbits
                                0
                                2
                                228

                              • Reactor Build 26284 stuck at Loading Reactor UI
                                T
                                tamorgen
                                0
                                16
                                1.8k

                              • MSR with reverse proxy
                                tunnusT
                                tunnus
                                0
                                12
                                885

                              • Missing attribute after upgrade
                                3
                                3rdStng
                                0
                                3
                                684

                              • Use of Google Gemini as an MSR and Hubitat configuration aid
                                therealdbT
                                therealdb
                                0
                                2
                                317
                              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