The transmit power was hardcoded to 19.5 dBm. Some setups need a lower
value (device right next to the AP, weak 3.3V rail), so it is now a user
setting instead of a per-chip constant.
- wlan.cpp: load/save/apply TX power (0.1 dBm steps, NVS key wifi_txpwr,
default 195), re-applied on GOT_IP so it survives a reconnect
- website.cpp: /api/wifi-power GET/POST with validation
- setup.html: "WiFi Settings" card
- README.md/README.de.md: pin table gets an ESP32-S3 column plus a warning
that GPIO19/20 are the native USB data lines
- config.cpp: same warning next to the HX711 pin definitions
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three independent improvements to the WiFi/webserver stability:
1. /api/register called registerDevice() directly inside the AsyncWebServer
body handler. That function does a blocking HTTPClient POST with a 5s
timeout, freezing the AsyncTCP task and tearing down every in-flight HTTP
and WebSocket connection. It now goes through the existing apiQueue /
filamanApiTask machinery: the endpoint answers 202 immediately (or 503 if
the queue is full, which would otherwise leave the UI waiting forever) and
the outcome is pushed to the browser as a "registerResult" WebSocket
message. setup.html waits for that message instead of the HTTP response.
2. TX power raised from 17dBm to the 19.5dBm maximum. The reduced setting was
a compromise against heat, but at marginal signal levels it invites
AP-side auth/assoc kicks (reason=2/4/9/202).
3. Disconnect/GOT_IP logging now includes BSSID, RSSI and channel, so a device
bouncing between two APs (mesh/repeater with separate DHCP scopes) can be
told apart from webserver-induced drops.
Both build environments verified.
Adafruit_PN532::begin() drives the reset line too briefly for some
modules to reliably leave powerdown (~1ms LOW/2ms HIGH internally),
which then makes getFirmwareVersion() return 0 right after begin() and
startNfc() report "Kann kein RFID Board finden". Add an explicit
50ms/200ms reset pulse before begin(), shared via pulsePn532Reset()
so startNfc() and the interface recovery path in ntag2xx_WriteNDEF()
don't duplicate the timing.
Adopts the fix from PR #24 (credit: rsantamaria01), refactored into a
shared helper per review feedback (duplicate pulse code flagged by the
automated Copilot review on that PR).
Co-Authored-By: Raul Santamaria <raulsantamariao@hotmail.com>
Adafruit_PN532::begin() drives the reset line too briefly for some
modules to reliably leave powerdown (~1ms LOW/2ms HIGH internally),
which then makes getFirmwareVersion() return 0 right after begin() and
startNfc() report "Kann kein RFID Board finden". Add an explicit
50ms/200ms reset pulse before begin(), shared via pulsePn532Reset()
so startNfc() and the interface recovery path in ntag2xx_WriteNDEF()
don't duplicate the timing.
Adopts the fix from PR #24 (credit: rsantamaria01), refactored into a
shared helper per review feedback (duplicate pulse code flagged by the
automated Copilot review on that PR).
Co-Authored-By: Raul Santamaria <raulsantamariao@hotmail.com>
PR #14 (0f43f22) unconditionally replaced the classic ESP32 Dev Board
pin numbers for PN532 (NFC), HX711 (scale) and TTP223 (touch) with the
ESP32-S3 values in the single shared src/config.cpp, even though the
esp32dev build environment (used for all standard-hardware releases)
still links against it unchanged. This caused nfc.begin() to talk to
the wrong physical pins on ESP32 Dev Board hardware, producing a
watchdog reset during NFC init and a subsequent bootloop.
Verified via objdump on both compiled config.cpp.o that esp32dev now
resolves to 32/33/16/17/25 and esp32-s3-devkitc-1 to 15/16/19/20/7.
devel was 16 commits behind main and had diverged with the
esp32-s3-devkitc-1 board support (PR #14) that never made it back to
main. Merges main into devel so both stay on the same feature/fix
baseline; resolves the platformio.ini conflict by keeping devel's
shared [env] section (used by both esp32dev and esp32-s3-devkitc-1)
and carrying forward main's AsyncTCP watchdog fix
(-DCONFIG_ASYNC_TCP_USE_WDT=0).
- Introduced language management with English and German translations.
- Added language settings to NVS for persistent storage.
- Updated display functions to use translated strings for various messages.
- Implemented API endpoints for language retrieval and setting.
- Refactored existing text strings in the codebase to utilize the new translation system.
- Updated page titles and structure for clarity.
- Enhanced sidebar navigation and status indicators.
- Improved form styling and user feedback during updates.
- Added WebSocket handling for real-time status updates.
- Streamlined version fetching logic across pages.