-
Notifications
You must be signed in to change notification settings - Fork 106
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
ESP8266 crashing on data received #51
Comments
Maybe a stack issue - could you try to replace the _onData function in uMQTTBroker.cpp with this version:
|
Same-ish error Ill keep looking on my end.
|
Seems to be in the copying of the topic string. Anything special with your topic str? |
Nope, I just call |
hi Andrew, |
I use https://github.com/me-no-dev/EspExceptionDecoder Seems to look to work for ESP8266? Let me know if you want anymore info, sorry just a bit confused by your question |
Hi, |
Hi,I've changed the architecture and use a RPi as Broker now.The 8266 ist the just the mqtt client, which works reasonably stable.Bye martinAm 10.03.2022 09:48 schrieb navdeepssidhu ***@***.***>:
Hi,
i am also facing the same issue, could you please share how you resolved the issue?
thanks
—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.Message ID: ***@***.***>
|
Thanks for the suggestion. I am interested in ESP broker (connected to cloud through GSM module) and would like to connect couple of Tasmota devices. Any help would be appreciated. |
hi,
as the 8266 broker wasn't too stable, I've evaluated a public offering:
https://myqtthub.com/en
depending on the volume, it's free (which worked for me for a while). It
offers secure connections; though the memory footprint on your
uController is then severely challenged, as it a 30k+ usage when using
mqtts over WiFiClientSecure.
This can be an issue on the esp8266.
As you're connected via GSM, this may be an alternative.
At the time (1+ year ago), I didn't find an emebedded mqtt-broker in the
arduino framework other than martin's. Unfortunately porting this to
e.g. an esp32 (to be more flexible wrt. memory) is not straight forward
and the 8266 version isn't stable enough for production - at least in my
case.
As already said; I've put a RPi (std. distro) in the same WiFi acting as
mqtt-broker (mosquitto) and have all uControllers connect as mqtt
clients; there are plenty clients around; normally i use the simple
(very stable) PubSubClient.
If you use a public cloud service, you may check if one can't host a
mqtt-broker there.
bye, martin
…On 3/10/22 15:04, navdeepssidhu wrote:
Thanks for the suggestion. I am interested in ESP broker (connected to
cloud through GSM module) and would like to connect couple of Tasmota
devices. Any help would be appreciated.
Thanks
—
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO43X2NQHWM7VSPYH7WJJCLU7H6ODANCNFSM4VVAZGFA>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi, |
Hello, I am having trouble with my ESP8266 crashing when data is received by the broker.
Here is all the information I have, if you need anything more specific let me know, any help would be appreciated.
Payload
Exception
Sample class
The text was updated successfully, but these errors were encountered: