If the first power meter triggers its ISR and then the second power meter triggers another ISR while the first ISR is still executing, the second ISR will not be immediately serviced. Instead, it will be put in a queue and handled after the first ISR completes.

This is something really new that I am hearing. Where can we get such NOC certificates from. I hope ESP authority will give a guidline.

Is this thread helpful to you?

viewtopic.php?t=16115

It's a good idea to check for the existence of the operational file system on startup. You can use various methods to do this, such as checking for the presence of certain files or directories that are expected to exist in the operational file system.

For the ESP32-S3, similar to the ESP32, one common eFuse setting that affects flash encryption is DISABLE_DL_ENCRYPT. If you're encountering this error after enabling flash encryption in RELEASE mode, it's likely that you need to burn the DISABLE_DL_ENCRYPT eFuse to disable flash encryption.

you can modify your code to include the WiFi.persistent(true) function call after setting the Wi-Fi credentials: void getWiFi() { Serial.printf("Reconnecting to %s\n", WIFI_SSID); byte retry; WiFi.begin(); WiFi.waitForConnectResult(); if (WiFi.status() == WL_CONNECTED) { Serial.println("Connected");...

Looks like no wireguard-related library has been updated for S3. The following is applicable for S2 and C3 but there is no mention of S3.
https://github.com/trombik/esp_wireguard

On the iPhone, check the network settings to see if it's set to automatically switch to cellular data when the WiFi network has no internet access.

I mean, i fixed the bug by moving the ledcAttach() parts back to global setup() but does anyone have an explanation for this? If the ledHandler class or its setup() method has different scope or lifetime compared to the global setup, it could potentially lead to unexpected behaviour. It is more lik...

Perform checks on your custom board to ensure there are no hardware issues such as signal integrity problems, clock mismatches, or power supply fluctuations affecting the I2S peripheral.