We’re debugging some issues we’ve come across with SoftAP. It used to work, but somehow something broke…
We have an Ionic app that used the http-based softap library via browserify. That implementation would send the
configure-ap commands without issues. We built on top of that a custom UI similar to what is done with the Particle branded app.
I’m not sure at what point things stopped working because we didn’t test this for a while, but now when I go back to test it, the
public-key command is timing out.
I’m able to reproduce this when I connect to the device using a Macbook Pro and send the command via postman. I can get good responses from
public-key times out.
The device is a P1 running system firmware 0.6.2.
In looking at the release notes for the 0.7.0 release candidates, I notice there’s a lot of activity regarding SoftAP. Is it possible this is an issue with 0.6.2? I will probably try running 0.7.0-rc.2 and see if this resolves it.
I know there has been a lot of issues with the HTTP-based implementation of SoftAP as well. In fact I’m able to run the
public-key command just fine using TCP and my macbook. Unfortunately the TCP workflow still fails in the
configure-ap step, I created another topic for that issue. Since we’re running Ionic (Cordova) we could migrate to use TCP in the app instead of HTTP, but would require a custom implementation of the softap-setup-js library which I was hoping to avoid. So anyway, is there any hope for HTTP or should I just focus on the TCP solution?