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. Opening curtains with a motion sensor but only once?
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
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
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
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
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

Opening curtains with a motion sensor but only once?

Scheduled Pinned Locked Moved Multi-System Reactor
9 Posts 5 Posters 1.5k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #1

    Hi

    I've just put a motion sensor under my bed so when I get up in a morning it will open the curtains.

    However how do you make it so that action only happens once until the next morning?

    For example if I later in the day enter the bedroom again, I don't want this rule to be triggered again and its action run again etc.

    Thanks

    tunnusT A 2 Replies Last reply
    0
    • cw-kidC cw-kid

      Hi

      I've just put a motion sensor under my bed so when I get up in a morning it will open the curtains.

      However how do you make it so that action only happens once until the next morning?

      For example if I later in the day enter the bedroom again, I don't want this rule to be triggered again and its action run again etc.

      Thanks

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

      @cw-kid try latching

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

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

        Hi

        I've just put a motion sensor under my bed so when I get up in a morning it will open the curtains.

        However how do you make it so that action only happens once until the next morning?

        For example if I later in the day enter the bedroom again, I don't want this rule to be triggered again and its action run again etc.

        Thanks

        A Offline
        A Offline
        Alan_F
        wrote on last edited by
        #3

        @cw-kid I'm sure there are multiple ways to do this, and probably some better than what I'm thinking...

        Create an expression "g_curtains_open_today"

        Create a rule. At midnight every day set g_curtains_open_today to false

        Motion sensor rule: If motion sensor trips AND g_curtains_open_today is false then:

        -> Open curtains
        -> set g_curtains_open_today to true

        The next time the motion sensor trips before midnight the curtains will not open

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

          Great thanks I like your idea of using an expression / variable and that makes sense as a possible solution. I will give it a try.

          1 Reply Last reply
          0
          • tunnusT tunnus

            @cw-kid try latching

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

            @tunnus said in Opening curtains with a motion sensor but only once?:

            try latching

            I've never used latching before. I will read the user manual about that then also.

            Thanks.

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

              @tunnus said in Opening curtains with a motion sensor but only once?:

              try latching

              I've never used latching before. I will read the user manual about that then also.

              Thanks.

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

              @cw-kid Do read up, but make sure you get this important point:

              A latching condition must be paired with at least one other condition in an AND group. The latch is reset by the group going false. Since your latching condition will be latched true at some point (maybe), that means the other condition(s) going false determine when and how the latched condition is reset/unlatched.

              I'm curious to see what you come up. Latching is a concept that takes some thinking for undergrad electrical engineering students to apply well and correctly, and it's the same here. I can see a very simple two condition implementation for your stated rule, but I'm going to leave this as an exercise for you and the group for the moment.

              Other readers, no spoilers, please! If you can't wait, you're welcome to PM me your thoughts.

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

              wmarcolinW 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                @cw-kid Do read up, but make sure you get this important point:

                A latching condition must be paired with at least one other condition in an AND group. The latch is reset by the group going false. Since your latching condition will be latched true at some point (maybe), that means the other condition(s) going false determine when and how the latched condition is reset/unlatched.

                I'm curious to see what you come up. Latching is a concept that takes some thinking for undergrad electrical engineering students to apply well and correctly, and it's the same here. I can see a very simple two condition implementation for your stated rule, but I'm going to leave this as an exercise for you and the group for the moment.

                Other readers, no spoilers, please! If you can't wait, you're welcome to PM me your thoughts.

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

                @toggledbits

                624383a2-53bf-47dc-aac7-70f2d1f1d38a-image.png

                I have something similar, but with a pressure sensor on the bed (Amazon Thin Film Pressure Sensor Flex/Bend Sensor SF15-600), besides opening the curtain in the morning when I get up, also serves for another rule, if I'm not in bed and there is no movement in the room, turns off the air conditioning.

                1 Reply Last reply
                0
                • A Alan_F

                  @cw-kid I'm sure there are multiple ways to do this, and probably some better than what I'm thinking...

                  Create an expression "g_curtains_open_today"

                  Create a rule. At midnight every day set g_curtains_open_today to false

                  Motion sensor rule: If motion sensor trips AND g_curtains_open_today is false then:

                  -> Open curtains
                  -> set g_curtains_open_today to true

                  The next time the motion sensor trips before midnight the curtains will not open

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

                  @alan_f said in Opening curtains with a motion sensor but only once?:

                  Create an expression "g_curtains_open_today"
                  Create a rule. At midnight every day set g_curtains_open_today to false
                  Motion sensor rule: If motion sensor trips AND g_curtains_open_today is false then:
                  -> Open curtains
                  -> set g_curtains_open_today to true
                  The next time the motion sensor trips before midnight the curtains will not open

                  This works I have just set it up and tested it.

                  Ignore the additional optional extra conditions I added for Vera to be in Home Mode and for a master virtual switch called "Dark Mode" must be OFF.

                  a3b31021-90fd-473a-9632-b09b1f9ddd72-image.png ce957fb6-3384-4d13-9024-73429abdcdcb-image.png 9cca77f8-8d50-4be9-b441-2e8b7f031034-image.png

                  The other option of using Latching I am not so sure about.

                  "A latching condition must be paired with at least one other condition in an AND group. The latch is reset by the group going false. Since your latching condition will be latched true at some point (maybe), that means the other condition(s) going false determine when and how the latched condition is reset/unlatched."

                  What would be my one other Condition in the AND group I could use?

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

                    @alan_f said in Opening curtains with a motion sensor but only once?:

                    Create an expression "g_curtains_open_today"
                    Create a rule. At midnight every day set g_curtains_open_today to false
                    Motion sensor rule: If motion sensor trips AND g_curtains_open_today is false then:
                    -> Open curtains
                    -> set g_curtains_open_today to true
                    The next time the motion sensor trips before midnight the curtains will not open

                    This works I have just set it up and tested it.

                    Ignore the additional optional extra conditions I added for Vera to be in Home Mode and for a master virtual switch called "Dark Mode" must be OFF.

                    a3b31021-90fd-473a-9632-b09b1f9ddd72-image.png ce957fb6-3384-4d13-9024-73429abdcdcb-image.png 9cca77f8-8d50-4be9-b441-2e8b7f031034-image.png

                    The other option of using Latching I am not so sure about.

                    "A latching condition must be paired with at least one other condition in an AND group. The latch is reset by the group going false. Since your latching condition will be latched true at some point (maybe), that means the other condition(s) going false determine when and how the latched condition is reset/unlatched."

                    What would be my one other Condition in the AND group I could use?

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

                    @cw-kid said in Opening curtains with a motion sensor but only once?:

                    What would be my one other Condition in the AND group I could use?

                    Date/time...

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

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


                    Recent Topics

                    • DynamicGroupController and attributes
                      toggledbitsT
                      toggledbits
                      1
                      6
                      154

                    • Bail out of failed reaction?
                      T
                      tamorgen
                      0
                      3
                      50

                    • Arming Envisalink panel from MSR
                      T
                      tamorgen
                      0
                      7
                      265

                    • [Solved] DynamicGroupController updating members issue
                      CrilleC
                      Crille
                      0
                      5
                      183

                    • Reactor (Multi-System/Multi-Hub) Announcements
                      toggledbitsT
                      toggledbits
                      5
                      148
                      131.7k

                    • Upgrade Issues
                      T
                      tbully
                      0
                      9
                      290

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

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

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

                    • Logon screen timeout
                      G
                      gwp1
                      0
                      5
                      216

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

                    • Upgrade advice - upgrade from aarch64 to ARM64 image
                      toggledbitsT
                      toggledbits
                      0
                      4
                      236
                    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