-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix ESP32 webquery response #20111
Fix ESP32 webquery response #20111
Conversation
Stil there is something wrong
|
I need to check further because it seems that rules get impacted |
I'll do some chks too using this on my server:
It works on ESP8266 but fails on ESP32 and ESP32-C3. UPDATE1: Your rule2 needs to be changed to: I'll remove the "Done" message when a valid result is received. UPDATE3: Here is the result of a manual interrogation of the command. It responds as expected:
|
Your PR fixes at least the missing/corrupted response so I'll merge this. The issue with rules executing while another rule is busy (Rules.busy flag) is a different longstanding problem without a sinple solution. |
Doing a simple WebQuery (3-character response) started to work now, on an ESP32-C3. |
However, I'm still seeing WebQuery ESP32 badness with a file containing
Looks like something is seeing usage of |
strange because characters are copied 1 by 1 from the http response to the MQTT message |
That what I was first thinking but I found old notes from rules I was using more than a year ago that were apparently working like that. May be a change in Tasmota.
So that seems to confirm that there is something broken in the kingdom of ext_vsnprinf_P ? |
No, I don't think something is off with the long standing ext_vsnprintf_P. Something is off with releasing Strings. ANyway, I'll remove the unnneeded "Done" message resulting in a single response as expected.
Works fine on ESP8266 (but removes the %) and fails on any ESP32. Investigating too with focus on EDIT2: As expected see note:
So we need to test for % and provide %%. Working on it. |
Should be fixed now. |
Better now, Trying with double
Good idea. Makes |
That's because every character is individually send to the
Not anymore ;-) All formatting is now disabled in Using the |
Description:
Related issue (if applicable): fixes #20102
Creating a copy of the response seems to solve the problem
Checklist:
NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass