Custom component Afvalbeheer - Support for multiple waste collectors

Just chiming in to confirm the trouble with the Belgian RecycleApp integration. I got it working when the changeover from Ophaalkalender was made, but lately - when upgrading from v4.6.0 to v4.6.2 - it broke again. With the exact same config the sensors became unknown, and errors were logged for them. Reverting to v4.6.0 got it working again, but it’s obvious the latest version is broken - either that or it introduced a breaking change, in that case undocumented as far as I know …

There was no breaking change. only added more mapping for the fractions (and better error handling).
Are there any errors? If not, dm me your config (with address)

recycleapp still working with the latest release, no issue here.

I can only say, 4.6.2 works for me. Zone mirom, southwest Flanders.

Aha, its working again for me ! thx, latest version :wink:

Hi @Pippyn,

Log details with v4.6.2 :

Logger: homeassistant.helpers.entity
Source: custom_components/afvalbeheer/sensor.py:1388
First occurred: August 13, 2020, 8:21:40 PM (5682 occurrences)
Last logged: 12:08:12 PM

Update for sensor.ophaalkalender_gft fails
Update for sensor.ophaalkalender_glas fails
Update for sensor.ophaalkalender_papier fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 263, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 456, in async_device_update
    await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/afvalbeheer/sensor.py", line 1361, in update
    self.__set_state(collection)
  File "/config/custom_components/afvalbeheer/sensor.py", line 1388, in __set_state
    self._state = self._state.replace(EN_day, NL_day)
TypeError: an integer is required (got type str)

dm’ed you my config.

Hope this helps - thx for looking into it …

@skank, oops - dm’ed you iso Pippyn. Sorry for that, corrected now :upside_down_face:

Found the bug. The option dateobject was not working correctly. Fixed in v4.6.3

1 Like

Hi @Pippyn great component, thanks for that.
Is it also possible to integrate www.afvalwijzer-arnhem.nl ?

use the suez integration (see issue 103)

i installed afvalbeheer today, thank you for all the hard work.
the sensor for gft stays at unkown. As someone mentioned that it worked with version 4.6.0 for recycleapp i tried this as well, but same error for gft unknown

I use the suez integration but it is unstable (often doesn’t show any information) and suez doesn’t show all waste streams. De afvalwijzer-arnhem.nl, for example, also shows textile and Christmas trees collection days

@ralphklos Use the option printwastetypes to view all possible waste types. If gft is listed, it should work. If it is listed under a different name please make an issue on my github (with your config and an address).

@djim01 Use the option printwastetypes to view all possible waste types. Because all waste types available in the API are supported.

About the unstableness of the sensor; This is the first time I hear about it. Please make an issue on my github (with your config and an address) and an detailed description of what is happening.

@Pippyn , Thank you. it’s working now.

I don’t think the problem goes wrong with the integration, but with Suez. They also do not show the collection days for textiles and Christmas trees in their own calendar, while this can be seen in the Afvalwijzer-arnhem.

afvalwijzer oktober 2020:

suez oktober 2020:

this is my config:

sensor:
   - platform: afvalbeheer
     wastecollector: Suez
     resources:                       
       - restafval
       - textiel
       - gft
       - papier
       - pmd
     postcode: !secret afbeheer_zip                 
     streetnumber: !secret afvalbeheer_nr 
     printwastetypes: 1
     upcomingsensor: 1                #(optional)
     dateformat: '%d %b'           #(optional)
     dateonly: 1                      #(optional)
     nameprefix: 1                    #(optional)
     builtinicons: 0                  #(optional)
     dutch: 1                         #(optional)

the instability is also more on the Suez side … for example, no data was available from 08-24 from 20:42 to 25-08 at 9:28, also not on the Suez website, screenshot of my history in Home Assistant:

Well this sensor is dependant on the Suez API. The site and this component use the same data resource. If the Suez site doesn’t work, neither will the sensor. There not much I can do about that.

I was unable to find the Afvalwijzer-arnhem API, so I can’t switch to that one.

thanks for finding out, that was the reason to ask for the afvalwijzer-arnhem to be added … too bad that the afvalwijzer-arnhem cannot (yet) be added.

keep up the good work!!!

1 Like

Is there any chance to get irado added to this? It’s waste collector in Schiedam Vlaardingen area ( near Rotterdam)

could you please make an issue on my github page? please provide an address for me to test with