#14 The Deep Dive Fix Files: Week Ending 4 September 2026

This is a weekly roundup of significant sports tech problems that the endurance community has encountered and, where possible, resolved. Each entry covers the issue, the affected hardware or software, and the current best fix or workaround known to the community.

Garmin weather widget rain percentage stuck at zero across Forerunner 970, Fenix 8, Venu 4 and Forerunner 570

The Forerunner 970 weather widget shows the correct temperature, the correct condition icon and the correct map location, then reports a zero percent chance of rain while it is raining. Owners have posted photographs of the watch displaying rain on a window graphic next to a zero percent figure. The thread has been running since October 2025 and took new replies this week.

The fault reaches beyond the 970. Owners report it on the Venu 4 41mm, the Forerunner 570, the Fenix 8 and the Enduro 3. One Venu 4 owner narrowed the behaviour further: the value is either correct or zero, and never a plausible but wrong percentage in between, which points at a missing value rather than a poor forecast. A Fenix 8 owner in the Netherlands reports the hourly precipitation figures inverted while the daily figure stays correct.

Garmin support responded with the weather widget checklist. Restart the phone and the watch, confirm Garmin Connect shows the device as connected, start an outdoor activity to refresh the location, and keep Garmin Connect running in the background on iPhone. Owners have worked through those steps and report no change. Location appears to matter: one owner had the figures wrong for three weeks in a small Alpine town and correct again on returning to Milan, which fits the resolution of the underlying data source. The workaround adopted in the thread is a Connect IQ weather app such as Windy, which allows a choice of forecast model and carries a radar view. The native widget and the watch face weather data fields cannot be pointed at that source.

This issue remains unresolved — if you have encountered it and found a fix, the discussion is open on r/the5krunner.

Garmin Edge 850 embedded map panel will not stay North Up

Setting map orientation to North Up on an Edge 850 applies to the dedicated map page and does not apply to the map panel inside a multi field data screen. The owner who reported it runs a seven field layout with an embedded map and had the same layout behaving correctly on an Edge 840.

The cause is which control was used to set the orientation. Changing orientation with the compass icon on the map page is a temporary override that applies to that page only. Leaving the map page and returning restores the value held in the profile menu, and the embedded map panel reads the profile menu value at all times.

The setting sits under Activity Profiles, then the profile name, then Navigation, then Map, then Orientation. Selecting North Up there gives North Up on the dedicated map page and on the map panel in the data screen. An enhancement request has been submitted asking Garmin to make the compass icon write the change into the profile setting so that it saves and applies globally.

Garmin Edge 850 home screen showing Everyday Rest instead of the Garmin Coach workout

Installing firmware 31.33 on an Edge 850 broke the middle field of the home screen, which stopped showing the Garmin Coach workout for the day and displayed Everyday Rest instead. The same field had broken on 31.30 and had been working on 31.31.

The owner worked through the obvious candidates without result. He edited the Garmin Coach preferences, paused and resumed the plan to force a refresh, and raised his maximum heart rate by one beat on a suggestion found online. He then deleted the data and reset the device twice, configuring it from scratch both times with no backup restored and no sensors or activity settings transferred. The field stayed broken.

On 31.29 and 31.31 the behaviour was controllable. The Daily Suggested Workout and the Garmin Coach glance each carried a toggle for showing on the home screen. With the toggle off the field read Go for a ride, and with the toggle on the field showed the coach plan for that day. The toggle produced no effect on the affected releases, which left the 850 unusable for coached rides and sent the owner back to a Fenix 8 for the daily plan.

Firmware 32.20 restored it. The owner posted a one line confirmation that the field is fixed on 32.20, which is now live for the Edge 850 and the Edge 1050.

Garmin Edge 850 screen going black every few seconds after firmware 32.20

A new Edge 850 that ran two rides without fault on firmware 31.33 started blanking the screen every six or seven seconds during activities immediately after the 32.20 update. The screen returns each time and the cycle repeats until the unit is switched off. Five other owners have since reported the same behaviour on their own units.

The map update made it worse on the original unit. After installing maps through Garmin Express the screen stayed on for about three seconds from startup and then went black permanently. Removing all Connect IQ apps and data fields, restarting, and running a full factory reset did not recover it.

Factory reset works for other owners, but only briefly. One owner had normal behaviour for a single day after a reset and the flicker returned the next day. Another got a clean ride by restarting the unit three or four times in a row, then found the problem back after the next restart. A third had the unit crash completely on startup, held the power button down to force it off, and rode without any blinking, only for it to return after recharging at home.

