Frosty

This is about 500-800m from the start. I’d be concerned about potholes on the opposite side of the road, in places along the route. Cars approaching from the front will need to swerve into the middle of the road to avoid some of these larger ones. And then there is the speed of some road users on some of the roads.

Good weather conditions for riding, and a few not so good road conditions (the FastOne is using some of these roads). We also had some involuntary experimentation of carbon monoxide inhalation (non-medical grade) on a section of the route today… 🚗💨

https://wahoofitness.co.za/product/zwift-click-zwift-cog-upgrade-kit-pre-order/?gad_source=1&gbraid=0AAAAAo3jt7IgvXELTxs1WF718E1VEVQ2Y&gclid=CjwKCAiAnKi8BhB0EiwA58DA4U5emTkqheOJlM_87NFc40OjI0E8M5B8fqUlr_WDTSaHEKpv15nDrxoCkV8QAvD_BwE

Some of the roads are excellent, and some are terrible. With the recent rains in GP, it’s hard to say what it will be like now and going forward.

I’m blown away by your excellent sense of humour

Today was a chilled ride, but rather windy; both a head- and tail-wind at the same time, while riding up a 10% climb (Ven-Top).

From there, it becomes a process of elimination, where you make one change at a time and see how it responds. Write it down, so the next time you don’t have to guess. I found that a restart fixes most things, follow by disconnecting all devices that could possibly connect (head unit, watch, other computers, etc). Last bit is that I will always make sure the connection is made the day before I want to workout. App updates, device issues and more can be resolved before the intended session starts. Even logging in and letting it idle helps.

Which model do you have? There are a few listed on the site. This one shows that it works on Zwift, and therefore should work on other similar apps. Ant+ and BLE troubleshooting 101: 1. Bluetooth (BLE) connections work on a 1:1 relationship, meaning it can only pair with one device at a time. If you use BLE, switch off all other devices that could use the same connection. 2. Ant+ can read from multiple devices at the same time, and is widely regarded as a better protocol to use, it also has its own problems. 3. When pairing equipment, in TP Virtual, it can show all devices in range, both Ant+ and BLE, so you need to try both connection protocols. see images in Zwift, and TP Virtual below, where the Ant+ and BLE sensors are picked up where Ant+ is not picking up. I use a Kickr Core and hardly ever have problems with TP Virtual, but more so with Zwift, when the Ant+ dongle isn’t picked up by my 2012 Macbook. Do you have the Bluetooth and Ant+ icons (top left of the pair device screen in TPV) showing active?

SMART was mentioned a few times, but not SMARTer: The E=evaluate, and final R=reward Evaluate what you did, both success and failure, so you know what to change for next time. Reward can be yourself, as well as others (if they were involved); think when a TdF winner presents the entire team with a thank you gift).

Two of us (Vaalies) that I am aware of, failed to succumb to the “lie in”, due some less than desirable conditions. The original plan (for me) was +/-79Km, 3.75 hours, about 150 load (hrTSS), and most importantly a breakfast with dirty dish water. It turned out to be less than planned by 12km, 1 hour, 45 hrTSS and no breakfast, but a semi-decent coffee. Tomorrow’s a planned rest day, and it doesn’t matter that I’m an hour off my target from today and therefore the week. I don’t have to catch up, as it won’t make a difference if I do or not. But I might go for a short ride, tomorrow morning just because I can and it’s nice to have a chilled day.

Strava works in two numbers after the decimal point… so 364.99 😊😁😂

Local is lekka… the planned route to breakfast and back was replaced with a local ride around town, due to the inclement weather.

Even a race-minded person will have days like this. Being flexible and making adjustments to the plan knowing that one missed session doesn't kill the plan. It's the multiple missed sessions.