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
while working on the support for ESPHome (#67), we found that it offers a nice capability in the spirit that it will publish metadata information about each sensor to the MQTT broker on startup. The corresponding JSON payload(s), as outlined below, are published to the /config topic suffix.
From this metadata information, Kotori would be able to derive relevant information to make the "instant-on" experience more pleasant. For example, by using the full name of the sensor like "name": "EVB-02-BME280 Relative Humidity" and its "unit_of_measurement": "%".
We just discovered that this style and mechanism of sensor announcements to the MQTT bus is actually called »MQTT discovery«, as defined by Home Assistant at [1]. On behalf of a quick research, we also discovered corresponding generic implementations for C++/Arduino [2], and Python [3].
Hi once more,
while working on the support for ESPHome (#67), we found that it offers a nice capability in the spirit that it will publish metadata information about each sensor to the MQTT broker on startup. The corresponding JSON payload(s), as outlined below, are published to the
/config
topic suffix.From this metadata information, Kotori would be able to derive relevant information to make the "instant-on" experience more pleasant. For example, by using the full name of the sensor like
"name": "EVB-02-BME280 Relative Humidity"
and its"unit_of_measurement": "%"
.Example:
MQTT topic
homeassistant/sensor/evb-ea-ind-02/evb-02-bme280_relative_humidity/config
JSON payload:
With kind regards,
Andreas.
mosquitto_sub -h daq.example.org -t '#' -v
The text was updated successfully, but these errors were encountered: