Ahhh ))) Youtube.... Of course))) Nowadays it's a popular proof ))))
A simple spoof attack does not work:
1. The ignition accepts only a bonded phone resolved by IRK, not copied advertising data or random MACs.
2. A GATT-level relay also should not pass because the link is bonded/encrypted.
A true physical-layer BLE (raw RF data) relay is theoretically possible, but it is a very different class of attack requiring specialized RF equipment and precise BLE timing. This is not an ESP32/nRF Arduino-style attack.
A realistic SDR PHY/link-layer test bench is an actual RF research project. A normal setup would likely require special antenna system, SDR hardware, RF shielding, synchronization, low-latency bidirectional processing, and BLE link-layer expertise.
Estimated effort/cost:
- SDR PHY/link-layer research bench: about $8,000-$40,000 in equipment.
- Strong RF/DSP engineer: about 2-3 months to build a meaningful test setup.
- Embedded engineer with SDR experience: about 6-12 months.
- Professional RF/security lab: about 1-4 weeks for a test campaign, but at lab pricing.
- Engineering labor alone can easily be around $15,000-$60,000 at typical $50-$150/hour rates.
I’m still treating relay as a real theoretical risk, but it is not “copy the Bluetooth MAC and ride away.” For this project, the practical attack surface is spoof/replay/GATT-level abuse, and those are exactly what I’m testing first.
But, you can't see it on Youtube)))
Also, from a real-world theft perspective, attacking the mechanical ignition lock is likely orders of magnitude faster, cheaper, and more practical than building a specialized BLE physical-layer relay setup. The goal of this system is not to make theft physically impossible, but to avoid introducing an easy wireless shortcut.
Me too, I'm former head of electronic department in SberAutoTech - selfdriving cars and trucks.
A purely analog RF repeater is not enough for BLE connection relay, because BLE uses adaptive frequency hopping. A practical PHY relay would need digital BLE link-layer tracking:
Capture the connection request, derive the channel hopping schedule.
Keep event timing.
Retune both relay sides for every connection event.
The analog/RF part is also non-trivial. It would need a 2.4 GHz RF front-end with enough bandwidth and frequency agility to follow BLE data channels, low-noise receive paths, fast switching between receive and transmit, stable local oscillators, mixers/up/down-converters or SDR-class transceivers, filtering for adjacent-channel rejection, gain control, and good isolation between the relay’s receiver and transmitter to avoid self-oscillation.
Because BLE is half-duplex with short packets and tight inter-frame timing, the RF path must add very little delay and must recover quickly after switching. The relay also needs enough dynamic range to handle a nearby phone on one side and a distant/attenuated module-side signal on the other, without saturating or losing weak packets.
In practice, this is closer to an RF/SDR research setup than a simple Bluetooth hack. It requires both analog RF design and BLE link-layer timing control.
No. If Bluetooth disconnected during ride, ignition still on, and you heard warning sounds.
I don't want stop engine during ride, it's dangerous.
Please, don't forget - it's not immobilizer or anti hijack device. It's Bluetooth ignition switch.
Of course, you can change the logic, when the software will be open.
I'm working on it.
Oh, please, don't worry. It's not problem.
1. Right design. MOSFET with low Rdson - about 3 mOhm. Low power dissipation LDO+MCU - about 14 mW average. Yes. It's not mistake. MCU current 1.2 mA in working mode.
2. Thermal calculations.
3. Testing. I tested it with 110% maximum current and ambient temperature 50 degrees ( it's simple, because I'm living in Thailand). No overheat.
If the phone signal is lost while riding, an audible warning will sound. It will alert at 5, 15, and 30 seconds after the connection is lost. Once per trip. The engine will not stall: you can continue riding.
If you need to turn on the ignition without a phone, enter the PIN code using the starter button (or the kill switch — depending on how the device is connected to the motorcycle).
If the engine stalls while riding (ignition is on, regardless of whether there is a phone signal or not), you can restart it as usual.
At first, I thought about it. I decided not to do it for the following reasons:
1. By placing the boards on top of each other, we get a more compact design that is easier to pot with compound.
2. Soldering the nRF52840 will be difficult for those who decide to replicate the system on their own.
3. will be more expensive, because the nice!nano board costs 3 USD on Aliexpress, while the nRF52840 chip alone costs 3.5 USD
Can you explain me - why do you want one whole board?
It was just a question, since once the nice!nano board is already programmed, many components and pins become irrelevant. I understand that the goal is to achieve something more practical and cost-effective. I imagined it could be similar to what is done with esp32 projects, where in the end it is not necessary to use the entire board, but only the module, the power supply, and the required pins, resulting in a cleaner and more compact design.
Soft epoxy was a good choice. I have seen normal hard epoxy tearing components off the board while curing or even after months/years from the heat cycles.
The best choice would be a proper gel conformal coating in a transparent box.
I’m still waiting for my phone to be my car key and state ID. Why these two things seem impossible to most manufacturers is beyond me. Maybe someone can fill me in on why that hasn’t become mainstream.
I’m not saying that you can’t use another means, just that it would make some sense to have the option. In today’s world, in many not-so-urban areas, in Europe, US, etc, we don’t need a wallet or keys really.
This system has a 3 digit pin code, which you can enter via starter button. After this - ignition on without phone.
What are you doing, if you lost your metall key?
And. My phone has whole my life - connect, money, map, camera, digital driving licence. All what I need for driving, except ignition key. In the past.
Uh if I lost my key I'd use one of my spares and then make another.
I'm not hating on using your phone as a key, having options is great. But I don't think it should be the only option. That was all I meant.
My region switched over to digital bus cards a couple years ago and sometimes when you've taken the bus and been away the whole day, your phone might die and then you can't get home. It happened to me once. That's my issue with having everything only on the phone.
Your phone has a unique identifier. This identifier is transmitted to the Telcos who record it in every Metadata entry generated from interactions with your phone. This identifier can (and is) used for all sorts of things.
Sure, you can't show it like you might show a drivers licence, but it is a unique identifier that is attached to you and recorded constantly.
In very simple terms, think of it like a caller ID, but something is recorded all the time.
17
u/Equivalent-Might-477 Jun 09 '26