Garmin Edge support: on the bench, in the open

What exists today

The Edge's own radio language, rebuilt from scratch inside the same head-unit layer the ELEMNT uses:

• How messages are packed, checked for corruption, and routed.
• How a phone introduces itself and pairs with the device.
• All of it under automated tests against recorded real-device traffic.

None of it is wired into the shipping app yet — a deliberate gate: nothing gets claimed until it has run against a physical Edge.

What's left

On-device bring-up against a Garmin Edge 540: authentication and pairing on real hardware, then the feature dialects — course push, activity pull, screen notifications — validated byte-for-byte, the same way every ELEMNT feature earned its place.

What Edge riders will get

The same companion, not a port: one app whose planning, weather engine, rule engine, ride archive, Strava queue and live tracking already exist and are brand-agnostic. The Garmin layer only has to move bytes; everything above it is built and riding daily on Wahoo hardware. Where the Edge protocol allows, that means:

• Course push from the phone, with the same route planner and POI editor.
• Activity download into the same one-list ride history, with Strava auto-upload.
• Weather look-ahead and custom rules as on-device notifications.
• Live tracking through BikeScout's own backend — no vendor cloud.

Anything the protocol turns out not to allow will be listed here plainly, the way the comparison table does for Wahoo.

Why cross-brand is credible

BikeScout's ELEMNT support wasn't built on a vendor SDK — it was built by treating the head unit as an honest peer: read the protocol, respect the device, verify on hardware. That method is brand-portable, and the codebase was shaped for it from the start: one HeadUnit abstraction, transport seams, and a domain layer that doesn't know which logo is on the mount.