Skip to content

History / Automations

Revisions

  • Document safe external lock-screen shops New page covering the external kiosk/parental-control integration pattern: the reward event lifecycle with claim_id, when points actually move (wallet on approval, pool/jackpot at allocation), a safe automation that acts only on approval, and the sensor-attribute alternative with its two limits. Also adds claim_id to the reward approved/rejected rows in Automations and links the page from Home.

    @tempus2016 tempus2016 committed Aug 10, 2026
  • docs: document 15 missing bus events, fix badge sensor id and stale counts - Automations is the canonical event reference and was missing 15 of the 36 events TaskMate fires: the whole mandatory-miss set, allowance, family goal, season champion, undo, and every v5.0.0 event (chore expired, roulette spun, unlock started/ended, scheduled change applied, guest archived, read aloud). Payload fields taken from each async_fire call. - Achievement Badges and Sensor Reference gave the per-child badge sensor as sensor.taskmate_badges_<child>. It is sensor.taskmate_<child>_badges. - Notifications said the routing matrix has 6 built-in types; there are 15, and its bus-event table listed only 11 of them. - Notifications' migration section still pointed at the removed config flow. - Chores had a note saying due days are set via the config flow, described 'Add Multiple Chores' rather than Bulk add, and its field table predated the weather, scheduled-change and visibility sections. - Visibility Operators Reference omitted the default None operator and the attribute-matching fallback.

    @tempus2016 tempus2016 committed Jul 22, 2026
  • 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
  • Document v4.4.0: allowance ledger, family goals, chore dependencies, leaderboard seasons, quiet hours, reminder escalation, monthly report, to-do lists, config number/select entities, voice intents, ICS subscription feed, blueprint pack, negative-balance policy, photo gallery card; add 9 pages; update Services/Settings/Sensors/Dashboard-Cards reference; bump index to 4.4.0 (20 cards)

    @tempus2016 tempus2016 committed Jun 26, 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
  • Update wiki for v3.6.2: add timed tasks, task groups, bonus subtasks, admin panel pages; update 13 existing pages with missing features

    @tempus2016 tempus2016 committed May 4, 2026
  • Add Settings, Localization pages; card selection guide; calendar event format; clarify assignment/visibility/claim_allowance

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

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

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

    @tempus2016 tempus2016 committed Mar 23, 2026