-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Could not rename sensors warnings #135
Comments
From which version to which version have you updated? |
I had updated HA from 2023.8.? to 2023.9.2 before installing the AlphaPreview. I'm not 100% sure about the luxtronik2 version. |
Looking at the code of the 'old' integration, the sensor "domestic_water_energy_input" is only added conditionally: Also the other sensor (luxtronik2_domestic_water_charging_pump) that reported the warning it could not be renamed does not exist in my configuration. This sensor is also only added if a specific condition is met. Could the problem be that you don't check if the sensor exists before trying to rename it? |
Yes, I change it. |
* Remove own translations - use ha entity translation * Fix missing/hardcoded device_key in climate * Fix some key_value UNSET warnings
Should fixed with 2023.10.9-Alpha-Core-Preview |
2023-09-20 00:10:49.472 INFO (MainThread) [custom_components.luxtronik2] Connected to Luxtronik heatpump 192.168.1.190:8889
2023-09-20 00:10:49.492 WARNING (MainThread) [custom_components.luxtronik2] Could not rename entity sensor.luxtronik2_domestic_water_energy_input->sensor.luxtronik2_dhw_energy_input
File "/config/custom_components/luxtronik2/init.py", line 113, in _up
KeyError: 'sensor.luxtronik2_domestic_water_energy_input'
2023-09-20 00:10:49.502 WARNING (MainThread) [custom_components.luxtronik2] Could not rename entity binary_sensor.luxtronik2_domestic_water_charging_pump->binary_sensor.luxtronik2_dhw_charging_pump
File "/config/custom_components/luxtronik2/init.py", line 113, in _up
KeyError: 'binary_sensor.luxtronik2_domestic_water_charging_pump'
The text was updated successfully, but these errors were encountered: