Custom component Afvalbeheer - Support for multiple waste collectors

Hey Pippyn!

Nice work there! Could you implement it for the Belgian waste collector ‘Ilva’?

Would be so nice :smiley:

Cheers!

1 Like

For some reason your address is not supported. The API returns an empty response. I’m not sure if and how I can fix that.

1 Like

Could you create a issue on my github repo? Please provide an address for me to test with.

1 Like

sure! thanks bro :smiley:

Please keep us posted! Thx
I can test too if you want.
EDIT: looks like RecycleApp does the trick!

Recycle is a smartphone app that isn’t reliable at all… I miss all notifications cause that shitty app isn’t stable at all :frowning:

I know, that’s the reason why i’m looking into this.
But RecycleApp is integrated in Afvalbeheer and it works if you enter your address.

I’ll look into integrating the Ilva API directly for a more stable integration. But I’ll need some time, as I have to find some spare time to code and test this. I’ll keep you posted on the progression!

2 Likes

I thought so. It is what it is.

I have tested postal codes and house numbers from other local districts (gemeente) where Omrin was already active for a longer time and this worked. Omrin started as our waste collector beginning of this year. So that may be the cause.

For now, I will try to find an address in other districts that have the same calender as we do.

@Pippyn I’ve been trying to use your plugin with various addresses in Sint-Niklaas (multiple postal codes) using the RecycleApp collector. None of them seem to work.

To check my own configuration skills, I’ve also tried an address in a totally different town (my parent’s address), which perfectly configures the sensors.

Could you have a look on what goes wrong with addresses in our community? No errors are reported in the logs (also on purpose configured non-existing postal code and in that case errors did pop up, so logging is also sane).

Some addresses of local shops in the neighbourhood that don’t work:
Hoge Bokstraat 97, 9111 Sint-Niklaas
Vleeshouwersstraat 30, 9112 Sint-Niklaas
Laarstraat 5, 9100 Sint-Niklaas

Many thanks for your time in maintaining this plugin!

Hi @pdcleyn ,

I live in Sinaai and it works just fine…

- platform: afvalbeheer
  wastecollector: recycleapp
  resources:
    - restafval
    - papier
    - pmd
    - gft
    - textiel
    - takken
  postcode: 9112
  streetname: Vleeshouwersstraat
  streetnumber: 30
  dutch: 1
  dateonly: 1
  dateformat: "%A %d %B"
  upcomingsensor: 0
  dateobject: 0
  alwaysshowday: 0
  builtinicons: 1

Hope it helps :wink:

Hi @geertmeersman ,

Thanks for your input.

Was about to write “Pasted in your code, but this still does not produce any results …”

Wastecollector: recycleapp
Hidden: false
Sort-date: 0
Days-until: null
unit_of_measurement: ''
friendly_name: recycleapp restafval

and then I refreshed and there it is … Seems I wasn’t patient enough during testing?

Looking at my initial config, only differences I can see is case difference in wastecollector and use of quotes for the street name. As it worked for that other address, I can only pinpoint it to lack of patience from my side …

  - platform: afvalbeheer
    wastecollector: RecycleApp    
    resources:
      - restafval
      - gft
      - papier
      - pmd
    postcode: 9112
    streetnumber: 30
    streetname: 'Vleeshouwersstraat'
    upcomingsensor: 0
    dateformat: '%d-%m-%Y'
    dateonly: 0
    name: ""
    nameprefix: 1
    builtinicons: 0
    dutch: 0
    printwastetypes: 0

So for all others: give it some time to update the sensors after a restart, even if initial result is showing ‘null’ value!

I’m glad it’s working now.
Yes you should give it some time to request the information (especially on boot). Depending on your Hardware, system config and the API speed, it could take several minutes.

After last update to V4.8.0, it seems that “days-until” is now “days_until”.
Take care if you use this on your automations.

It is indeed written in the release notes :slight_smile:

1 Like

Yes indeed. This is a breaking change for some, but this had to be done. This “bug” has been there for way to long. Sorry for any inconvenience.

1 Like

@Pippyn : I am busy with configuring the Afvalbeheer but I have a problem. The “restafval” keeps on empty and I don’t know how to fix it. The wastecollector is Cyclus.

sensor:

  • platform: afvalbeheer
    wastecollector: !secret wastecollector
    resources:
    • papier
    • pmd
    • gft
    • restafval
      postcode: !secret postcode
      streetnumber: !secret straatnummer
      upcomingsensor: 1
      dateonly: 0
      dateobject: 0
      nameprefix: 1
      builtinicons: 0
      disableicons: 0
      dutch: 1

image

Can you help me?

Do you get a date for Restafval on the official Cyclus calendar?
If not: Please create an issue on the github page.

I found the issue. Thanks for the reply! Keep up the great work

Hi @Pippyn ,

Love your work, finally a handy ‘tool’ for our dashboard. BUT, I’m stuck on following. I can’t get de ‘limburg.net’ wastecollector showing up results.

This is the error:

please find below my PAGE file

- type: custom:dwains-flexbox-card
  items_classes: 'col-xs-12 col-sm-6 col-md-6 col-lg-6'
  padding: true
  cards:
    - type: horizontal-stack
      cards:
        - type: picture-entity
          style: |
            ha-card {
              padding: 5px;
              border-radius: 5px;
              background-color: var(--dwains-theme-primary);
            }
          entity: sensor.{{ (data | fromjson)['wastecollector'] }}_vandaag
          name: Vandaag
          image: /local/images/afval_geen_large.png
          state_image:
            'gft': /local/images/afval_gft_large.png
            'papier': /local/images/afval_papier_large.png
            'restafval': /local/images/afval_rest_large.png
            'pmd': /local/images/afval_pmd_large.png
            'pbd': /local/images/afval_pmd_large.png
            'papier, pmd': /local/images/afval_papier-pmd_large.png
            'kca': /local/images/afval_kca_large.png
        - type: picture-entity
          style: |
            ha-card {
              padding: 5px;
              border-radius: 5px;
              background-color: var(--dwains-theme-primary);
            }
          entity: sensor.{{ (data | fromjson)['wastecollector'] }}_morgen
          name: Morgen
          image: /local/images/afval_geen_large.png
          state_image:
            'gft': /local/images/afval_gft_large.png
            'papier': /local/images/afval_papier_large.png

This is my configuration file (afvalbeheer.yaml)

sensor:
  - platform: afvalbeheer
    wastecollector: limburg.net
    resources:
      - restafval
      - gft
      - papier
      - pmd

    # Postcode is required and is your own postcode
    postcode: 3980

    # Street number is required and is your own street number
    streetnumber: 1
    
    #streen name
    streetname: Russelenberg
    
    Cityname: Tessenderlo

    # If you activate this option you'll get 2 extra sensors (today and tomorrow)
    # which are handy for automations. The today sensor will display the fractions
    # collected today. The tomorrow sensor will display the fractions collected tomorrow.
    # Default is 0.
    upcomingsensor: 1

    # If you wish to remove the year and the dashes and want to show the name
    # of the month abbreviated, you would provide '%d %b'.
    dateformat: '%d %b'

    # If you don't want to add dayname, tomorrow or today in front of date
    # activate this option. Default is 0.
    dateonly: 1

    # If you don't want to add the waste collecoctors name to the sensor name. Default is 1.
    nameprefix: 1

Can you help me out ?

Kr,

Bart

1 Like