Problem with Robo Pacers:
Kickr v5 and Kickr Climb not working. Climb does stick to 0%.
While doing free riding Sessions, Climb works as expected.
I have the same Kickr v5 and Climb. I rode with a Robo Pacer tonight and the Climb worked as expected. v1.56 on MacOS. Kickr is connected with DIRCONN and I use Zwift Play controllers.
BUG
Weekly goal is not working with this version.
I have set an hour (yep just one hour 
) weekly goal for ride.
When I did my first ride of week the popup âyou have reached your weekly goalâ popped immediately.
Same here, but windows. Last two rides with that error. Free rides without problems.
Since the update I have had problems with losing bluetooth connection, although it then reconnects within 30 seconds. This happened in the pen first at the weekend and then half way through an event and continued. I got the threat of being thrown out the event and then it reconnected. Zwiftilizer doesnât seem to see them as drop outs. I then did free ride and it was fine. Is this a bug?
Update: now NO ATV restart required to pair with H3, Zwift seems to âhold onâ to Bluetooth connection better.
Thanks guys!
Gary D
1 Like
Thank you for looping back to report!
Bad newsâŚ
Group ride re-routing is back again; folks getting split if late joining.
Happening on the AHDR Bagel rolls this morning on Watopia Waistband we had folks getting redirected through Titans (which of course isnât even part of the route)
Follow up; one ride in particular seems to now be locked into Sand and Sequoias⌠if that helps figure anything out. Windows/PC user as well.
funny-ish:
Interesting as well that it doesnât show Group Ride, or âIn Watopiaâ, as it does on mine and others that were on the ride.
1 Like
I had the same issue on Achterbahn in the Rhino Migration thatâs on right now, and saw several others misrouted as well. Also was left in the pen on the first late join attempt, with the group several minutes up the road.
I had a similar issue with hrm. Hrm to laptop and wahoo headwind. Social rides and warm ups fine. Enter pen. In a short space of time. Hrm drops out and unable to re pair. Need to exit Zwift completely and all is good again.
Only happened during two RGV route race and this update
Fan still works with hrm bit Zwift drops out
Since game update 1.56 (& 1.57) on Apple TV, riding with pace partners thru Stoneway Sprint (Southern Coast expansion) causes frame-rate to drop below 1 fps. Iâm connecting all sensors (trainer, HRM, Zwift Play controllers) thru Zwift Companion, and power, cadence, and heart-rate show as dashed-values or 0 on the Apple TV, but my avatar still moves forward on the Zwift Companion screen. After a few seconds of >1fps and rider-less bikes, I get dropped from the Pace Partner group. Iâve had this happen 3 times since updating to 1.56, and it persists with 1.57. Usually, after about a minute, the issue self-resolves and Iâm able to teleport back to the group, but having lost the pace-partner bonus. I started to dual-record (ATV all BLE, Garmin 1030 all ANT+) after this started so I know my sensors arenât dropping out.
impossible, Iâm constantly told that Apple TV âjust worksâ and is far superior to any other device.
3 Likes
Which model of ATV is this?
Do you always force-quit Zwift after each time you ride? Because thatâs what you need to do.
I have Apple TV (4K 1st gen) and Iâve recently ridden with large numbers of other riders and Iâve never seen this sort of behaviour.
If you do already force-quit, then I would.reboot your ATV and see if you can reproduce this.
As a longtime PC user, I have been told that about Apple products more or less since there have been Apple products. I have never quite seen the light.
1 Like
Also 4k, not sure of generation but model is A2737 (64GB).
I donât generally quit Zwift, except to check for updates. To be clear: this has ONLY happened in Pace Partner rides (D. Maria, I think) and ONLY going thru the Stoneway Sprint toward the Alpe. Iâve not experienced it in any Tour de Zwift events, and I didnât experience it with B. Genie going the other way thru that sprint area.
The first time I waited it out. The 2nd time I rebooted and rejoined the ride. 3rd time I waited again.
This really is contrary to recommendations from Zwift themselves and also from other ATV users.
Always force-quit Zwift after each session. Itâs not designed to just sit in the background being put to sleep with the ATV and woken up again over and over. Zwift unlikely test this either.
Thatâs fine, but the issue still remains after a reboot, so Iâm disinclined to believe that this one very specific issue is related to force-quitting. Again: this began with 1.56, and the app necessarily restarted after the update to 1.57.
I would speak to Zwift support about it. If you do that relatively soon (e.gâŚnot a week later) after hitting the problem, then the server logs that Zwift staff can access might tell them whatâs going on there.