-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in LOG after upgrading to the latest version #34
Comments
Parece ser um problema com o teu Podes verificar se ele tem um nome atribuído ou usa o default ? |
Sera que podes utilizar a ultima versão "beta" ? (é preciso ir as configurações do HACS escolher "beta") |
Duarte, obrigado pela ajuda/resposta :-) O meus Utility Meters estão criados no configuration.yaml desta forma
Ja te digo alguma coisa. |
Instalei a beta: Depois reiniciei o HA e configurei o Componente: Os sensores são criados mas ficam em estado 'unknown' E depois se reinicio o HA tenho a mesmo erro no Log:
e apos reiniciar os sensores ficam assim Fiz a mesma configuração que tinha com a 2.1.7. |
Upgrade done using HACS teh Delete the old configuration and create a new one.
HA version: 2023.9.2
ERSE Version 2.2.0
Log error
2023-09-22 23:49:12.080 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up erse platform for sensor Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 359, in _async_setup_platform await asyncio.shield(task) File "/config/custom_components/erse/sensor.py", line 79, in async_setup_entry TariffCost(hass, config_entry.entry_id, tariff, meter_entity) File "/config/custom_components/erse/sensor.py", line 419, in __init__ self._attr_name = hass.states.get(meter_entity).attributes.get("friendly_name") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'attributes'
The entities were created
But after a HA restart, they are no longer available:
And then with a reload they seem to be available again:
Thank you for this awesome component!
The text was updated successfully, but these errors were encountered: