Managing guests: a shared booking calendar doesn't revoke a past guest
calendar.bookings is on during every booking, so keeping a guest with it as
their condition gave their code back during later bookings. Recipe 1 now says
the remove automation is what revokes the code, and Pattern 2 says to add the
guest when their stay starts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
881f3fa
Blueprints: a short index that links to BLUEPRINTS.md
The full blueprint reference now lives in the repository's BLUEPRINTS.md
(#1788), next to the blueprint YAML. This page keeps one section per
blueprint, so existing links still land, plus the guidance that spans
blueprints: finding a slot number and combining blueprints with conditions.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ca5b193
Home: list the new subpages and correct stale descriptions
Nest the External Keypads and Managing Guests subpages as the sidebar does,
and describe Custom Cards, the events page, the Development Guide and
Provider State Management as they are now. Architecture no longer lists the
Supporting new lock integrations redirect stub as a guide.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
8714f44
Provider pages: document each primitive once, and match the code
Provider State Management is the reference for every provider primitive and
the slot teardown hook; Adding a Provider keeps short examples that link to
it and collapses the complete example; Architecture links instead of
listing the primitives again.
Corrects what disagreed with the code: async_fire_code_slot_event requires
credential_type, the event is lock_code_manager_credential_used, ownership
is slot_tag's decision rather than parse_tag's, legacy adoption checks the
lock's pre-4.0.0 position, a kept user keeps its display name on release,
async_setup runs on every reload, and _require_readable_pin is the base's
check, not a provider helper.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0bc1ad6
Managing Guests and Rentals: move the recipes to a subpage
The overview keeps the patterns, keeping guests apart from household codes,
and things that bite; the three paste-able recipes and what they share move
to Managing-Guests-and-Rentals-Recipes, nested under it in the sidebar.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
950167b
Services and Actions: name the provider methods subclasses implement
async_set_usercode and async_clear_usercode are BaseLock orchestration that
providers must not override; the methods a provider implements are
async_set_credential, async_delete_credential and the rest.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2b2ff84
External Keypads: split the recipes into ESPHome and Z-Wave subpages
The overview keeps the action, what a valid code produces, security, and
things to know; each device's recipes get their own page, nested under it in
the sidebar.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cb9bd34
External Keypads: Z-Wave alarm keypads (Ring Alarm Keypad v2) arming Alarmo
Entry Control keypads store no codes; each entry arrives as a
zwave_js_notification event, so they are code sources for use_credential.
Covers the button event types, an Alarmo arm/disarm automation, the Alarmo
code settings it needs turned off and what that gives up, keypad feedback,
and keeping the code out of the recorder. Prompted by #858.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
e0b2feb
Zigbee2MQTT: where to keep keypad codes on a lock that can't report
Carried over from the README footnote, which is being removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bd13a8d
Using Condition Entities: presence, groups, and other states via templates
Old-style group.* entities (such as groups of people) and other non on/off
entities are used through a template binary sensor, which also covers
inverted conditions. Clarify that UI-created binary sensor and switch groups
work directly. Prompted by #1768.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ea0f33b
docs: Lock Code Manager 7.0
Bring the wiki up to date with 7.0.0 (the clean-room core):
- New pages: Upgrading to 7.0, Repair Issues; linked from Home and the sidebar.
- Developer pages (Architecture, Provider State Management, Adding a
Provider, Development Guide, Configuration Structure) rewritten around the
per-lock worker, the core store, and the sync/model/ha/providers layout.
- Integration pages: Zigbee2MQTT locks that can't report their codes,
Matter fabric-aware release and name limits, no restart rewrites,
Z-Wave removal and name fallback, ZHA 0xFF, Akuvox/Schlage leave
untagged codes alone, credential_used events.
- User pages: refused lock adds, forget_reporting, self-lifting holds,
PIN masking salt, LCM diagnostics, event entity attributes, keymaster
migration, card states, UI strategy options, blueprint variables.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0147zKneN1dB51wr1z5orrDQ
54306f1
docs: Zigbee2MQTT -- one more code read before a lock is classified
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
930de6d
docs: the unconfirmed sync state
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
58f048c
docs: Zigbee2MQTT -- an answering lock is never reclassified
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
4e47478
docs: Zigbee2MQTT -- adding users to a lock that doesn't report its codes needs consent
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
3cb80f8
docs: Zigbee2MQTT -- recommend last_seen, and explain locks that don't report their codes
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
380694b
docs: prepare the wiki for 6.0
Users live in config subentries: Configure edits only the locks, and Add
user offers one user or a pasted block. The four slot-addressed actions and
the lock_state_changed event are removed, with their replacements listed
where people will look for the old names. The Condition Linker takes a
name. A new Upgrading to 6.0 page covers the migration, the removals, the
disabled-by-default PIN in-sync sensor, and the fixes since 5.5.5.
Also corrects drift found on the way: removing a lock has cleared its PINs
since 5.0.0, the usage limiter and notifier take entities rather than slot
numbers, and the keymaster steps still described slot ranges.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
34a0800
docs: add_user and delete_user take lists, with the single-user shorthand
157f898
docs: the four name-addressed actions, and ESPHome is supported without a provider
ce74274
docs: document set_credential and clear_credential, and deprecate the usercode pair
d65618d
docs: the sidebar is bare links; show the UI hub by nesting, not prose
91f8e99
docs: home page lists every page the sidebar does
ba563fc
docs: paste-able guest recipes, and fix a fragment that referenced an undefined variable
66ad48f
docs: reconcile every blueprint's inputs with what ships
4f9c7f1
docs: a keypad-only setup needs no lock (5.3.0)
20e5189
docs: Virtual locks are a credential store, not just a test double
8b3ffdc
docs: add External Keypads and note the Virtual lock's second use
4702a6b
docs: Manual gateways run api-only; gateway binding comes from discovery data
4fd04b0
docs: name the page Z-Wave JS UI (MQTT)
b8a9102
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.
3e2f2d0