Bug: Web Interface Fails to Start When Wombat is Connected to External WiFi
Description
When the wombat is connected to an external WiFi network (client mode) instead of running as an Access Point, the wombat_launcher.sh script times out waiting for the AP to be created and exits before starting the web interface (voldigate/harrogate).
Expected Behavior
The web interface should start automatically on boot regardless of whether the device is in Access Point mode or connected to an external WiFi network.
Actual Behavior
The launcher script waits 60 seconds for the AP (e.g., 4310-wombat) to appear, then exits with an error:
[DEBUG] Waiting for AP '4310-wombat' to be created by Botui...
[ERROR] AP '4310-wombat' not found within 60 seconds.
The web server never starts, making the device inaccessible via the web interface.
Root Cause
In configFiles/wombat_launcher.sh, lines 44-47:
if [[ $elapsed_time -ge $TIMEOUT ]]; then
echo "[ERROR] AP '$AP_NAME' not found within $TIMEOUT seconds."
exit 1 # Exit if the AP wasn't found
fiThe script exits entirely if the AP isn't found, which prevents the web server from launching.
Introduced In
Commit 0592ce4 (Oct 14, 2024) - "Edit to wombat_launcher for logging bootup scripts and network balancing output"
Suggested Fix
Remove the exit 1 and continue to start the web server regardless of AP status:
if [[ $elapsed_time -ge $TIMEOUT ]]; then
echo "[WARNING] AP '$AP_NAME' not found within $TIMEOUT seconds. Continuing anyway..."
# Removed: exit 1
fiAlternatively, skip the AP check entirely when already connected to a WiFi network.
Environment
- Wombat OS Image = Wombat_v32.2.0.img
- Device connected to external WiFi network in client mode
Bug: Web Interface Fails to Start When Wombat is Connected to External WiFi
Description
When the wombat is connected to an external WiFi network (client mode) instead of running as an Access Point, the
wombat_launcher.shscript times out waiting for the AP to be created and exits before starting the web interface (voldigate/harrogate).Expected Behavior
The web interface should start automatically on boot regardless of whether the device is in Access Point mode or connected to an external WiFi network.
Actual Behavior
The launcher script waits 60 seconds for the AP (e.g.,
4310-wombat) to appear, then exits with an error:The web server never starts, making the device inaccessible via the web interface.
Root Cause
In
configFiles/wombat_launcher.sh, lines 44-47:The script exits entirely if the AP isn't found, which prevents the web server from launching.
Introduced In
Commit
0592ce4(Oct 14, 2024) - "Edit to wombat_launcher for logging bootup scripts and network balancing output"Suggested Fix
Remove the
exit 1and continue to start the web server regardless of AP status:Alternatively, skip the AP check entirely when already connected to a WiFi network.
Environment