-
Notifications
You must be signed in to change notification settings - Fork 1
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
No controller connection with WLED firmware greater than 0.14.1 #46
Comments
Mine was able to connect to both 14.2 and 15.1b1, but it would cause the WLED device to crash and reboot. See Aircoookie/WLED#3847 for potentially related issue on the WLED device side. |
Disabling the plugin in homebridge has caused my WLED device to be stable. |
Thanks for your comment! I am still trying to get the crash dumps to find out what happens. My feeling is that this behavior was introduced with any version coming after 0.14.1. The Wled changelog shows updates in json buffer handling and a newer version of the AsyncWebserver was integrated. Both are involved when controlling Wled via websockets using my plugin. I stripped down my implementation to native socket handling and it immediately crashes. In the meantime the only solution is to stick on 0.14.1 if possible... |
Sadly my WLED is in an inconvenient spot to access so I can't get the crashdumps. |
Filed an issue here: Aircoookie/WLED#3855 |
@mariusstrom : I was able to build a WLED firmware from scratch. I monitored the serial debug output to save the crash dumps. It turned out, that there was a memory issues with the AsyncWebserver library WLED is using. A fix is underway. As soon as it is merged I will re-test. Hopefully, everything will work again. |
Fixed in WLED 0.14.3 (https://github.com/Aircoookie/WLED/releases/tag/v0.14.3) |
Describe The Bug:
The plugin is not able to connect to a Wled controller running a firmware version greater than 0.14.1.
To Reproduce:
Update your Wled controller to a firmware greater than 0.14.1 and restart the plugin. The last log message will be the Connect request. It will timeout.
Expected behavior:
Connection should be successful
Logs:
Environment:
The text was updated successfully, but these errors were encountered: