Skip to content

History / Installation

Revisions

  • docs: fix wrong entity id, stale install instructions and card_design options Checkpoint from a full page-by-page read. - sensor.pending_approvals does not exist. The entity is sensor.taskmate_pending_approvals. The wrong id appeared 11 times across 8 pages, including copy-paste automations and a card config option, none of which could ever have worked. - Installation still said TaskMate is not in the HACS default store and told users to add a custom repository. It was accepted into hacs/default on 2026-06-22; the README has been right and the wiki wrong for a month. - The YAML-mode resource list was missing four cards (routine, badges, family goal, photo gallery), and the globally-registered modules were listed as localize/config-sounds/attr-resolver when they are actually config-sounds/localize/design — attr-resolver is a normal card resource. - Configuration Entities listed the card_design select without accessible. - Managing Rewards still described a config-flow 'Action selector' and 'Add New Reward' menu. - Tidied doubled horizontal rules I introduced in earlier edits.

    @tempus2016 tempus2016 committed Jul 22, 2026
  • docs: stop sending readers to a configuration UI that was removed in v4.0.0 Fourteen pages still documented the old options/configure flow — "Settings → Devices & Services → TaskMate → Configure → Manage Chores", a Step 1/Step 2 wizard, a four-item menu. None of that exists. config_flow.py has exactly one step (async_step_user) and does nothing but initial setup. Admin-Panel.md has said the flow "was retired in v4.0.0" the whole time, while the rest of the wiki kept pointing at it — including line 1 of Settings.md and the first walkthrough a new user reads in Getting Started. Visibility Configuration Guide was the worst of them and is substantially rewritten. Beyond the dead setup flow it also had: - No mention of the "None" operator, which is what every chore starts with. - A wrong claim that an unavailable entity defaults to visible. Only a MISSING entity short-circuits to visible; "unavailable" is an ordinary state string that fails the comparison, so the chore hides. That is the opposite of what a reader was told to expect. - Two "common mistakes" that contradicted each other and the code — one said matching is case-insensitive, the next implied case matters. It is case-insensitive. - No mention that a value beginning >=, <=, >, < or != overrides the operator dropdown, or that attribute values are matched when the state doesn't match. Both are real behaviours in _is_visibility_entity_active. Also corrected: card counts of 17 and 18 in Getting Started, Installation and Card Design Styles (21), and [[Configuration Guide]] links on two pages, which pointed at a page that has never existed.

    @tempus2016 tempus2016 committed Jul 22, 2026
  • docs: illustrate the wiki — 44 new screenshots across 59 pages Image coverage goes from 6/71 pages to 65/71, and from 8 images to 52. Captured from the live dev instance: every admin panel tab (including the Audit tab, which only became reachable in the panel fix that accompanies this), all four Insights reports, all 21 Lovelace cards, the five card design styles side by side, and the Home Assistant surfaces the reference pages describe — the integration entry, Developer Tools states, and the to-do lists. Two things worth recording about how these were produced: - Scaffolding data in the dev instance (I558 Step A, E2E Test Quest, E2E687 Cousin) would have looked unprofessional in a public wiki, so the capture relabels it to realistic household chores. That relabelling happens on an in-page copy of the state only — nothing is written back, and the dev instance keeps its issue-reproduction data intact. - Child-scoped cards pick the child who actually has chores outstanding, otherwise half of them would have documented their own empty state. The design-styles image was replaced rather than added: the previous one showed four styles and predated Accessible, so its caption was wrong too. Six pages are still text-only — Automations, FAQ, Services, Troubleshooting, Visibility-Operators-Reference and Voice-Assistants. All six are reference tables or prose where a screenshot would decorate rather than explain.

    @tempus2016 tempus2016 committed Jul 22, 2026
  • docs: comprehensive v4.0.0 update — levels/XP, quests, challenges, avatars, celebrations, difficulty tiers, photo proof, vacation mode, swaps, points economy, gifting, audit log, backup/restore, weekly digest; update chores/rewards/notifications/admin/services/sensors/settings; reorganize Home index

    @tempus2016 tempus2016 committed Jun 17, 2026
  • Complete wiki audit — document all remaining features, services, internals

    @tempus2016 tempus2016 committed Apr 21, 2026
  • Updated Installation (markdown)

    @tempus2016 tempus2016 committed Mar 25, 2026
  • Updated Installation (markdown)

    @tempus2016 tempus2016 committed Mar 23, 2026
  • Created Installation (markdown)

    @tempus2016 tempus2016 committed Mar 23, 2026