One way that customers claim their device through our webapp is connecting to a HTTP page hosted on their device. This device-hosted page then runs through a claim flow that interacts with the SoftAP. It has generally worked well and will successfully claim the device, add the customer to our product, and connect the device to WiFi.
Recently, however, we tried the claim flow on a new computer, and were unable to connect to the device-hosted server on that computer. When we went to http://192.168.0.1/ in the browser was unable to connect.
We then tried a different approach, connecting to the device through the browser, but with a downloadable local file, the same approach used in setup.particle.io. With this approach, we were able to connect to the SoftAP. We were also able to connect to the device’s SoftAP via
curl commands on the command line.
This was consistent across browser. The computer that we used was a Macbook Air, OS X El Capitan, Version 10.11.2.
I had seen in this thread that the SoftAP has experienced issues on different devices before, so this doesn’t seem unprecedented. After reading that thread, however, I’m not sure how to approach debugging this.
If it helps, the softapp code that we are currently running on our device is compiled using the
compress.py script in my fork of the
softap-setup-page repo. Perhaps the rsa files I’m using are out of date?