MUST haves:
- Async web server
- OTA Update (AsyncElegantOTA)
- WiFi access point for limited time after device startup - providing a web form to enter Internet AP credentials
- Storing credentials to EEPROM with simple and clear API
- Occasional Online mode - Internet connection can't be relied upon, device must manage reconnects to WiFi AP
- No ESP-IDF, only VSCode and PlatformIO required
Good to haves:
- As close to RTC as possible, even after multi-day offline modes. Without RTC, with occasional NTP availability
- Easily compilable and deployable example
- MQTT publisher - logs, telemetry
- MQTT subsriber - reboot, receive URL to new firmware.bin
TBD:
- Total control with a Telegram bot MQTT client (telegram publisher to MQTT is behind the scope of ESP32Base)
Dashboard set up using data reported to MQTT:
