fix optional pcb command API on esp32#877
Merged
Merged
Conversation
On ESP32 the periodic optional PCB send runs in a FreeRTOS task that reads exclusively from pcbQueue via xQueuePeek. When the /command? API handled an optional PCB command (e.g. /command?SetZ2WaterTemp=45), tmp.func() correctly updated optionalPCBQuery but never wrote the new value to pcbQueue, so the task kept sending stale data indefinitely. The rules path had the same bug and was fixed in 0da01f7. Apply the same fix here: call xQueueOverwrite after invoking the command function. On ESP8266 the periodic send reads optionalPCBQuery directly, so no change in behaviour there. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.