-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tesla presence seems unreliable #65
Comments
It happened again today. Three times in a row now. |
Others have reported similar issues. I have not had the issue myself and have been unable to reproduce. Temperature might be a factor, it's winter here in the UK so no chance of it getting too hot for me |
Hi Iain,I don’t know if your stuff and the iBeacon tracker play together (I’m guessing that you don’t even use the beacon), but I am going to try to compare their outputs. I might also build the ESPHome ESP32 iBeacon hub and see what it says. Neil Higgins ***@***.*** 19 Nov 2024, at 6:26 PM, Iain Bullock ***@***.***> wrote:
Others have reported similar issues. I have not had the issue myself and have been unable to reproduce. Temperature might be a factor, it's winter here in the UK so no chance of it getting too hot for me
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Not sure. I am experimenting with https://gateway.theengs.io/ to track my Apple watch using the same RPi. Seems to work fine. I therefore suggest you can run another iBeacon tracker on the same device, which might turn out to be more reliable than the Presence detection used on this project |
I have Googled around a bit (a sad excuse for research, I admit) and I must say I can’t find any confirmation that the Model Y puts out a conforming iBeacon. That leaves open the question as to why Presence ever worked for me (if it relies on an iBeacon) but might also explain why it stopped working (I have recently had two Tesla software updates in quick succession). So if I can scan for Bluetooth devices of any kind (not just iBeacons), I might have better luck. Neil Higgins ***@***.*** 20 Nov 2024, at 2:40 AM, Iain Bullock ***@***.***> wrote:
Not sure. I am experimenting with https://gateway.theengs.io/ to track my Apple watch using the same RPi. Seems to work fine. I therefore suggest you can run another iBeacon tracker on the same device, which might turn out to be more reliable than the Presence detection used on this project
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
FWIW, I took a deep breath and had a look at the _core source code. It appears (to me) that Presence is not derived from an iBeacon. And for the fourth day in a row, my Tesla is shown as “Away” when it’s at home. It behaved in more-or-less random fashion between about 5:30am and 11:00am, then settled to “Away”.
From: Iain Bullock ***@***.***>
Sent: Wednesday, 20 November 2024 2:40 AM
To: tesla-local-control/tesla_ble_mqtt_docker ***@***.***>
Cc: etherbrat ***@***.***>; Author ***@***.***>
Subject: Re: [tesla-local-control/tesla_ble_mqtt_docker] Tesla presence seems unreliable (Issue #65)
Not sure. I am experimenting with https://gateway.theengs.io/ to track my Apple watch using the same RPi. Seems to work fine. I therefore suggest you can run another iBeacon tracker on the same device, which might turn out to be more reliable than the Presence detection used on this project
—
Reply to this email directly, view it on GitHub <#65 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKEPQNHZVSWPM6XGQQ6DFC32BNSWRAVCNFSM6AAAAABR7MZLH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWGIYTKMBYHA> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AKEPQNADGB5JT2OIOC66W5L2BNSWRA5CNFSM6AAAAABR7MZLH2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUUGCQ3A.gif> Message ID: ***@***.*** ***@***.***> >
|
Sorry I misunderstood your previous quetion. You are right the code doesn't look for iBeacons it just scans for the BLE MAC; which should work reliably, but clearly it doesn't. I recommend you try turning off Presence detection in this code and using another docker container on your device which can provide the required functionality. I haven't tested any project for doing this for the car, but as I said earlier I have got https://gateway.theengs.io working for tracking my Apple watch, so maybe it can be configured to track your car |
Yes, I’ll try that.
I have raised an Issue on the _core project – hopefully their powers of diagnosis are better than mine.
Cheers,
Neil
From: Iain Bullock ***@***.***>
Sent: Wednesday, 20 November 2024 4:39 PM
To: tesla-local-control/tesla_ble_mqtt_docker ***@***.***>
Cc: etherbrat ***@***.***>; Author ***@***.***>
Subject: Re: [tesla-local-control/tesla_ble_mqtt_docker] Tesla presence seems unreliable (Issue #65)
Sorry I misunderstood your previous quetion. You are right the code doesn't look for iBeacons it just scans for the BLE MAC; which should work reliably, but clearly it doesn't.
I recommend you try turning off Presence detection in this code and using another docker container on your device which can provide the required functionality. I haven't tested any project for doing this for the car, but as I said earlier I have got https://gateway.theengs.io working for tracking my Apple watch, so maybe it can be configured to track your car
—
Reply to this email directly, view it on GitHub <#65 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKEPQNA2C6VWVJIDLVK52T32BQU77AVCNFSM6AAAAABR7MZLH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBXGYZDCOBWGE> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AKEPQNBTCJA6XNBIUFSM2FT2BQU77A5CNFSM6AAAAABR7MZLH2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUUIYMOK.gif> Message ID: ***@***.*** ***@***.***> >
|
I'm a dev on the core project too, so it might become a circular conversation. @raphmur @baylanger have a look to see what you think, there are issues with presence detection but I can 't replicate it myself |
Good for you! (seriously). Bear in mind that I am now uncertain whether charge rate setting controls will get to the Tesla when the Presence is “Away”. If not, the whole bloody exercise is pointless, yah?Neil Higgins ***@***.*** 20 Nov 2024, at 5:22 PM, Iain Bullock ***@***.***> wrote:
I'm a dev on the core project too, so it might become a circular conversation.
@raphmur @baylanger have a look to see what you think, there are issues with presence detection but I can 't replicate it myself
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
As long as the car is not really away, the commands will still work. The presence detection and command sending are completely seperate and independent of each other in the code. Others who have reported this issue have found command sending still works even when presence doesn't |
That’s reassuring. Thanks. Neil Higgins ***@***.*** 20 Nov 2024, at 6:55 PM, Iain Bullock ***@***.***> wrote:
As long as the car is not really away, the commands will still work. The presence detection and command sending are completely seperate and independent of each other in the code. Others who have reported this issue have found command sending still works even when presence doesn't
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
There might be other way to detect presence that you anyway have or need (I use evcc). PS: I did struggle a bit to find the right device to talk reliably BLE with the car... at the end I am using a Pi 4 and that what has been the most reliable for me. I believe external BLE USB key might be good as you can position it where you want with a USB extension cable. |
RPis with built in BLE seem to be good (I'm using RPi3b+). Many people report issues with USB devices. Probably depends exactly which type you have. |
Just chiming in as I'm encountering the same issue from time to time. |
See here. Work in progress to resolve what I believe is causing this for many people. In the meantime if you have automations trying to send commands when the car is away it will definately cause problems |
I have implemented improvments into v0.4.3b-dev which is on DockerHub. Main changes are robustness improvements, see the CHANGELOG. |
I'm still having presence inconsistency, but it seems to be more a value not being updated than a BLE issue: MQTT topics are updated while polling, but presence is not. Maybe presence should be set to true whenever a value is updated?
|
Interesting. There are two 'presences' being reported here:
This one is derived from a call to body-controller-state and results in the Presence_BC binary_sensor in HA. It should get updated during the polling
This is derived from a passive bluetooth scan i.e. doesn't talk to the car at all. It results in the Presence binary_sensor in HA. It doesn't get updated duirng the polling it is done seperately I am currently recommending that the passive presence is used as I find it more reliable, and it gets updated more often. However maybe you could compare trends to see how they compare on your system over time |
@iainbullock indeed, after 2 days using the |
Both presence entities work reliably on my setup, but I know it's not the case for some. I will therefore continue to offer both which the user can decide which is best for them, or maybe even apply some logic in a HA to use both |
Just a heads-up, not an issue until confirmed by someone else. Twice in two days the Presence has remained “Away” after I returned to the garage from an outing. The only way I could restore correct operation was by rebooting my HA machine (RPi5, HA in a Container, located right beside the Tesla in the garage). The Pi5 talks WiFi to an access point which is also located in close proximity. The Tesla shows up in BLE Hero on my phone. I do not have the HA BLE Tracker installed. As best I can recall, the Presence indication has been quite accurate and responsive prior to this. Summer is warming up the garage down here in AU, so it may be a chip temperature problem, although I do have the Pi in an enclosure with a fan.
The text was updated successfully, but these errors were encountered: