Pile of cut logs stacked in a foggy forest clearing, muted greens and browns, calm quiet mood. Sweatfest

Set Up Zwift’s Companion App for Live Race Updates

Zwift’s Companion app can put live ride data on a phone, send event reminders and make a Tuesday SweatFest race easier to follow without leaving the main game view. Depending on your sensors, the display can include power, heart rate, speed, cadence, distance and elapsed time. The annual league is organised from the Pacific Northwest, but riders across Australia and elsewhere can compete in its two 10-week seasons, weekly category races, prime segments and overall points standings.

Getting the pairing right before race night is simple, yet small mistakes can leave a phone showing stale data or missing the start alert. Use the same Zwift account on the computer and phone, confirm that both devices have a working internet connection, and leave enough battery for a full race plus setup checks. This matters in Australia, where race times shift between standard time and daylight saving and a Tuesday event can fall on a different local day for some riders.

For real-time SweatFest race updates, the Companion app is best treated as a live dashboard and reminder tool rather than a second race client. It mirrors selected metrics while you ride, but the game remains the authoritative place for your position, category, prime results and finish time. After the event, official points and overall standings should be checked through the league’s published information and Zwift event pages.

Check compatibility, timing and race details

Before installing anything, check that your phone supports the current Zwift Companion release and has a few hundred megabytes of free storage. Download it from the Apple App Store or Google Play, verify that the publisher is Zwift, and review the permissions it requests. Bluetooth, notifications, physical activity and nearby-device access may all be involved, depending on the operating system and the way your sensors are connected.

Menu labels change more often in companion apps than in the main Zwift program, so keep a second reference nearby while you work through the process. A current Companion setup reference can help with device and pairing variations, but the official in-app instructions should take priority if the two differ. Avoid APK files, unofficial stores and “Zwift support” messages that request your account password.

Next, open the SweatFest race schedule and the corresponding Zwift event listing. Confirm the event date, course, race type and assigned category, since choosing the wrong listing can produce a valid but irrelevant reminder. Check the displayed start time against your local clock rather than assuming every Australian rider starts on the same evening. Brisbane remains on AEST throughout the year, Sydney and Melbourne move to AEDT during daylight saving, and Perth uses AWST, which is two hours behind Brisbane in standard time and three hours behind Sydney or Melbourne during eastern daylight time. South Australia and Tasmania should also be checked when the clocks change.

Install the app and pair your Zwift account

Install the official app and sign in with the same email address or social sign-in method used for Zwift. A separate Companion account is unnecessary. Open Zwift on the computer or TV, sign in, and check that the dashboard, trainer, heart-rate monitor and cadence sensor are working before attempting a phone connection. The Companion app does not replace these sensor connections; it receives the data that Zwift is already receiving.

In the desktop game, open the profile or account menu and look for Pair Device, Pair Phone or an option labelled for the Companion app. Exact wording varies between releases. One screen will generate a short numerical code and the other will accept it. If the game generates the code, open Companion, choose the pairing option and enter it promptly before it expires; if the phone generates it, reverse the order. Keep both apps open until pairing completes, and never share the code with anyone, including someone claiming to be support staff.

Once paired, allow the notification, activity and device permissions requested by the app. On Android, also check that battery optimisation is not suspending Companion, and on iPhone, confirm that notifications are enabled at the system level. Run a two-minute test ride, then compare the phone’s power and heart-rate figures with the main Zwift screen. The values should be close, although brief differences can occur as Bluetooth sensors update. If the display remains blank, reconnect the sensor to Zwift rather than repeatedly pairing the phone.

Configure alerts, metrics and display options

Open the app’s event or notification settings and enable a reminder for the SweatFest event you intend to enter. Check the lead time against the start shown on the event listing, then test it with a nearby event rather than waiting for race night. Allow critical race alerts through any Do Not Disturb setting, but mute non-essential social messages. A clear start notification is useful, yet it is still worth confirming the route and category a few minutes beforehand because the app cannot correct a mistaken event selection.

Choose the metrics that help you manage effort without distracting you. Power is usually the better basis for race tactics, while heart rate can show the physiological cost of holding that effort. SweatFest’s explanation of heart rate versus power is useful for understanding why the two numbers may diverge during a prime sprint or steep section. Keep heart rate in a range that is meaningful to you, and avoid chasing a spike that the race does not require.

Companion data may refresh a second or two after the game, particularly when the phone is locked or moving between access points. For official updates, remain familiar with the race panel in Zwift itself: category placement, prime-segment points and the final result are generated there. The phone display is valuable for watching watts, heart rate and distance, but it is not a live copy of the leaderboard. If the two screens seem seriously inconsistent, trust the game and check the sensor rather than altering your pace based on a delayed phone value.

Build a dependable Tuesday race routine

A short routine on race day prevents most problems. Start Zwift, confirm the trainer and sensors, pair or reconnect the phone, open the correct event and place the phone within easy reach but away from pedals and bottles. Use a charger if the race will approach the limit of your battery. During the race, let the app remain in the background and avoid opening other apps, which can reduce update reliability on some phones.

Australian home setups also deserve a little planning. In flats in Sydney, Melbourne, Brisbane, Adelaide or Perth, secure the bike on a trainer, use a floor mat to protect the boards and reduce noise, and check any building or body-corporate rules about shared spaces. Summer “gumboot season” can make a compact training room hot even before the rider starts, so begin in the evening if needed and use a fan without blocking ventilation. For connectivity, know whether your fixed broadband uses NBN, fibre, fixed wireless or another service, and check Telstra, Optus or Vodafone coverage at your address. A dual-SIM phone can provide a useful fallback where one local network is less dependable.

After completing the list, put the phone on vibration and keep the main game in view. If a connection drops mid-race, let Zwift continue and check the phone rather than restarting the event. Staying connected matters, but missing a category, prime or points update is more costly than losing a mirror display for a few seconds.

Troubleshoot pairing and race interruptions

If pairing fails, work through the layers rather than reinstalling immediately. Confirm that both devices are signed into the same Zwift account, that the app and game are updated, and that the code was entered before it expired. Turn off a VPN or restrictive private DNS temporarily if it blocks the connection, then reopen both apps. A stale paired phone can also prevent a replacement from pairing, so remove old devices from the relevant account settings when that option is available. For blank metrics, check sensor connections and permissions before changing the phone.

An interruption during the event can involve either the virtual bike or the real equipment behind it. If a puncture or trainer fault occurs, consult the league’s Zwift flat tyre guide and follow the event-specific procedure. A Companion notification may tell you that the race has started, but it cannot repair equipment or determine whether the event can continue safely; that decision rests with the rider and the relevant race service.

Before asking for help, note your phone model, operating-system version, Companion version, Zwift version, the time of the failed attempt and whether the pairing code appeared. Screenshots of the relevant screens can speed up a diagnosis in the SweatFest Facebook group or with league administrators. Keep a copy of the event confirmation, because race support can then distinguish an account or pairing problem from a scheduled-category issue. Once connectivity is restored, the stable routine is the same: trust the game’s results, watch live effort on the phone and verify the official standings after the finish.