Scroll up to see the issue’s. Maybe you’ll need to reselect your fractions?
I think I have found the cause.
I had a custom mapping in my YAML:
custommapping:
Keukenafval: Keukenafval
Related to this: Missing waste fraction - keukenafval for Limburg.net · Issue #550 · pippyn/Home-Assistant-Sensor-Afvalbeheer · GitHub
The config flow added “keukenafval” to the waste types at the top:
(keukenafval was already removed when I took the screenshot)
Additionally, this was added at the bottom of the screen:
My entity (sensor.limburg_net_keukenafval) is working fine this way, however I cannot complete the config flow.
When I remove “keukenafval” as a waste type, the config flow is completed correctly. However, the result is that keukenafval is not working anymore:
Additionally, the config flow does not allow me to add “keukenafval” as a custom waste type (I could probably re-import from YAML as a workaround).
2 Likes
I’m using Afvalbeheer for a long time (years) now and at the moment using 5.6.6, great work by the contributors!
As this new 6.x version has major changes I read the release annoucement and see a calendar is created with the collection dates. I never had this and frankly wouldn’t need it as my automations are based on the next-day sensor.
Is the calendar optional and just out of interest how often is it updated with changes in the schedule? We had a few changes recently and I never had a problem using the next-day sensor.
I upgraded to 6.02 and all my sensors now have the _2 added to the name.
Removing the integration and all sensors, reinstall and still _2, renamed by hand removing the _2.
The calendar is not optional in the settings, question remains how often is it updated?
Ok, release 6.0.6 has fixed this issue. Thanks!
Does anyone experience issues with the Afvalbeheer currently?
Since yesterday my waste types are not calculated anymore. So I don’t know when the garbage collector (Limburg.NET) will come.
When I try to reconfigure the integration, I get this error:
So I am unable to complete the configuration wizard.
Does that mean the Limburg.Net API is down? I didn’t change anything on my setup.