The hope is to run the nodes with as little power as possible. Meaning BLE is strongly desired instead of WiFi. For devices that support Web Bluetooth, once the web app is downloaded and cached with Service Workers the user will be compelled to disconnect from the WiFi allowing it to enter a lower power state where it is simply broadcasting beacons.
Service Workers will take care of reloading the application from a local browser database on future visits to the now unavailable Captive Portal. Future updates can even be provided over BLE.
"Excuse me, will you kindly f*ck off?"
Or... How do we compel the user to not reconnect to WiFi?
- Determine if there is a mechanism in the 802.11 spec to help
- Rotate AP name after successful BLE connection
- Badger user to 'Forget' network if they reconnect.