Battery Save Mode is worth ruling out before assuming the display has failed. Under Power Manager it dims the screen after a few seconds and wakes it only at a stop or an alert, which produces a similar pattern. Owners who checked confirmed the setting was already off. Garmin has acknowledged the reports and is investigating. No rollback to 31.33 has been offered, and at least one owner has already sent a unit back for replacement on the assumption of an LCD fault.

This issue remains unresolved — if you have encountered it and found a fix, the discussion is open on r/the5krunner.

Garmin Fenix 8 heart rate, compass, altimeter and temperature sensors dead after software 22.41

A Fenix 8 47mm auto-installed software 22.41 overnight and lost most of its sensors. Battery drain ran at five to six percent per hour in power saver mode, dive water temperature read 32 Celsius against an actual 19, and the depth sensor returned a read error on a red background. The step counter stopped, the optical heart rate sensor stopped while the green LED kept blinking, and the compass, altimeter and barometer apps showed nothing. A factory reset changed none of it.

Garmin support asked for the BMX and Sensor Hub versions, found under Watch Settings, then System, then About, scrolling down five times. The versions shown indicated that the software had not fully installed on the device, which is why the system firmware reported 22.41 while the sensor firmware did not match it.

The recommended step is a manual reinstall. Hold the middle left Menu button, select Watch Settings, System, then About, rapidly press and release the top left Light button, and select Reinstall Software. The device restarts and reinstalls. On the original unit the install failed and the BMX and Sensor Hub versions stayed unchanged. A second route worked for one owner with battery drain only: reset the watch through Recovery and Reset to delete data and restore defaults, remove the device from Garmin Connect, unpair it in the phone Bluetooth settings, then pair again from the QR code and select keep default settings rather than restoring the previous backup. Restoring the backup carries the fault back onto the device.

Two further owners reported identical Sensor Hub versions and identical dead sensors, and the reinstall did not help either of them. Garmin has moved both cases to email. A buyer who picked up a Fenix 8 47mm reports the same behaviour out of the box and cannot complete pairing.

This issue remains unresolved — if you have encountered it and found a fix, the discussion is open on r/the5krunner.

Suunto Vertical 2 open water swim recording zero distance

A Vertical 2 logged zero metres over fifteen minutes of freestyle in an outdoor hotel pool recorded as an open water swim. The owner performed a soft reset, swam a second fifteen minutes, and the watch logged 52 metres. He had waited for the GPS arrow to turn green before entering the water.

The soft reset is what made the second attempt worse rather than better. A soft reset deletes the AGPS data held on the watch, so the next fix is acquired from a cold start. A green arrow indicates a usable fix rather than a good one, and open water mode derives distance entirely from position fixes taken while the wrist is above the surface.

The workaround is to sync the watch with the phone before the swim, which refreshes the satellite data, and then wait several minutes on the pre-start screen rather than entering the water as soon as the arrow turns green. Freestyle is required for this to work at all, since breaststroke keeps the watch under the surface and produces no fixes.

Pool mode is the correct choice for any pool, including one with a non-standard length. It counts lengths from wrist movement rather than GPS, and the pool length is editable in the sport mode options to match the pool being used. One owner running open water mode in an outdoor pool for triathlon training logged 449 metres against an actual 500, which sets a realistic ceiling for the mode when it is used this way.

Garmin Connect web will not open the individual sport inside a multisport activity

Opening a multisport activity in Garmin Connect on the web, selecting Edit, then clicking through to one of the individual sports returns you to the multisport summary page instead of the editor. Selecting the strength activity first and then choosing Edit Weight produces the same loop.

The browser and the operating system make no difference. The original poster sees it on Linux with both Chromium and Firefox. A second owner reports identical behaviour on Windows in every browser he has tried. Clearing the cache and switching browsers changes nothing. Standalone activities are unaffected: a strength session recorded on its own opens in the editor and the exercises can be corrected normally. The failure is specific to the individual sports held inside a multisport container, which is where triathletes and anyone logging brick sessions do most of their post-activity correction.

Garmin closed the report in late June with a statement that an update a few weeks earlier should have resolved it. Two owners replied that it had not. The thread became active again this week and Garmin has emailed both of them for further detail, roughly four months after the first report.

The phone app is the working route in the meantime. The same strength activity inside the same multisport session opens correctly in Garmin Connect on iOS and Android, and the original poster moved his editing there after giving up on the web version.

