Newest firmware break vehicle commands?

[williamd314]

I've added the integration, I can read all of the sensors and points that are passed through the API to HA. However, I've been trying to pair my car with HA using a bluetooth proxy, and cannot get it to pair. Verified the BT proxy is scanning.

I have 2024.19.04 installed in my R1S Dual Motor (large pack).

Viewing the logs on the BT proxy device, I tap "Press" for the "Pair" command, and get this in the logs:

[12:47:25][I][bluetooth_proxy:282]: [0] [40:F3:B0:78:02:61] Connecting v3 without cache [12:47:25][D][esp32_ble_tracker:219]: Pausing scan to make connection... [12:47:25][I][esp32_ble_client:067]: [0] [40:F3:B0:78:02:61] 0x00 Attempting BLE connection [12:47:34][D][esp-idf:000][BTU_TASK]: W (77387840) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e [12:47:35][I][esp32_ble_client:084]: [0] [40:F3:B0:78:02:61] Disconnecting. [12:47:55][D][esp-idf:000][BTU_TASK]: W (77408845) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x100 [12:47:55][D][esp-idf:000][BTU_TASK]: W (77408848) BT_APPL: gattc_conn_cb: if=4 st=0 id=4 rsn=0x100 [12:47:55][D][esp-idf:000][BTU_TASK]: W (77408851) BT_APPL: gattc_conn_cb: if=5 st=0 id=5 rsn=0x100 [12:47:55][D][esp32_ble_client:172]: [0] [40:F3:B0:78:02:61] ESP_GATTC_DISCONNECT_EVT, reason 256 [12:47:55][D][esp32_ble_tracker:270]: Starting scan...

I take this to mean the pair is using the Bluetooth Proxy to attempt a connection. However, when sitting in the car, I tap "Setup" for the Phone Key showing from my HA (it shows as simply "Home"), and then tap "Press" to pair, but it never makes the connection.

Features that should be vehicle commands like "Wake" and "Windows" (venting), it shows as Unavailable.

[natekspencer]

Can you also enable debugging for the Rivian integration, attempt the pairing process again, and post those logs as well?

[doggkruse]

Also to clarify, is this a Gen 1 vehicle that has been paired on a previous firmware?

[spiffyvmlab]

I have this same issue. I have a 2024 (Gen 1) R1T, running 2024.27.01, and a bluetooth proxy in ESPHome. The phone key shows up, but when I try to do the setup and press the button in the integration nothing happens. I can see some logs in the bluetooth proxy when I press the button on the HA side, but nothing after that.

[natekspencer]

@spiffyvmlab can you please enable debugging for the rivian integration and post your logs to enable us to help you?

That being said, we are aware that there may be changes coming to the pairing process for gen 1 vehicles as well.

[cowboyrushforth]

Hi there,

Have a Gen 2 here. My logs at first contained this a couple times:

2024-10-05 11:01:37.821 DEBUG (MainThread) [custom_components.rivian.button] Found 30:AF:7E:7D:5E:CD: Rivian Phone Key (RSSI: -85) 2024-10-05 11:01:37.823 DEBUG (MainThread) [custom_components.rivian.button] Making sure BT controller can be paired 2024-10-05 11:01:37.823 WARNING (MainThread) [rivian.ble] Couldn't determine BT controller path, defaulting to /org/bluez/hci0: {'source': '84:FC:E6:52:20:28', 'address_type': 0} Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/rivian/ble.py", line 145, in set_bluez_pairable path = device.details["props"]["Adapter"]

KeyError: 'props'
2024-10-05 11:01:37.827 ERROR (MainThread) [rivian.ble] interface not found on this object: org.bluez.Adapter1
2024-10-05 11:01:37.827 WARNING (MainThread) [custom_components.rivian.button] Couldn't set BT controller to pairable, phone pairing may fail
2024-10-05 11:01:37.827 DEBUG (MainThread) [rivian.ble] Connecting to 30:AF:7E:7D:5E:CD: Rivian Phone Key
2024-10-05 11:01:50.114 DEBUG (MainThread) [rivian.ble] Couldn't connect to 30:AF:7E:7D:5E:CD: Rivian Phone Key. Make sure you are in the correct vehicle and have selected "Set Up" for the appropriate key and try again

Now after playing with it a lot more, I just see this any time.  I have tried rebooting everything including the car.

2024-10-05 11:23:08.420 DEBUG (MainThread) [custom_components.rivian.button] Searching for Rivian Phone Key
2024-10-05 11:23:38.421 ERROR (MainThread) [custom_components.rivian.button] Rivian Phone Key not found
2024-10-05 11:23:38.421 DEBUG (MainThread) [custom_components.rivian.button] Unable to complete pairing

I have an esphome esp32-s3 based bluetooth_proxy, and it works great with other devices such as my home smart lock.  

The device is temporarily on a usb powerbank, and it is sitting on the dashboard of the car.  Overall the instructions work good, I enabled 2fa, and then re-configured the integration, and then the opportunity to "set up" appeared in the rivian dash.  I have tried undoing and redoing this a few times, and tried changing the scan_parameters: in esp32_ble_tracker, but nothing seems to work.  Have also tried making sure there are no other bluetooth devices nearby, and good signal to wifi as well.

[spiffyvmlab]

@spiffyvmlab can you please enable debugging for the rivian integration and post your logs to enable us to help you?

That being said, we are aware that there may be changes coming to the pairing process for gen 1 vehicles as well.

So sorry. I completely missed this reply. I'll enable it and try pairing again later this afternoon.