zigbee-ux Phase 4. Operator overlay (settings zigbee_custom_roles / zigbee_custom_recipes) merges over the Python base. Custom ROLES are pure routing labels — a climate/safety kind slots into fleet handling. Custom TASKS are datapoint-only (when=None → evaluate_device_policies no-ops; no actuator/banner). Slug-validated, built-ins refused. New ZigbeeCatalogCard on Settings → Device manages them on the SettingsTable primitive. Tests: test_zigbee_policies.test_custom_role_overlay / test_custom_recipe_is_datapoint_only. NOTE: actuator/banner task authoring stays code-defined.
Journey event · 5 Sep 2026
Zigbee role/recipe catalogs are hardcoded Python, not operator-extensible
zigbee-ux Phase 4. Operator overlay (settings zigbee_custom_roles / zigbee_custom_recipes) merges over the Python base. Custom ROLES are pure routing labels — a climate/safety kind
● state copied from the tracker, never improved
● event date 2026-09-05
| Event date | 2026-09-05 |
| Version found | |
| Version fixed | |
| Expected kit firmware | |
| Release file | |
| SHA-256 | |
| Served count | |
| Source | https://app.notion.com/3d22b4cda370816d87d7eaa830c50e28 |
All events · DSC · CannaLib · Site · Firmware releases
Empty rows are honest
A blank cell means the tracker has no value for it. Nothing on this page is filled in to look complete.