Attention iPhone users: iOS 15.0 through 15.2.x contain bugs that affect the auto-open feature. Versions above or below work fine.

Failed due to connection interruption.

Comments

11 comments

  • Official comment
    Scott Riesebosch

    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 Permalink
  • Jason Zuchelli

    I am having the exact same problem.

    0
    Comment actions Permalink
  • jeremy denton

    Has tailwind been of any help?

    0
    Comment actions Permalink
  • Jason Zuchelli

    I actually used my son's iphone to connect and that worked for me.

    0
    Comment actions Permalink
  • Jason Zuchelli

    I have a S10e that didnt work.

     

    0
    Comment actions Permalink
  • Scott Riesebosch

    Ok thank you. We are testing this to try and reproduce the issue.

    0
    Comment actions Permalink
  • Margarita Monsalve

    I keep getting this error and it tells me to try again due to connection interruption. Anybody else have this problem? My Wi-Fi in my garage says excellent.

     

    0
    Comment actions Permalink
  • jeremy denton

    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.

    0
    Comment actions Permalink
  • Sam McLaughlin

    Currently having the same issue with Galaxy S10. Currently running Android 10 if that makes a difference.

    0
    Comment actions Permalink
  • Scott Riesebosch

    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.

    0
    Comment actions Permalink
  • deepak garg

    Having the exact same problem with my Samsung s10 plus and my wife's s10. No other phones available to us. Please help. When is the next version of the app going to come out?

    0
    Comment actions Permalink

Please sign in to leave a comment.