To be clear, this is why I wish the keyfob used RF, and not bluetooth.
Because Bluetooth sucks.
Bluetooth sucking is not Lucid's fault, because as mentioned earlier, Bluetooth
always sucks.
Choosing Bluetooth as their technology of choice for the keyfob? Yes, that is Lucid's fault.
And before anyone tells me their AirPods work fine, most Apple devices including AirPods support Bluetooth Class 1, which have a 40 times higher maximum transmit power than the more common Class 2.
From the Air manual:
Component: Bluetooth® Vehicle Key
- Manufacturer: Pektron Group Ltd
- Model: A-0820G01
- Operating Frequency: 2402-2480 MHz
- FCC ID/ISED ID: AQO013/IC: 10176A-013
- Maximum Transmit Power: 2402 – 2480 MHz: ≤ 1.36 mW EIRP
Component: Access Control Module BTLE/LF Node
- Manufacturer: Pektron Group Ltd
- Model: A-0819G13,A-0819G16
- Operating Frequency: 125 KHz, 2402-2480 MHz
- FCC ID/ISED ID: AQO012/IC: 10176A-012
- Maximum Transmit Power: 125kHz: ≤ 0.0057mW EIRP, 2402 – 2480 MHz: ≤ 1.35 mWEIRP
From the Gravity manual:
Component: Keyfob
- Manufacturer: Marquardt GmbH
- Model: UK1
- Operating Frequency:
UWB: 5-9 GHz
NFC: 13.56 MHz (passive tag)
BLE: 2.4 GHZ
- FCC ID: IYZUK1
IC: 2701A-UK1
- Maximum Transmit Power: UWB: ≤ -41.3 dB/MHz
BLE: ≤-1 dBm
Component: UWB/BT Anchor MQD
- Manufacturer: Marquardt GmbH
- Model: MUB1
- Operating Frequency: UWB: 5-9 GHz, BLE: 2.4 GHz
- FCC ID: IYZMUB1
IC: 2701A-MUB1
- Maximum Transmit Power: UWB: ≤ -40 dBm/ 0.001 mW
BLE: ≤ -3.19dBm / 0.48mW
Component: UWB/BT Anchor MQD
- Manufacturer: Marquardt GmbH
- Model: MU3
- Operating Frequency: 5-9 GHz
- FCC ID: YZMU3
IC: 2701A-MU3
- Maximum Transmit Power: ≤ -40 dBm/ 0.001 mW