// the find
mampfes/hacs_waste_collection_schedule
Home Assistant integration framework for (garbage collection) schedules
A Home Assistant custom component that scrapes or parses waste/garbage collection schedules from several hundred municipal and private waste providers across Europe, Australia, and North America, then exposes them as Home Assistant calendar entities and sensors. It's for HA users who want to stop checking the council website and get bin-day reminders as automations instead.
The provider count is the real feature — hundreds of source files under waste_collection_schedule/source/, each a thin adapter that normalizes a council's ICS feed, JSON API, or HTML page into a common Collection model, so adding your own municipality is a well-trodden path (there's a documented CONTRIBUTING.md and a step-by-step guide). The shared service/ layer (AbfallIO, CitiesAppsCom, ArcGis, ICS, etc.) means dozens of councils that happen to use the same white-label backend share one implementation instead of duplicating scraping logic. They've also invested real effort in contributor tooling — Claude/Codex agent configs and GitHub chatmodes for issue triage, source implementation, and PR review — which matters given how many source-request issues a project like this generates.
Each source is a scraper or private-API client against a website that owes it no stability, so breakage from a council redesigning their bin-day page is a permanent, ongoing cost, not a one-time integration problem. The one-file-per-council pattern has produced genuine sprawl (500+ nearly-identical files), and the README itself flags that maintainers are largely underwater reviewing PRs rather than adding sources, so response time on new requests is slow. The in-progress 3.0 rework replacing hand-written sources with a declarative model is a tacit admission the current architecture doesn't scale, and it ships with a breaking change to waste-type label strings that will silently break anyone's existing automations matching on the old text. It's also inherently narrow: if your council isn't one of the ~500 listed, you get nothing until someone writes and merges a new source.