Impossible to pair keys with the car with 4.0 bluetooth dongle #116
Comments
|
This sounds very similar to the issues I was having. #106 I've managed to solve it but I'm not sure how. When pairing was successful, I received the following (on attempt 2): For whatever reason, the key isn't being delivered to the car. My final setup has my Pi4B connected by ethernet, with WIFI turned off. Its probably 2 metres away from the car, inside the house. |
|
I will try to move the NUC inside the car… Hope this will work, but I don’t know if it should be near the car only for the pairing or always. in my case, I see the car at « home » correctly, and it is well detected each 10 seconds, even the NUC is at more than 10 meters from the car. if it is only for the pairing, then it is OK… I just need to pass this step X-D |
|
I guess, I couldn't be closer... And it didn't work again.
I don't understand why the presence is detected, and when I ask to deploy the keys, it becomes not detected and come back after the deploying procedure...
|
|
Yes you can't get closer I agree! Presence Detection is done by a completely different method compared to communication with the car. It doesn't use the Tesla provided vehicle-command library. Maybe the system doesn't like your hardware. What hardware are you using? Can you try a different Bluetooth adapter? Do you have another device e.g. Raspberry Pi that you could try (with the docker version of this project perhaps) |
|
I am using the dongle Sena UD100a: http://www.senanetworks.com/ud100-g03.html i have two raspberry PI3b, I don’t use anymore. it could work with it ? the bluetooth was not going far enough, with the raspberry, that’s why I bought the Sena in the past, before to change for a NUC. |
|
Maybe something is missing in my configuration… I have actually nothing in the configuration.yaml file regarding the bluetooth. I only use these integrations for the bluetooth :
This is the Sena USB dongle :
I don’t see any device in the ibeacon tracking integration. It was the case when I installed HA at the beginning, but as I didn’t know what was the device, I deleted the integration, and now nothing appears.
|
|
I added the integration Bluetooth LE Tracker, via the configuration.yaml file, and I see the bluetooth name of the Tesla inside the file known_devices.yaml. I don't know if there is other things I can try, via command line in SSH or something else ? |
|
The car been finally added in the iBeacon tracker integration :
The signal seems to be OK, but the pairing is still not working.
|
|
Not sure what you could try next, other than different hardware. Also I'm not sure having Bluetooth LE Tracker integration interferes with this or not (although it seems it wasn't setup previously and you still had the problem) @raphmur have you any ideas? |
|
Hi there @HiFuGa, Thanks for all the detailed feedback. I wonder however if there is a compatibility issue with your hardware ?
Can you try with a different device, supporting bluetooth 5.0 and BLE? |
|
Hi @raphmur ! HA is installed directly on a NUC, I followed this procedure : https://www.home-assistant.io/installation/generic-x86-64/ No VM or proxmox used. The Sena UD100 is supported and listed here :
This is this one : https://www.lextronic.fr/dongle-usb-bluetooth-longue-portee-ud100-3805.html Pictures of mine :
I tested again this morning, and I see the signal dropping each time I push the deploy-key button.
I will try to see if I can find another dongle somewhere... |
|
I removed all batteries and deconnected the power supply of all bluetooth device but it is still not working. The connection is lost with the ibeacon device in HA... Reharding this point : "1/ Remove any previously deployed BLE keys from vehicle before deploying this one". Should have remove as well the key linked to my phone ? Or it is only for previous keys used by this addon ? It seems to match the time each time I asked to deploy the key, I found this in the HA logs :
|
|
I've the same issue with realtek bt adapter of my nuc, with ha supervisor. |
|
I appreciate there are various specifications of NUCs however have @guyank @dettofatto either of your got built in Bluetooth adapters (of any kind not necessarily BLE)? |
|
This is mine: |
|
I see it has built in Bluetooth. Please can you remove the usb Bluetooth and try it with the built in? (At least I think it has I can't really read Italian) Thanks |
I’m just using the Pi4 B’s built in bluetooth |
Ok that should work we have others using a RPi4 with no problems. I use a RPi3b+ running the Docker version of this project with no issues I'm out of ideas for your situation. Do you have other hardware you could try? |
|
Sorry. As I thread in the other thread, I’ve got it working but had the same symptoms. Not sure what I changed, but being further away but connected by Ethernet is ultimately what worked. |
|
Ok thanks. I sometimes forget who has already updated. Glad it works for you ! |
In my situation I'm already using realtek internal BT, so I must try with an usb bt. I'll buy and I'll try. |
|
I've bought but Anyway can I use hci1, instead the default hci0? I can't disable hci0, and as default is the internal. So the addon connect only with hcio. |
|
I was going to suggest looking at this post, but I see you already have. #114 (comment) Let's take the conversation over to that post, at least until we've gone as far as we can with that idea |
|
Hmmm yes, nice observation. Indeed, freeing the Wifi/BT device from the main standard traffic is better. But this does not look to be the issue of @HiFuGa. @iainbullock , I wonder if the communication protocol with the Tesla is only supported in bluetooth 4.2 minimum? The Sena dongle seems to be only bluetooth 4.0. @HiFuGa maybe can you try with a powered USB hub? |
|
|
With 5.3 adapter it is all ok! |
|
@dettofatto That's good news. We will note that the minimum spec is >4.0 (we don't know what exactly). I think we should recommend >=5.0 I believe @guyank has got it working. I will keep the thread open for now as I think @HiFuGa still has issues. |
|
Hello, You found the root cause. But instead buying a new bluetooth dongle >5.0, I bought a VE-Tronic charger to manage the charge automatically when solar panels are producing. |
HiFuGa
changed the title
|
Sorry for adding a comment, but i've done some new discoveries.
|
|
Thanks for this. Did you try all these? I hope you could send those back that didn't work! It's therefore not just a case of BLE version. Maybe the underlying Bluetooth chipset. Maybe also depends on whether using HAOS (used by the HA add-on version of the project) or Alpine (which the Docker version uses), as they may have different Linux drivers |
Hello,
I can not pair the keys with the car, with the addon on HAOS.
I initialy followed the doc of the addon :
Then I saw some users met some trouble and the doc of the docker version has been modified, to tell to put the card key just after pushing the pairing button :
I did it, but nothing changed, I don't see any pop-up on the screen of the car.
This is what I have in the logs :
The bluetooth is working fine (I can command bluetooth devices in my home).
The car is saw :
I tried to add a longer USB cable, to be nearest the car, the bluetooth devices in my home are still working fine, but I got the same logs and still no message on the screen of the car...
I you have any advice...
Thank you !
PS : There is as well maybe a bug with the wake up fonction :
I rebooted the car, in the logs of the addon, I saw the addon was trying to wake up the car, but without success.
I had to restart the addon to get back the status "presence" at ON.
The text was updated successfully, but these errors were encountered: