Skip to content

History / Hardware Compatibility

Revisions

  • docs: document the named command queue (#1189) New Command Queue page covering what the queue is for, how to name one, when to bother creating a queue entry, and the three behaviours that are not obvious from the UI: safety jumps the line but still takes its spacing, a newer decision replaces an older waiting one, and no command waits longer than its budget. The in-app Learn more links on both queue steps point at Configuration-Automation, so that page carries a real section rather than a bare pointer, plus the field row in the options table. Also corrected the assumption that sent the reporter down the wrong path in the first place: the Cover Group stagger only spaces commands the group itself dispatches, never a member's own sun tracking. Said so on the Cover Groups page where the stagger is documented, and on the Somfy RTS entry in Hardware Compatibility where someone hunting a collision problem will actually look. Nothing added to What's New. That belongs to the stable release; the feature is on develop and the new page says so.

    @jrhubott jrhubott committed Aug 5, 2026
  • docs: fix every broken internal wiki link Three classes, all pre-existing. **Anchor-only links (19).** `[text](#section)` does not resolve across pages in a GitHub wiki, which is why the convention bans them. All were same-page self-references, so each becomes `Page-Name#section`. **Links to pages that do not exist (4).** `UNIT_TESTS.md` is a repo file, not a wiki page — now an absolute URL to `docs/UNIT_TESTS.md`, per the convention for anything outside the wiki. `CLAUDE.md` is excluded from the repo entirely, so that link could never have resolved for anyone; it pointed at the notebook walkthrough, which has its own page. `Lovelace-Card` is now `Dashboard-Cards`. **Anchors that do not match any heading (16).** Mostly one missing hyphen: GitHub replaces each space in a heading individually rather than collapsing runs, so `Z height — protecting…` anchors as `z-height--protecting…` with two. Same for `Safety Priority — the Force Override replacement`. `Open/Close-Only Covers` loses its slash entirely, giving `openclose-only-covers`. Three pointed at Panel Card and Automation sections that no longer exist under any name. Those keep the page and lose the anchor — a reader lands somewhere correct, rather than somewhere I guessed.

    @jrhubott jrhubott committed Aug 3, 2026
  • docs: Bond RF bridge — open/close leaves current_position stale (#1026)

    @jrhubott jrhubott committed Jul 25, 2026
  • docs: document v2026.7.0 features (export/import services, venetian tilt refinements, Geometry step, device targeting)

    @jrhubott jrhubott committed Jul 7, 2026
  • docs: purge Force Override remnants from operations pages Delete the removed force_override_triggers sensor and phantom control_method sensor, drop force_override from decision-trace value lists and the trace example, recast Troubleshooting Step 5 as the safety Custom Position slot, fix custom-slot count 1-10, and correct the transit_timeout option key.

    @jrhubott jrhubott committed Jul 1, 2026
  • docs: note no-feedback cover resend fix (#779) in Known Limitations + Hardware

    @jrhubott jrhubott committed Jul 1, 2026
  • Updated Hardware Compatibility (markdown)

    @jrhubott jrhubott committed Jul 1, 2026
  • Make every hardware entry self-contained (symptom, mechanism, fix inline)

    @jrhubott jrhubott committed Jul 1, 2026
  • Make J4 and KNX skip-tilt entries self-contained (no section/issue deferral)

    @jrhubott jrhubott committed Jul 1, 2026
  • Call out Skip-Tilt Mode suppress for Somfy J4 + Shelly 2PM

    @jrhubott jrhubott committed Jul 1, 2026
  • Remove 'ships in the next release' notes from Hardware Compatibility

    @jrhubott jrhubott committed Jul 1, 2026
  • Add Hardware Compatibility page consolidating cover/hardware-specific settings

    @jrhubott jrhubott committed Jun 30, 2026