Closed Getslow6 closed 11 months ago
This is a bug and is fixed in v5.2.10 Thank you for reporting the bug!
Super! Dank voor het snelle oplossen en alle moeite.
Hi Pippyn, sorry to bother again. I've just tested the solution and apparently there is still an issue somewhere:
Maybe there are two separate issues:
sensor.hvc_today
is currently not provided (while sensor.hvc_tomorrow
exists). sensor.hvc_tomorrow
does not reflect this.Do you have any errors in your log?
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.
v5.2.11 fixed it! Thank you!
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:
Note that the
dutch
option is not used: https://github.com/pippyn/Home-Assistant-Sensor-Afvalbeheer#translationSince 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
?