Tasmota 15.0.1 does not send the mqtt topic "homeassistant" after SetOption19 1 command

[konraddi]

I checked via mqtt explorer but nothing ist there except tele and stat, but it does not integrate into homeassistant

Gemini says that the topic homeassistant/sensor/ and homeassistant/switch and so on should be there to work.

Is this a bug? Problem on NOUS A1T and Refoss P11 both ESP8266 flashed with https://ota.tasmota.com/tasmota/release/ https://ota.tasmota.com/tasmota/release/tasmota.bin.gz

Many thanks,
Konrad

[sfromis]

That's as designed, the deprecated support for the old MQTT Discovery format has not been included in standard builds for a long time, with the intention to upgrade to the newer Tasmota Integration feature in Home Assistant.

The tasmota/discovery/... payloads (at the bottom of your screenshot) are where the Tasmota Integration finds the device info to integrate with HA.

Don't ask AI tools about what will work or not, they tend to hallucinate badly when they don't have an answer.

You could do a custom build with the older format, but this was deprecated for a reason, not providing the details needed for better integration.

[konraddi]

many thanks. I now integrated these devices via HA Tasmota integration but had the problem that the sensors did not send actual (power) data, no updates for minutes or hours. The console command "TelePeriod 10" fixed that.

[sfromis]

When it comes to power data, my general recommendation is to stay with the default telemetry period of 5 minutes, but use the PowerDelta command to get values when consumption level steps up or down, without waiting for the slower 10-second rhythm.

Usually, I have something like PowerDelta 110, to get messages with 10 W changes, but the number depends on the consumption profile, and I do avoid going so low that small "noise" in the sensor readings trigger publishes without real change.