Settings and activity
81 results found
-
6 votes
Mei Rits
supported this idea
·
-
9 votesMei Rits
supported this idea
·
-
5 votesMei Rits
supported this idea
·
-
7 votesMei Rits
supported this idea
·
-
6 votesMei Rits
supported this idea
·
-
4 votesMei Rits
supported this idea
·
-
6 votesMei Rits
supported this idea
·
-
3 votesMei Rits
supported this idea
·
-
5 votesMei Rits
supported this idea
·
-
6 votes
An error occurred while saving the comment An error occurred while saving the comment Mei Rits
commented
Update for 0.4.9:
Nice extended pairing screen but DirCon still not working.Found a more or less reliable method disconnecting and reconnecting the USB network dongle shortly after starting TPV but had to relaunch TPV most of the time at least once afterwards lately.
There are tips over on Discord (I'v just discovered via tpvirtualhub yesterday) for a workaround using `netsh` ? or something the like prior to launching TPV.Something on Linux I'd use:
```bash
nmcli d disconnect enp0s31f6
nmcli d connect enp0s31f6
```
for,
but I didn't know how to do on Windows.I could imagine that there might be a workaround on Mac-OS too.
I'll try the workaround over the next days. Still, hoping for a thorough fix, though.
As a side note: It seems to me Wahoo is using a not very common protocol for DirCon.
Quote form wahoofitness support pages:
Direct Connect and Bluetooth
Direct Connect requires Bluetooth® to function and uses the Bluetooth® protocol over TCP/IP. Your PC/MAC must have Bluetooth® drivers and must be enabled in the OS and App. Most computers in the past 7 years should have Bluetooth® by default, but a Bluetooth® adapter may be required if not.An error occurred while saving the comment Mei Rits
commented
Update 2025-01-09:
Unfortunately, my workaround described below no longer works.
Even worse, I had to restart my computer twice yesterday before the Kickr Bike was recognised even via BLE.
Tried everything, switching ethernet ports, removing the USB-Dongle network device, nothing.
The reinstall TPV trick including restart the computer didn't work either. Tried it, just in case.
Haven't had any updates for my support tickets for a while now.An error occurred while saving the comment Mei Rits
commented
Update:
George's comment below about "multiple network interfaces" sparked an idea.
What if I tested a different network interface? I do not know how to disalbe the built in one on Windows (would know how to do this on Linux though).
Hoewever, I just added a USB network dongle, attaching the network cable to it after detaching it from the built in interface.
Surprise: Direct Access is working on the dongle interface. (Can't be a general problem with the built in interace since DA is working fine when using the built in interace on Zw*ft).
So if anyone has some sort of USB-Network dongle: would be interesting if it was working for someone else too. Even though, it's still a workaround only.An error occurred while saving the comment Mei Rits
commented
Update: Customer Support suggested that I looked out for a installed Garmin Express on the computer as this had been causing trouble for other users.
Even though, Garmin Express was installed (long ago and not causing trouble with IV or in the early days of TPV), I removed this from the computer, rebooted it several times, reinstalled TPV but:direct access is still not working again.
(Tests it with two other cycling platforms, capable of direct access on the same computer are still sucessful. So it must be some TPV and not a setup issue.)
Mei Rits
supported this idea
·
An error occurred while saving the comment Mei Rits
commented
Reinstalling helped only once, now, reinstalling TPV and rebooting the computer several times doesn't work any longer.
Screenshots and Logfiles have been sent to Customer Support.--For me, reinstalling TPV on Win 11 seems to have solved the issue.
I was in the process of assembling all the relevant data, logs, screenshots and just as a last ressort, reinstalled the application, and now TPV suddenly picks up the ethernet port, cable, network switch connected Kickr bike in addition to the BLE listed Bike again. And lets me select it.
Will report (including logs), if the problem occures again. --
Hope, the OPs issue will be resolvable as well.An error occurred while saving the comment Mei Rits
commented
I cam here to report a similar issue (or look for a place for reporting this issue.)
My Trainer (Kickr Bike v2) is connected via a lan cable to the router.
My computer fitted with win 11 is connected via lan cable to the same router.
Until recently TPV picked up the trainer via direct access.
Zwift and MyW**sh is still discovering it via direct access running on the exaclty same computer.
Nowadays my trainer is only detected via Bluethooth.
I recently switched the computer and the old one had WiFI additionally to the ethernet lan cable connection. I'm not sure if direct access connection dropped after the recent update or after changing computers.
Is direct access only supported via WIFI? I can't really imagine that. -
21 votes
We are researching this currently.
Mei Rits
supported this idea
·
-
11 votes
An error occurred while saving the comment Mei Rits
commented
Last year support for the KickrBike buttons was added which I'm very grateful for.
https://thezommunique.com/2024/05/13/kickr-bike-button-mapping-on-indievelo/
However, I'm a notorious Campagnolo rider (Never had any other brand on my bikes. So it was naturally to choose this layout on my KickrBike.)
This results in a clash when switching gears with LF and RF, leading to unwanted route changes, though.
The only button shortcut I'm able to remember by heart is changing the camera view angle.
I'd love to have some config file (yaml, json, ini, even xml) where I can overwrite the button mapping. I wouldn't need some fancy UI for this.
This idea might be related to this idea https://peaksware.uservoice.com/forums/964442-trainingpeaks-virtual-customer-feedback/suggestions/49107008-custom-controller-mapping in case a generic mapping solution is implementable.Mei Rits
supported this idea
·
-
6 votesMei Rits
supported this idea
·
-
8 votesMei Rits
supported this idea
·
-
6 votesMei Rits
supported this idea
·
-
22 votesMei Rits
supported this idea
·
-
24 votesMei Rits
supported this idea
·
-
7 votesMei Rits
supported this idea
·
-
31 votesMei Rits
supported this idea
·
-
14 votesMei Rits
supported this idea
·
Update for 0.4.10:
It might have fixed the issue.
KickrBike was immediately recognised via DirCon and wired ethernet after update 0.4.10 was installed and it was still recognised after one power cycle of the computer.
All on the built in network interface and without the workaround dis- and reenabeling the interface.
Haven't had a look at the log files yet but will further watch this issue.