Skip to content
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

Logifile warning: Flowrate is not using a native unit of measure #149

Open
4 tasks done
w-Oeps opened this issue Dec 27, 2024 · 2 comments
Open
4 tasks done

Logifile warning: Flowrate is not using a native unit of measure #149

w-Oeps opened this issue Dec 27, 2024 · 2 comments

Comments

@w-Oeps
Copy link

w-Oeps commented Dec 27, 2024

System Health details

System Information

version core-2024.12.5
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.0
os_name Linux
os_version 6.6.62-haos-raspi
arch aarch64
timezone Europe/Amsterdam
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.1
Stage running
Available Repositories 1496
Downloaded Repositories 6
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 14.1
update_channel stable
supervisor_version supervisor-2024.12.0
agent_version 1.6.0
docker_version 27.2.0
disk_total 439.4 GB
disk_used 34.5 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board rpi4-64
supervisor_api ok
version_api ok
installed_addons File editor (5.8.0), Mosquitto broker (6.4.1), InfluxDB (5.0.1), Grafana (10.2.2), Advanced SSH & Web Terminal (19.0.0), Samba Backup (5.2.0), Samba share (12.3.2), Zigbee2MQTT (1.42.0-2)
Dashboards
dashboards 5
resources 2
views 32
mode storage
Recorder
oldest_recorder_run December 8, 2024 at 12:27
current_recorder_run December 27, 2024 at 16:07
estimated_db_size 1860.41 MiB
database_engine sqlite
database_version 3.45.3

Checklist

  • I have enabled debug logging for my installation.
  • I have filled out the issue template to the best of my ability.
  • This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
  • This issue is not a duplicate issue of currently previous issues..

Describe the issue

A warning appears in the logfile of HA after reboot about unit of measure.
Not really important as all works fine. I do not understand the complaining of HA as L/h is the UoM of the flow rate.
Warning message:
2024-12-27 16:08:10.097 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.heatpump_flowmeter_flowrate (<class 'custom_components.quatt.sensor.QuattSensor'>) is using native unit of measurement 'L/h' which is not a valid unit for the device class ('volume_flow_rate') it is using; expected one of ['ft³/min', 'L/min', 'mL/s', 'm³/h', 'gal/min']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/marcoboers/home-assistant-quatt/issues

Reproduction steps

  1. In my case: Reboot HA and it is one of the first entries in the logfile

...

Debug logs

Not needed(?), this is about a warning log entry

Diagnostics dump

No response

@patrick-reijnen
Copy link

I have the same in logging. It is the result of Home Assistant doing a metrics rework. L/h now has become m3/h.
I haven't seen an announcement yet when they stop supporting the old metrics like L/h.

@tuimz
Copy link

tuimz commented Jan 27, 2025

It is not an effect of the metric rework. L/h was never an option, see also https://github.com/home-assistant/core/pull/106077/files

The reason for this error to appear is that since the latest release the flow meter uses the proper device class.
So effectively this addmon needs to convert Litres/hour to litres/minute and use the proper unit for that sensor.
This is the affecting PR https://github.com/marcoboers/home-assistant-quatt/pull/137/files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants