You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.
Eg when subscribing to "Vehicle.Speed", the value is in "km/h" as specified. Since the spec can be overriden, it's hard for generic tools ("VSS Browser") to know the specific data type unit, unless it is exposed via the metadata interface.
The text was updated successfully, but these errors were encountered:
@argerus - could you possibly give quick feedback. Is it Databroker that does not send unit to clients, or is clients that does not show it. No change in proto required I assume?
Test Client> getMetaData Vehicle.Speed
{
"path": "Vehicle.Speed",
"metadata": {
"data_type": "FLOAT",
"entry_type": "SENSOR",
"description": "Vehicle speed."
}
}
sdv.databroker.v1 > metadata Vehicle.Speed
[metadata] OK
Path Entry type Data type
Vehicle.Speed Sensor Float
@mikehaller@argerus - do we consider this one still relevant? If so I could "migrate" it to kuksa.val, or the new kuksa-databroker repo when migration is finished.
The data unit types of VSS should be exposed via GetMetadata as well.
Eg when subscribing to "Vehicle.Speed", the value is in "km/h" as specified. Since the spec can be overriden, it's hard for generic tools ("VSS Browser") to know the specific data type unit, unless it is exposed via the metadata interface.
The text was updated successfully, but these errors were encountered: