Schlage BE469 Issues

Posted on
Sun May 21, 2017 7:10 pm
NewfD90 offline
Posts: 58
Joined: Mar 17, 2017

Re: Schlage BE469 Issues

Things are definitely looking up! I got a trigger to fire:

Code: Select all
   Upgrading plugin Z-Wave Lock Manager to newer version 1.0.32 (previous version moved to trash)
   Loading plugin "Z-Wave Lock Manager 1.0.32"
   Starting plugin "Z-Wave Lock Manager 1.0.32" (pid 77035)
   Started plugin "Z-Wave Lock Manager 1.0.32"
   Z-Wave Lock Manager Debug       startup called
   Z-Wave Lock Manager Debug       Start processing trigger Deadbolt Jammed
   Z-Wave Lock Manager Debug       Start processing trigger House Cleaner Arrive
   Z-Wave Lock Manager Debug       Start processing trigger House Cleaner Depart
   Z-Wave Lock Manager Debug       Start processing trigger Invalid Code Limit Reached
   Z-Wave Lock Manager Debug       Start processing trigger Judy Arrive
   Z-Wave Lock Manager Debug       Start processing trigger Judy Depart
   Z-Wave Lock Manager Debug       Start processing trigger Pet Sitter Arrive
   Z-Wave Lock Manager Debug       Start processing trigger Pet Sitter Depart

May 21, 2017, 6:10:08 PM
   Z-Wave Lock Manager             Debug logging enabled

May 21, 2017, 6:13:24 PM
   Z-Wave Lock Manager Debug       Checking if node 11 is a Lock...
   Z-Wave Lock Manager Debug       Node 11 is not a lock - ignoring

May 21, 2017, 6:13:58 PM
   Z-Wave                          received "Rear Garage Thermostat" temperature update to 59.0 °F
   Z-Wave                          received "Rear Garage Thermostat" temperature update to 59.0 °F
   Z-Wave Lock Manager Debug       Checking if node 12 is a Lock...
   Z-Wave Lock Manager Debug       Node 12 is not a lock - ignoring
   Z-Wave Lock Manager Debug       Node 12 is not a lock - ignoring

May 21, 2017, 6:21:28 PM
   Z-Wave Lock Manager Debug       Checking if node 15 is a Lock...
   Z-Wave Lock Manager Debug       Node 15 is not a lock - ignoring

May 21, 2017, 6:41:50 PM
   Z-Wave Lock Manager Debug       Checking if node 14 is a Lock...
   Z-Wave Lock Manager Debug       Node 14 is not a lock - ignoring

May 21, 2017, 7:06:24 PM
   Z-Wave Lock Manager Debug       Checking if node 19 is a Lock...
   Z-Wave                          received "Front Door Lock" status update unlocked (manually)
   Trigger                         Front Door Unlocked
   Z-Wave Lock Manager Debug       Node 19 added to list of lockIDs
   Z-Wave Lock Manager Debug       Node ID 19 found in lockIDs
   Z-Wave Lock Manager Debug       Node ID 19 found in lockIDs
   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       Lock Status Report received:
   Z-Wave Lock Manager Debug       Raw:   01 0F 00 04 00 13 09 71 05 00 00 00 FF 06 02 00 FF
   Z-Wave Lock Manager Debug       Node:  19
   Z-Wave Lock Manager Debug       Type:  6
   Z-Wave Lock Manager Debug       Event: 2
   Z-Wave Lock Manager             Status: Door unlocked manually [Node: 19]
   Z-Wave Lock Manager Debug       Node ID 19 found in lockIDs
   Z-Wave Lock Manager Debug       Node ID 19 found in lockIDs
   Z-Wave                          received "Front Door Lock" status update locked (via keypad)
   Trigger                         Front Door Locked
   Z-Wave Lock Manager Debug       Node ID 19 found in lockIDs
   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       Lock Status Report received:
   Z-Wave Lock Manager Debug       Raw:   01 0F 00 04 00 13 09 71 05 00 00 00 FF 06 05 00 FF
   Z-Wave Lock Manager Debug       Node:  19
   Z-Wave Lock Manager Debug       Type:  6
   Z-Wave Lock Manager Debug       Event: 5
   Z-Wave Lock Manager             Status: Door locked by user 255 [Node: 19]
   Z-Wave Lock Manager Debug       triggerEvent called
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #19#
   Z-Wave Lock Manager Debug       eventNode: #19#
   Z-Wave Lock Manager Debug       dUserNo:   #4#
   Z-Wave Lock Manager Debug       userNo:    #255#
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #19#
   Z-Wave Lock Manager Debug       eventNode: #19#
   Z-Wave Lock Manager Debug       dUserNo:   #5#
   Z-Wave Lock Manager Debug       userNo:    #255#
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #19#
   Z-Wave Lock Manager Debug       eventNode: #19#
   Z-Wave Lock Manager Debug       dUserNo:   #3#
   Z-Wave Lock Manager Debug       userNo:    #255#
   Z-Wave Lock Manager Debug       Node ID 19 found in lockIDs
   Z-Wave Lock Manager Debug       Checking if node 10 is a Lock...
   Z-Wave Lock Manager Debug       Node 10 is not a lock - ignoring
   Z-Wave Lock Manager Debug       Node ID 19 found in lockIDs
   Z-Wave                          received "Front Door Lock" status update unlocked (via keypad)
   Trigger                         Front Door Unlocked
   Z-Wave Lock Manager Debug       Node ID 19 found in lockIDs
   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       Lock Status Report received:
   Z-Wave Lock Manager Debug       Raw:   01 10 00 04 00 13 0A 71 05 00 00 00 FF 06 06 01 02 FF
   Z-Wave Lock Manager Debug       Node:  19
   Z-Wave Lock Manager Debug       Type:  6
   Z-Wave Lock Manager Debug       Event: 6
   Z-Wave Lock Manager             Status: Door unlocked by user 2 [Node: 19]
   Z-Wave Lock Manager Debug       triggerEvent called
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #19#
   Z-Wave Lock Manager Debug       eventNode: #19#
   Z-Wave Lock Manager Debug       dUserNo:   #4#
   Z-Wave Lock Manager Debug       userNo:    #2#
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #19#
   Z-Wave Lock Manager Debug       eventNode: #19#
   Z-Wave Lock Manager Debug       dUserNo:   #5#
   Z-Wave Lock Manager Debug       userNo:    #2#
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #19#
   Z-Wave Lock Manager Debug       eventNode: #19#
   Z-Wave Lock Manager Debug       dUserNo:   #Any#
   Z-Wave Lock Manager Debug       userNo:    #2#
   Trigger                         Judy Arrive
   Z-Wave Lock Manager Debug       Executing trigger
   Z-Wave Lock Manager Debug       Node ID 19 found in lockIDs
   Schedule                        Front Door Unlocked (delayed action)
   Schedule                        Front Door Unlocked (delayed action)

Posted on
Sun May 21, 2017 11:31 pm
howartp offline
Posts: 3771
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

Excellent; sorry about the delay, and sorry for the bug in the first place - I know perfectly well not to use the Zwave nodeid variable I was using and I don't use it anywhere else in my plugins so why I had it there in this plugin I haven't a clue.


Sent from my iPhone using Tapatalk Pro

Posted on
Mon May 22, 2017 7:46 am
NewfD90 offline
Posts: 58
Joined: Mar 17, 2017

Re: Schlage BE469 Issues

No worries. Just glad it's all functioning now. It's nice to know when the house cleaner or pet sitter has arrived.

At first, the triggered user number didn't line up with the pins I had set. Then I realized that the same pins had been set when I was using Vera and I guess the lock is smart (or dumb) enough not to override what pins are tied to a user number. So I executed your Clear Pin action and then re-executed the Set Pin action and THEN all the codes and user ids lined up correctly.

