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
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
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor

Schlage Lock - Alert when PIN Entered

Scheduled Pinned Locked Moved Multi-System Reactor
17 Posts 5 Posters 1.2k 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.
  • T Offline
    T Offline
    tbully
    wrote on last edited by
    #1

    Hello All -
    I'm still slowly migrating from Vera Reactor to MSR (w/ Home Assistant). Everything is going fairly smooth. However, I've ran in to an issue and can't find an analog solution.

    On Vera, I get email notifications when someone enters their PIN by using the below logic:
    3db4fe6d-2d02-444b-b0ae-27cbfa6e03a1-image.png

    However, I've noticed that there is no "Updates" selection for sl_UserCode in MSR. The updates trigger is important as the sl_UserCode stays the same until another PIN is entered. So, for example, if Jennifer unlocks the door two times in a row, the condition is already set and won't send an alert without it.

    Work arounds?

    Here's MSR:
    5c8ed91a-949b-4a73-84d8-62816029c40b-image.png

    1 Reply Last reply
    0
    • T Offline
      T Offline
      tbully
      wrote on last edited by
      #2

      I found the following thread after searching a little differently:
      https://smarthome.community/topic/517/vera-vs-msr-lock-code-logic

      I'm going to look in to this as it seems logical. Apologies for the likely duplicate post.

      T 1 Reply Last reply
      0
      • T tbully

        I found the following thread after searching a little differently:
        https://smarthome.community/topic/517/vera-vs-msr-lock-code-logic

        I'm going to look in to this as it seems logical. Apologies for the likely duplicate post.

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

        I'm struggling with this. The concept in the above link seems sensible. And, in fact, I've seen it work a few times inconsistently. However, it seems like the lock doesn't want to always write to the variable as my condition never fires because the sl_UserCode never changes from the "none" value set. The prior Vera-based logic has worked for years, so I'm having a hard time blaming the lock. I'm wondering if I'm upsetting it by manually changing the variable? Too often? Not allowing it to sleep, etc?

        ca3d5839-f328-4e87-973b-38e89a44273b-image.png

        17df93dd-8b50-44eb-9f2e-5cea8b4d5824-image.png

        1 Reply Last reply
        0
        • 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.151
                                    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                    *HASS 2025.3.4
                                    w/ ZST10-700 fw 7.18.3

                                    *Prod MSR in docker/portainer
                                    MSR: latest-25082-3c348de6
                                    MQTTController: 24257
                                    ZWave Controller: 25082

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


                                    Recent Topics

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

                                    • Reactor (Multi-System/Multi-Hub) Announcements
                                      toggledbitsT
                                      toggledbits
                                      5
                                      122
                                      36.5k

                                    • Z-Wave Future....
                                      CatmanV2C
                                      CatmanV2
                                      0
                                      5
                                      153

                                    • Can´t restart or upgrade/deploy MSR
                                      toggledbitsT
                                      toggledbits
                                      0
                                      4
                                      104

                                    • [Solved] Limit HA Entity in MSR
                                      wmarcolinW
                                      wmarcolin
                                      0
                                      7
                                      222

                                    • Disaster recovery and virtualisation
                                      CatmanV2C
                                      CatmanV2
                                      0
                                      5
                                      682

                                    • Remote access of Zwave stick from Z-wave server
                                      CatmanV2C
                                      CatmanV2
                                      0
                                      3
                                      396

                                    • Organizing/ structuring rule sets and rules
                                      G
                                      gwp1
                                      0
                                      5
                                      395

                                    • Moving MSR from a QNAP container to RP 5 - some issues
                                      G
                                      gwp1
                                      0
                                      5
                                      367

                                    • Widget deletion does not work and landing page (status) is empy
                                      G
                                      gwp1
                                      0
                                      4
                                      356

                                    • Need help reducing false positive notifications
                                      T
                                      tamorgen
                                      0
                                      7
                                      548
                                    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