You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, Just to let you know that most unexpected resets on ESP8266 come from calling AT+CIPCLOSE at an already closed (i.e. by a webserver) connection, even if AT+CIPSTATUS does not say so (is not aware about).
The text was updated successfully, but these errors were encountered:
This project is un-tested and left out during development. I moved to do other stuff and forgot about it. Sorry but for a long time I will not be updating this project.
From what I remember, last time I used this code, I was able to publish mqtt message but not receive and parse correctly. It's bee a long time since I do not run this code.
To use MQTT on the ESP8266 I encourage you to use the Lua firmware, I believe they added mqtt support.
This project is un-tested and left out during development. I moved to do other stuff and forgot about it. Sorry but for a long time I will not be updating this project.
From what I remember, last time I used this code, I was able to publish mqtt message but not receive and parse correctly. It's bee a long time since I do not run this code.
To use MQTT on the ESP8266 I encourage you to use the Lua firmware, I believe they added mqtt support.
Reply to this email directly or view it on GitHub: #2 (comment)
Hi, Just to let you know that most unexpected resets on ESP8266 come from calling AT+CIPCLOSE at an already closed (i.e. by a webserver) connection, even if AT+CIPSTATUS does not say so (is not aware about).
The text was updated successfully, but these errors were encountered: