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 ?
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
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
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
[Solved] build 26150 - engine not starting
G
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline. The log looks like it ends with 26143. [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Multi-System Reactor
http request action & digest auth
tunnusT
I’m using the HTTP Request action in MSR and need to authenticate against an endpoint that uses HTTP Digest authentication. Now that endpoint was changed to use SHA-256 in digest auth, so I would like to know if MSR supports it, or is it limited to MD5-based digest auth?
Multi-System Reactor
Cloning actions in reactions does not work
tunnusT
With build 26140 (on Docker) I'm not able to clone any actions in reactions. Using Chrome if it has any relevance.
Multi-System Reactor
Has ping command been removed?
tunnusT
Topic thumbnail image
Multi-System Reactor

Rule for devices battery level ?

Scheduled Pinned Locked Moved Multi-System Reactor
43 Posts 6 Posters 13.9k 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

                              • Arming Envisalink panel from MSR
                                T
                                tamorgen
                                0
                                4
                                8

                              • Upgrade Issues
                                T
                                tbully
                                0
                                9
                                126

                              • [SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
                                toggledbitsT
                                toggledbits
                                0
                                10
                                96

                              • [SOLVED] Question regarding "in" vs "contains" vs contents of the string
                                G
                                gwp1
                                0
                                5
                                44

                              • Reactor (Multi-System/Multi-Hub) Announcements
                                toggledbitsT
                                toggledbits
                                5
                                147
                                127.5k

                              • openLuup console disappeared - 500 - Internal Server Error
                                A
                                a-lurker
                                0
                                2
                                150

                              • Logon screen timeout
                                G
                                gwp1
                                0
                                5
                                175

                              • [MSR] Copy&past of actions and/or drag&drop between set/reset
                                toggledbitsT
                                toggledbits
                                0
                                9
                                325

                              • Upgrade advice - upgrade from aarch64 to ARM64 image
                                toggledbitsT
                                toggledbits
                                0
                                4
                                189

                              • Alexa for MSR, any interest?
                                CatmanV2C
                                CatmanV2
                                2
                                4
                                323

                              • Ezlo Paid Subscription for Vera Cloud Services
                                therealdbT
                                therealdb
                                4
                                2
                                456
                              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