BertL
Active Member
Befuddled with Homelink 17.11.3
I'm (fortunately for me), one of the MS owners that set both of my garage doors with Homelink one time when it first became available in Fall 2015, and have not touched the settings or had a problem since ...until 17.11.3. It's one of the new features since taking delivery that I've enjoyed most for "just working" as it should -- at least for me.
Now, perhaps half the time, when I back out of my garage, the door will not automatically trigger to close. The other times, it works fine as it always has. I see no correlation to one or the other. I can open the door via my wall switch before getting into my MS, or inside via the CID either before or after putting the MS into reverse, just as I always have. ...but then when Homelink is going to fail, there is no indication in the dropdown for the garage door that it's going to close or it's been bypassed. I can just close the garage door manually inside my MS out in the street where it normally would do it by itself. When I return home, the door opens 100% of the time from exactly the same position in the street as it always has. It's just weird, as absolutely nothing has changed in more than a year, except 17.11.3 is now in place.
My MS shows it's location on the Nav display properly, including pointing in the right direction all the time, so that isn't a possible correlation to the occasional failure. The only other thing that has happened is my $%(* new next door neighbor has parked a very old ugly metal trailer (domed on the front and top, with peeling paint -- sighhhh), next to my picket fence which is no more than 10' from my garage door at it's closest point -- but the trailer appeared before 17.11.3, and I was not having any odd Homelink issues before the update. Unless someone has a great idea, I'll likely do nothing until the next "real" big code drop of 8.1, then if I'm still having problems, I'll delete the garage doors from Homelink and add them back as some others have had success with. If that fails, it goes onto my next SvC problem report.
Odd, huh?
I'm (fortunately for me), one of the MS owners that set both of my garage doors with Homelink one time when it first became available in Fall 2015, and have not touched the settings or had a problem since ...until 17.11.3. It's one of the new features since taking delivery that I've enjoyed most for "just working" as it should -- at least for me.
Now, perhaps half the time, when I back out of my garage, the door will not automatically trigger to close. The other times, it works fine as it always has. I see no correlation to one or the other. I can open the door via my wall switch before getting into my MS, or inside via the CID either before or after putting the MS into reverse, just as I always have. ...but then when Homelink is going to fail, there is no indication in the dropdown for the garage door that it's going to close or it's been bypassed. I can just close the garage door manually inside my MS out in the street where it normally would do it by itself. When I return home, the door opens 100% of the time from exactly the same position in the street as it always has. It's just weird, as absolutely nothing has changed in more than a year, except 17.11.3 is now in place.
My MS shows it's location on the Nav display properly, including pointing in the right direction all the time, so that isn't a possible correlation to the occasional failure. The only other thing that has happened is my $%(* new next door neighbor has parked a very old ugly metal trailer (domed on the front and top, with peeling paint -- sighhhh), next to my picket fence which is no more than 10' from my garage door at it's closest point -- but the trailer appeared before 17.11.3, and I was not having any odd Homelink issues before the update. Unless someone has a great idea, I'll likely do nothing until the next "real" big code drop of 8.1, then if I'm still having problems, I'll delete the garage doors from Homelink and add them back as some others have had success with. If that fails, it goes onto my next SvC problem report.
Odd, huh?