Definitely lots of settings for the ESP. Which brings me to my single biggest complaint about Arduino IDE: it does not save those settings per program. Case in point, I went to look at my settings before answering your post. I'd been working on STM32s (for my Christmas lights) last time I used the IDE. So I open up the clock WiFi program and everything is still set for STM32. Which means having to remember or write down all the damn settings for ESP when I have been doing STM32 - and vice versa. Grrrrr.
Look into it later when the dust is clearing off the crater.
Following the re-programming - time has been spot on though I just noticed this when looking at the summary on the clock web page:
Time according to server: ERROR: -1 (connection refused)
Timeserver URL is set to:
It did sync time initially, is this a transient thing or indicative of something more sinister?
SPIFFS is a sort of "flash disk" protocol, we don't use it. It's OK either way. On the new models that are coming out later this month with a WEMOS controller, it will be relevant (instead of using EEPROM to store configuration, I'll be using SPIFFS).
QIO and DIO ("Quad" data I/O" and "Dual Data I/O", I believe) are the data transfer mode between the flash and the controller. It's also not really that important - if it is wrong, the flashing process will fail and you'll stop and fiddle with it.