The Tesla broadcasts an iBeacon all the time. I use an esp32 in the garage to see if the car is located there. Connected to the same esp32 I have a sonar, this used the distance to tell if the car is in the spot. Between these 2 sensors I have the garage door opening and closing quite well. I also put an iBeacon in my old truck and get all the same advantages.
I've actually been using this for several months to see how it works and if it would be useful as an alternative approach. With Elon about to charge for using the Fleet API, it might become the only way of accessing the car state for free. So far I've only been investigating how it works and come across the odd issue (eg https://github.com/yoziru/esphome-tesla-ble/issues/82#issuecomment-2553492073).
Have not noticed this although I have not been using the Bluetooth too control it. I will experiment a bit today and see if I have the same behavior. I could also monitor it through the unifi perimeter add-on. Either way this would not interfere with my automation. When you drive up your are not on WiFi, and Bluetooth connects faster than the WiFi. My other automation closes the garage when we leave Bluetooth. I will try pinging the car and see if Bluetooth still works. You could use the sonar to tell if the car has started moving as a trigger for the gate to open on leaving. Or just one Bluetooth at the gate to open when you are in range (leaving our arriving).
So I just tested this I ran a ping to the Tesla's IP and was getting responses and it was still communicating with my Bluetooth proximity esp32. I looked at the graph for the proximity center and there were no disconnections while the car was home. It is possible you can't control it when it's on Wi-Fi but that the IBeaonn part is still broadcasting.
I tried again today. It seems rather inconsistent. I opened my car and sat inside with the door open. MY HA BLE sensors quickly went unknown seemingly confirming my original findings. However, I repeated this a few times, shutting the door etc. and found that the sensors didn't always go unknown. I think my ESP32 BLE scanner is at such a distance that it can be affected by little changes!
Interesting, is your scanner looking for the ibeacon or regular Bluetooth communication. my sensors are bluetooth proxy's. could just be a distance thing. Are you going to put/do you have a bluetooth proxy at the gate? The one for my driveway picks the car up very quick.
keep me in the loop i am curious what you end up settling on.
The Tesla broadcasts an iBeacon all the time. I use an esp32 in the garage to see if the car is located there. Connected to the same esp32 I have a sonar, this used the distance to tell if the car is in the spot. Between these 2 sensors I have the garage door opening and closing quite well. I also put an iBeacon in my old truck and get all the same advantages.
I've actually been using this for several months to see how it works and if it would be useful as an alternative approach. With Elon about to charge for using the Fleet API, it might become the only way of accessing the car state for free. So far I've only been investigating how it works and come across the odd issue (eg https://github.com/yoziru/esphome-tesla-ble/issues/82#issuecomment-2553492073).
Have not noticed this although I have not been using the Bluetooth too control it. I will experiment a bit today and see if I have the same behavior. I could also monitor it through the unifi perimeter add-on. Either way this would not interfere with my automation. When you drive up your are not on WiFi, and Bluetooth connects faster than the WiFi. My other automation closes the garage when we leave Bluetooth. I will try pinging the car and see if Bluetooth still works. You could use the sonar to tell if the car has started moving as a trigger for the gate to open on leaving. Or just one Bluetooth at the gate to open when you are in range (leaving our arriving).
So I just tested this I ran a ping to the Tesla's IP and was getting responses and it was still communicating with my Bluetooth proximity esp32. I looked at the graph for the proximity center and there were no disconnections while the car was home. It is possible you can't control it when it's on Wi-Fi but that the IBeaonn part is still broadcasting.
I tried again today. It seems rather inconsistent. I opened my car and sat inside with the door open. MY HA BLE sensors quickly went unknown seemingly confirming my original findings. However, I repeated this a few times, shutting the door etc. and found that the sensors didn't always go unknown. I think my ESP32 BLE scanner is at such a distance that it can be affected by little changes!
Interesting, is your scanner looking for the ibeacon or regular Bluetooth communication. my sensors are bluetooth proxy's. could just be a distance thing. Are you going to put/do you have a bluetooth proxy at the gate? The one for my driveway picks the car up very quick.
keep me in the loop i am curious what you end up settling on.