@Gorkde it requires new deploy. In case of local server I could just give you server with fix.
Limitations :Maximum allowed email + subject + message length is 120 symbols.Only 1 email per minute is allowed. For local server you can change 1 minute interval.[quote=“Gorkde, post:17, topic:7236”]
Is that still correct? That would be way to few to send error mail containing actual sensor data at error time for me. I read about #define BLYNK_MAX_SENDBYTES but what is the maximum number of bytes I am able to put there?
[/quote]
Would be great if you could add some way to send larger email bodys for such status reports. Maybe upload in multiple packets then finally sent by command
Will need to go now.
Once the bug has been identified I got no problem waiting since I got much left to do anyway
@Gorkde by the way I just made a test for old server code and it displays umlauts just fine, however my fix may also help. So either problem in your client (it ignores UTF-8 header) or in hardware. However pushes works, so seems like problem not in hardware.
I tried and found its working as long as I keep my Email Body limited to 1183 chars.
There is no Email is sent by Blynk once the Body is 1184 or larger.
I found this also is independent of the Subject field.
Body > 1183 failed
Body 1183 works with one Char in Subject as well as 40 chars in subject.
But why that strange numer? Together with that ending 0 it’s 1184.
So this probably is a limitation by Blynk. Else if that were a linitation on the bytes ESP might send it also should stop once I raise the suject chars.
No problem for me since my mail is shorter anyway but maybe some thing to improve, since I found the ESP should be able to send 2048 bytes.