So I can say all functionality works great, or as good as the BE469 lets it work (as rhanson noted, it returns 0x2A '*' when requesting pins).

Posted on
Sat Jun 03, 2017 2:56 pm
jasongcummins offline
Posts: 2
Joined: Oct 05, 2016

Re: Schlage BE469 Issues

I think I may be having a similar issue and I am running 1.0.37 of the plugin.

Here are the logs:

Z-Wave received "Front Door" status update unlocked (via keypad)
Trigger Autolock Front Door
Z-Wave Lock Manager Debug Node ID 32 found in lockIDs
Z-Wave Lock Manager Debug Raw: 01 10 00 04 00 20 0A 71 05 13 05 00 FF 06 06 01 05 FF
Z-Wave Lock Manager Status: User 5 unlocked door [Node: 32]
Z-Wave Lock Manager Debug triggerEvent called
Z-Wave Lock Manager Error Error in plugin execution ReceivedBroadcast:

Traceback (most recent call last):
File "plugin.py", line 290, in zwaveCommandReceived
File "plugin.py", line 526, in triggerEvent
KeyError: (1914413740,)

Z-Wave Lock Manager Debug Node ID 32 found in lockIDs
Z-Wave Debug reusing outgoing nonce A6 C0 77 F1 48 A9 29 11
Z-Wave Debug RCVD encryptedPacket: 00 71 05 13 05 00 FF 06 06 01 05 (decrypted)
Z-Wave Error encrypted command received from node ID 032 has invalid CBC-MAC value (ignoring)
Z-Wave Lock Manager Debug Node ID 32 found in lockIDs

Posted on
Sat Jun 03, 2017 3:39 pm
howartp offline
Posts: 3771
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

Yes, I think I've a bug in triggers that a user pointed out on other thread.

Hopefully sort early this week - unlikely this weekend.


Sent from my iPhone using Tapatalk Pro

Posted on
Mon Jun 05, 2017 12:27 am
jasongcummins offline
Posts: 2
Joined: Oct 05, 2016

Re: Schlage BE469 Issues

Thanks, let me know if I can provide any additional information to assist.

Posted on
Fri Jun 16, 2017 11:55 am
howartp offline
Posts: 3771
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

Give 1.0.38 a try... (same link)

Peter

Posted on
Sun Jul 16, 2017 12:56 pm
kmarkley offline
Posts: 127
Joined: Nov 15, 2016

Re: Schlage BE469 Issues

Hi.

I am experiencing the same/similar problem with a new Schlage BE469. It is almost as if Lock Manager doesn't see the lock device, except a few things do work.

The lock is reporting and operating correctly from Indigo client.

Lock Manager reports status changes in the log, but all device states remain blank, e.g.:
Code: Select all
Z-Wave Lock Manager             Latch open, Bolt locked, Door open [Node: 4]
Also the Last Update field never changes.

Triggers that work:
  • Manual un/locked
  • Code un/locked
Triggers that FAIL (silently):
  • Indigo un/locked

Actions that work:
  • Get PIN (returns asterisks as expected)
  • Set PIN
Actions that FAIL (with errors):
  • Enable/disable auto relock
  • Set operating mode
Action errors are always:
Code: Select all
InvalidParameter: could not find module/node for action
(with different line numbers and method name depending on the action)

Menu Items:
  • Test status response: Z-Wave Lock Manager Debug lockIDs: [4]
  • All others: <no feedback>

Thanks.
Attachments
Untitled.png
Lock Manager device states
Untitled.png (47.83 KiB) Viewed 1904 times

Posted on
Sun Jul 16, 2017 2:03 pm
howartp offline
Posts: 3771
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

Can I check you're on 1.0.38?

Peter


Sent from my iPhone using Tapatalk Pro

