A Docker container for Raspberry Pi that provides a JSON REST API to configure WiFi, enabling simultaneous access point and client modes.
IOT Wifi is a lightweight Docker container designed for Raspberry Pi (ARM) that manages WiFi connectivity through a JSON-based REST API. It allows the device to operate as both a WiFi access point and a client simultaneously, enabling 'configure WiFi over WiFi' functionality common in IoT devices. It wraps the complexity of WiFi management into a small, containerized service, reducing device dependencies to just Docker.
IoT developers and hobbyists building Raspberry Pi-based devices that require initial WiFi configuration over WiFi, similar to commercial IoT products like Nest or Echo. It is specifically for those using stock Raspberry Pi hardware with Docker installed.
Developers choose IOT Wifi for its minimal footprint (~8MB Docker image) and production-proven reliability, with over 800 devices using it for WiFi configuration. Its unique selling point is the dual-mode operation via a simple REST API, isolating WiFi management in a container to simplify deployment and focus on IoT device provisioning.
Raspberry Pi (arm) wifi configuration container. Configure and control wifi connectivity with a JSON based REST api.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The Docker image is only ~8MB, built with Go and Alpine Linux, ensuring low resource usage as highlighted in the README.
Manages WiFi as both an access point and client simultaneously, enabling the 'configure WiFi over WiFi' feature common in IoT devices.
Provides JSON endpoints for scanning networks, connecting, and checking status, making it programmable and easy to integrate, as shown in the API examples.
Used in over 800 devices for initial WiFi configuration, demonstrating reliability in real-world IoT deployments as stated in the README.
The project was archived in December 2018, with the author seeking contributors but not actively supporting it, risking bugs and compatibility issues.
Only designed and tested for stock Raspberry Pis, limiting its use to specific hardware without guarantees on other platforms.
Requires disabling the host's wpa_supplicant and running Docker in privileged mode, adding steps and potential points of failure during deployment.