docs: home page lists every page the sidebar does
docs: Virtual locks are a credential store, not just a test double
docs: add External Keypads and note the Virtual lock's second use
docs: name the page Z-Wave JS UI (MQTT)
docs: add zwave-js-ui MQTT provider page
Documents the new Z-Wave JS UI (MQTT) provider (bridged via zwave-js-ui's
MQTT discovery gateway, distinct from the official websocket zwave_js
provider), and links it from the nav and integrations list.
docs: delete the Notifications stub
One paragraph from years ago that cited a wrong event name
(lock_code_manager_state_changed; the event is
lock_code_manager_lock_state_changed) and predated the tools that now
answer the question: the Slot Usage Notifier blueprint and the per-user
event entities, both covered by Blueprints and
Tracking-lock-state-change-events. Sidebar and Home links removed with
it.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
docs: finish the 5.0 pass — integration and developer pages
The "bring the wiki up to 5.0" commit covered the user-facing pages but
left the per-integration pages, the developer pages, and a handful of
smaller ones on the 4.x slot model. Every claim below was verified
against the 5.0.0-tagged code rather than carried over.
Integration pages:
- Z-Wave — users-first framing; Set/Clear PIN go through the driver's
unified access_control API, not the set/clear_lock_usercode services;
PIN length bounds are enforced in the PIN field before a write.
- Matter, Schlage, Akuvox — tag examples reframed onto users ("an LCM
user named Alice whose internal slot number is 3"), version-history
heading framing dropped. ZHA and Zigbee2MQTT needed nothing: their
slot references are device-level facts and their cited symbols
(async_set_usercode, UNREADABLE_CODE) still exist.
Developer pages (Architecture, Provider-State-Management,
Adding-a-Provider, Development-Guide), audited method-by-method:
- async_set_credential returns WriteResult (CONFIRMED / NO_CHANGE /
OPTIMISTIC), not bool; the OPTIMISTIC path drives the
unverified-slot / PENDING_CONFIRMATION lifecycle.
- Coordinator data is keyed by CredentialAddress, not bare slot ints.
- Push providers override setup/teardown_push_subscription; the
subscribe/unsubscribe wrappers are @final.
- async_is_integration_connected is async with a base default;
async_get_users takes a slots scope; slot teardown clears the
credential by default (the #1453 fix), it is not a no-op.
- credential_index_follows_slot documented (pinned everywhere except
Matter, which lets the lock allocate).
- Z-Wave is one native-user provider for both User Code CC and User
Credential CC; exception routing rewritten around the slot circuit
breaker and repair issues; number_of_uses entity row removed.
Smaller pages: Using-Condition-Entities rewritten onto name-keyed users
and the `condition` key (examples still showed slot-keyed YAML with
`entity_id` and the removed number_of_uses check, and a card example
still used the deprecated lcm-slot type); Advanced-Usage no longer tells
you to pick slot ranges; Adding-and-Removing-Locks, the activity-log
page, scheduler-component notes, Home, and debug-logs reframed onto
users. Dashboard/view-level condition_helpers examples deliberately keep
slot-number keys — that is still the real strategy config shape.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
docs: add migrating-from-keymaster page
Walks through the practical steps to move from keymaster to LCM: the PIN
cleanup situation (keymaster does not call clear_usercode on slot or entry
removal), feature mapping (notifications/access-count/date-range/day-of-week
limits map to LCM blueprints and condition entities), a 10-step migration
procedure, conversion recipes for each keymaster restriction type, provider
parity, and what doesn't translate (the auto-generated Lovelace dashboard,
autolock entity model, entity naming).
Wired into the Getting Started section in both the sidebar and the home
page.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
docs: split UI page into hub + UI-Strategies + Custom-Cards; update options
The single Add-a-UI-for-lock-code-management page was conflating four
distinct surfaces (dashboard creation, four strategies, two cards, code
display modes, legacy mode) into 264 lines that were hard to scan and
out of date in several places.
Split into three pages along the natural strategy/card seam:
- Add-a-UI-for-lock-code-management — slimmed to a hub with a "which
approach should I pick?" decision table and the dashboard quick-start.
URL preserved so external links continue to resolve.
- UI-Strategies — dashboard strategy, view strategy, slot section
strategy, lock section strategy, legacy mode, and the deprecated
option mappings. Common audience: "let LCM generate UI from my config".
- Custom-Cards — slot card, lock codes card, code display modes, and
the visual-editor note. Common audience: "I'll compose my own dash".
While restructuring, document options that were missing from the old
page or had drifted from source:
- condition_helpers (all four strategies + slot card) — extra helper
entities surfaced inside the slot card. Schema differs across
strategies (per-config-entry vs per-slot vs flat array).
- show_lock_count (slot card + slot section strategy) — header badge.
- collapsed_sections accepts both `condition` and `conditions`.
- Slot card status badges include `pending sync` and `suspended`.
- Lock codes card sync indicators distinguish in-sync, out-of-sync,
syncing, and suspended.
- Inline-edit on unmanaged slots in the lock-codes card calls
set_usercode/clear_usercode (cross-link to Services-and-Actions).
Sidebar gains a new UI section listing all three pages; Home.md mirrors
the change. Configuration-Structure stays under Getting Started.
docs: add Services and Actions page; list ZHA + Z2M; remove Number of Uses
- New Services-and-Actions page documenting all six registered actions
(set_usercode, clear_usercode, set_slot_condition, clear_slot_condition,
hard_refresh_usercodes, generate_pin) with parameters, errors, and
example automations. Linked from sidebar and Home under Features.
- Add ZHA and Zigbee2MQTT to the Supported Integrations list on Home.md
(already present in the sidebar; Home was out of date).
- Delete Using-"Number-of-Uses".md — the feature was removed in 2.0; the
Slot Usage Limiter blueprint is the replacement. Update the dangling
reference in Blueprints.md to plain text.
Add FAQ: PIN codes visible in activity log
Add Z-Wave wiki page, reorganize sidebar, add HA docs links, add Blueprints to nav
Add Matter, Schlage, Akuvox wiki pages; update blueprints and deprecation notices
Add Browser Console Logs troubleshooting page
- New page with instructions for Chrome, Firefox, Safari, and mobile
- Guidance on capturing and sharing console output
- Updated troubleshooting index, sidebar, and home navigation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Revert blueprint wiki changes pending blueprint PR merge
Reverts Blueprints page, sidebar/home nav entries, and cross-references
in Using-Condition-Entities and Using-Number-of-Uses. Blueprints.md
remains on disk as an untracked file for re-adding when PR #902 merges.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add Troubleshooting pages and Blueprints wiki content
- Add Troubleshooting overview page with pre-filing checklist
- Add Debug Logs subpage with configuration.yaml instructions
- Add Device Diagnostics subpage with download steps
- Add Blueprints page with import badges and setup docs
- Update sidebar and home page navigation
- Add blueprint cross-references to condition entities and number of uses pages
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add documentation for excluded condition entity integrations and optimistic updates
- Add Unsupported-Condition-Entity-Integrations.md for scheduler-component
- Update Adding-a-Provider.md with optimistic updates guidance
- Update Using-Condition-Entities.md with useful integrations section
- Update Home.md and _Sidebar.md with new page links
Add Unsupported Integrations wiki page
Document why ESPHome, Matter, and Yale/August integrations cannot
currently be supported due to library limitations.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Fix broken link to condition entities page
Add developer docs and organize sidebar
- Add Development-Guide.md with architecture overview and dev container setup
- Add Adding-a-Provider.md with step-by-step tutorial
- Add Provider-State-Management.md with poll/push modes documentation
- Add _Sidebar.md for organized navigation
- Update Home.md with structured sections
- Update Supporting-new-lock-integrations.md to redirect to new docs