Posted on
Sun Jul 16, 2017 2:08 pm
kmarkley offline
Posts: 127
Joined: Nov 15, 2016

Re: Schlage BE469 Issues

Downloaded and installed v1.0.42 today.

Posted on
Tue Jul 18, 2017 5:48 am
kmarkley offline
Posts: 127
Joined: Nov 15, 2016

Re: Schlage BE469 Issues

In case it wasn't clear before, I meant to say that I installed ZWave Lock Manager for the first time on Sunday and the problems I am experiencing are all on v 1.0.42.

I was also seeing a number of ServerCommunicationErrors that stopped when I disabled the plugin. Not too surprising, since the blank device states suggest some kind of communication problem...

Posted on
Tue Jul 18, 2017 11:12 pm
howartp offline
Posts: 3771
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

I'll try and sort this at the weekend.


Sent from my iPhone using Tapatalk Pro

Posted on
Sat Jul 22, 2017 4:54 am
howartp offline
Posts: 3771
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

Right, I've had a look.

kmarkley wrote:
Lock Manager reports status changes in the log, but all device states remain blank, e.g.:
Code: Select all
Z-Wave Lock Manager             Latch open, Bolt locked, Door open [Node: 4]
Also the Last Update field never changes.

That is (was) expected behaviour; the coding for status's of the dummy device weren't added until 1.0.43 released this morning. (They existed because I had to back-port some code from my beta which does use them)

kmarkley wrote:
Triggers that FAIL (silently):
  • Indigo un/locked

Can you try this again; I don't know why it's not working.

kmarkley wrote:
Actions that FAIL (with errors):
  • Enable/disable auto relock
  • Set operating mode
Action errors are always:
Code: Select all
InvalidParameter: could not find module/node for action
(with different line numbers and method name depending on the action)

Fixed in 1.0.43

kmarkley wrote:
Menu Items:
  • Test status response: Z-Wave Lock Manager Debug lockIDs: [4]
  • All others: <no feedback>

You shouldn't have seen the menu items; I use them for testing but forgot to remove the file when I uploaded to Dropbox.

Peter

Posted on
Tue Jul 25, 2017 10:09 pm
peter offline
Posts: 32
Joined: Feb 09, 2011

Re: Schlage BE469 Issues

Hello. I've just added a Schlage 469 to my z-wave network in Indigo. 7.0.3. I've turned on the debug in Lock Manager v.43 and it does not seem to recognize the lock at all. Also, I've tried several time to tell the lock to to included in the z-wave network, but I get a red X every time. I hit the Schlage button, enter in my 6 digit code and 0, and then get a red X. My z-wave stick picked up the lock information and Indigo seem to act like the lock is locking and unlocking, but nothing is happening at the lock. This is the first z-wave device I am trying to integrate with Indigo, so please bear with me? Any help would be appreciated! Here is the latest log:

Jul 25, 2017, 11:55:50 PM
Reloading plugin "Z-Wave Lock Manager 1.0.43"
Stopping plugin "Z-Wave Lock Manager 1.0.43" (pid 26926)
Z-Wave Lock Manager Debug shutdown called
Stopped plugin "Z-Wave Lock Manager 1.0.43"
Starting plugin "Z-Wave Lock Manager 1.0.43" (pid 27038)
Started plugin "Z-Wave Lock Manager 1.0.43"
Z-Wave Lock Manager Debug startup called

Peter

Posted on
Wed Jul 26, 2017 9:39 am
howartp offline
Posts: 3771
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

This is likely due to encryption failing - its unfortunate that Schlage is your first Zwave device cos they're probably the hardest to get working first time!

Are you able to take the lock (with temporary power) near the Mac whilst you include it WITH encryption?

Once you've got the device included and working, then we can look at Lock Manager.


Sent from my iPhone using Tapatalk Pro

Who is online

Users browsing this forum: No registered users and 1 guest

cron