cjkas 4a33b0d7dd fix: set rolling codes only on the main loop ... Sending a command reads a remote's next rolling code, queues the frame and commits the code, all on loop(). /setRollingCode, a shades restore and /updateShadeConfig wrote the same codes from the web server task, so a set could be undone by a command's commit, and a restore could save an older code to NVS that survived the reboot. All three now go through the web command queue to loop(). They don't use the radio, so they are never held back or refused while it is busy. /restore now answers after queueing the restore. A broken options string used to send an error after the success answer had already gone out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>		2026-10-14 16:01:55 +02:00
..
test_webcmd.cpp	fix: set rolling codes only on the main loop	2026-10-14 16:01:55 +02:00