-
Notifications
You must be signed in to change notification settings - Fork 172
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
Need to verify if websocket data is revceived #65
Comments
Traced it to ESPAsyncWebServer before but didn't get a fix and haven't had chance to look recently - me-no-dev/ESPAsyncWebServer#138 Sending one message, e.g |
@cinoan Appreciate the help, thanks! I'll look into it. |
@cinoan I'm having issues re-creating this locally. It looks as if it may have fixed here - me-no-dev/ESPAsyncWebServer#144. They have since fixed the IE issue as well so my fork of ESPAsyncWebServer should no longer be required. Any chance you can see if the latest ESPAsyncWebServer upstream still has the issue? |
@forkineye Sorry I hadn't got back to this before. Just tried updating the ESPAsync libraries and still getting the same issue with messages being missed. Short on time at the moment but will try to find some to look at it. |
Sometimes, configuration data fails to show up in the web UI. Root cause is unknown, however configuration receipt verification / re-querying should be done to prevent this from happening.
Example: https://diychristmas.org/vb1/showthread.php?7969-ESPixelStick-WiFi-Renard-amp-Pixel-Control-from-XLights&p=88776&viewfull=1#post88776
The text was updated successfully, but these errors were encountered: