Connection lost, Connected to broker

[onlize]

My garage door opener worked for a few days and started giving me problems. After I check logs, I see the following:
338723 : WD : Uptime 6 ConnectFailures 20 FreeMem 23048
338723 : MQTT : Connection lost
339782 : MQTT : Connected to broker
339790 : Subscribed to: NodeMCU/#
363536 : EVENT: Clock#Time=Sat,15:29
369455 : WD : Uptime 6 ConnectFailures 22 FreeMem 22904
369455 : MQTT : Connection lost
370516 : MQTT : Connected to broker
370527 : Subscribed to: NodeMCU/#

And it continues.....

Does it mean that my NodeMCU is bad? Can I do anything? Reboot does not help.

[grovkillen]

That happens from time to time. If it is able to reconnect I wouldn't worry about it. But as you experience problem, what is the RSSI level of the WiFi?

[onlize]

It does it constantly every couple of seconds.

RSSI level is -55

[grovkillen]

What pin did you switch to (from the malfunction GPIO 12)?

[onlize]

GPIO 13

[grovkillen]

Ok, no problem there. What else is connected?

[onlize]

GPIO13 and GPIO14 connected. Nothing else.

The device is connected using OpenHub to MQTT broker.

[grovkillen]

Other ESP Easy units connected to the same broker? Are the working all right?

[mrwee]

Have you verified that it's not a WiFi issue? (e.g. Interference from other WiFi's, 2.4GHz equipment etc.)

[onlize]

I do not know how to verify it, but I have multiple devices and none of them have this issue. I do not believe that I have an issue with my WiFi.

For example, I have Raspberry Pi camera in my garage and, in addition, I have another camera that I am testing now and it is also in my garage. No issues with those two WiFi cameras.

[Shardan]

In a nutshell:
Go to "Devices" and chose an empty task.
Edit it, chose "System info".
In System Info settings chose "RSSI".

Post the value here.

As patrickwilson said above the RSSI represents the field strength of the received WiFi signal.
So this is a quite good marker if the signal is good enough.

Don't get trapped in the "It has worked for x months" trap. Tech devices can break at any given time.
It might be a fault in the nodeMCU itself for sure. But i've seen long working devices loosing connection
because of the metal parts of a newly placed planter, so checking is better
It might be a fault within the WiFi Router or networking too, a second device using a hard set IP address colliding
with the address of the ESP for example.

Regards
Shardan

[Ton_vN]

Possibly a similar issue (but yet without good solution): viewtopic.php?f=2&t=3339
Still searching & experimenting .........