Replies: 3 comments 2 replies
-
Try latest development. We reverted a PR in Arduino Core which has a bad impact for wifi especially UDP traffic. |
Beta Was this translation helpful? Give feedback.
-
To be correct to compile Arduino 3.0.0 IDF 5.1.4 is used. |
Beta Was this translation helpful? Give feedback.
-
Found bugs in IDF master are usually backported to older IDF versions (which are still in support). |
Beta Was this translation helpful? Give feedback.
-
I've been doing something evil the last few days.
Building a webcam with bluetooth.
This configuration highlights an issue with ESP32. Wifi and BLE do NOT play nice. But worse than 'bad wifi performance', on a 'normal' esp32, I can reliably cause a complete failure of the IP subsystem (no web, no ping until power cycle. Serial logs OK).
I thought that the esp32s3 was better. It is better, but still not good enough (i.e. I have seen the same death of connectivity, just harder to reproduce).
Now, this situation is sad, because I wanted to have temp/hum from an external BLE temp sensor, as well as webcam recording to SD. I assume even MQTT will eventually hit a conflict point and kill network access.
So, Question:
1/ Is there something we can do to improve 'coexistence'. Reading the docs, it seems that they don't guarantee anything...
We could live with poor performance, but not network death.
2/ does anyone have ideas about what could cause the network death? Are we using the right libraries for wifi/webserver?
3/ should we abandon BLE completely on ESP32 tasmota, and always recommend a separate device/radio (could be a variant of TAS connected by serial...)?
Beta Was this translation helpful? Give feedback.
All reactions