pippyn / Home-Assistant-Sensor-Afvalbeheer

Provides Home Assistant sensors for multiple Dutch and Belgium waste collectors
Apache License 2.0
277 stars 86 forks source link

Base entity names on configuration option 'dutch:' #426

Closed Getslow6 closed 9 months ago

Getslow6 commented 9 months ago

Hello!

First of all, thank you for developing this integration.

I'm from the Netherlands, but use the integration in the English language with the following config:

afvalbeheer:
  wastecollector: HVC
  resources:
    - restafval
    - gft
    - papier
    - pmd
  postcode: [redacted]
  streetnumber: [redacted]
  upcomingsensor: 1
  alwaysshowday: 1

Note that the dutch option is not used: https://github.com/pippyn/Home-Assistant-Sensor-Afvalbeheer#translation

Since the last update, my entities have been renamed from:

sensor.hvc_today -> sensor.hvc_vandaag sensor.hvc_tomorrow -> sensor.hvc_morgen

Would it be possible to tie the naming of the entities to the option dutch?

pippyn commented 9 months ago

This is a bug and is fixed in v5.2.10 Thank you for reporting the bug!

Getslow6 commented 9 months ago

Super! Dank voor het snelle oplossen en alle moeite.

Getslow6 commented 9 months ago

Hi Pippyn, sorry to bother again. I've just tested the solution and apparently there is still an issue somewhere:

image

Maybe there are two separate issues:

  1. The sensor.hvc_today is currently not provided (while sensor.hvc_tomorrow exists).
  2. The contents of the sensor are not correct; paper will be picked up here tomorrow (as shown in other sensors), but sensor.hvc_tomorrow does not reflect this.
pippyn commented 9 months ago

Do you have any errors in your log?

Getslow6 commented 9 months ago
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:612
Integration: Sensor (documentation, issues)
First occurred: 09:34:07 (1 occurrences)
Last logged: 09:34:07

Platform afvalbeheer does not generate unique IDs. ID hvc tomorrow already exists - ignoring sensor.hvc_tomorrow

This talks about sensor.hvc_tomorrow though.

I've removed sensor.hvc_today (which was unavailable) and restarted Home Assistant and it created the same error message as above.

pippyn commented 9 months ago

Could you try version v5.2.11?

Getslow6 commented 9 months ago

image

v5.2.11 fixed it! Thank you!