-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESPAsyncTCP version in libs/ won't compile with recent platforimIO ESP8266 SDK #23
Comments
I've tried to use latest version of ESPAsyncTCp and ESPAsyncWebServer. Update: I'll see how me-no-dev response and try if I can modify the code by myself. |
Reverted to the previous platformIO esp8266 platform version and it now compiles OK with your versions of the ESPAsyncTCP libraries. In platformio.ini modified As changelog for the espressif8266 platform is: Finally! Release of Arduino Core v2.4.0 I suspect the Arduino Core upgrade to v2.4.0 was the culprit. Would be good to get a fixed latest ESPAsyncTCP library though. |
I am working on the migration of latest ESPASyncTCP/ESPAsyncWebServer library. The latest version seems to work fine. Maybe it has something to do with new version of framework. I've tested it for a while, and it seems to work fine. I applied the temporal solution mentioned. If you want to try it, you can try the branch: If the build "passes" my stability test, I will try to use WebSocket instead of current ServiceSideEvent. By using two-way WebSocket, the button action will be more smooth and responsive. |
Good stuff, I will try the latest version. You going to do similar for BPL too ? |
Yes. |
The new libraries as well as WebSocket pass my stability test. I also fixed some bugs: |
Just loaded up the v404pre branch and it's looking good. |
Having upgraded the PlatformIO ESP8266 SDK version recently, I then got compilation errors when building BMEsp.
I believe the issue is this one: me-no-dev/ESPAsyncTCP#57
I updated the ESPAsyncTCP library to the latest version and BMEsp now compiles [I'm yet to test it].
The text was updated successfully, but these errors were encountered: