ISSUE: Child Locks not getting Code Slot Name or PIN from Parent Lock.
Describe the bug After updating to V0.1.0 then V0.1.1-b1 I had to reconfigure my locks which is fine as I can sort of see where you're going with this. I reconfigured my Parent Lock, which is Front Door but on the 3 subsequent locks the Code Slot information is not being populated from the Parent Lock.
Environment (please complete the following information):
Installation method Home Assistant OS Core 2025.11.1 Supervisor 2025.11.1 Operating System 16.3 Frontend 20251105.0
- OS: 16.3
- Type of system that HA is running on: Oracle Virtual Box / Virtual Machine on Window 10.
- Home Assistant version: 2025.11.1
- Hassio/Docker/Core?
- Component version: ?
- Z-Wave integration name: zwave_js
- Lock make and model: Kwikset HC620
Logs I have Logging turned on but where are the logs located?
Screenshots There's a lot of things in the UI for Keymaster.. Too many to get a meaningful screenshot.
Additional context
I can override the Parent Lock but with 3 Child Locks and 10 Code Slots, this will become quite tedious. I'm not sure why the Code Slots form the Parent Lock are not being copied over. Please help!
I have Logging turned on but where are the logs located?
/config/home-assistant.log
I just now deleted a lock (Laundry Room Lock) and then added it back in making sure the Parent Lock (Front Door Lock) was selected. No Code Slots were generated and strangely enough, no logs are being created either.
I can't help you with why your home assistant isn't generating any logs.
I can't help you with why your home assistant isn't generating any logs.
No worries. I'll figure that out.
Nevertheless, looking at the issues in this git, it seems this is a common problem with this release and I trust you are working on it. In the meantime, I'll just manually enter the Names and PINs for each Code Slot for each lock.
Could it be the lack of entities for the Parent Door Lock (Front Door)?
Could it be the lack of entities for the Parent Door Lock (Front Door)?
No idea, would need to see the debug log output.
Could it be the lack of entities for the Parent Door Lock (Front Door)?
No idea, would need to see the debug log output.
I'll try to figure out why the logs aren't generating.
Don't know if there's any thing usefull here but here you go.
What model lock is the guest bathroom door lock?
What model lock is the guest bathroom door lock?
Kwikset HC620. I bought all the locks at the same time, BTW.
Could it be the lack of entities for the Parent Door Lock (Front Door)?
No idea, would need to see the debug log output.
HA 2025.11 stopped writing logs to /config/home-assistant.log you can get logs via ha core logs from the CLI or you have to get them from the UI.
HA 2025.11 stopped writing logs to
/config/home-assistant.log
Sounds like a HAOS thing only, my container install still writes out the log file.
HA 2025.11 stopped writing logs to
/config/home-assistant.logSounds like a HAOS thing only, my container install still writes out the log file.
True and I managed to find it..
Try the "Reset Lock" for the "Guest Bathroom Door" lock.
Try the "Reset Lock" for the "Guest Bathroom Door" lock.
Sorry it took so long. This week got busy. I reset each Code Slot and then Reset the lock. Here's the latest log.
Please make sure you're running the latest beta and see if the issue persists please. Thanks.
Please make sure you're running the latest beta and see if the issue persists please. Thanks.
I'll check and update if needed in a bit but wanted to post these logs with "coordinator" errors.
Please make sure you're running the latest beta and see if the issue persists please. Thanks.
Issue still persists. I just reset the Guest Bathroom Door Lock again. Log snippet:
025-11-15 15:47:36.494 DEBUG (MainThread) [custom_components.keymaster.coordinator] [update_lock_data] Guest Bathroom Door Lock: usercodes: [{'code_slot': 1, 'name': 'User Code (1)', 'in_use': False, 'usercode': ''}, {'code_slot': 2, 'name': 'User Code (2)', 'in_use': False, 'usercode': ''}, {'code_slot': 3, 'name': 'User Code (3)', 'in_use': False, 'usercode': ''}, {'code_slot': 4, 'name': 'User Code (4)', 'in_use': False, 'usercode': ''}, {'code_slot': 5, 'name': 'User Code (5)', 'in_use': False, 'usercode': ''}, {'code_slot': 6, 'name': 'User Code (6)', 'in_use': False, 'usercode': ''}, {'code_slot': 7, 'name': 'User Code (7)', 'in_use': False, 'usercode': None}, {'code_slot': 8, 'name': 'User Code (8)', 'in_use': False, 'usercode': None}, {'code_slot': 9, 'name': 'User Code (9)', 'in_use': False, 'usercode': None}, {'code_slot': 10, 'name': 'User Code (10)', 'in_use': False, 'usercode': None}] 2025-11-15 15:47:36.494 DEBUG (MainThread) [custom_components.keymaster.coordinator] [clear_pin_from_lock] Guest Bathroom Door Lock: Code Slot 3: Clearing PIN 2025-11-15 15:47:37.527 DEBUG (MainThread) [custom_components.keymaster.coordinator] [clear_pin_from_lock] Guest Bathroom Door Lock: Code Slot 3: Clear command sent, confirming 2025-11-15 15:47:37.527 DEBUG (MainThread) [custom_components.keymaster.coordinator] [clear_pin_from_lock] Guest Bathroom Door Lock: Code Slot 3: PIN Cleared (or 0000 - Schlage bug)
Does the UserCodes command class show up for your lock in zwavejs UI?
Does the UserCodes command class show up for your lock in zwavejs UI?
Yup but everything is blank except my other locks which were manually entered one by one:
Next question, does your zwave network ONLY consist of these locks?
Next question, does your zwave network ONLY consist of these locks?
Nope. I have lights, thermostats and smoke detectors too.
any errors in zwavejs log regarding your locks?
any errors in zwavejs log regarding your locks?
The Guest Bathroom Lock is Node 9. I see this currently:
025-11-16 12:15:49.108 INFO Z-WAVE: [Node 009] Value updated: 113-0-alarmType 168 => 168 2025-11-16 12:15:49.110 INFO Z-WAVE: [Node 009] Value updated: 113-0-alarmLevel 1 => 1 2025-11-16 12:15:49.112 INFO Z-WAVE: [Node 009] Value updated: 113-0-Power Management-Battery maintenance status 10 => 10 2025-11-16 12:34:55.235 CNTRLR » [Node 009] Battery CC values may be stale, refreshing... 2025-11-16 12:34:55.236 CNTRLR » [Node 009] querying battery status... 2025-11-16 12:34:57.884 CNTRLR « [Node 009] received response for battery information: 2025-11-16 13:18:58.994 INFO Z-WAVE: [Node 009] Value updated: 113-0-alarmType 168 => 168 2025-11-16 13:18:58.998 INFO Z-WAVE: [Node 009] Value updated: 113-0-alarmLevel 1 => 1 2025-11-16 13:18:59.001 INFO Z-WAVE: [Node 009] Value updated: 113-0-Power Management-Battery maintenance status 10 => 10 2025-11-16 13:25:25.049 CNTRLR » [Node 009] Battery CC values may be stale, refreshing... 2025-11-16 13:25:25.051 CNTRLR » [Node 009] querying battery status... 2025-11-16 13:25:26.607 CNTRLR « [Node 009] received response for battery information: 2025-11-16 14:15:54.858 CNTRLR » [Node 009] Battery CC values may be stale, refreshing... 2025-11-16 14:15:54.860 CNTRLR » [Node 009] querying battery status... 2025-11-16 14:15:56.285 CNTRLR « [Node 009] received response for battery information: 2025-11-16 14:22:08.880 INFO Z-WAVE: [Node 009] Value updated: 113-0-alarmType 168 => 168 2025-11-16 14:22:08.882 INFO Z-WAVE: [Node 009] Value updated: 113-0-alarmLevel 1 => 1 2025-11-16 14:22:08.884 INFO Z-WAVE: [Node 009] Value updated: 113-0-Power Management-Battery maintenance status 10 => 10 2025-11-16 15:06:24.671 CNTRLR » [Node 009] Battery CC values may be stale, refreshing... 2025-11-16 15:06:24.673 CNTRLR » [Node 009] querying battery status... 2025-11-16 15:06:26.148 CNTRLR « [Node 009] received response for battery information: 2025-11-16 15:25:18.774 INFO Z-WAVE: [Node 009] Value updated: 113-0-alarmType 168 => 168 2025-11-16 15:25:18.778 INFO Z-WAVE: [Node 009] Value updated: 113-0-alarmLevel 1 => 1 2025-11-16 15:25:18.780 INFO Z-WAVE: [Node 009] Value updated: 113-0-Power Management-Battery maintenance status 10 => 10
any errors in zwavejs log regarding your locks?
Any updates?
Nope, no idea why your lock isn't playing nice. Did you update to the latest beta?
Just recently installed KeyMaster and trying it out and noticed the same issue with @Sammy-cmd where the master/secondaries locks aren't sync. In fact, it show slot name and pin is greyed-out. Hope there's a future fix. Thanks
In fact, it show slot name and pin is greyed-out.
Pretty sure that's normal when they're set to child locks. Make sure you are running the latest beta and that the Usercode command class shows up in ZwaveJS UI for all locks.
I'm seeing the same issue with multiple Schlage Connect locks.
I'm seeing the same issue with multiple Schlage Connect locks.
Make sure you are running the latest beta and that the Usercode command class shows up in ZwaveJS UI for all locks.