Code slot names not showing in child lock

[bjh45964]

Is your feature request related to a problem? Please describe.

When looking at settings on child locks, the code slot name isn't populated.

Describe the solution you'd like

Populate code slot name on child locks with the code slot name of the parent locks corresponding code slot.

Describe alternatives you've considered

No response

Additional context

No response

[tykeal]

Slot names should already be getting set on child locks. You didn't provide any information as to what version of Keymaster you're using or type of lock. That information is important for us to be able to determine if this is an actual bug as it's something that should already be happening. I know this because I use it extensively with multiple different types of locks!

[bjh45964]

Thanks for the quick response, I wasn't thinking about this as a bug report :)

Keymaster version .5.2
Installation method: Home Assistant OS
Core: 2026.6.4
Supervisor: 2026.06.2
Operating System: 18.0

Locks are schlage zwave, mix of BE468 and BE469.

All of my child locks code slot names just show "unavailable".

[tykeal]

They're showing unavailable does the Override parent toggle show up and is it actionable? If you turn it on, does the slot become editable on the child lock? It shouldn't be showing as unavailable at all. The only time I can see that happening would be if the child lock wasn't currently manageable at all for some reason.

[bjh45964]

Override parent is visible and actionable. If I toggle Override parent, it does pull in the code slot info from the parent and is editable. Toggling back returns it to "unavailable"

I haven't made any changes to lock settings since maybe the first non-beta release (things have been stable!). I could rebuild a child and see if the behavior changes.

[bjh45964]

Removed and re-added a child lock. No change.
I also noticed the "Enabled" toggle is toggled off, I wonder if this is the actual issue. Locks are all working as expected in terms of code sync and zwave lock/unlock.

[tykeal]

Thanks for the extra detail — this helps narrow it down.

Here's what's going on under the hood: on a child lock, a code slot's Name field is deliberately shown as unavailable while Override parent is OFF. In that state the child slot simply inherits the parent's name internally, and the child's own Name entity is intentionally not editable (turning Override on is what "detaches" the slot and makes it editable — which is exactly the behavior you're seeing). The Enabled toggle being off is unrelated to the unavailable state.

Where this matters: the generated Keymaster dashboard is built to display the parent's Name row for a non-overridden child slot, so it should show the inherited name rather than unavailable. If you're instead looking at the child entity directly (e.g. on the device/entity page in HA settings), unavailable is expected there.

To confirm whether this is just an expectations mismatch or an actual dashboard bug, could you provide the following for one affected slot:

1. Where are you looking — the generated Keymaster Lovelace dashboard, or the device/entity settings page in HA?
2. The state of the child text.code_slots:<N>.name entity and the parent text.code_slots:<N>.name entity (the parent should hold the actual name).
3. The state of the child switch.code_slots:<N>.override_parent.
4. Screenshots of the parent slot and the corresponding child slot in question.

One note on the screenshots: if you have Keymaster configured to display PINs, please redact the PIN values before posting.

Thanks!