MQTT 6.4.0 / Tasmota failure

[obfri]

The problem

Problems with Tasmota devices - all devices are detected but no entity values. endless Mosquitto failures
[08:29:15] INFO: Starting mosquitto MQTT broker...
2023-11-25 08:29:15: Warning: Mosquitto should not be run as root/administrator.
mosquitto: persist_read.c:550: persist__restore_sub: Assertion client_id' failed. [07:29:16] INFO: Service restart after closing [08:29:16] INFO: Successfully send discovery information to Home Assistant. [08:29:17] INFO: Successfully send service information to the Supervisor. [08:29:17] INFO: Starting mosquitto MQTT broker... 2023-11-25 08:29:17: Warning: Mosquitto should not be run as root/administrator. mosquitto: persist_read.c:550: persist__restore_sub: Assertion client_id' failed.
[07:29:18] INFO: Service restart after closing
see even home-assistant/addons#3264

What version of Home Assistant Core has the issue?

core-2023.11.2

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

No response

[videobuff]

Same problem over here.
This is what the logs tell me from Mosquitto
None of them seems to be authorized.

[10:58:29] INFO: Successfully send discovery information to Home Assistant.
[10:58:30] INFO: Successfully send service information to the Supervisor.
2023-11-25 10:58:34: New connection from 192.168.2.19:52505 on port 1883.
2023-11-25 10:58:34: Client DVES_8C52CF disconnected, not authorised.
2023-11-25 10:58:34: New connection from 172.30.32.1:49807 on port 1883.
2023-11-25 10:58:34: New client connected from 172.30.32.1:49807 as 50iNsOoi34ZzTSXDtjsEyO (p2, c1, k60, u'homeassistant').
2023-11-25 10:58:40: New connection from 172.30.32.1:36322 on port 1883.
2023-11-25 10:58:40: Client frigate disconnected, not authorised.
2023-11-25 10:58:56: New connection from 172.30.32.2:57088 on port 1883.
2023-11-25 10:58:56: Client closed its connection.
2023-11-25 10:59:36: New connection from 192.168.2.22:54499 on port 1883.
2023-11-25 10:59:36: Client DVES_68595F disconnected, not authorised.
2023-11-25 10:59:54: New connection from 192.168.2.27:58679 on port 1883.
2023-11-25 10:59:54: Client DVES_2DE31A disconnected, not authorised.

[home-assistant]

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.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[jbouwh]

If you try to re-setup the MQTT broker add-on and the MQTT integration, does that solve the authentication issues?
It might be the latest MQTT broker version does no longer support not authenticated connections.

[videobuff]

Mine is solved. For whatever reason I had to recreate the user for Mosquitto with HA. With Mosquitto itself it did not work.

[jbouwh]

Not sure if this will be resolved. Other users had similar issues before, mostly they had an older setup not using authentication.

[videobuff]

I used authentication for years and entered the username and password in Mosquitto. That stopped on Friday. After I created that same user in HA everything worked again.

[jbouwh]

May be it is an idea to open a issue at the addon repo. AFAIN there were some changes in the locations of config files. Not sure that is related though. Good to hear all is working again.

[obfri]

MQTT users were already added as HA users months ago within my system , couldn't causing this problem... still mqtt problems ...
20:39:02] INFO: Starting mosquitto MQTT broker...
2023-11-25 20:39:02: Warning: Mosquitto should not be run as root/administrator.
mosquitto: persist_read.c:550: persist__restore_sub: Assertion client_id' failed. [19:39:03] INFO: Service restart after closing [20:39:04] INFO: Starting mosquitto MQTT broker... 2023-11-25 20:39:04: Warning: Mosquitto should not be run as root/administrator. mosquitto: persist_read.c:550: persist__restore_sub: Assertion client_id' failed.
[19:39:05] INFO: Service restart after closing
continuing endless...

[jbouwh]

I suggest you remove the addon and re-add it. After that re-install the MQTT integration, the last step is needed if you use the preinstalled account homeassistant as the password will change.

[obfri]

log from tasmota device:
20:52:16.971 MQT: Attempting connection...
20:52:16.988 MQT: Connect failed to 192.168.123.175:1883, rc -2. Retry in 20 sec
20:52:37.964 MQT: Attempting connection...

Problem started Nov 20 ... (MQTT 6.4.0 update)
Fallback to Full backup before Nov20 works - so looks like MQTT Mosquitto problem...

[obfri]

Thanks, after more investigation (failure occurred after MQTT update to 6.4.0 Nov20 ) I did a full backup to Nov 19 state (thanks to google backup doing regulary backuos :)) and all is running well again… waiting now for MQTT fix… have a nice weekend Uwe Von: Jan Bouwhuis ***@***.***> Gesendet: Samstag, 25. November 2023 19:45 An: home-assistant/core ***@***.***> Cc: Uwe Fricke ***@***.***>; Author ***@***.***> Betreff: Re: [home-assistant/core] MQTT 6.4.0 / Tasmota failure (Issue #104489) May be it is an idea to open a issue at the addon repo. AFAIN there were some changes in the locations of config files. Not sure that is related though. Good to hear all is working again. — Reply to this email directly, view it on GitHub <#104489 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABYFGJYYPCDWD4BONSDOEJLYGI4BNAVCNFSM6AAAAAA7Z5J6C6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGM4TMMBXG4> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/ABYFGJ6KMHMLE43YECJYN6LYGI4BNA5CNFSM6AAAAAA7Z5J6C6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTM3SL22.gif> Message ID: ***@***.*** ***@***.***> >

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.