HomeAssistant Tasmota Integration: Unavailable Devices After HA core restart

[popy2k14]

The problem

I have an supervised HASS.OS installation. It runs Mosquito broker as addon and all my 8 tasmota devices are using the official tasmota integration in HA. SetOption19 is 0 on all of them.

Everytime when I restart HA core (NOT the broker), all my tasmota devices became unavailable and stay so. In MQTTExplorer and the tasmota console of each device, i can see the are publishing states. Just HA is saying "unavailable" on every light, switch, sensor of every device.

To workaround, i have to restart every tasmota device! In this thread over at HA forum are some people with the exact same issue and some workarounds. I have tried them all (deleting the retained discovery messages and so on), but none of them is a permanent solution, Thread: https://community.home-assistant.io/t/tasmota-integration-unavailable-devices-after-reboot/286814/37

As a workaround i have now made an automation which is sending "restart 1" as CMD to every device on HA startup.

I have already posted over there in the tasmota GitHub, and it seems that the retained discovery messages (which i can see in MQTTExplorer) are just not picked up on core restart. Thread: https://github.com/arendst/Tasmota/discussions/18412

Please fix

What version of Home Assistant Core has the issue?

2023.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

tasmota

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Please see info above and in the lnked threads.

[mib1185]

Thread: arendst/Tasmota#18412

Hi @popy2k14 you are referencing to a custom component, which is not maintained by the HA core project.

[popy2k14]

@mib1185 no it's not! Just go to Integrations and search for tasmota!

[popy2k14]

This is the integration: https://www.home-assistant.io/integrations/tasmota/

[home-assistant[bot]]

Hey there @emontnemery, mind taking a look at this issue as it has been labeled with an integration (tasmota) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tasmota can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tasmota Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

tasmota documentation tasmota source _{^{(message by IssueLinks)}}

[PRothDC]

I hadthe same problem, but with a different work-around. All my Tasmota devices were unavailable, and doing a Restart 1 did not help. Then I found that the MQTT broker on HA was not running, even though it was set to start on boot. Once I started it manually and waited a few minutes, the Tas devices reconnected. An update to the MQTT broker was installed a couple hours ago, but the problem started before the update. After a servver reboot, the MQTT broker restarted as it should, and the Tas devices reconnected. I'm not sure if the broker update fixed the problem, or it was a coincidence.

[popy2k14]

My workaround works for me, but now I have moved my devices over to homeesp. Sorry, can't test any further.

[emontnemery]

I'm closing this since you're no longer using Tasmota @popy2k14

[popy2k14]

@emontnemery Just because i am not using the integration doesn't mean the issue is solved!