Suunto Race 2 display staying on during activities with heavy battery drain on software 2.56.18

A Race 2 on software 2.56.18 keeps its display lit for the whole of an activity with brightness set to Low, always-on display Off and raise to wake Off. The owner is a trail runner following a route, sitting on the standard data screen rather than the map. A long day on the Karwendel Hohenweg started at 79 percent battery and the watch was dead after around nine hours.

Display settings inside the training options are separate from the general watch settings and are the first thing to check. A watch configured correctly on the general screen can still run a lit display during exercise because the sport mode carries its own values. In this case both sets matched, which rules the explanation out here but not for everyone reporting the same symptom.

Always-on display Off with raise to wake Off is the correct combination for a screen that stays dark until a button press. Turning raise to wake On is a common suggestion in these threads and it produces the opposite of what is wanted, since the display then lights on every wrist movement. With both set to Off the screen should dim after about five seconds and switch off a few seconds later, regardless of whether navigation is running.

A soft reset is the step that restores the behaviour once the settings are confirmed correct. One long-term owner reports needing a soft reset after every charge on a Vertical 2 to hold daily consumption at six to seven percent, and describes the drain as severe without it. Nine hours of recording from 79 percent falls well short of the Race 2 specification, so the lit screen and the drain are likely the same fault.

Suunto Race S Runna plans stuck on Not synchronized with the watch

Runna sessions listed under My SuuntoPlus Guides all show the status Not synchronized with the watch on a Race S running firmware 2.53.42, with the Suunto app at 3.13.1 and Runna at 8.50.2 on an iPhone 14. Disconnecting the watch from the phone and the app, reconnecting it, and soft restarting both the watch and the phone left the status unchanged.

There is a ceiling on the number of stored guides. One Race S owner found that SuuntoPlus Guide syncing stopped once his total passed somewhere around fifteen to twenty, and deleting the old entries along with sessions a few days out restored it. The owner reporting this fault had only six guides, so the ceiling does not account for his case, but it accounts for a good share of the reports.

Syncing a watch face or a SuuntoPlus app from the store separates the two possible causes. If those transfer normally, the problem is confined to Guides and to the Runna integration. If they fail as well, the sync channel between the phone and the watch is down and Runna is not involved. On this Race S neither the watch faces nor the apps would sync, which points at the channel.

The escalation from there is to remove every Guide, then sync the other apps and watch faces first to confirm the channel is working, then let Runna push the plan again. Runna initiates the sync from its own side and clears completed sessions automatically, so the plan repopulates once the watch accepts guides. A hard reset is the remaining option if the channel stays dead.

Garmin Edge 1040 recording wrong power and cadence from Vector 3 pedals after firmware 31.31

An Edge 1040 updated through 31.29, 31.30 and 31.31 started alternating power values between zero, over a thousand watts and figures close to the rider’s normal output, on a flat route ridden at constant effort. Average power came out heavily inflated and the cadence trace lost its true zeros.

Battery contacts are the first thing to rule out on Vector 3, and in this case they were not the cause. The pedals were on the redesigned battery caps with two LR44 cells per side, the batteries had been replaced ten days before the fault appeared, the caps were not loose and the last ride before the firmware update was clean. Removing and refitting the batteries changed nothing. Analysis of the FIT file by another forum member showed a very low transmit and receive ratio between the left pedal, acting as master, and the head unit, with large gaps in the power data. Heart rate, speed, radar and light data in the same file were stable, which places the fault in the pedal link rather than in the head unit’s ANT+ radio generally.

Removing the Vector pairing from the sensor list, powering the Edge fully off and on, then searching for a new power sensor and re-pairing did not fix it on its own. What did fix it was checking the pedals in the devices section of the Garmin Connect phone app, where the right pedal turned out to have lost its connection to the left. Re-establishing that pairing restored reliable power data. Calibration completed normally even while the right pedal was unpaired, so calibration success is not evidence that both pedals are talking to each other.

A second owner reporting the same firmware saw right-side power far too low, with balance showing 70/30 and dropping to 100/0 for seconds at a time. Calibrating from a device other than the Edge 1040 brought his data back.

Garmin Edge 1040 Asc. to Next Course Pt. data field blank on courses

The Ascent to Next Course Point data field on the Edge 1040 shows nothing while riding a course. Distance to destination, remaining ascent and distance to the next course point all populate correctly on the same screen, which confirms the course carries the altitude data the field needs. The owner rides without turn guidance and follows the purple line.

The course source makes no difference. The original files are TCX exports from RideWithGPS dropped into the Garmin/NewFiles folder, and courses built in Garmin Connect and sent to the device behave identically. The RideWithGPS export format has not changed and the field worked on the same files until a few months ago.

The field is misnamed. With turn guidance enabled it reports the ascent to the next turn instruction generated by the Edge, not to the next course point placed in the file. A second rider with turn guidance on sees a value, and it is the ascent to the next turn. Turning guidance on is therefore the closest thing to a workaround, at the cost of the field no longer answering the question it appears to answer.

Garmin has asked both reporters whether Turn Guidance was enabled and has emailed them for further detail, which suggests the blank field with guidance off is being treated as a separate defect from the naming problem. A third owner has since reported that after the same update Dist Next now shows the distance to the end of the route rather than to the next turn.

Garmin Edge 850 weather data field showing minus 43C while the weather widget is correct

An Edge 850 on firmware 31.33 shows the correct temperature in the weather widget, 28C on the day of the report, while the weather data field on the ride screen reads around minus 43.1C. Photographs of both screens are attached to the forum thread.

The first response in the thread was that the temperature sensor is faulty and that a failing sensor would also corrupt elevation readings. That diagnosis is worth testing on your own unit, because a genuine sensor failure needs a warranty claim rather than a firmware fix.

A factory reset, deleting the weather field and adding it back all left the reading unchanged. The widget remained accurate throughout, so the temperature reaching the device is correct and only the data field is wrong. Riding with the weather glance rather than the data field is the practical route until Garmin ships a fix.

A second owner with the same symptom received a reply from Garmin support stating that the behaviour is due to the software, that a ticket is open with the US team and that owners should wait for a resolution. The first reporter received a warranty email offer, then nothing, and had the reading flicker between correct and incorrect while staying mostly wrong across a full ride.

Garmin Edge 1050 map update stuck at 95 percent with Error code 0

A map download started from Settings, Map Manager on an Edge 1050 runs to about 95 percent over Wi-Fi and stops there. Powering the unit off shows the map as complete, and pressing install returns Error code 0. Falling back to Garmin Express produces a different failure, with the download stopping after a few percent and the software reporting that it cannot download the map.

The instinct to clear space by deleting the existing maps is the one action that turns an annoying error into an unusable device. The owner who reported it deleted everything except the base map, the error persisted, and he was left with no navigation at all. Other owners across several Edge models are reporting the same error, which points at the Garmin servers rather than at any one unit. Garmin has confirmed it is fielding reports of the installation error and is investigating. Owners seeing Error 0 on the Edge, or Some Changes Not Applied in Garmin Express, are being asked to contact their regional support office.

One rider has posted a recovery procedure that restored maps, routing and ClimbPro on both an Edge 1050 and an Edge 840. Start the Wi-Fi download in Map Manager and let it run until Error code 0 appears. Hold the power button for 10 to 15 seconds until the screen goes dark, then power the unit back on and connect it to a PC over USB. Open the internal storage, sort by date modified, and find the recently created .img files the device downloaded but failed to install. Move those files into the Garmin/Maps folder on an Edge 1050, or into the root Garmin folder on an Edge 840, then disconnect and restart the unit. Map Manager will still claim an update is needed. Ignore that message and do not delete the maps again.

Garmin Fenix 8 hardware buttons not working on the morning report screen after software 22.44

A Fenix 8 on software 22.44 stops responding to its hardware buttons every morning on the morning report screen. The owner runs with the touchscreen disabled because he prefers the buttons, so an unresponsive button set leaves no way to operate the watch at all.

The only recovery he has found is a forced restart, holding the power button until the watch reboots. The buttons then work normally until the next morning report appears. Disabling the morning report looked like a fix for one day. The buttons responded the following morning, then failed again the morning after that, and the watch also dropped from 88 percent to 61 percent battery overnight.

Button calibration is the first thing to rule out, since the Fenix 8 accepts a calibration file placed on the device and a miscalibrated button set produces the same dead-button symptom. The counter-argument raised in the thread is that a forced restart restores the buttons, which a calibration fault would not. The other check is the lock state, because locking the touchscreen and locking the device are separate settings on the Fenix 8 and a device lock disables the buttons by design.

This issue remains unresolved — if you have encountered it and found a fix, the discussion is open on r/the5krunner.

Garmin Fenix 8 alarms disabling themselves overnight and failing to ring on software 22.44

