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

Turning off Partial Open?

Comments

10 comments

  • Official comment
    Scott Riesebosch

    Brian,

    This isn't because of the partial open feature. There is something wrong with the door sensor. When Tailwind opens the door, it checks to see if the sensor has detected that the magnet moved away. If it doesn't detect that, it will try again 5 seconds later. This will cause the door to stop part way open. Usually this is caused by something metal near the sensor that has become magnetized by the powerful magnet used in our new sensor design. This design allows for a much larger gap between the magnet and sensor, and makes things more robust - but it can have the adverse effect of magnetizing things like drywall screws, etc and this can confuse the sensor.

    Comment actions Permalink
  • Brian S.

    Thanks Scott! Of course the day after I posted this the door stopped doing it.

    Pretty sure there are some exposed nails in the header near the magnet (I don't have any drywall covering it). I'll try covering them up with some duct tape if the door starts doing this again.

    0
    Comment actions Permalink
  • Sam Ralston

    I know this post is a year old but I am seeing the same thing. I however am only seeing it recently and I see it on both open and close events occasion. I just submitted a big report tonight for the first time.

    I look at the “event” history and there is nothing in my view. This also goes to my past posts that more information in the event history would help understand ourselves what might be going on vs having to always put in a big report.

    0
    Comment actions Permalink
  • Scott Riesebosch

    Hi Sam,

    Sorry you're having trouble.

    The bug reports are mostly helpful for troubleshooting app related issues such as auto-open / close, connectivity problems, etc. The bug report tells us what the phone did or did not do.

    The history should show any time the door opens / closes, and if the command came from someone's phone or an automation, the history should show that. If the command came from outside the Tailwind ecosystem, such as a wall control or standard garage remote control, the history would show "somebody" opened / closed the door. This is because Tailwind has no idea why the door opened or closed. It's just reporting what it sees.

    This of course assumes that the door sensor is working properly. There is one, and only one way to send the partial open command, and that's to tap and hold on the door icon. It takes a deliberate effort to send that command.

    In your case, it sounds like the door sensor isn't working properly and you have CASE 1 in this help article https://gotailwind.zendesk.com/hc/en-us/articles/360020903011-The-door-says-LOCKED-OUT-Tailwind-doesn-t-open-or-close-the-door-How-do-I-fix-it-

    All of the above assumes that you are experiencing the following symptom:

    You send a command to open or close the door and it does something expected, like opens partway and stops, or closes and then opens by itself.

    If your symptom is in any way different from this, please let me know what it is so I can help.

     

    0
    Comment actions Permalink
  • Sam Ralston

    Thanks for the feedback. I have updated to 1 pulse and 400ms for both open and close. Given it is intermittent, I will give it some time and see how it does.

    As far as the history and I missing something. I agree I can see I opened or Somebody opened (push button). But I do not see anything more than I open

    If I use the app to open the door I see

    Opened Garage Door two

    If the GPS auto opens the door I see

    Opened Garage Door two

    So I see no distinction between the different events.

    0
    Comment actions Permalink
  • Scott Riesebosch

    Hi Sam,

    Got it. So you want to see a different notification if you approach in your car vs if you open the door by tapping in the app? Something like "Sam opened garage door 2" if you use the app, and "Sam arrived in Tesla and opened garage door 2".

    Personally I am suspecting your door sensor is doing something wonky. If changing pulse settings fixes it, that's great.

    0
    Comment actions Permalink
  • Sam Ralston

    Exactly on the notifications. The more the better. Anytime tailwind does something even if door stopped because of sensor or auto close because of gps. Basically any event.

    I read through your info. Given I see both a 2 inch open and stop and a 2 inch close and stop. It did not make sense that it would be a sensor issue since it only makes “contact” on the close.

    Don’t know if it matters but this is my 2nd door and it is a long wire from the main controller.

    0
    Comment actions Permalink
  • Scott Riesebosch

    Sam,

    So if your garage door is open and you tap in the app to close it, the door closes 2 inches and then stops? And it does the same thing when you try and open the door?

    Please carefully look at the app and see if you can see any difference in the door icon for that door when it is open or closed. I want to make sure the app is correctly showing the open / closed state of the door. It's possible it is always showing closed. If the sensor is somehow stuck in the closed state, it will definitely cause the symptoms you describe.

    0
    Comment actions Permalink
  • Sam Ralston

    Understood. I almost never use the app.  This happened 3 times in the week before I posted the message. 1 on the close side using the siri voice command, and 2 times on the open side using the auto open as I came home. So I have no idea what the app showed for current state of the door.

    This drives more to my point that we need more in the event history log of what tailwind is doing. So given your above description I should see in the event history something like this:

    Sam GPS open attempted and failed because door was in open state

    It seems I only get good history, but I would think we should see "all" events

    Another example is the other day I could not get it to close. It kept saying command failed. If you had events like this too: (I assume everything goes to the cloud before the controller)

    Tailwind cloud received request to close door 2 from voice command

    Tailwind controller received request to close door 2 from voice command

    Tailwind closes door two from voice command

    Tailwind door 2 closed from voice command

    I can now tell where the failure occurs. If I get no history it is because my phone was not able to send the message out.

    Bottom line is there is never too much event history and you can always put levels on it ie general (what you see today) detail (every event) or anywhere in between. These can be dropped into the event history they don't all have to be push notifications.

     

    just some thoughts

     

    0
    Comment actions Permalink
  • Scott Riesebosch

    Understood. I've captured this and I like it. We will kick this around and see what we can do.

    Based on the symptoms you told me, I very strongly suspect an issue with the door sensor being stuck closed because Tailwind will automatically send a second pulse to the garage door opener 5 seconds later if it detects the door is still closed (magnet present) after the first pulse. Things change for a door close command. For door closing, it waits 45 seconds. If the door hasn't closed after 45 seconds it will send a second pulse. In one of your cases, the door was open. It started to close and then just a brief time later it stopped. That stopping is generally caused by a second pulse. Since you've confirmed your pulses are set to 1 pulse, it is likely that the door sensor was stuck in the closed position (often due to nearby metal objects becoming magnetized), the controller would send a second pulse for either open or closed, and do it just 5 seconds after the first one.

    0
    Comment actions Permalink

Please sign in to leave a comment.