Sigfox after sleep about sleep_n0m1 HOT 2 CLOSED

I found the solutions. Its a conflict between serial.print and sigfox. Without serial.print everything works fine. Thanks

from sleep_n0m1.

Sorry for the slow reply, Glade you could figure it out. Yeah serial.print is a common source of bugs, one of the first things I check while debugging mysterious issues. Somewhere I saw a library that logs the serial.printlns to flash or eeprom and then prints them later at a time when the processor is not busy, to avoid these kinds of issues. I think its all about processor cycles and timing. Another thing that sometimes helps is increasing the baudrate of the serial. Since then sending the data will take less time.

from sleep_n0m1.