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. Schlage Lock - Alert when PIN Entered
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

Schlage Lock - Alert when PIN Entered

Scheduled Pinned Locked Moved Multi-System Reactor
17 Posts 5 Posters 1.4k 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.
  • therealdbT Offline
    therealdbT Offline
    therealdb
    wrote on last edited by
    #4

    I have the very same problem with scene controllers. In a case, writing 0 to the variable is enough. In another one, 0 will stop any further update to the variable until I restart the luup engine. In this case the only workaround I found was to monitor the variable via luup code and write a new variable (ie last scene time) that I’ll monitor in MSR.

    --
    On a mission to automate everything.

    My MS Reactor contrib
    My Luup Plug-ins

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

      @tbully posting guidelines (here), please. You need to say what platform and architecture you are running on and what versions of everything.

      I have an experimental hack for all of the "sl" variables in VeraController that you can try out. I don't want to over-engineer a solution that only applies to Vera because it's a dead-end, but I think the quick-and-dirty approach may do what is needed more easily than the writing variables approach. Once I know what platform you are on, I will push a build for just that platform with the hack in it and you can try it.

      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
      • T Offline
        T Offline
        tbully
        wrote on last edited by
        #6

        Reactor: stable-22136-edaa0ce7
        Vera: 1.7.5187 (7.31)

        HomeAssistant

        • Core 2022.5.3
        • OS 7.6

        Agree that Vera is a dead end and extra energy shouldn't be expended. I have a HomeAssistant ZWave network started and have considered moving the lock over. The one thing keeping me from that is my lack of creativity as it related to Dashboards. The wife still prefers Vera's app when needing to control devices. (I have over 100 ZWave devices - many get manually controlled from time to time) So this migration will be slow and thoughtful. I figured I'd get Reactor / Automation / Scene logic over first.

        Thanks and sorry for not including platform / environment info. I'm used to conversing on Vera's boards for the past 10+ years where everyone is generally on the same version / platform.

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

          Bare metal or docker?

          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
          • T Offline
            T Offline
            tbully
            wrote on last edited by tbully
            #8

            Bare metal. Running in Ubuntu as a VM in VirtualBox.

            toggledbitsT 1 Reply Last reply
            0
            • T tbully

              Bare metal. Running in Ubuntu as a VM in VirtualBox.

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

              @tbully OK. Build (latest) 22144 is up on the download server.

              For each of the sl_ state variables on Vera, this version of VeraController adds an attribute of the same name with _updated appended. This is a timestamp for when the last state variable update was received for that variable. You can use this extra attribute in a changes condition pair in an AND group with the test for value on the sl_ variable.

              dfec2d2c-04d4-4d25-9c7c-c517b1f66010-image.png

              This is experimental. You are providing, in part, the test/validation for this experiment.

              Background (for documentation): the sl_ state variables on Vera are special variables that behave differently from Vera/Luup's regular variables. Normally, Luup does not send events when a state variable is written with the same value is already has. This behavior is problematic for locks and scene controllers because when the same lock code is used, or the same button is pressed, sequentially, the second (and any subsequent) uses would not cause an event. So Luup has a hack whereby any variable prefixed sl_ sends events no matter what the value being written. A further complication has been that Vera/Luup also does not have stable, persistent timestamps: every time Luup restarts, all state variable timestamps are updated to the restart time. This has made it much more difficult to detect state variable changes and differentiate actual changes from Luup restarts with no change. Recent modifications to Reactor have created the opportunity for this new hack/experiment, wherein VeraController need not rely on Vera/Luup's timestamps, rather keeping its own.

              Other hubs handle these events much differently, and IMO in a much more thoughtful and better-engineered way, so spending a ton of time engineering a formal solution that works well for those platforms while addressing the foibles of Luup seems a bit of a fool's errand, and Vera systems and Luup are now effectively EOL (timing uncertain). For platforms other than Vera, the Reactor-defined services can be used to successfully handle lock codes and button presses; for VeraController users, use of the x_svc extended attributes and this _updated addition/hack are the way to go.

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

              T 1 Reply Last reply
              1
              • toggledbitsT toggledbits

                @tbully OK. Build (latest) 22144 is up on the download server.

                For each of the sl_ state variables on Vera, this version of VeraController adds an attribute of the same name with _updated appended. This is a timestamp for when the last state variable update was received for that variable. You can use this extra attribute in a changes condition pair in an AND group with the test for value on the sl_ variable.

                dfec2d2c-04d4-4d25-9c7c-c517b1f66010-image.png

                This is experimental. You are providing, in part, the test/validation for this experiment.

                Background (for documentation): the sl_ state variables on Vera are special variables that behave differently from Vera/Luup's regular variables. Normally, Luup does not send events when a state variable is written with the same value is already has. This behavior is problematic for locks and scene controllers because when the same lock code is used, or the same button is pressed, sequentially, the second (and any subsequent) uses would not cause an event. So Luup has a hack whereby any variable prefixed sl_ sends events no matter what the value being written. A further complication has been that Vera/Luup also does not have stable, persistent timestamps: every time Luup restarts, all state variable timestamps are updated to the restart time. This has made it much more difficult to detect state variable changes and differentiate actual changes from Luup restarts with no change. Recent modifications to Reactor have created the opportunity for this new hack/experiment, wherein VeraController need not rely on Vera/Luup's timestamps, rather keeping its own.

                Other hubs handle these events much differently, and IMO in a much more thoughtful and better-engineered way, so spending a ton of time engineering a formal solution that works well for those platforms while addressing the foibles of Luup seems a bit of a fool's errand, and Vera systems and Luup are now effectively EOL (timing uncertain). For platforms other than Vera, the Reactor-defined services can be used to successfully handle lock codes and button presses; for VeraController users, use of the x_svc extended attributes and this _updated addition/hack are the way to go.

                T Offline
                T Offline
                tbully
                wrote on last edited by
                #10

                Amazingly quick turnaround and totally unnecessary. Thanks for that! This logic is sound.

                I updated to 22144 and set the new Trigger (and removed the old set logic). I'm still not seeing either variable get updated.

                I don't see anything interesting in the logs. It does see the door unlock and various rules get evaluated on that event. Is there any logging I can turn up to see more?

                7bb34576-c6c4-4acb-8e2f-9e8d3ad2e4e7-image.png

                MikeReadingtonM 1 Reply Last reply
                0
                • T tbully

                  Amazingly quick turnaround and totally unnecessary. Thanks for that! This logic is sound.

                  I updated to 22144 and set the new Trigger (and removed the old set logic). I'm still not seeing either variable get updated.

                  I don't see anything interesting in the logs. It does see the door unlock and various rules get evaluated on that event. Is there any logging I can turn up to see more?

                  7bb34576-c6c4-4acb-8e2f-9e8d3ad2e4e7-image.png

                  MikeReadingtonM Offline
                  MikeReadingtonM Offline
                  MikeReadington
                  wrote on last edited by MikeReadington
                  #11

                  Synology - Docker
                  Vera - 1.7.5187 (7.31)
                  MSR - latest-22144-c2512b52

                  I have one lock still remaining on a Vera that sl_UserCode won't write reliably. I can confirm this works for me.

                  Triggered using same code as stored sl_UserCode : Works
                  Triggered using different code from stored sl_UserCode: Works

                  Every trigger of the lock updates sl_UserCode_updated with a new value.

                  I hope this helps.

                  Screen Shot 2022-05-24 at 1.04.33 PM.png

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

                    Remember that the changes operator produces a pulse that lasts milliseconds, and is probably too fast to see in the UI. If your dependent logic is running, then it's working, you probably just can't see that on the condition itself. To make it stand out during debugging/verification, add a "delay reset" option on the changes condition of a couple of seconds.

                    It's probably more useful to screen shot the rule's status panel than the editing view, by the way. That shows the logic states and other timing.

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

                    T 1 Reply Last reply
                    1
                    • toggledbitsT toggledbits

                      Remember that the changes operator produces a pulse that lasts milliseconds, and is probably too fast to see in the UI. If your dependent logic is running, then it's working, you probably just can't see that on the condition itself. To make it stand out during debugging/verification, add a "delay reset" option on the changes condition of a couple of seconds.

                      It's probably more useful to screen shot the rule's status panel than the editing view, by the way. That shows the logic states and other timing.

                      T Offline
                      T Offline
                      tbully
                      wrote on last edited by
                      #13

                      @toggledbits Understood.

                      I'll test more when I get free from work. So far I'm seeing inconsistent variable updates but nice to see it worked for @MikeReadington .

                      One thing I've noticed is that when Vera reloads (which, let's face it, happens often), the last PIN triggers because the sl_User_code_updated gets updated to the reload epoch time.

                      Wondering of ways around this. I think one way could be to use a local expression that gets the current time (in epoch) and add a reasonable buffer (few minutes)? I'm not familiar with expressions but maybe something like that?

                      Something easier?

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

                        I've posted an updated 22144 build (stamped f4d0388a) that contains a potential workaround to fix the reload issue (so it's a workaround for the workaround to bypass Vera's kludge). The update attributes should be stable on both Vera reloads and Reactor restarts.

                        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
                        1
                        • T Offline
                          T Offline
                          tbully
                          wrote on last edited by tbully
                          #15

                          Latest build gets rid of the extra notifications on reload. Thanks for doing this instead of me having to figure out another hack. It's a shame we have to do any of this but I suppose we've beat that horse to death over the years.

                          Update on my weird variable issue: I was noting that the sl_User_code (and even the sl_User_code_updated) variables were only sporadically updating. After a lot of head-scratching, I noted that the servo was moving a little slow even though the batteries were showing 66%. I decided to replace them just in case. I noted much faster servo response but, more importantly, the variable writes stabilized. Very strange but I'm happy it's better.

                          Many thanks, @toggledbits , for your workarounds and your forum advice. My system has been mostly stable for a few years so I'm a little rusty.

                          1 Reply Last reply
                          2
                          • MikeReadingtonM Offline
                            MikeReadingtonM Offline
                            MikeReadington
                            wrote on last edited by MikeReadington
                            #16

                            Glad you got it. It is so funny this came up today because I actually had a Schlage direction sheet open to refresh my memory on Zwave exclude and include to move it to Hubitat.

                            I confirmed the reload issue would trigger the rule, and the updated 22144 resolved that for me.

                            I know I have said it before, but at this point I honestly can't imagine my automation life without MSR.

                            Thanks as always Patrick!

                            G 1 Reply Last reply
                            3
                            • MikeReadingtonM MikeReadington

                              Glad you got it. It is so funny this came up today because I actually had a Schlage direction sheet open to refresh my memory on Zwave exclude and include to move it to Hubitat.

                              I confirmed the reload issue would trigger the rule, and the updated 22144 resolved that for me.

                              I know I have said it before, but at this point I honestly can't imagine my automation life without MSR.

                              Thanks as always Patrick!

                              G Offline
                              G Offline
                              gwp1
                              wrote on last edited by
                              #17

                              @mikereadington If you're moving your locks to Hubitat I recommend you also add the Reliable Locks app available in HPM.

                              b7018093-6d72-4799-b53d-50b02d8d3d80-image.png

                              It's resolved many issues that Schlage and Hubitat have (even with the improved native integration.)

                              *Hubitat C-7 2.4.1.177
                              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                              *HASS 2025.6.0
                              w/ ZST10-700 fw 7.18.3

                              *Prod MSR in docker/portainer
                              MSR: latest-25139-fbd67abc
                              MQTTController: 25139
                              ZWave Controller: 25139

                              1 Reply Last reply
                              1
                              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
                                125

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

                              • Error After Upgrade
                                G
                                gwp1
                                0
                                4
                                101

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

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

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

                              • Links to MSR from HA
                                Tom_DT
                                Tom_D
                                0
                                1
                                88

                              • Set Reaction > Script Action
                                wmarcolinW
                                wmarcolin
                                0
                                11
                                431

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

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

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

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