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>
Document condition helpers, date range blueprint, and condition linker
Revert "Document date range condition, condition linker blueprints, and condition_helpers config"
This reverts commit 5422c3a6e1b7d06f612ecced404e218e4f193c2f.
Document date range condition, condition linker blueprints, and condition_helpers config
Co-Authored-By: Claude Opus 4.6 (1M context) <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
Update documentation for v1.0.0 release
Breaking changes documented:
- #785: calendar → entity_id (supports multiple entity types)
- #788: Event entity event_types now use lock entity IDs
Changes:
- Replace "Using a Calendar" page with comprehensive "Using Condition Entities"
- Document all supported entity types (calendar, schedule, input_boolean, switch, binary_sensor)
- Add migration guides for breaking changes
- Document slot event entity and automation examples
- Update Configuration Structure with new entity_id syntax
- Update sidebar navigation
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>