Zwave, Lock, requestedChange status=A, C-8 Hub

🛎️ Get Help Devices
, ,
1

(Move to this section from Devices. I'm hoping to get a reply.)

Hi All,

Let me get the background out of the way. Hub C-8, Original power supply, original antennas, Locks are Yale 216 ZW2 (24 of them), using Generic Z-Wave Lock driver, 1 Zooz S2 800 light switch.

I seem to be having an issue with a few locks on my Zwave network. Recently, I went to add a Code to one of the lock [ID# 0x002d] and it shows, "requestedChange : {12={code=XXXXX, name=XXXXX, status=A}" but nothing happens, and yes I've waited overnight.

I have tried several repairs, updating the ZW try (from LR to non-LR), restarts, shutdown/remove power, etc. but it just shows the same and never applies it.

Today, I went to remove codes from a different lock and it's not removing and just has "requestedChange : {4={code=null, name=null, status=D}, 5={code=null, name=null, status=D}}" thus I wanted to remove code 4 & 5 but again nothing is happening.

Now I'm wondering if this is a ZW issue or Hub issue because I have a hard time seeing two completely separate locks having issues with changes.

Here is the details of the lock not adding codes;

  • deviceId: 3840
  • deviceType: 32779
  • inClusters: 0x5E,0x72,0x98,0x5A,0x73,0x86
  • manufacturer: 297
  • S2: 128
  • secureInClusters: 0x80,0x62,0x85,0x59,0x71,0x70,0x63,0x8A,0x8B,0x4C,0x4E,0x7A
  • zwaveSecurePairingComplete: true
  • zwNodeInfo: 53 DC 80 04 40 03 5E 72 98 5A 73 86 68 23 F1 00 80 62 85 5C 59 71 70 63 8A 8B 4C 4E 7A

Any input or advice is greatly appreciated.

Thanks,
Charlie

This is from the Log of 0x002d, this one with the information above;

dev:662024-08-01 12:49:09.523 PMwarnencryption is: false

dev:662024-08-01 12:49:09.521 PMwarndescription logging is: true

dev:662024-08-01 12:49:09.518 PMwarndebug logging is: false

dev:662024-08-01 12:49:09.516 PMinfoupdated...

dev:662024-08-01 11:52:22.410 AMinfo102 HFNJA000034 was unlocked by Building[6:6]

dev:662024-08-01 09:50:16.836 AMwarnencryption is: false

dev:662024-08-01 09:50:16.834 AMwarndescription logging is: true

dev:662024-08-01 09:50:16.832 AMwarndebug logging is: false

dev:662024-08-01 09:50:16.828 AMinfoupdated...

dev:662024-08-01 09:47:38.239 AMwarnencryption is: false

dev:662024-08-01 09:47:38.236 AMwarndescription logging is: true

dev:662024-08-01 09:47:38.233 AMwarndebug logging is: false

dev:662024-08-01 09:47:38.188 AMinfoupdated...

dev:662024-07-31 10:38:05.718 PMwarnencryption is: false

dev:662024-07-31 10:38:05.716 PMwarndescription logging is: true

dev:662024-07-31 10:38:05.715 PMwarndebug logging is: false

dev:662024-07-31 10:38:05.713 PMinfoupdated...

dev:662024-07-31 10:36:21.482 PMinfostarting code fetch, trying to fetch code:1

dev:662024-07-31 09:12:39.869 PMinfo102 HFNJA000034 battery is 91%

dev:662024-07-31 09:12:12.863 PMwarndescription logging is: true

dev:662024-07-31 09:12:12.862 PMwarndebug logging is: false

dev:662024-07-31 09:12:12.860 PMinfoupdated...

2

can you add the code directly from the device details page?

3

Thank you for the reply!!

I tried Directly and via Lock Manager.

Lock Code Manager says: "Add new user Code add request completed" in this situation is would be Position #7 (see below)

When I go directly to the device it shows; (NOTE XXXX was an actual code)
requestedChange : {13={code=XXXX, name=Test, status=A}, 7={code=XXXX, name=Tester, status=A}}

But the actual codes never get added to the Device.

I just tested a lock that's about 5 feet away from the Hub and adding and deleting a code worked fine. However, when I tried a lock that is only 30' away, it doesn't work and I get the same as the original device I am referencing which is about 90' feet and a one floor lower but connects via the Zooz switch hop.

Thoughts?

4

What is odd is that the codes sometimes just disappear but not actually applied to the lock. Like right now, the working examples I gave you have cleared out and yet under Status is ...
"lastCodeName : unknown codeNumber: 13" and requestedChange : {} is blank.

5

So if we don’t get support here, where do we go to reach an actual support person?

6

You are interacting directly with an engineer on staff.

Given that it is Sunday, I might wait until regular business days resume to hear back.

3 Likes
7

Try power cycling the locks not working, pull batteries for 30 seconds. You could also try brand new batteries while you are at it.

9

What happens if you attempt to add the code directly from the driver details page?, if adding a code directly from the driver fails then there is some issue with the hub communicating with the lock.

1 Like
11

I tried under both Lock Code Manager and what I would assume is the Drive page is a URL like this; http://192.555.5.555/device/edit/67

ie. Main page->Devices->Lock->landing page for lock.

Yes and I have tried to power cycle the lock with no change.

I can add a code directly to the lock, via the lock keys.

12

I tried but will re-try right now and will allow for a minute to pass.

13

Wow... I just pulled up one of the devices that wouldn't delete codes and still have;

requestedChange : {4={code=null, name=null, status=D}, 5={code=null, name=null, status=D}}
but now it is deleting codes BUT there are a bunch codes that I did not add to the lock. As, I add everything via Excel and assign, Code 1, 2, 3, etc. so everything is organized but now there is like code position ie. "123":{"code":"10744","name":"code #123"}, which I never added!?

Thoughts!?

14

Still having this issue... @Hubitat_Staff can I get some Support please.

15

Since this support ticket has been raised, I have added three Zooz Z76, that is extending the network. Attached is my z-wave graph. Lock 101 & 102 are currently the ones that are giving me a hard time. I have tried updating the Driver from Generic Z-Wave Lock to Yale Conexis L1 Z-Wave Lock and back. I have performed Reboot, Z-Wave Network Repair, and Repair on the Lock itself.

I have not performed a reset on the Lock just because of the pain of taking it all apart and resetting it, which is my last ditch effort, but wanted to see if we can handle this through other means as I need to remotely control these and won't always have physical access.

Thanks in advance.

Screenshot 2024-09-03 at 8.36.48 AM
Screenshot 2024-09-03 at 8.36.48 AM1118×1254 119 KB

16

Have you tried just deleting all the codes from the device page, then setting them again either from LCM or from the device page? LCM will pick up on any changes made from the device page.

17

When I add the code via LCM, it initially gives me "jobs- failed:1," but when I go via Device Manager and select the lock in question, it shows lockCodes have been added.

My results have been hit-and-miss... I have a User on LCM that won't delete and isn't in the lock.

I will say that adding the Z76 has helped, which makes sense considering the size of the building.

Thoughts?

18

All LCM does is read the users and codes directly from the device attribute. So, the user is probably showing on one of the locks? The failed job alert could be from this messed up user.

If you dont have a bunch of special programs setup in LCM it is safe to delete and reinstall, it should pick up all the codes and users from the locks again. Take a backup first though just in case.

1 Like
19

Thanks, I might do that just to see if that fixes the problem. I'm assuming the Device Attribute is a db within hubitat, is there a way for hubitat to repair/rebuild it? Also, if I manually enter a code on the Lock (Yale 216), will the Lock report it to Hubitat or it read it?

20

The attributes are listed on the device page as "Current States", sorry I am using driver coding terms. They are saved there with the device and always visible. The codes themselves are saved on the lock as well and can be retrieved / refreshed with "Get Codes". The user tied to each code is only stored in the attribute, it is not a feature of the locks, something HE has added on top of the locks features.

If you manually add a code, its possibly the lock may report it but the user would ????. If the lock does not report it then I think you would need to run the Get Codes command on the device page, and let it go through every slot to fetch the codes (some locks have up to 255 slots). Then once the new code shows up with ???? user name you could re-set it from the device page and give it a user name. Much easier to just add codes via the hub on the device page or LCM.

If you do not fetch the codes at all, when that code unlocks the door you will usually get some messages about an unknown code or user unlocked the door.

21

What is odd, is like right now, I added via LCM a Lock to a user (Landlord) and on the Lock device page it is showing "requestedChange : {7={code=XXXXXX, name=Landlord, status=A}}" it's been well over 20 minutes and it's just sitting and not actually applying the code. I've tried refreshing the Device page, thinking maybe it is cached but nope. There is a pending "scheduled job" for dev52Recur.refresh any idea what that is?

22

Ok, now to make it more odd... the lock update without adding the User/Code to the lock but the requestedChange updated to not showing anything, as if it either Timeout or actually applied it but the code isn't showing, even after selecting, Refresh and Get Codes.

Under Event Log is showing:

|Id:|35699|
|Date/Time:|9/04/2024 7:56:04.146 am|
|Name:|command-setCode|
|Description:|Command called: setCode|
|State change:|false|
|Physical:|false|
|Digital:|false|
|Value:||
|Unit:||
|Source:|DEVICE|
|Type:|command|
|Device id:|52|
|Device name:|101 XC0VN600114|
|Produced by:|Lock Code Manager|
|Triggered apps:||

Past Log is showing:

[dev:52] 2024-09-04 08:40:42.058 AM[trace] trying to fetch code:64
[dev:52] 2024-09-04 08:40:42.055 AM[info]code:63 fetched
[dev:52] 2024-09-04 08:40:40.594 AM[trace] trying to fetch code:63
[dev:52] 2024-09-04 08:40:39.648 AM[trace] trying to fetch code:63
[dev:52] 2024-09-04 08:40:38.607 AM[trace] trying to fetch code:63
[dev:52] 2024-09-04 08:40:38.606 AM[info] code:62 fetched