Partial Open Issues
It is certainly strange that's for sure. I mentioned the wall control based on experience. Some wall controls have electronics in them and a fairly large capacitor that keeps the power to wall control during brief power interruptions (meaning when control signals are sent to the opener). This means that when the Tailwind controller shorts out the contacts to make the garage door opener start opening, as soon as the Tailwind releases the relay that capacitor in the wall control will start pulling more current than normal to charge back up. I have seen that temporary condition cause problems in the past, which is why I mentioned it as a test - to cross that one off the list as NOT being the root cause. If your wall control is just a standard doorbell button then this most likely would not apply - and thank you Alex for that feedback so we can scratch that one off the list.
I have a Samsung S20 running Android 12 and the partial open works every single time without fail on all 3 doors. This does not appear to be a widespread issue. We have 10s of thousands of customers running Samsung phones and at this time there are 2 reports of this problem (the two of you).
Flemming - since you're an engineer could you please try the following test?
If you have an ohm meter, connect it to the Tailwind control wires. You'll need to disconnect the control wires from your garage door opener first so the control wires only go to the ohm meter.
Set your open pulse time to something like 2000mS. This makes the pulse long enough to catch it on a digital ohm meter.
Use the Tailwind app to partially open the door (tap and hold), and then also immediately tap your wall control so the door starts to open (because the Tailwind control wires are no longer connected to the opener obviously.
Then watch your meter and see what it does. It should beep with continuity for 2000mS, or show something like less than 10 ohms of resistance while the internal relay closes. Then, after the door starts to go up and the partial open time has expired, your meter should again beep and indicate continuity for 2000mS. That would be the "stop" command.
Could you also check one more thing please? Use your wall control to open the door while you have the Tailwind app open on the door control screen so you can watch it. Within about 2 seconds of the door starting to open, you should see the door icon open in the app. There have been some cases where door sensors would "stick" closed for a while either due to erroneous magnetic fields or defects. Just want to cross this one off the list as well.
I saw there was an Android OS update for my phone so I am applying that update to see if it makes a difference.
I have reviewed both of your bug reports and your phones are sending the partial open commands.
Now you got me to go up to the door opener and take it apart although I already knew that it was not the problem.
I have testet the signal from Tailwind it only gives on signal to open and not the signal to stop.
Same when my wall contact with no electronics is not connected.
And the sensor is also okay, it shows that the door is open right away.
My installation works just as well as when I installed it and just as well as when I use the iPhone, or when I used my previous one+ 8pro, except from the fact that if I use my samsung phone to activate partial open it only gives that one open signal and not the stop signal.
Thanks Flemming. We are going to need to schedule some kind of real-time test when one of our firmware developers can be monitoring the commands in real-time. This just doesn't make any sense at the moment, so the only way to get to the bottom of it will be to gather some data from either your device or Alex's device in real-time. Please let me know if either of you have availability in the next few days, and what time zone you're in.
All we will do is ask you to send the command to partially open your door a couple times.
Ok, so a bit of an update from me, and I don't quite know what's going on as I've changed nothing, but I've just tried the partial open command several times in a row and for some reason it seems to be working as intended. Unless there was a background Android update to some kind of service (Play Services perhaps), the issue for now at least, seems to have resolved itself. I'll continue to periodically check throughout the coming days and let you know how I get on.
Ok, so an update regarding the Partial Open feature... I'm afraid that after that one day when everything seemed to be working as intended, I am now back to the Partial Open feature not working at all. I've tried logging out of the app, restarting the device and adjusting the time setting again but all to no avail. I think I'm going to have to resign myself to the fact that this feature is never going to work other than on a very rare occasion for me. I don't know if this is a combination of my door opener or the Samsung phone I'm using, but the device is not supplying the command to stop the door at the specified time despite the app clearly stating the door is partially opening. I doubt that the recent update on my S22 Ultra to Android 13 has anything to do with this as this problem existed prior to the update.
Sorry for the late reply on this. Please try turning the WiFi OFF in your phone settings and then try the partial open feature. I suspect that will fix it. I know that's not a permanent fix obviously, but it should restore the feature for now until our team fixes the issue.
Thanks for the reply Scott, sorry for the delay in responding myself, I've been away for a few days. I have disabled WiFi for the Tailwind app only, forcing it to use only cellular data, and can confirm that this does indeed restore the partial open feature. Many thanks for your ongoing support in this issue.
I just installed a new Tailwind iQ3 device today and seem to be having the same problem detailed in this thread. When my Android phone is connected to the WiFi, Partial Open doesn’t work (that is, the phone will confirm that a “Partial Open” command has been sent, but the door will open fully). When I disconnect the phone from the WiFi, the Partial Open feature works as intended.
Thank you. Our team has been working on this but we can't reproduce the issue. Could you please help us fix this for you?
If you would be so kind as to connect your phone to the same wifi network and send the partial open command. Then if you can get the door to open all the way, please do the following:
Tap the top left corner in the Tailwind app to bring up the main menu
Tap on "send bug report". Choose "other".
Fill in basic information - something like "just tapped and held on the door icon to open partially but it opened fully" and then send the bug report.
Then please either post here that you sent it, or send an email to firstname.lastname@example.org to let us know you sent it. I'll have it immediately escalated.
We have been trying to find this bug but we just cannot reproduce it. Hoping a bug report from you will help us find out what's going on.
I have just now sent a bug report. I’m a little puzzled that you say that you can’t replicate the fault. If you look at the comments in this thread immediately preceding mine, you’ll see that it was you, in an exchange with a user named “Alex” who advised him to disconnect his phone from the Wifi in order to make the “partial open” command work, and Alex confirmed in his reply that this did, indeed, allow the partial open command to work. This must have been a known issue two months ago.
We know that disconnecting WiFi fixes the issue, but our challenge is that we cannot create the issue. Every time we send a partial open command in our test environments, it works as designed. I suggested trying to disconnect WiFi on a hunch and I was right - but we have never been able to confirm this ourselves because it always works.
So that's why I was asking if you could send the bug report - hoping there might be a nugget in there that can help our team find this bug and fix it. We know approximately where to look in the code but are trying to narrow it down further.
Thank you for sending the bug report Hugh.
Please sign in to leave a comment.