Skip to content

Minor error in Units causing errors in Home Assistant #1778

Description

@Grey-Sheep

Description

The definition

src/vaillant/08.hmu.HW5103.tsp
TypeSpec
·
1
(1)
@inherit(r_2)
@ext(0x3c)
model BuildingCircuitFlow {
@Unit("l/h")
value: UIN;
}

specifies "l/h" as the rate, but this causes errors in MQTT/Home Assistant as it is expecting "L/h"

It's a very minor change and It took opencode to find it for me!

Actual behavior

definition is "l/h"

Expected behavior

It should be "L/h"

ebusd version

current source from git

ebusd arguments

N/A

Operating system

other

CPU architecture

arm64

Dockerized

None

Hardware interface

Adapter Shield v5/C6/Stick via Ethernet

Related integration

No response

Logs

Logger: homeassistant.components.mqtt.entity
Source: components/mqtt/entity.py:165
Integration: MQTT (documentation, issues)
First occurred: 13:28:55 (1 occurrence)
Last logged: 13:28:55

Error 'The unit of measurement l/h is not valid together with device class volume_flow_rate' when processing MQTT discovery message topic: 'homeassistant/sensor/eas_hmu_BuildingCircuitFlow_value/config', message: '{'state_class': 'measurement', 'max': 65534, 'min': 0, 'name': 'BuildingCircuitFlow', 'value_template': '{{value_json["value"]}}', 'unique_id': 'eas_hmu_BuildingCircuitFlow_value', 'device': {'via_device': 'eas', 'identifiers': 'eas_hmu', 'name': 'eas hmu', 'manufacturer': 'ebusd.eu', 'suggested_area': 'Heating', 'configuration_url': 'http://192.168.1.149/#/msg?q=hmu'}, 'device_class': 'volume_flow_rate', 'state_topic': 'eas/hmu/BuildingCircuitFlow', 'unit_of_measurement': 'l/h', 'step': 1}'

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions