MQTT discovery question

[macle]

Hello, I’m trying to setup mqtt sensors based on “mqtt discovery” feature.

My configuration.yaml on hass:

mqtt:
  broker: !secret mqtt_broker_ip # external broker
  username: !secret mqtt_username
  password: !secret mqtt_password
  discovery: true
  discovery_prefix: home

I see proper messages from publisher on my mqtt broker.
mosquitto_sub output:

home/sensor/esp1/si7021/Temperature 21.3
home/sensor/esp1/si7021/Humidity 47.0

And… I see messages on hass logs (home-assistant.log):

2018-02-02 13:13:28 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on home/sensor/esp1/si7021/Temperature: 21.3
2018-02-02 13:13:28 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on home/sensor/esp1/si7021/Humidity: 46.0

But… I don’t see any new entities on my hass.

Do I need to perform any additional configuration tasks?

Regards,
ML

[Sthope]

Hello macle,

Please have a look and read the documentation about MQTT Discovery https://home-assistant.io/docs/mqtt/discovery/, the device has to be configured differently.

[macle]

You mean:

<discovery_prefix>/<component>/[<node_id>/]<object_id>/<>

?

I’m publishing at the moment following topic:

home/sensor/esp1/Temperature 21.1

but still I don’t see any kind of new entity in hass…

[fabaff (Fabian Affolter)]

First message needs to go to <discovery_prefix>/<component>/[<node_id>/]<object_id>/config with the details as JSON payload.

[macle]

I see.

So… it looks like that there is a need of special implementation (in all cases) on the publisher side.
It’s not so easy in “closed solutions” case (like ESPeasy).

Overall it’s much more complicated than I expected.

Anyway, thank you for answer.

Regards,
ML

[fabaff (Fabian Affolter)]

There is already support by at least three projects.

[macle]

However… still no ESPeasy support ;-(

[fabaff (Fabian Affolter)]

If you want ESPEasy support then you should talk to them or open an issue at https://github.com/letscontrolit/ESPEasy.