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 ?
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor

Rule for devices battery level ?

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

      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 ).

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

      @toggledbits did what you suggested, but situation didn't really change, array is still empty:

      Screenshot 2021-09-30 at 19.25.05.png

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

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

        Can you show the entity detail for device 216 please?

        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
        • tunnusT tunnus

          @toggledbits did what you suggested, but situation didn't really change, array is still empty:

          Screenshot 2021-09-30 at 19.25.05.png

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

          @tunnus I had some issues as well. I got an empty array and when tried getEntity() I got some "Type Error". Was sure I was doing something wrong but I restarted Reactor and copied the same expression to a new one and suddenly it worked.
          @toggledbits I also noticed the array isn't updated when entity changed so I pulse the trigger every minute to update it. Will change to getEntity() for next update.

          1 Reply Last reply
          0
          • 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, Hubitat C-8, 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, Hubitat C-8, 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

                                      • Copying a global reaction
                                        toggledbitsT
                                        toggledbits
                                        0
                                        3
                                        78

                                      • [HowTo] Using HABridge with Reactor
                                        CatmanV2C
                                        CatmanV2
                                        0
                                        9
                                        380

                                      • [Reactor] Bug when sending MQTT boolean payloads
                                        toggledbitsT
                                        toggledbits
                                        0
                                        4
                                        130

                                      • Genuinely impressed with Zigbee and HA / Reactor
                                        therealdbT
                                        therealdb
                                        1
                                        8
                                        297

                                      • Difficulty defining repeating annual period
                                        G
                                        gwp1
                                        0
                                        5
                                        97

                                      • Need help with sequence
                                        therealdbT
                                        therealdb
                                        0
                                        3
                                        61

                                      • Possible feature request?
                                        therealdbT
                                        therealdb
                                        0
                                        5
                                        161

                                      • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
                                        CatmanV2C
                                        CatmanV2
                                        0
                                        11
                                        337

                                      • Time series documentation
                                        tunnusT
                                        tunnus
                                        0
                                        11
                                        389

                                      • MQTT templates for ZIgbee scene controller, or a better way?
                                        CatmanV2C
                                        CatmanV2
                                        0
                                        3
                                        156

                                      • Reset a delay
                                        CatmanV2C
                                        CatmanV2
                                        0
                                        8
                                        218
                                      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