A Fenix 8 Solar Sapphire on software 22.41 disabled a one-time alarm overnight. The owner confirmed the alarm was enabled before sleeping, with the alarm icon visible on the sleep watch face, and found it set to Inactive in the morning with no alarm having sounded. It had happened twice within a few days.

Restarting the watch cleared it. Garmin could not reproduce the behaviour on 22.41 and recommended power cycling the watch, deleting the alarm and recreating it, then setting a test alarm for a waking hour to confirm whether the fault returns.

The advice circulating on the forums is to use recurring alarms rather than one-time alarms. That advice has now failed. The same owner, running software 22.44, reports a recurring alarm that did not ring, with the icon and the scheduled time both visible on the sleep screen the night before.

A second owner hit the same thing on a beta release and found that rebooting did not help. What worked was visiting each alarm individually and either deleting it or toggling it off and on again.

Garmin Forerunner 970 pace flatlining to zero after pressing the lap button mid-run

A Forerunner 970 on the current release software records pace that drops to zero and flatlines on the Garmin Connect chart immediately after a manual lap press. Heart rate and elevation keep recording normally through the same section of the run, and only the pace trace is lost, in some cases until the end of the activity. Average pace and distance for the run come out distorted as a result. The owner dates the onset to the software update that arrived about a week before he posted.

Garmin has replied in the thread that beta version 18.23 has been released to address the issue. Owners can enrol in the beta programme and pull it down through System, then Software Updates, then Check for Updates, or wait for the correction to reach the public release channel.

This is a separate fault from the older Forerunner 970 complaint about pace dropping to zero after a sprint or hard acceleration on software 17.33. That one is triggered by a rapid change in speed rather than by a button press. Establishing which of the two is present comes before deciding whether the beta is worth installing.

The reporting owner had not tested the beta when the thread went quiet and said only that he would try it. No one else has confirmed that 18.23 clears the flatline, so the fix currently rests on Garmin’s word rather than on a community result.

Suunto Vertical 2 crashing during an ultra and splitting the race into three activities

A Suunto Vertical 2 used for the full Ultra Trail du Mont Blanc course crashed twice during the race. The first crash came about five hours in, at the approach to the Les Contamines aid station, and the runner attributes it to a waypoint notification. The second came roughly twenty two hours later, a few hundred metres short of Champex-Lac, and coincided with an incoming text message. Battery was not the cause, since the watch still held 31 percent the next morning after more than forty hours of recording with maps, navigation and the best accuracy setting active.

After each crash the watch reboots, saves the data collected up to that point and does not resume the activity. One 170 km race therefore came off the watch as three separate files, all of which auto-uploaded to Strava before they could be stitched together. Another rider in the thread sets every Strava upload to private by default so that split or corrupted activities can be dealt with before anyone comments on them.

A Race S owner says the crash reproduces when a route is being navigated at the same time as a SuuntoPlus Guides workout, and again when a third party live tracking app runs during navigation. He runs the same S+ workout three times a week without navigation and has never seen it crash. The UTMB runner avoided S+ apps entirely as a precaution and the watch still went down twice.

Suunto released hotfix 2.56.28 for the Vertical 2 and Race 2 on 31 August, described as improving firmware stability, fixing several crash issues and correcting pool swimming distance and duration. The rollout is staged at 50 percent for the first 24 hours and 100 percent after that. One owner whose watch had just come back from the service centre with a replaced battery and barometer sensor installed the hotfix and had another restart the following morning.

Suunto Race 2 display staying off during activities with no GPS or heart rate in custom sport modes after hotfix 2.56.28

A Suunto Race 2 became close to unusable after the 2.56.28 hotfix installed. The display stayed off during running, weightlifting and trekking activities regardless of the always-on display and raise-to-wake settings, and GPS and heart rate were unavailable in custom sport modes. Soft resets and a factory reset changed nothing, and after the factory reset the watch rebooted several times during a single activity.

Downgrading to 2.53.42 cleared all of it. The same owner then reinstalled 2.56.28 from the downgraded state to see whether a clean second installation behaved differently. It did not, and the install threw error 1403. Logs have gone to Suunto support. The fact that the symptoms track the firmware version in both directions points away from a hardware fault.

Two smaller changes carried over from 2.56.18 on the same watch. A small blue icon resembling an envelope now appears at the bottom of the activity screen in every sport mode, and the recovery heart rate screen after a run no longer shows the countdown, heart rate and BPM per second fields, leaving only the crown graphic.

Other Race 2 owners on the same hotfix report no problems at all. One describes the update as smooth with everything working, and another says only that the install ran longer than the advertised ten minutes. The rollout was staged at 50 percent for the first 24 hours from 31 August before reaching everyone, so the affected population is still being established.

Garmin Fenix 8 booting to a blue triangle with no fenix 8 animation on software 22.44

Garmin opened this thread itself and asked Fenix 8 owners whose watches power on to the blue triangle and then straight to the watch face, with no fenix 8 boot animation in between, to report in. The thread has been running since the 22.35 release and is still collecting reports.

Affected watches take around 55 seconds to boot. The blue triangle holds at full brightness for roughly 45 seconds, dims slightly, then the screen goes black, and the watch face appears only after a button press. One owner also lost Bluetooth heart rate broadcast on the same watch until a restart, with ANT+ still working throughout.

With the touchscreen disabled the animation appears and runs smoothly. With the touchscreen enabled only the blue triangle shows. With always-on display enabled and the touchscreen on, the watch keeps returning to the main screen after a reboot until AOD is toggled off and back on again. Owners who took a new watch straight to software 21.39 out of the box report the fault. Those who installed an earlier build first, or went directly to 22.35, do not. Neither 22.39, 22.43 nor 22.44 has corrected it, and one owner has been living with it since January.

Garmin says its engineers are still investigating and want the affected hardware. Owners on 22.44 who have already power cycled and still see the behaviour are being asked to post in the thread, and Garmin will contact them to discuss exchanging the watch.

This issue remains unresolved — if you have encountered it and found a fix, the discussion is open on r/the5krunner.

Garmin Edge 850 and Edge 1050 turning Battery Save Mode off by themselves on firmware 32.20

An Edge 850 on firmware 32.20 asks at every power on whether Battery Save Mode should be turned off. Pressing the X to decline should leave the setting alone. Instead the screen fails to blank during the ride, and Power Manager shows Battery Save Mode disabled. Enabling it again from Power Manager makes it behave normally for that ride.

It repeated the following morning. The owner declined the prompt, started riding, noticed the screen was still on, stopped, and found the setting off again. On one of the occasions he had just ridden over a heavy bump shortly before noticing, though he could not tie the two together.

The same owner then tested an Edge 1050 on 32.20. He enabled Battery Save Mode in Power Manager, powered the unit off and back on, saw no prompt at all, and found the setting disabled when he went back into Power Manager. Two different head units on the same firmware version lose the setting across a power cycle, one after declining the prompt and one without ever being asked.

The practical workaround is to treat the prompt as unreliable and go into Power Manager to confirm the setting before setting off, rather than answering the dialogue and assuming it held. For anyone running an Edge close to its battery limit on a long day, checking the screen behaviour in the first few minutes is the only quick way to tell whether the mode actually took.

This issue remains unresolved — if you have encountered it and found a fix, the discussion is open on r/the5krunner.

Wahoo ELEMNT Bolt V3 showing N/A for cadence and power then shutting off mid-ride

A Wahoo ELEMNT Bolt V3 with roughly 6000 km on it this year stopped reporting cadence and power mid-ride, showing N/A for both while speed, time and distance kept recording. The sensor menu listed every sensor as disconnected and searching. The unit then powered off on its own and would not restart until a long press on the power button some 30 km later, came back with Ride Resumed, still found no sensors, and switched itself off again.

Charging to 90 percent ruled out the battery. The unit booted normally and still failed to find the Wahoo cadence sensor, the power meter and a heart rate strap sitting next to it. It also would not connect to the phone app. The same sensors were recognised by the phone app itself, which places the fault in the head unit rather than in the sensors.

Unpairing everything on the phone, choosing Forget Phone on the unit, clearing the app data and pairing again produced the QR code and the pairing screen, then the error about sensors not being visible. A second phone that had never been paired with the Bolt gave the same result. A factory reset left the unit showing only the initial setup QR code, with the same failure when the app tried to pair.

Other owners in the thread suggest removing the Bolt from the phone Bluetooth device list before pairing, which had already been tried, and then going to Wahoo support. The stopgap offered is the Wahoo phone app, which records rides and connects to Bluetooth sensors directly, though it gives no navigation.

This issue remains unresolved — if you have encountered it and found a fix, the discussion is open on r/the5krunner.

More from last week’s Fix Files roundup.

Browse every issue in the archive at the Deep Dive Fix Files hub.

Last Updated on 4 September 2026 by the5krunner