Cyberham
Well-known member
- Joined
- Jan 20, 2025
- Threads
- 10
- Messages
- 140
- Reaction score
- 202
- Location
- Penticton BC
- Vehicles
- Cybertruck
Your fault. Took too long to back in and door was closing as you approached
Sponsored
The garage was already coming down before you entered. It was close, but that's on you to look at it.
The fact that you even question if Tesla is to blame is just odd. This has happened to me when my wife and I were switching cars, but our garage door has a pressure sensor and went back up when it touched the roof....that was also my fault, though.
This should have been a video on "I made a dumb mistake" or "careful because you could make this mistake, too"....that's not how you presented it.
Sorry about your mishap. My first thought is that it was BAD TIMING because the wheels did not get a chance to cross the SAFETY SENSOR (the green led light). When that sensor light gets any interference the door automatically switches to open mode and cancels any other command. It is put there in case a person or a child walks into or out of the garage or backing in a Model Y while the door is closing.The MyQ integration is intended to open your garage door when you arrive and close it when you leave. This time it did something different, shortly after opening my garage door, it closed again and damaged my vehicle and garage door. It started to close after the door was not visible from the rear view mirror.
The glass roof is shattered and the garage door has damage as well.
This happened to my Model Y, but it could have easily happened in the Cybertruck as well.
Has anyone had this happen, who do you think bares the responsibility here? MyQ, Tesla, or me? I'm pretty sure I know what the lawyers would say.
What might have happened. You have the distance to open and close very close. When you did the K turn you probably hit that 12 ft mark and it closed. I have mine set at 25 ft.I was using FSD so the car stopped on its own and was a little bit short of where I would normally stop. This forced me to do a k-turn. I was looking in the rearview mirror so I did not see if the screen was warning about an auto close or not, however there was no tone and I have it configured to play a tone.
Is it truly a plane? I think a long narrow cylindrical region is the more likely profile. This is why it’s possible to just step over the sensor while it’s closing.Precisely. The door didn't close onto the top of thetruckcar. He backed into a closing door. If it had been the other way around, the ground safety sensor would have triggered the door to open back up as the tires/underbody broke the plane.
Yeah, I think most of them are a low power/grade IR lasers.Is it truly a plane? I think a long narrow cylindrical region is the more likely profile. This is why it’s possible to just step over the sensor while it’s closing.
This has less to do with the myQ app and more to do with your garage door opener and the safety systems it has built into it. It will not shut the door if the garage door safety system believes there’s something in the way. So one of your safety systems, probably the light based safety sensor that’s at the bottom of the door… Or at least supposed to be at the bottom of the door… Versus the myQ app.The MyQ integration is intended to open your garage door when you arrive and close it when you leave. This time it did something different, shortly after opening my garage door, it closed again and damaged my vehicle and garage door. It started to close after the door was not visible from the rear view mirror.
The glass roof is shattered and the garage door has damage as well.
This happened to my Model Y, but it could have easily happened in the Cybertruck as well.
Has anyone had this happen, who do you think bares the responsibility here? MyQ, Tesla, or me? I'm pretty sure I know what the lawyers would say.
Congrats! Great outcome!UPDATE: With the details I provided, including the video of the events. Liftmaster/Chamberlain accepted my claim and is going to pay for the roof glass replacement on my Model Y. They took a while to investigate, including looking at event logs. I am thankful to put this issue to rest.