Parallel Development Paths

  As of August 13, 2026, the dynamic task scheduling concept is being developed in two separate repositories with different goals and priorities.  

Version 3: Standalone Web Application - https://github.com/nremey/dynamic-Cleaning-Schedule-in-Home-Assistant

It serves as a playground for new ideas, scheduling concepts, user interface experiments, and feature development. The standalone website architecture allows changes to be implemented quickly and with few external constraints. New functions can be tested, modified, or even completely reworked if an idea turns out to be better in practice or removed if deemed not got.   The primary goals of Version 3 are flexibility, experimentation, and exploring new concepts.

Version 4: Home Assistant Integration - https://github.com/nremey/remeys_taskboard_integration

  Version 4 is a more focused approach. In some ways, it is a return to the roots of the project, concentrating primarily on task scheduling, task management, and task presentation within Home Assistant.

The focus of Version 4 is long-term stability, seamless Home Assistant integration, and a user experience that feels like a native part of the Home Assistant ecosystem. While visual customization, themes, dashboard layouts, and usability improvements will continue to evolve, the underlying task scheduling logic is expected to remain comparatively stable.  

Why Two Repositories? and: No Planned Merge

  Both projects share the same core vision: managing recurring household tasks through dynamic scheduling. However, they are not different releases of the same application anymore. They have evolved into two independent development branches, as mentioned. Think of Version 3 as the laboratory and Version 4 as the production-oriented implementation.    Due to their fundamentally different architectures, the projects have effectively become two independent forks. While ideas and concepts may influence each other, they are not expected to converge into a single codebase, and a future merge through pull requests is currently not considered realistic.

In practice, this means:  

• New ideas will often appear in the web app approach (aka currently Version 3) and prioritizes flexibility, experimentation, and rapid iteration.
• Successful concepts may later be adapted for the integration approach (aka currently in Version 4) and prioritizes stability and Home Assistant integratio
• Both projects continue to evolve in parallel and influence each other.

The update philosophy is also different:  

• Version 3: Manual installation and updates. You decide when, how, and even if you want to update. This provides maximum control, especially when testing experimental features.
• Version 4: Installed and updated through Home Assistant / HACS. Updates are delivered through the normal Home Assistant workflow, making it easier to stay current.

so in short: choose wisely, what you want or willing to test

Version 3 is out

check the ReadMe there for more Info about functions, changes, Screenshots.

Choreboard / Cleaning Schedule (Version 2) - Overview

This single-file web app (index_taskboard.html) is a task board for cleaning and household chores in Home Assistant.
It is hosted under /config/www and opened via /local/....
Task changes can be stored locally and optionally written back to Home Assistant via webhook (data.updated.js).

Version 2.0 note:

The newest release is inside remeys_choreboard.zip. Installation steps are provided in README_english.md and README_german.md within the ZIP.

Core Features

• Task dashboard grouped by Area with collapsible sections and due-date logic
• Mark tasks as done (sets date to today and recalculates)
• Sorting and filtering:
  • by due date or alphabetical order
  • search across Task and Area
  • time filters (overdue, next X days, all)
• Add, edit, and delete tasks
• Frequencies in days, weeks, or months
• Per-task month rules:
  • ignore specific months or restrict to selected months
• Optional icon picker (Iconify, including mdi:*)
• Theme switching: Dark / Light / System
• Automatic synchronization through Home Assistant webhook with cache-buster reload
• HA sensor integration (one sensor per task as due/done indicator)
  • warning if sensor is missing
  • warning on rule conflicts
  • sensor friendly name, value, and unit shown on task cards
  • normalization of sensor state strings (e.g. On/on/true/true )
• Calendar views (week, month, list)
  • navigation and separate overdue sidebar
  • drag and drop tasks between calendar days (updates due date)

User Management and Personalization

• Create, edit, and delete users
• Profile fields: name, role, stars, motto, avatar
• Switch active user via user bar
• Optional task assignees:
  • visibility by user, role, and mapped group
  • assignment suggestions/autocomplete
• Home Assistant user mapping:
  • mapping between HA users and internal users
  • optional role/group filter
• Card metadata:
  • "Last done by"
  • assignees shown directly on cards for admins (admin sees all tasks no matter the Assignee)
• Per-user theme:
  • custom colors/CSS per user
  • stored under usersettings/

Additional Enhancements

• Automatic runtime path detection (BASE_PATH, HA_ORIGIN, etc.), no manual HTML path setup required
• Optional panels:
  • Quick Notes (shared across users)
  • External Home Assistant calendar events
• Quick Notes include a small rich-text editor (e.g. bold, italic, list, font size)
• Task visualization:
  • progress gauge as ring or bar
  • overdue cycles displayed as +N
  • history as heatmap or timeline (configurable per user)
• UI/settings updates:
  • "User Management" renamed to "Settings"
  • tabs reorganized (User / Setup / Display)
  • improved icon selection
  • paperclip indicator for task notes (hit the paperclip and the Note of the task is shown)
  • small usability and layout improvements

Known issues (to be addressed in upcoming versions):

• The calendar view (week and month) looks poor on small screens. There’s no nicer way to put it. Open to suggestions.
• Having many tasks — either in the overdue section or grouped within a single day — can distort the month layout. It’s unclear whether this is primarily a layout limitation or simply an edge case caused by an excessive number of overdue tasks (not that this would ever happen to me, of course 😉).
• Open issue since v1.2: sorting for sensor-indicated tasks by due/done/warning is not fully resolved

Some Impressions