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

Opening curtains with a motion sensor but only once?

Scheduled Pinned Locked Moved Multi-System Reactor
9 Posts 5 Posters 452 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, Hubitat C-8, Zigbee2MQTT

      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

                    • Gradually turn on lights.
                      G
                      gwp1
                      0
                      4
                      141

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

                    • Error After Upgrade
                      G
                      gwp1
                      0
                      4
                      105

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

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

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

                    • Links to MSR from HA
                      Tom_DT
                      Tom_D
                      0
                      1
                      91

                    • Set Reaction > Script Action
                      wmarcolinW
                      wmarcolin
                      0
                      11
                      437

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

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

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

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