search

enbility / eebus-go

EEBUS protocol implementation in go
https://enbility.net
MIT License
50 stars 14 forks source link

mDNS TXT record field `type` is not used consistently #52

Closed DerAndereAndi closed 7 months ago

DerAndereAndi commented 1 year ago

The SHIP spec defines in 7.3.2 the optional type field for the TXT record in the mDNS entry as String with device type. Without further definition this field is not helpful by any means. Different EVSE vendors already use different values. E.g. Porsche uses EVSE and Elli uses Wallbox.

This way the field can not be used in a UI to show only potentially compatible devices for pairing.

As a suggestion, the SHIP model DeviceType should be used. The example references such a value Dishwasher, but the specification does not reference the data model.

DerAndereAndi commented 7 months ago

These fields are free text. As SHIP and SPINE are independent specs, therefor the SPINE definitions "can not" be used for these SHIP definitions.