Garmin Varia Rearvue 820 Radar development

The new Varia Rearvue 820 radar can pair in Ant+ mode and works great with the popular MyBikeRadarTraffic data field I created. But in order to access the new lateral information, one needs to have connected the sensor via the secure BLE connection instead of Ant+. This means that the BikeRadar object part of the Ant+ MonkeyC library isn't being populated at all b/c it's not using Ant+. 

I am wondering if a ConnectIQ app or data field can intercept/access the BLE data coming from the Rearvue when it is connected via Bluetooth instead of Ant+. My guess is that it cannot, but I am wondering if there are any Garmin developers who could put this on their roadmap to extend the BLE library https://developer.garmin.com/connect-iq/api-docs/Toybox/BluetoothLowEnergy.html in some way to make it easy to access newer devices/sensors that are paired with newer Garmin devices via Bluetooth instead of Ant+.

Garmin specifically said that third parties won't be able to access the new lateral data (presumably b/c they aren't sharing the "secure" Bluetooth credentials you would need). I would like to propose that Garmin allow us Connect IQ app developers to access this extra info via some sort of Bluetooth extension to the SDK either specifically for the new Reavue 820 radar or for any of the likely upcoming BLE connected sensors (rather than Ant+). The app shouldn't be involved with the pairing at all since the Garmin device is already managing pairing with the new BLE sensor (e.g., Rearvue 820 radar). It should just be able to access the data coming from the sensor.

I would really like to extend my data field to record the "history" of what cars behind the rider are doing including what position within the lane and how close they are laterally at the last reading (when they pass). But even if that is not possible, I want my data field to work when a user pairs the radar via bluetooth instead of via Ant+. Thanks in advance for any tips, or pointers in the right direction, or for committing to put this on the development roadmap for the Connect IQ SDK.

  • What's the point? Is it only for development? How will it work in real usage? Won't it connect via BT as well?

  • The goal is to collect lateral passing data and other vehicle statistics and share with city planners, transportation engineers, to better understand how the design of roads affects the way motorists pass cyclists. It doesn’t help a rider much during the ride, it’s post ride where riders can contribute data to make roads safer for all. About the new radar - it can connect via regular Bluetooth (LTE/Smart) without any of the lateral or vehicle size features, but that means the data field would need to manage the BT connection and parse the data directly. I’m working on decoding the BT data stream as Garmin only shares the official protocol with approved hardware developers (Wahoo, SRAM, etc…). I can only reliably get information about the closest car at the moment and only approach distance measurements, which means having to redo some of the speed calculations, which are done much better by the radar itself. The reason for this is that range data is reported in whole meters at about 8 readings per second, which means the rounding or truncation to the nearest meter causes weird fluctuations in speed. 

  • I wasn't asking about what's the goal of the DF. What's the point of doing that "hack" as a user? Will your users connect 2 or 3 phones to engage the BT connections just to be able to connect to the ANT from the DF? Doesn't sound very likely.

    BTW I don't have a radar, but in some HR straps you can enable/disable certain features using the phone app. Like: whether it has 1 or 2 bluetooth connections or if ANT is enabled. Isn't there such an app for the radar?

  • Yes, I feel like Ant+ is on its way out, especially since the new radar even if you do manage to connect it in Ant+ mode no longer populates the BikeRadar object correctly. See my separate bug report here:  BikeRadar object broken with Garmin Rearvue 820 

    As far as the bluetooth developer program, I have applied twice to that program using my university email address (I am a professor), and never heard back from Garmin either time. The application form on the right just opens up an email with a template of the information you are supposed to provide in the email. Based on the questions, it certainly looks like they are not working with independent developers. You need to be a big company with a large user base for them to even acknowledge the email (I guess?). Or maybe I have just been unlucky with whoever is managing that email address? 

  • The new radar (the Garmin Varia RearVue 820) can connect via Secure Bluetooth, or regular Bluetooth LTE/Smart, or  or Ant+ to Edge devices. Once you have selected Secure Bluetooth (the default), there is no easy way to get it to connect again via Ant+. Even just removing the device from the list of sensors isn't enough. When you try to add the sensor again, you don't get a prompt of what mode you want to use. It just automatically connects again via Secure Bluetooth. The only phone app for connecting to the radar via bluetooth is the Garmin Varia app, and it does not have a way of controlling the radar connection mechanism either b/c it only uses Secure Bluetooth, there is no Ant+ option.

    Regarding the workaround I described, it's just a workaround for people who have the new radar and still want to be able to save and view radar data. Garmin doesn't do that natively, you need an add on extension such as the one I created. If you are interested in the data, it's the only way at the moment to make things work with the new radar. I don't think it's realistic, but I figured it out and a few other people may be able to figure out / follow the steps to get it working. It's the best we can do until Garmin updates the firmware probably on a ALL devices with a new option for switching between Bluetooth and Ant+ as the connection mechanism. I think that is unnecessary, though, all they really need to do is provide us ConnectIQ developers with access to the data coming from a Bluetooth paired sensor. They have already done that with Bluetooth paired HR monitors through the heartrate field being populated. They may need to update the ConnectIQ SDK to make it possible to access the radar data. That's the purpose of my feature request. 

    The new radar does connect via Bluetooth LTE/Smart (probably what you meant by BT), but you have to parse the packets coming across and Garmin does not document the packet format unless you are an approved third party ... they have an application form I've sent in twice and never even got an acknowledgement that they received my application. Based on the fields you fill out in the application form, that program is targeted at large hardware manufactures such as Wahoo or SRAM who have display units that want to communicate with the radar.

  • Interesting how Garmin enforces secure BT. I wonder if you take this radar that already switched to secure BT, and try to connect to another Garmin device, that you never connected it to. Even then it doesn't let you connect via ANT? And what happens when you try to connect it to an older device that doesn't support secure BT?

  • They did that part right, older head units that don’t have support for secure Bluetooth only connect via Ant+. The main thing that is missing for newer devices is the ability to switch the connection. Should just be an option in the sensor menu.

  • I suspect that's due to EU RED (see the link I posted to DC Rainmaker from about a year back).

    "The core reason for this change is the European Union’s Radio Equipment Directive (simply called EU RED), which will ultimately take full effect next summer (it’s currently in a transitional phase). That directive covers a flotilla of different areas, but one of the most applicable pieces is that it requires authentication and encryption for wireless communications of personal information. Or, at the very least, it requires manufacturers to make you aware when data is being transmitted without such protections."

    We are close to "next summer".

    Currently I can only connect my watch with secure BLE to an HRM 200.  I've not tried the multiple phone thing so that may work, but it's like if secure is available, that's really your only option - no open connects for BLE or ANT in general

    Sounds like the data you want is only available with BLE, so you'll ever see it with ANT.