Error using RMN as provider

[wtrdk]

Support guidelines

• I've read the support guidelines

Description

I have a problem, using RMN as provider. The RMN app on my iPhone still works, but the integration gives this error:

Other error occurred _get_next_waste_in_days: unsupported operand type(s) for -: 'datetime.datetime' and 'str'

It used to work, up until a few days ago...

Expected behaviour

Show right pickup days

Actual behaviour

Gives an error, see message

Version

• HASS version: 2023.1.0
• Component version:
• Useful system info:

HASS logs

• logger -> logs -> custom_components.afvalwijzer: debug in you configuration.yaml

[mrksmts]

I have the same error, I am new to HASS so wasn't 100% sure if I was doing something wrong or not. Provider here is gad

Other error occurred _get_next_waste_in_days: unsupported operand type(s) for -: 'datetime.datetime' and 'str'

Not sure if this is related:

Other error occurred _get_next_waste_date: list index out of range

Version

• HASS version: 2023.1.0
• Component version:
• Useful system info: Home Assistant Yellow

[xirixiz]

I`ll have a look. Can you share the postal code of your area?

[wtrdk]

Great, thanks! My postal code is 3701XK (Zeist, NL) Op vr 6 jan. 2023 om 09:44 schreef Bram van Dartel ***@***.***

…

I`ll have a look. Can you share the postal code of your area? — Reply to this email directly, view it on GitHub <#212 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABC3RHFXJBL3C6R2NB3ILILWQ7LPFANCNFSM6AAAAAATR3U2ZQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[xirixiz]

What is the housenumber you are using? When I use 46, I get the following data:

{'gft': datetime.datetime(2023, 1, 17, 0, 0), 'kerstbomen': datetime.datetime(2023, 1, 19, 0, 0), 'papier': datetime.datetime(2023, 1, 27, 0, 0), 'pmd': datetime.datetime(2023, 1, 10, 0, 0)}
{'gft': datetime.datetime(2023, 1, 17, 0, 0), 'kerstbomen': datetime.datetime(2023, 1, 19, 0, 0), 'papier': datetime.datetime(2023, 1, 27, 0, 0), 'pmd': datetime.datetime(2023, 1, 10, 0, 0)}
{'next_date': datetime.datetime(2023, 1, 10, 0, 0), 'next_in_days': 4, 'next_type': 'pmd', 'today': 'Geen', 'tomorrow': 'Geen', 'day_after_tomorrow': 'Geen'}
['gft', 'kerstbomen', 'papier', 'pmd']
['day_after_tomorrow', 'next_date', 'next_in_days', 'next_type', 'today', 'tomorrow']

[wtrdk]

Hi, my full config:

  - platform: afvalwijzer
    provider: rmn 
    postal_code: 3701XK 
    street_number: 24 
    suffix: "B" 
    exclude_pickup_today: true 
    default_label: Geen 
    id: "" 
    exclude_list: "" 

Also, I don't see all the sensors (just found out...)
I only see these sensors:

[xirixiz]

Thanks! I just found out the suffix is the issue... I`ll have a look why this is.

[wtrdk]

Thanks! I just found out the suffix is the issue... I`ll have a look why this is.

Strange thing is that upon a few days ago it worked with exactly the same config. Thanks for looking into it!

[xirixiz]

Yeah, sometimes providers implement changes at the beginning of the year. Should be an easy fix :)

[xirixiz]

New release available: https://github.com/xirixiz/homeassistant-afvalwijzer/releases/tag/2023.01.01

[wtrdk]

Hi, something is still wrong. I removed the integration, reinstalled it (the latest version: 2023.01.01), and added my configuration in the yaml file, and I still get the following:

Am I doing something wrong?

[xirixiz]

This seems to be an issue with an "old" entity still in the list of sensors. You can remove old/outdated entites yourself.
Remove all entites of afvalwijzer and restart, then the name will be as it was again. Most probably you have something like 👍

sensor.afvalwijzer_today
sensor.afvalwijzer_today_2
sensor.afvalwijzer_today_3

Of which only 1 is active, and the one you posted isn't active currently.

You can check it at this page:

http(s)://<your_hass_url:8123/config/entities

[wtrdk]

Works like a charm, thanks a lot!