Open klementuel opened 3 years ago
I think it was the combination with my DEBUG_Print Stuff without I think it works so I build my Debug Section like this: but any ideas how to make the telegram Code a little bit more memory safe?
Debug.h:
/**
* @brief Comment out if you are not in the code development phase
*
*/
#define DEBUG
#ifdef DEBUG
//Debug Print with Text like #define DEBUG_PRINT_TXT("Test")
#define DEBUG_PRINT_TXT(x) Serial.println (F(x))
#define DEBUG_PRINTIN_TXT(x) Serial.print (F(x))
#define DEBUG_WAIT() Serial.print (F("."))
//DEBUG Print for Dynamik Staff
#define DEBUG_PRINT(x) Serial.println (x)
#define DEBUG_PRINTIN(x) Serial.print (x)
#else
#define DEBUG_PRINT_TXT(x)
#define DEBUG_PRINTIN_TXT(x)
#define DEBUG_PRINT(x)
#define DEBUG_PRINTIN(x)
#define DEBUG_WAIT()
#endif
Ok this was not a Solution, it give me just more time before the ESP Crash....
Hello Every one, I think I found the Problem, I think there is a problem with with the Wifi Secure Client... after long nights I found out that every things works a little bit better when I start and stop the client manually, but not at 100% If anybody has an better idea, pls I need help ;-))
for the rest Merry Christmas :-)
Hi there, First of all, thank you for your work and the Telegram bot. However, since my project got bigger and I use some inline keyboards, my ESP8266 crashes all the time, it always ends between exception 28 and 9 ... Since this is my first large project in C ++ for university, I don't rule out the Fault lies with me. So maybe someone can help me?
In this project I use a web server where I can make all settings, an MQTT service to communicate with my OPENHAB and Telegram so that I receive notifications.
If I don't use inline keyboards, the code works super fast and without errors for days. As soon as I use this, everything crashes ...
My h. Telegram file looks like this:
My cpp file like this:
and my settings for the inline keyboards, where I finally came up with this PROGMEM solution, but this did not lead to success:
I thank you in advance and look forward to tips to fix the error ...