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
wled json api over serial communication problems #2557
Comments
Hey! |
@Aircoookie Thank you for your prompt reply!
Nothing is applied at all when this error occurs. Nothing changes. Indeed I was using this tool for this sketch. If I copy ur JSON object
and then paste it into the assistant, the code is exactly the same as I used.
|
Problem solved!( @Aircoookie ) Checkout my simple demo code if you want to use the json api over serial too: |
Nice! SoftwareSerial is only suitable for very slow baud rates, definitely not 921600 in most cases. You should always use HW serial if possible, and in case SoftwareSerial is indispensable, use the lowest possible rate. |
Hello guys and especially @Aircoookie !
my setup:
I have a "main mcu" (which is a esp32) that shall control the "wled mcu" (esp8266 d1 mini) via serial communication.
I use the WLED-0.13.0-b6 version. I compiled it myself and changed the Serial baudrate to 921600, hoping to improve serial communication.
current state:
I experimented with the json api over serial now for about 5 days, and after some success I stuck on an annoying problem / (bug?).
The communication itself works but not ALL JSON objects arrive at the wled mcu.
I've read about a "verboseResponse mode" which sometimes blocks the serial input, but I think that this is not the case with my setup.
the problem:
Unfortunately, despite successfully sending a json package, sometimes the expected change does not occur. (The package doesn't seem to be received).
demo / test code
Here you can see a very simple demo code which I wrote for sending the JSON objects:
https://github.com/miwied/wled-json-api-over-serial
Do u guys have some ideas what the problem could be and how I could fix it?
I've already had read #1173 and #1146 but unfortunately it didn't help me.
The text was updated successfully, but these errors were encountered: