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. Contact Sensor Opened > 1 minute ago how ?
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
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
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor

Contact Sensor Opened > 1 minute ago how ?

Scheduled Pinned Locked Moved Multi-System Reactor
10 Posts 3 Posters 820 Views 2 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'm stuck migrating one of my PLEG conditions.

    tFrontDoorOpened;NOW>1:00

    Which means the trigger "Front Door Opened" happened more than 1 minute ago.

    How do I do this in MSR ? An expression I assume ?

    I want to use it as part of a Constraint.

    Any help please.

    Thanks.

    1 Reply Last reply
    0
    • ElcidE Offline
      ElcidE Offline
      Elcid
      wrote on last edited by
      #2

      If you use sustain for 60 seconds, then the sensor would need to be tripped for a minute before going true.

      cw-kidC 1 Reply Last reply
      0
      • ElcidE Elcid

        If you use sustain for 60 seconds, then the sensor would need to be tripped for a minute before going true.

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

        @elcid

        I'm not sure that will work for what I am trying to setup.

        In fact I don't think I can even replicate the set of conditions I had setup in PLEG for this same rule.

        Let me back up and start again, as I am sure there will be a better way of doing this.

        Doorbell Camera Motion detected is the trigger for this rule.

        The actions "Set Reaction" is to do some TTS and bring up the camera feed on some tablets / TVs etc.

        The conditions "Constraints" I only want this rule to run its actions, If the front door hasn't been recently opened or closed for that matter.

        e.g. when I come back in to the house and open / close the door to get in, I don't want this rule to run.

        But if I am already in the house and its someone else outside mooching about near the doorbell cam, then I do want the rule to run its actions.

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

          @elcid

          I'm not sure that will work for what I am trying to setup.

          In fact I don't think I can even replicate the set of conditions I had setup in PLEG for this same rule.

          Let me back up and start again, as I am sure there will be a better way of doing this.

          Doorbell Camera Motion detected is the trigger for this rule.

          The actions "Set Reaction" is to do some TTS and bring up the camera feed on some tablets / TVs etc.

          The conditions "Constraints" I only want this rule to run its actions, If the front door hasn't been recently opened or closed for that matter.

          e.g. when I come back in to the house and open / close the door to get in, I don't want this rule to run.

          But if I am already in the house and its someone else outside mooching about near the doorbell cam, then I do want the rule to run its actions.

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

          @cw-kid Try this:

          60049cbf-261c-47aa-8bc5-6f53a96b2be7-image.png

          Ignore my device names. They should be at least close enough to express the relationships.

          The trigger is the motion sensor. Easy enough.

          The constraints have been set to NOT AND, which inverts the output of its logic. The only condition in the constraints is a check to see if the door sensor has changed state, and it delays reset for 60 seconds. When the door changes state to either open or closed, the changes operator will start the 60-second clock and be true that entire period, which means the Constraints will be false (because of the not). When the time expires, the condition will go false, which means the Constraint group is then true, and reactions can run.

          In English: run the reactions when the motions sensor trips and the door hasn't changed state in the last 60 seconds.

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

          cw-kidC 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            @cw-kid Try this:

            60049cbf-261c-47aa-8bc5-6f53a96b2be7-image.png

            Ignore my device names. They should be at least close enough to express the relationships.

            The trigger is the motion sensor. Easy enough.

            The constraints have been set to NOT AND, which inverts the output of its logic. The only condition in the constraints is a check to see if the door sensor has changed state, and it delays reset for 60 seconds. When the door changes state to either open or closed, the changes operator will start the 60-second clock and be true that entire period, which means the Constraints will be false (because of the not). When the time expires, the condition will go false, which means the Constraint group is then true, and reactions can run.

            In English: run the reactions when the motions sensor trips and the door hasn't changed state in the last 60 seconds.

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

            @toggledbits said in Contact Sensor Opened > 1 minute ago how ?:

            In English: run the reactions when the motions sensor trips and the door hasn't changed state in the last 60 seconds.

            Yes that's what I want.

            I will give it a try.

            Thank you.

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

              No worries. FYI, watch out for a small UI bug (fixing, of course): if you edit an existing condition with the changes operator in it, it will put "null" in the operands where they were previously blank before, and when you save that, the condition will stop working. Will fix for today's build, but be on the lookout. Just blank those fields back out before saving. You don't care what the change is (open to close or close to open isn't relevant -- it's either).

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

              cw-kidC 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                No worries. FYI, watch out for a small UI bug (fixing, of course): if you edit an existing condition with the changes operator in it, it will put "null" in the operands where they were previously blank before, and when you save that, the condition will stop working. Will fix for today's build, but be on the lookout. Just blank those fields back out before saving. You don't care what the change is (open to close or close to open isn't relevant -- it's either).

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

                @toggledbits

                OK this is what I've got. I also added a check for a virtual switch in the constraints, hope that works.

                I haven't tested anything yet.

                af63b444-bc01-49a7-8f82-0b9ab1cdceda-image.png

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

                  You don't have the delay reset on, it appears (the three dots would appear yellow if you did).

                  And you're bringing in a group and another device, so that changes the logic. You didn't mention that before, so you need to work it into the logic correctly given that the entire Constraints group is now inverted (false means true and true means false). Have you accounted for that in the test of the switch state? And... why wrapped in a group? Are you going to add more conditions there?

                  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
                  • cw-kidC Offline
                    cw-kidC Offline
                    cw-kid
                    wrote on last edited by
                    #9

                    I've changed the constraints to this:

                    82240050-fbb2-46b0-ac63-5d3f27950ec4-image.png

                    8518f9b9-d74a-4c91-bd14-c0bb3876b104-image.png

                    I think this is working. If in Vera I trip the front door opened then closed and then trip the doorbell camera motion sensor, the rules reaction is not run as expected.

                    If I wait over the 60 seconds and trip the doorbell camera motion sensor again, then the rules reaction does run as expected.

                    I need to test it actually approaching the front door from outside and really opening / closing it, to then hear if it does the TTS announcement or not, that is in the reaction. I shouldn't hear the TTS if I have just changed the doors state etc.

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

                      Another thing that's been annoying, is when my garden lights via a schedule turn on or off in the back garden, the Hikvision IP camera triggers motion being detected as a result.

                      I could maybe use this method to stop that happening and stop MSR running the actions "Set Reaction", by checking that the state of the lights hasn't changed within the last X seconds.

                      Seems to be working, checking if the patio door has changed state in the last 60 seconds OR if the Festoon Lights in the garden have changed state in the last 10 seconds.

                      89079f2a-927a-48cc-9078-dc2b5553a109-image.png

                      1 Reply Last reply
                      0
                      • toggledbitsT toggledbits locked this topic on
                      • cw-kidC cw-kid referenced this topic on
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      Recent Topics

                      • Gradually turn on lights.
                        toggledbitsT
                        toggledbits
                        0
                        2
                        36

                      • Error After Upgrade
                        G
                        gwp1
                        0
                        4
                        44

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

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

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

                      • Links to MSR from HA
                        Tom_DT
                        Tom_D
                        0
                        1
                        59

                      • Set Reaction > Script Action
                        wmarcolinW
                        wmarcolin
                        0
                        11
                        349

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

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

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

                      • Advice reqeusted to migrate MSR from Bare Metal to Container
                        T
                        tamorgen
                        0
                        5
                        212

                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        122
                        48.7k
                      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