-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disconnect Reason: 8 #71
Comments
@PhracturedBlue are you still maintaining this project? |
hi, is it possible, that you use Delays in your Code? For me it seems like your relay Node is not able to respond in time to the message from your "Mesh node". This could be caused by using Delays or manny Interrupts in your Code. But that's only a guess. |
Hi! No delays, no. Just yesterday I added a "setErrorCallback" to the library, and I just check the error code and ESP.restart() if it's this disconnect reason. Annoying, but seems to allow it to connect again after that. |
ok, in my fork of the Project i have fixed lots of stability issues (and also added verry little features).Maybe you can try out my Fork and report back if everything starts working. |
I have same issue, and I think that is caused when router changing channel. The mesh node lost connection and it can't establish again |
@kcbleeker Do you can share this workaround, please? |
Make sure you have the latest version of ESP8266MQTTMesh before reporting an issue.
Please Provide the following information:
If you are you using platformio or Arduino, which one?
Arduino
Description of problem:
I have only 2 nodes:
Everything works, something happens so the node with no access starts reporting disconnected from the other node with reason 8.
My "relay" node is a Wemos D1 Mini, the other is a NodeMCU 1.0
These are the closest similar issues I can find, but I have no idea what could be the cause.
letscontrolit/ESPEasy#1447
and #3
My temporary and awful solution is just for all my nodes to periodically restart, and then they seem able to connect again.
Any ideas?
The text was updated successfully, but these errors were encountered: