fix: autolock timer persistence, race conditions, and throttle gaps

custom_components/keymaster/coordinator.py

@@ -918,6 +918,13 @@ async def _setup_timer(self, kmlock: KeymasterLock) -> None:
                 call_action=functools.partial(self._timer_triggered, kmlock),
             )
 
+        if (
+            kmlock.autolock_enabled
+            and kmlock.lock_state == LockState.UNLOCKED
+            and not kmlock.autolock_timer.is_running
+        ):
+            await kmlock.autolock_timer.start()
+
     async def _timer_triggered(self, kmlock: KeymasterLock, _: dt) -> None:
         _LOGGER.debug("[timer_triggered] %s", kmlock.lock_name)
         if kmlock.retry_lock and kmlock.door_state == STATE_OPEN:

custom_components/keymaster/switch.py

@@ -5,6 +5,7 @@
 import logging
 from typing import Any
 
+from homeassistant.components.lock.const import LockState
 from homeassistant.components.switch import SwitchEntity, SwitchEntityDescription
 from homeassistant.config_entries import ConfigEntry
 from homeassistant.core import HomeAssistant, callback
@@ -292,6 +293,15 @@ async def async_turn_on(self, **_: Any) -> None:
                     self._kmlock.autolock_min_day = DEFAULT_AUTOLOCK_MIN_DAY
                 if self._kmlock.autolock_min_night is None:
                     self._kmlock.autolock_min_night = DEFAULT_AUTOLOCK_MIN_NIGHT
+                if (
+                    self._kmlock.lock_state == LockState.UNLOCKED
+                    and self._kmlock.autolock_timer
+                    and not self._kmlock.autolock_timer.is_running
+                ):
+                    await self._kmlock.autolock_timer.start()
+                    self.coordinator.async_set_updated_data(
+                        dict(self.coordinator.kmlocks)
+                    )
             if (
                 self._property.endswith(".enabled")
                 and self._kmlock

docs/plans/2026-03-10-strategy-config-validation-design.md

@@ -0,0 +1,65 @@
+# Strategy Config Validation Design
+
+## Problem
+
+The dashboard, view, and section Lovelace strategies accept config objects but lack
+full schema validation. The view and section strategies have some inline checks
+(e.g., requiring one of `config_entry_id`/`lock_name`), but:
+
+- The dashboard strategy does no validation at all.
+- No strategy rejects unknown keys (typos pass silently).
+- Type validation is missing (e.g., `slot_num` could be a string).
+- Validation logic is scattered and inconsistent.
+
+## Design
+
+### New module: `validation.ts`
+
+A centralized validation module with three exported functions:
+
+```ts
+validateDashboardConfig(config): ValidationResult
+validateViewConfig(config): ValidationResult
+validateSectionConfig(config): ValidationResult
+```
+
+**Return type:**
+```ts
+type ValidationResult = { valid: true } | { valid: false; error: string };
+```
+
+#### Dashboard validation rules
+- `type` must be `'custom:keymaster'`
+- No other keys allowed
+
+#### View validation rules
+- `type` required, must be `'custom:keymaster'`
+- Exactly one of `config_entry_id` or `lock_name` (not both, not neither)
+- Allowed optional keys: `icon`, `path`, `theme`, `title`, `visible`
+- All provided values must match expected types
+- Unknown keys rejected
+
+#### Section validation rules
+- `type` required, must be `'custom:keymaster'`
+- `slot_num` required, must be a number
+- Exactly one of `config_entry_id` or `lock_name`
+- No other keys allowed
+- All provided values must match expected types
+
+### Strategy changes
+
+Each strategy's `generate()` calls its validator first. On failure, returns an
+error card/section using the existing `createErrorView`/`createErrorSection`
+pattern. Existing inline validation in view and section strategies is replaced
+by the centralized validators.
+
+### Error behavior
+
+Validation failures return error cards (markdown cards with error messages),
+consistent with the existing pattern. No thrown errors.
+
+### Tests
+
+- `validation.test.ts`: Unit tests for each validator covering valid configs,
+  missing required fields, unknown keys, wrong types, and edge cases.
+- Existing strategy tests updated to verify validation integration.