Custom component Afvalbeheer - Support for multiple waste collectors

[Johan_L (Johan)]

How does the custom mapping function works?

At the moment i only see a plastic icon for “papier-pmd” and the default eye for Duobak and Tuinafval.

My guess is that I need to use something else instead of restafval

afvalbeheer:
  wastecollector: MijnAfvalwijzer
  resources:
    - Duobak
    - Papier-PMD
    - Tuinafval
  postcode: ????!!
  streetnumber: ##
  upcomingsensor: 1                # (optional)
  dateformat: '%d-%m-%Y'           # (optional)
  dateonly: 0                      # (optional)
  name: ""                         # (optional)
  nameprefix: 1                    # (optional)
  builtinicons: 1                  # (optional)
  builtiniconsnew: 1
  dutch: 1                         # (optional)
  custommapping:
    Duobak: restafval

[Pippyn]

You should not use the custom mapping for the icons. It is there to correct the few errors made by the data providers.

[mountainbikert]

try this:

sort:
  method: entity_id
  attribute: sort_date
  reverse: true

[Thunderbold (Roland Verheijden)]

Please add: Afvalkalender | Gemeente Venlo

5922TE is post code and 32 is house number. Any valid combinations in Venlo work.

[Pippyn]

You’ll need to contact the Venlo municipality to open up their API. Because I cannot access it right now.
See Support for Venlo (venlo.nl) · Issue #457 · pippyn/Home-Assistant-Sensor-Afvalbeheer · GitHub

[DriesA (Dries)]

Hi Pippyn,

Thanks for creating this custom component. I really love it!

I think for Limburg.net, a type of waste fraction is missing.

When I check the waste calendar on Limburg.Net, I see that they will collect “keukenafval” next Friday:

When I print the waste types, I see keukenafval is not listed:

[Pippyn]

I’ll look into it. Please open an issue on the github repo and provide your config with a working address.

[crosseel]

Is there a way to show opening hours for the local recycling park based on the given location in yaml?

[barrelful]

The HACS is working great, but I am not sure there is an option to send on Android app notifications from Home Assistant App alerting me to put the paper out for tomorrow, did someone already configure that?

[bram13134]

@Pippyn I love your component and I use it to remind me in different ways. But now my muniicipality has decided to move to a different collector: RD Maasland. Is it possible to add support for this collector? Or is this a collector that is already there but under a different name? I couldn’t find any info about their API.

[weemaba999 (Bart Weemaels)]

Hi @Pippyn ,

Are you aware of any issues regarding the integration after installing the 2025.03 update ? My entities are not available anymore.

Kr,

Bart

[Pippyn]

@bram13134 Can you please make an issue on my github repo.
Also include an address for me to test with.

[Pippyn]

No, I wasn’t aware. Please create an issue on my Github repo. Include your config, an address and any related errors.

[sammyke007 (Sammy Verdonck)]

I can confirm.

Edit: it’s working again…

[Marijn]

The same issue that I read about many times I also have, I can’t get those icons working… This my current configuration:

afvalbeheer:
wastecollector: Limburg.NET
resources:
- restafval
- gft
- papier
- pmd
postcode: 0000
cityname: ABCD
streetname: ABCD
streetnumber: 1
upcomingsensor: 1
dateformat: “%d-%m-%Y”
nameprefix: 1
builtiniconsnew: 1
dutch: 1

0000 is off course my zipcode, and ABCD is replaced with my city and streetname.

I’ve tried replacing “builtiniconsnew: 1” with “builtinicons: 1”, but nothing changes. I’ve restarted, HA has been upgraded since I started playing around with it, it keeps showing up like this:

I’m not sure what else to try…

[Pippyn]

The icons are dark, try a light theme

[Marijn]

Damn… Sometimes it’s right in front of you and you don’t see it Is there a possibility to get dark mode supported? Can I help?

[sammyke007 (Sammy Verdonck)]

Anyone else using RecycleApp (BE) where the fetching of data stopped working recently?

[Pippyn]

Afvalbeheer v6.0.0 Released - Major Config Flow Update!

Hi everyone!

I’m excited to announce the release of Afvalbeheer v6.0.0, bringing some major improvements to the popular Dutch and Belgian waste collection integration!

What’s New in v6.0.0

Config Flow UI Support

The biggest change in this release is the addition of Config Flow support! You can now configure the integration entirely through the Home Assistant UI:

• Step-by-step wizard for easy setup
• Visual waste collector selection from 50+ supported collectors
• Interactive address configuration with validation
• Resource selection with checkboxes for different waste types
• Advanced options configuration through the UI

Important: YAML configuration is now deprecated and will be removed in a future version. The integration will automatically import existing YAML configurations, but please migrate to the UI configuration for future updates.

Enhanced Architecture

• Complete refactor of sensor setup logic
• Improved error handling and validation
• Better entity cleanup when configuration changes
• More robust data management

Improved User Experience

• Clear validation messages for invalid configurations
• Better support for special cases (Limburg.NET, RecycleApp requirements)
• Streamlined entity naming and management

Still Supports All Your Favorite Features

• 50+ waste collectors across Netherlands and Belgium
• Sensor entities for each waste type
• Calendar entity showing all upcoming collections
• Upcoming sensors (today, tomorrow, next upcoming)
• Custom date formatting and display options
• Built-in icons (including new icon set)
• Dutch translation support
• Custom waste type mapping

How to Install

HACS Installation

1. Go to HACS → Integrations
2. Search for “Afvalbeheer”
3. Install the integration
4. Restart Home Assistant
5. Go to Settings → Devices & Services → Add Integration
6. Search for “Afvalbeheer” and follow the setup wizard

Manual Installation

1. Download the files from the repository
2. Copy to config/custom_components/afvalbeheer/
3. Restart Home Assistant
4. Add through the UI as above

Migration from Previous Versions

If you’re upgrading from v5.x:

• YAML configurations will be automatically imported on first startup
• Existing entities will continue to work without interruption
• New UI configuration is available for future changes
• No breaking changes to entity names or functionality
• Recommended: Remove YAML configuration from configuration.yaml after successful migration

Testing Notes

As this is a new major version, please:

• Test thoroughly before using in production
• Report any issues on the GitHub repository
• Backup your configuration before upgrading
• Check entity names haven’t changed unexpectedly

Looking for Testers!

I need your help to make v6.0.0 rock solid!

Are you willing to help test this release? Your real-world testing with different waste collectors and configurations is invaluable for identifying any remaining issues.

Safe Testing - Easy Rollback

Don’t worry about getting stuck! You can always revert back to the previous stable version:

• HACS users: Simply reinstall the previous version through HACS
• Manual users: Replace files with the previous release from GitHub
• Your YAML config: Will continue to work if you need to rollback
• Entity history: Will be preserved during version changes

What I’m Looking For

• Different waste collectors: Especially less common ones
• Various configurations: Different address formats, special requirements
• Edge cases: Commercial addresses, special suffixes, multi-instance setups
• UI feedback: How intuitive is the new Config Flow?

Feedback Welcome

Please test and report:

• Successful configurations with your waste collector
• Any bugs or unexpected behavior
• Suggestions for UI improvements
• Documentation updates needed
• Migration experiences from YAML to Config Flow

---

Let me know in the comments how v6.0.0 works for you and if you encounter any issues!

[DriesA (Dries)]

Great update!

I think my upgrade to version 6 went without issues.

The only thing I noticed is that when I press “verzenden” (submit) on the following page in the config flow, nothing happens (not sure if this screen is supposed to close).

But everything seems to work, so that is a minor issue.

Thanks for the update!