Home Assistant Discovery Meter Type water_l values m³ instead of L

[tunip]

The Problem

Enabled Home Assistant Discovery and changed Meter Type to "water_l", but the MQTT values are still in m³ instead of L (value * 1000).

Version

13.0.8

Logfile

[0d00h00m04s] 2022-12-28T22:01:29 <INF> [MAIN] Reset reason: Via esp_restart
[0d00h00m16s] 2022-12-28T22:01:41 <INF> [MAIN] =================================================
[0d00h00m16s] 2022-12-28T22:01:41 <INF> [MAIN] ================== Main Started =================
[0d00h00m16s] 2022-12-28T22:01:41 <INF> [MAIN] =================================================
[0d00h00m16s] 2022-12-28T22:01:41 <INF> [MAIN] The device has 8 MBytes of PSRAM
[0d00h00m18s] 2022-12-28T22:01:43 <INF> [MAIN] Initialization completed successfully!
[0d00h00m20s] 2022-12-28T23:01:46 <INF> [SNTP] Time zone set to CET-1CEST,M3.5.0,M10.5.0/3
[0d00h00m20s] 2022-12-28T23:01:46 <INF> [SNTP] Set SNTP-Server to pool.ntp.org
[0d00h00m20s] 2022-12-28T23:01:46 <INF> [SNTP] Waiting until we get a time from the NTP server pool.ntp.org
[0d00h00m21s] 2022-12-28T23:01:46 <INF> [SNTP] Status: Reset
[0d00h00m23s] 2022-12-28T23:01:48 <INF> [SNTP] Status: Reset
[0d00h00m25s] 2022-12-28T23:01:50 <INF> [SNTP] Status: Reset
[0d00h00m27s] 2022-12-28T23:01:52 <INF> [SNTP] Status: Reset
[0d00h00m29s] 2022-12-28T23:01:54 <INF> [SNTP] Status: Reset
[0d00h00m31s] 2022-12-28T23:01:56 <INF> [SNTP] Status: Reset
[0d00h00m33s] 2022-12-28T23:01:58 <INF> [SNTP] Status: Reset
[0d00h00m35s] 2022-12-28T23:02:00 <INF> [SNTP] Status: Reset
[0d00h00m37s] 2022-12-28T23:02:02 <INF> [SNTP] Status: Reset
[0d00h00m39s] 2022-12-28T23:02:04 <INF> [MQTT IF] Init
[0d00h00m39s] 2022-12-28T23:02:04 <INF> [MQTT IF] Client started, waiting for established connection...
[0d00h00m39s] 2022-12-28T23:02:04 <INF> [MQTT IF] Connected to broker
[0d00h00m39s] 2022-12-28T23:02:04 <INF> [TFLITE SERVER] Round #1 started
[0d00h00m49s] 2022-12-28T23:02:14 <INF> [MQTT SERVER] MQTT - Sending Homeassistant Discovery Topics (Meter Type: water, Value Unit: L , Rate Unit: L/h)...
[0d00h01m35s] 2022-12-28T23:03:01 <INF> [POSTPROC] main: Raw: 684.6176, Value: 684.6176, Status: no error
[0d00h01m35s] 2022-12-28T23:03:01 <INF> [TFLITE SERVER] Round #1 completed
[0d00h04m30s] 2022-12-28T23:05:55 <INF> [TFLITE SERVER] Round #2 started
[0d00h05m08s] 2022-12-28T23:06:33 <INF> [POSTPROC] main: Raw: 684.6244, Value: 684.6244, Status: no error
[0d00h05m08s] 2022-12-28T23:06:33 <INF> [TFLITE SERVER] Round #2 completed
[0d00h08m21s] 2022-12-28T23:09:46 <INF> [TFLITE SERVER] Round #3 started
[0d00h08m59s] 2022-12-28T23:10:24 <INF> [POSTPROC] main: Raw: 684.6265, Value: 684.6265, Status: no error
[0d00h08m59s] 2022-12-28T23:10:24 <INF> [TFLITE SERVER] Round #3 completed
[0d00h12m12s] 2022-12-28T23:13:37 <INF> [TFLITE SERVER] Round #4 started
[0d00h12m50s] 2022-12-28T23:14:15 <INF> [POSTPROC] main: Raw: 684.6305, Value: 684.6305, Status: no error
[0d00h12m50s] 2022-12-28T23:14:15 <INF> [TFLITE SERVER] Round #4 completed
[0d00h16m03s] 2022-12-28T23:17:28 <INF> [TFLITE SERVER] Round #5 started
[0d00h16m41s] 2022-12-28T23:18:06 <INF> [POSTPROC] main: Raw: 684.6346, Value: 684.6346, Status: no error
[0d00h16m41s] 2022-12-28T23:18:06 <INF> [TFLITE SERVER] Round #5 completed
[0d00h19m54s] 2022-12-28T23:21:19 <INF> [TFLITE SERVER] Round #6 started
[0d00h20m32s] 2022-12-28T23:21:57 <INF> [POSTPROC] main: Raw: 684.6348, Value: 684.6348, Status: no error
[0d00h20m32s] 2022-12-28T23:21:57 <INF> [TFLITE SERVER] Round #6 completed
[0d00h23m45s] 2022-12-28T23:25:10 <INF> [TFLITE SERVER] Round #7 started
[0d00h24m23s] 2022-12-28T23:25:48 <INF> [POSTPROC] main: Raw: 684.6387, Value: 684.6387, Status: no error
[0d00h24m23s] 2022-12-28T23:25:48 <INF> [TFLITE SERVER] Round #7 completed
[0d00h27m36s] 2022-12-28T23:29:01 <INF> [TFLITE SERVER] Round #8 started
[0d00h28m14s] 2022-12-28T23:29:39 <INF> [POSTPROC] main: Raw: 684.6387, Value: 684.6387, Status: no error
[0d00h28m14s] 2022-12-28T23:29:39 <INF> [TFLITE SERVER] Round #8 completed

Expected Behavior

MQTT values in L and not in m³

Screenshots

Additional Context

No response

[caco3]

Please see #1528 (comment)