Schlage BE469NX connectivity issues / unreliable

🛎️ Get Help
70

Support told me the same thing... but I struggle to believe that given all other evidence.

I shared a video I made with support 2 weeks or so ago where I illustrated the following:

  1. The locks tend to work when used one at a time direct from the Device page.
  2. The locks tend to 'freeze' the z-wave network for 3-5 minutes when a rule is used to operate two locks simultaneously.

I was told that the video would be shared with Hubitat devs to help identify the issue, but Youtube stats tell me that the video hasn't been viewed by anyone other than me. I'm sure they were busy with the sale over Easter, and getting the 2.9 release out. I know what it's like to not have enough resources to make everyone happy, so I'm not significantly upset by the lack of followup just yet. Support has otherwise been great.

Here were the results of a series of tests I ran and shared with support. This has me convinced that the issue appears to be in the software on HE side, and not due to any repeaters (I have many z-wave + repeaters, and again, never had the issue with Wink (just like you) or a significant popcorn effect longer than a few seconds).

Conclusion : When the following is true, my z-wave network freezes for 3-5 minutes:

  • MORE than 1 BE469 z-wave lock receives an UNLOCK command simultaneously

Symptoms :

  1. The z-wave network will freeze for 3-5 minutes.
  2. Any z-wave command that is attempted from the hub during the freeze is stored and eventually triggered when the freeze ends.
  3. During the freeze no z-wave devices will respond to any z-wave commands.
  4. During the freeze no z-wave commands will appear in the Hubitat logs.
  5. During the freeze, zigbee devices are not impacted and can be used normally.
  6. After the freeze, all z-wave commands that were sent during the freeze will fire simultaneously and also display in the log.

TESTS to determine impact from Rule Machine on issue (2.5 and issue persists in 3.0) . Again - no issues encountered when ANY locks were individually locked/unlocked directly via the device page:

  1. ONE LOCK - side door
    Trigger: Cloud End Point
    Select Actions: Unlock: Garage Lock
    SUCCESS - ran several times. No issue. Lock always unlocked. Could always be re-locked in a few seconds. Ruled out issues with repeaters, z-wave mesh. Ruled out issue with Rule Machine if only a single lock and no other devices were triggered.

  2. ONE LOCK - garage
    Trigger: Cloud End Point
    Select Actions: Unlock: Side Door Lock
    SUCCESS - ran several times. No issue. Lock always unlocked. Could always be relocked in a few seconds. Ruled out issues with repeaters, z-wave mesh. Ruled out issue with Rule Machine if only a single lock and no other devices were triggered.

  3. TWO LOCKS SIMULTANEOUSLY
    Trigger: Cloud End Point
    Select Actions: Unlock: Garage Door Lock, AND Side Door Lock
    FAILURE - Every time the Garage door unlocked, and then the z-wave network froze for 3-5 minutes. Any command sent to any z-wave device during the 'freeze' time was queued and instantly ran as soon as the freeze ended.

  4. ONE LOCK, 2 Z-WAVE LIGHTS SIMULTANEOUSLY
    Trigger: Cloud End Point
    Select Actions: Unlock: Side Door Lock, Turn On 2 Z-Wave Lights in Garage
    FAILURE - ran several times. First time no issue. Second time z-wave network froze for 3-5 minutes. Any command sent to any z-wave device during the 'freeze' time was queued and instantly ran as soon as the freeze ended.

  5. 1st LOCK UNLOCK, delay 10 seconds, 2nd LOCK UNLOCK - two triggers
    First Trigger: Cloud End Point
    Select Actions: Unlock: Side Door Lock
    Second Trigger: Other trigger fires: if Trigger above is run, delay 10 seconds, Unlock: Garage Door Lock
    SUCCESS : ran several times. First time no issue. Second time there was a 5-10 second delay before first triggered lock unlocked. Locks could be individually locked via Hubitat without issue or delay immediately following this test.

  6. 1 LOCK, delay, 2nd LOCK AND 2 Z-WAVE LIGHTS SIMULTANEOUSLY - two triggers
    First Trigger: Cloud End Point:
    Select Actions: Unlock: Side Door Lock
    Second Trigger: Other trigger fires: Unlock Garage Door, turn on 2 Z-Wave lights in Garage
    FAILURE : ran several times. First time both locks unlocked and lights turned on, but the z-wave network immediately froze for 3-5 minutes.

  7. 1 LOCK, delay, 2nd LOCK, delay, 2 z-wave lights on - three triggers
    First Trigger: Cloud End Point
    Select Actions: Unlock: Side Door Lock
    Second Trigger: Other trigger fires: if Trigger above is run, delay 10 seconds, Unlock: Garage Door Lock
    Third Trigger: IF Garage Door Lock unlocks, delay 1 second, turn on 2 z-wave lights
    MIXED SUCCESS : ran several times. First time no issue . Second time there was a 5-10 second delay before first triggered lock unlocked. Locks could be individually locked via Hubitat without issue or delay. Third time, the second trigger never fired according to the logs , but I was able to unlock/lock both doors via the device page lock/unlock buttons with no z-wave freeze issues. Fourth time ran without issue.

After each z-wave network freeze was cleared and z-wave network was working again , each z-wave lock was re-tested by clicking on "Lock" and "Unlock" on the device settings page for that lock. Each time ALL of the locks responded normally when used individually and directly from their device page.

I share all of our hopes that there is one day a resolution to this.

2 Likes