The attraction was wide availability of chrome across os/hardware platforms; thus having access to chrome was all that was needed for configuaration.
I already have a wifi/ap/web server for configuration. It works well but it coexists with my mqtt client STA and that was messy to make work and maintain. But the web interface to my preferences was great: web browser was all I needed.
My new configuration interface is via bluetooth (serial); no messing with much code and no complications with wifi. Just begin, end, and write.
Here is a screen shot:
[img]
- Capture.PNG (24.11 KiB) Viewed 2745 times
The code in the esp32 arduino is straight forward. The data is stored in preferences. The code defines the n/v pairs, descriptive text and regex for validation in the chrome app.
The app can run wherever there is chrome.
I am currently cleaning-up the code in the app and esp32. It accomplishes what I wanted a browser based app that uses bluetooth Classic/Serial.
One unsolveable issue is the dependability of initiating a connection on the first try; minor inconvenience.
Note: I burned 4 days trying to make google's bt examples work.
Tom Meyers