Please I really need your help with my mqtt that go crazy

Configuration
21

This really sounds like the problem that many people had with versions of Tasmota built with Core 2.4.x. I would recommend verifying this using “cmnd/TOPIC/status 2”. I had a few devices that were built with Core 2.4.x that I had this problem with, but I’ve had absolutely ZERO issues with Tasmota 6.5.0 which is built with the older Core 2.3.x.

cmnd/NodeMCU02/status 2
stat/NodeMCU02/STATUS2 {"StatusFWR":{"Version":"6.5.0(release-sonoff)","BuildDateTime":"2019-03-19T12:24:10","Boot":31,"Core":"2_3_0","SDK":"1.5.3(aec24ac9)"}}

The latest Tasmota binaries can be found here:
http://thehackbox.org/tasmota/release/

22

@123 Yes of course

@SteveDinn
ID 5 (LuceDivano) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:6,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 1 (Bridge RF) => {“StatusFWR”:{“Version”:“6.5.0(sonoff)”,“BuildDateTime”:“2019-06-08T22:14:45”,“Boot”:7,“Core”:“2_5_0”,“SDK”:“3.0.0-dev(c0f7b44)”}}
ID 2 (Luce Giardino) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:7,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 9 (Luce Tavolo 1) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:6,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 6 (LuceLavatrice) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:6,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 11 (Scale1) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:7,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 12 (Luce Scale 2) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:7,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 3 (Casetta TH16) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:7,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 4 (Lumino) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:7,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 10 (Disimpegno 1) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:6,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 7 (Sirena) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:7,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 8 (LuceGiulia) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:6,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}
ID 14 (Deumidificatore) => {“StatusFWR”:{“Version”:“6.5.0(sonoff)”,“BuildDateTime”:“2019-05-10T09:36:58”,“Boot”:7,“Core”:“2_5_0”,“SDK”:“3.0.0-dev(c0f7b44)”}}
ID 15 (Ventola Bagno) => {“StatusFWR”:{“Version”:“6.5.0(release-sonoff)”,“BuildDateTime”:“2019-03-19T12:24:10”,“Boot”:7,“Core”:“2_3_0”,“SDK”:“1.5.3(aec24ac9)”}}

23

There goes that theory. Except for a couple of instances where it looks like you’re running a dev version, you have exactly the same version as I have on all of my devices.

24

It’s not necessarily “of course”, the other possibility is no access was possible to the web console and that would be an equally meaningful clue to the underlying problem.

The fact you can access it, means poor signal strength is not necessarily a cause. The implication is that the device is only dropping its MQTT connection to the broker (which is an entirely separate issue from basic network connectivity).

If you’ve experienced this problem for a year, I assume you have upgraded Home Assistant at least once or twice during that period. That means the problem persists from one version of Home Assistant to another. The question is what has been the constant over the past year? The version of MQTT broker? The version of tasmota firmware? Whatever remains unchanged might be the source of this year-long problem.

25

“of course” was just because when the devices are off-line I can always log in to try to solve …
I don’t know what to do anymore but in the meantime I thank you for the help you are giving me.

26

This error seems interesting:

1560266949: Client DVES_917D33 already connected, closing old connection.
1560266949: Socket error on client DVES_917D33, disconnecting.

It’s like closing the connection because it receives the request twice