search

nfarina / homebridge-tesla

Tesla plugin for homebridge: https://github.com/nfarina/homebridge
154 stars 38 forks source link

HomeLink don‘t response #71

Closed LeBaron90 closed 1 year ago

LeBaron90 commented 3 years ago

Hi, Great Plugin! Everything works fine, except homelink, there is no answer. I added the geo cooridnates, but it still doesn‘t work… 739F7C82-D9B5-4EB2-9F2E-ED3BB64390F4

pguich commented 2 years ago

I have the same issue. I can control Homelink from homebridge, therefore I think the setup is correct, but in the home app, it says “no response”. Not sure what I’m doing wrong?

rondorn commented 2 years ago

Same here. Hopefully this can be resolved with an update. I am curious. Why do you need the location data, and how precise does it have to be to where your car is?

nfarina commented 2 years ago

I don't have HomeLink myself so I'm not sure how this works exactly. Perhaps @focher could chime in?

focher commented 2 years ago

The way Tesla has implemented Homelink from the car is to verify the car is in proximity to the Homelink device. In the car, you set your location that defines your "home" in the Homelink settings.

When calling Tesla's Homelink API endpoint, you need to include the car's latitude and longitude so the API can verify you are in proximity to the Homelink location. The Homebridge solution I implemented uses a "kludge" by letting the user define the car's location as always being within proximity and therefore allow the API to tell the car to send the Homelink signal.

As Homelink doesn't have a status method to determine state (it's implemented as a dumb switch), there's no way to send status info to HomeKit. It should be reporting the fixed status of Closed (which I hardcoded) so not sure why it doesn't for some.

Personally I finally switched to Tailwind, which implements a smarter set of functionality (door state, status, etc) because of Homelink's limitations.