Waste Collection Schedule

repository·master·Indexed 24 days ago

https://github.com/mampfes/hacs_waste_collection_schedule

A custom Home Assistant component that retrieves and manages waste collection schedules from various service providers and integrates them into the Home Assistant Calendar. It supports schedules via provider websites, local ICS/iCal files, or user-defined date patterns. The integration supports a wide range of international providers across countries including Sweden, Switzerland, Germany, France, Hungary, Iceland, Ireland, and others, utilizing custom scrapers or iCalendar feeds.

Tokens
459.1K
Snippets
1.8K
Records
3.4K
Agent score
78%

What's inside hacs_waste_collection_schedule

  1. Overview of Waste Collection Schedule

    master

    Waste Collection Schedule is a custom Home Assistant component designed to retrieve waste collection schedules from various service providers. It supports schedules updated daily from provider websites, local ICS/iCal files, or user-defined date patterns.

    Key features include:

    • Automatic Calendar Integration: Populates the Home Assistant built-in Calendar with schedules.
    • Flexible Display: High flexibility in formatting and displaying information via entity cards or pop-ups.
    • Extensible Framework: Designed to be easily extended to support new service providers or other schedule-based services.
  2. View supported waste collection service providers by country

    master

    The hacs_waste_collection_schedule project supports various waste collection service providers across multiple countries. You can find specific documentation and source files for each provider within the /doc/source/ directory of the repository.

    Supported providers include:

    Hungary

    • FKF Budaörs (fkf.hu): See /doc/source/fkf_bo_hu.md
    • Győri Hulladékgazdálkodási Nonprofit Kft. (gyhg.hu): See /doc/source/gyhg_hu.md
    • MOHU Budapest (mohubudapest.hu): See /doc/source/mohu_bp_hu.md
    • ÉTH (Érd, Diósd, Ráckeresztúr, Sóskút, Tárnok) (eth-erd.hu): See /doc/source/eth_erd_hu.md

    Iceland

    • Kópavogsbær (kopavogur.is): See /doc/source/kopavogur_is.md

    Ireland

    • Greyhound Recycling (greyhound.ie): See /doc/source/greyhound_ie.md
    • Panda Waste (panda.ie): See /doc/source/panda_ie.md

    (Note: This list is partial based on the current document segment.)

  3. Key features and limitations of the Waste Management (WM) source

    master

    Capabilities

    • No account required: Uses WM's public guest lookup; no MyWM account is needed.
    • Municipal/Franchise support: Works for addresses where the township contracts with WM.
    • Comprehensive service coverage: Automatically returns all active services (Trash, recycling, yard waste, etc.).
    • Holiday awareness: Reflects adjusted pickup dates caused by holidays.

    Troubleshooting

    • API Key Rotation: WM's internal API keys are embedded in their web app and may rotate. If the integration stops working, it is likely due to a key rotation. Please report this by opening an issue in the repository.
  4. Identify supported waste collection service providers by country

    master

    The project supports various waste collection service providers across multiple countries. You can find specific documentation and source files for each provider organized by country.

    Supported countries include:

    • Japan
    • Liechtenstein
    • Lithuania
    • Luxembourg
    • Malta
    • Netherlands
    • New Zealand
    • Norway
    • Poland (and others in subsequent segments)

    Each entry in the documentation typically links to a specific source file (e.g., /doc/source/...) and identifies the provider's official website URL.

  5. View supported waste collection service providers

    master

    The project supports a wide range of waste collection service providers across multiple countries, including Poland, Portugal, Slovakia, Slovenia, South Africa, and Sweden. Each provider is associated with specific documentation and a source URL.

    To find information for a specific municipality or provider, refer to the documentation files listed in the README. For example, many Polish municipalities use the sisms.pl service, while others use smiecioplan.pl, kiedyodpady.pl, or custom local APIs.

  6. Identify supported service providers

    master

    The Waste Collection Schedule project supports various service providers globally, categorized by country and specific provider type.

    Generic Providers

    • Generic ICS / iCal File: For users who have a standard iCal/ICS calendar file.
    • Static source: For users with a fixed/static data source.

    Regional Providers

    Providers are organized by country, including:

    • Australia: Various City Councils (e.g., Brisbane, Melbourne, Sydney) and RecycleSmart.
    • Austria: BMV.at, Data.Umweltprofis, etc.
    • Belgium: Hygea, RecycleApp.be.
    • Canada: City of Toronto.
    • Germany: Numerous providers including Abfall.IO, BSR.de, and various local waste management authorities (Abfallwirtschaft).
    • Lithuania: Kauno švara.
    • Netherlands: HVCGroep, Ximmio.
    • New Zealand: Auckland, Christchurch, Wellington, etc.
    • Norway: Min Renovasjon, Oslo Kommune.
    • Poland: Warsaw, ecoharmonogram.
    • Sweden: Lerum.se, Sysav.se, etc.
    • Switzerland: A-Region.ch, Lindau.ch.
    • United States: PGH.ST, Republic Services, Seattle Public Utilities.
    • United Kingdom: Extensive list of local councils (e.g., Cambridge, Manchester, Sheffield, etc.).

    To find specific setup instructions for your local provider, locate your provider in the list and refer to its dedicated documentation page.

  7. Configure Impact Apps address via property_id or address components

    master

    When configuring an impactapps_com_au source, you can identify the property in two ways:

    1. Using property_id: An integer that can be found by inspecting network traffic when using the council's website to find the schedule.
    2. Using address components: Provide suburb (string), street_name (string), and street_number (string). These must exactly match the address information available via the council's website calendar.

    Note: You should use one method or the other; do not mix them if you want predictable results.

  8. Use the Multiple Source Wrapper to combine sources

    master

    The multiple source is a wrapper used to include multiple different waste collection sources within a single calendar entity.

    When to use it: Use this wrapper when you want all collected dates to appear in one single calendar. If you prefer to have separate calendar entities for different sources, do not use this wrapper; instead, pass multiple source objects directly to the top-level sources parameter in your configuration.

    Note on configuration syntax: When defining multiple sources of the same type (e.g., two ics sources), you cannot use the same key twice in a dictionary. Instead, you must use the list syntax for that key.

    waste_collection_schedule:
      sources:
        - name: multiple
          args:
            SOURCE_NAME: SOURCE_ARGS
            SOURCE_NAME: 
              - SOURCE_ARGS_1
              - SOURCE_ARGS_2