Replies: 1 comment 2 replies
-
The issue with this approach is that it's a little dicey for onboarding and it is very manual. Additionally, the typical use case of Willow is multiple devices and repeating the steps required with this approach is very tedious and error prone. There's a good reason why (for example) ESPHome uses either a web flasher (via WebSerial) or requires direct serial connection for initial device configuration and flash. It's still early but our initial thinking for this approach is a Tovera hosted WebSerial flasher that (other than initial loading of the web page) runs completely locally in the browser. Of course it could also be self-served by the user but there are issues related to TLS certs for WebSerial usage in browsers so self-hosting with this approach can be challenging. This is what ESPHome does today and I think it's a fantastic approach. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I believe this might already be "in the works" but I could not find it in the list "Future" section so I'm suggesting to have Willow create an access point the first time it runs or when booting while holding the top button pressed.
The display could show something like "Waiting for you on WILLOW wifi network" and a QR code to the captive portal URL so that the end user can then enter Wifi parameters and other options.
This would make for a friendlier user experience, especially when it comes to the final Wifi network and password that are currently hard coded in the firmware.
In personal ESP32 Arduino based projects, I have used IotWebConf which has its own limitations but is just a good illustration of what I have in mind:
I totally understand that because IotWebConf is Arduino based it is not usable in Willow but that could serve as an inspiration.
Beta Was this translation helpful? Give feedback.
All reactions