I use the utility_meter integration to get aggregate data for my power, gas and water consumption.
This was working fine for some time, but the power sensors are not available anymore since a few weeks.
I am using packages structure for my configuration and directory looks as follows:
This is exactly the same structure as gas.yaml and water.yaml which are working just fine.
Double checked indenting and syntax and the name and availability of sensor.youless_power_total entity.
I have enabled debug logging for the utility_meter and see the following in the logs:
I have checked, but actually the sensor is a kWh sensor. I don’t understand why this is not working and have no clue how to debug this yet. Will have to debug the python code in a development instance I assume.
There is another sensor provided by the Youless LS120 called youless_usage and I use that one for actual realtime power display (in watts), but not using that one for the utility_meter.
hmmm, tried to move the power utility configuration into main configuration.yaml and now it’s working. So it seems to be some nasty bug in the include configuration code. Will investigate some further.
Ok I have found the culprit.
Apparantly you cannot have two yaml files with the same name (in different subdirectories) when using the !include_dir_named packages directive.
I have renamed the other power.yaml to power2.yaml, and now it is working. This also explains why it was working with this sensor for months and all of a sudden stopped working when I added the second power.yaml file.
This would be quite cumbersome when the system keeps growing and chances of duplications will get higher. Especially because there is also no error whatsoever in the logs and this makes debugging difficult. But I think I’ll have to live with that.
I have also SolarEdge, but frequently the data is not showing correctly Some days only a total at the and of the day.
I use also a YouLess Ls120 for getting real-time data of my solar system. But I get the following error:
Logger: homeassistant.components.integration.sensor
Source: components/integration/sensor.py:184
Integration: integration (documentation, issues)
First occurred: 9:28:02 (88 occurrences)
Last logged: 9:59:12
Invalid state (5522,382 > 5522,383): [<class 'decimal.ConversionSyntax'>]
Invalid state (5522,383 > 5522,384): [<class 'decimal.ConversionSyntax'>]
Invalid state (5522,384 > 5522,385): [<class 'decimal.ConversionSyntax'>]
Invalid state (5522,385 > 5522,386): [<class 'decimal.ConversionSyntax'>]
Invalid state (5522,386 > 5522,387): [<class 'decimal.ConversionSyntax'>]
I think the comma is the issue.
A made a template sensor but get no result: 0,0
Configuration.yaml:
As seen in the log the sensor name is not taken from from the setup name but from the friendly name of the definition. That’s why the sensors are named like the are
for example the sensor
daily_gas_useage:
source: sensor.energiemonitor_total_gas
name: Dagelijks gas
cycle: daily
is named sensor.dagelijks_gas and not sensor.daily_gas_usage
