Notifications do not work on ESP32?

[ohaldi]

Hello,
I have multiple projects using the ESP8266 and ESP32, and I regularly utilize the Notifications module.
In my latest project based on the ESP32 (Build: ESP_Easy_mega_20240617_normal_ESP32_4M316k_LittleFS_ETH, Jun 17, 2024), pressing "Test" does not yield any response. In contrast, all my other projects based on the ESP8266 (Build: ESP_Easy_mega_20230508_normal_ESP8266_4M1M, May 8, 2023) work perfectly. The notification settings are identical for both projects.
Could you please advise on how to debug this issue with my ESP32?
Thank you in advance for your assistance!
Best regards,
Otto

[Ath]

There has been work in the email plugin in recent months, and possibly the release you're on might have some issues. Older releases did not have changes in that area for a long time, so they should indeed work flawless, but I think we've nailed all these issues, and also made some improvements.
Best would be to try the latest mega build, either from the Github actions run or a recent build from the Web flasher (latest) (using Chrome or Edge browsers).

[TD-er]

Oh and as a nice bonus... on ESP32-builds you can use SSL when sending email, so you could also use mail services like GMail

[ohaldi]

OK and thanks for your help.
I'll go and dismantle my project and try using WebFlascher to make an update according to your advice.
Is the normal 4M LittleFS [ESP32-C2] for my ESP32-WROOM-32E OK? I'm still struggling to figure out which version to use given the number of choices!

[Ath]

To avoid dismantling you can of course use the OTA tool built into ESPEasy, (at least when not using a 1MB Flash ESP8266, as currently that's won't work with OTA), at the Tools page "Firmware update" button.

[ohaldi]

Witch one should I use:
1. ESP_Easy_mega_20240822_normal_ESP32_4M316k.bin
2. ESP_Easy_mega_20240822_normal_ESP32_4M316k_ETH.bin
3. ESP_Easy_mega_20240822_normal_ESP32_4M316k_LittleFS_ETH.bin

[Ath]

When currently having a LittleFS build installed you should stay with LittleFS, and vise-versa, when not having LittleFS (that's thus using the 'old' SPIFFS file system) you should keep using a non-LittleFS build.

By switching file system, you will LOSE all configuration, as these file systems are not compatible with each other, and the file system will be formatted!

To be safe, first make a backup using the "Backup files" option, that can be restored on both SPIFFS and LittleFS. Be sure to confirm that you want to keep the .tar file, as your browser might find .tar a somewhat outdated file type, but it's still in wide use.

[TD-er]

On the sysinfo page you have the filename of the bin that you used to flash your current setup.
Apart from the date in the name, the rest should be the same.
But as Ton mentioned, the most important aspect is the presence of "LittleFS" in the filename (or lack of...)
And when you update via the button on the tools page, you should select the filename without "factory" in the filename as that's the file used when flashing via serial.

So as checklist:
- Via upgrade button on tools page -> Do not have "factory" in the filename
- Check to use the same flash size (e.g. 4M316k)
- Make sure to have the same file system type ("LittleFS" in the filename)

And as always, it is best to have a backup of your settings and rules.
Ton made the backup feature which will download a tar file with all files.
Just make sure the browser actually does "keep" the file. For example Chrome will not continue to download unless you click in a Chrome pop-up you like to "keep" the file.

[ohaldi]

Hello,
Thanks so much that fixed the problem, you help is appreciated.
I used the OTA tool built into ESPEasy and uploaded the following Build : ESP_Easy_mega_20240822_normal_ESP32_4M316k_LittleFS_ETH Aug 22 2024
Regards
Otto

[Ath]

Ah, great it's working again