twislaandClaude Opus 5.5 e14eb304b5 Wi-Fi: SNTP could be started twice at a join, and ESP-IDF asserts on that ...

At every join the DNS and NTP setup ran twice in the same pass: the
"check now and then" timer compared this pass's time with a stamp taken
from millis() a moment later, and the unsigned difference underflowed.
Starting SNTP is only queued for the network task, so when the second run
looked before the first had been carried out, it queued a second start:
"Operating mode must not be set while SNTP client is running", a panic
nine seconds after boot. Rare (once in the dozen or so boots of this
branch's testing), there since v0.7.0. Rollback caught it: the update
was on Probation and the device went back to the build before.

The service now remembers that it started SNTP instead of asking
esp_sntp_enabled(), and the timer compares signed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT

2026-10-06 08:52:54 +02:00

..

apps

F1 steps 2-6: the Storage App, its viewers, and Maintenance moved in (#3)

2026-10-06 08:45:43 +02:00

platform

S1 #11: the System App: tasks, memory, network and system, live

2026-10-06 01:28:26 +02:00

services

Wi-Fi: SNTP could be started twice at a join, and ESP-IDF asserts on that

2026-10-06 08:52:54 +02:00

ui

M3 step 5: Sweep, the band's signal strength as bars and a waterfall

2026-10-05 20:28:46 +02:00

main.cpp

F1 steps 2-6: the Storage App, its viewers, and Maintenance moved in (#3)

2026-10-06 08:45:43 +02:00