Open zeus86 opened 2 days ago
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!
(message by CodeOwnersMention)
tasmota documentation tasmota source (message by IssueLinks)
+1 Same problem after updating to core-2024.10.2. With core-2024.10.1 all work fine.
Update Affected all tasmota before 14.1.0. Updated to 14.2.0 or 14.3.0 not have this problem.
Please try by your side
Update Affected all tasmota before 14.1.0. Updated to 14.2.0 or 14.3.0 not have this problem.
Please try by your side
I cannot confirm this. All my devices already have been on 14.2.0 and after spotting this problem, I upgraded to 14.3.0, but the problem persists for me.
I had the same problem. All tasmota devices unavailable in HA, with their web UIs perfectly accessible. And sure enough, tracking my Watchtower logs, it seemed like the update of HA was the issue.
But a bit more careful digging proved it was not: I couldn't get through to the tasmota devices using my MQTT tools. So then I started looking at Mosquitto (my MQTT server). Again, the Watchtower logs showed an update. I rolled back to previous versions. Nothing.
In the end, I reset the fingerprint on the tasmota devices through their console using the command that allows them to auto-learn it:
MqttFingerprint 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
...and it worked. Not sure why this became necessary, but...might help someone else, so I'm posting it.
The problem
After updating to
core-2024.10.2
the reporting of values from all my tasmota devices (around a dozen) stopped working, the only metric not shows as unknown is the IP-address. Everything worked before the upgrade, and no configuration changes have been made. I use RSA-keys with nginx, as ecdsa-Keys with letsencrypt are known to be problematic with some mqtt-devices.What version of Home Assistant Core has the issue?
core-2024.10.2
What was the last working version of Home Assistant Core?
core-2024.10.1
What type of installation are you running?
Home Assistant OS
Integration causing the issue
tasmota, maybe mosquitto
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tasmota
Anything in the logs that might be useful for us?
nothing helpful in the mosquitto-log:
(the
<unknown>
is literal, I only truncated the IP).--
Connection-Failures in the Tasmota-Log:
Additional information
Tested with recent Versions of tasmota: 14.2 and 14.3.
Without SSL (on port 1883) everything works fine, but as said: before the Upgrade everything worked, so I think this is a Homeassistant-Issue, not a Tasmota one.
While TLS-Error 1 indicates, that this is a fingerprint-issue (https://tasmota.github.io/docs/TLS/#tls-troubleshooting), i don't think this is actually true, because it worked before, and the cert did not change during the upgrade.
All Tasmota-Devices in question are ESP32-based, not ESP8266-based.