Failed due to connection interruption.
-
Official comment
We are looking into this right now. What kind of phone are you using Jason? We've had a report of this happening on an S10+ so far.
Comment actions -
Scott has been on top of this issue for the last few days. They are trying to resolve it. The immediate fixes to try to find someone with an iPhone and then connect that way. When you get into the app put in your credentials and then they can delete it off of there iPhone. There's something happening in the app with Android phones. But he is working on it.
We were able to get it installed on an iPhone and now it works flawlessly.
-
This issue is being caused by the BLE in Android in some wireless environments - it drops the connection. The current version of our app doesn’t try to automatically reconnect - it just reports the dropped connection. The only way we could reproduce the issue was for me to actually drive to Jeremy’s house. Sure enough, the Bluetooth connection kept dropping on both Samsung phones. Yet when I took that same Tailwind controller and the same phone to another location it worked perfectly every time.
So our updated app (coming shortly) will have the following changes:
1) it will automatically attempt to reconnect the BLE connection instead of just reporting that it dropped.
2) We are adding back our “AP mode” WiFi config screens that will kick in if the BLE fails. This is the typical setup used for many IOT devices - the device becomes a WiFi access point that you connect to. It launches a splash screen and takes you from there.
Please sign in to leave a comment.
Comments
11 comments