Feature request: disconnect after timeout of no-use (zwift click v2)

[zerkms]

I suspect that if one does not explicitly disconnect their zwift click v2 (or disable bluetooth entirely) then bikecontrol keeps the zwift click up and running effectively forever until next use.
That obviously drains the click's battery.

My observations that back-up this suspicion: I have ridden the bike in the evening. Didn't disconnect the click v2 and did not disable bluetooth.

Then on the morning I remembered about it, and disabled the bluetooth on the tablet. And immediately click's diodes started pulsing blue light, which they do when they get disconnected/ready to pair.

Hence a request: what if it was an option that defines a timeout of no controller interaction detected, after which the controller is disconnected automatically.

[jonasbark]

Thanks for your feedback!

I'm not sure about the "inactivity timeout", but what I already planned to add was a way to turn off BikeControl, i.e. disconnect all devices and stop scanning. Given that there's a notification active when the Clicks are connected, I think it may be obvious enough that BikeControl is still connected

[zerkms]

think it may be obvious enough that BikeControl is still connected

Correct, but I try to address the case when you forget to disconnect or do something to avoid battery drain.

a way to turn off BikeControl, i.e. disconnect all devices and stop scanning

It wouldn't address the same problem: you still need to remember to disconnect every time you finish riding.

I guess, I suck at explaining, so will try rephrase it with a more detailed repro steps:

1. It's the evening, you have a nice ride on a bike (with the help of bike control)
2. You're super tired, you get off the bike
3. You open strava (on the same tablet) and see how many PR's you've achieved ("great job" you say to yourself)
4. You then get distracted by a cat demanding some attention and meanwhile the tablet screen turns off (as it's configured to turn off after couple of minutes of inactivity, and strava does not keep it awake)
5. You totally forget you need to disconnect/disable something and go to sleep
6. zwift click v2 stays connected overnight til the next ride and drains its battery

Proposed solution:

• there is a setting in bikecontrol "Disconnect a controller after X (text input) minutes of inactivity".
• "inactivity" is defined as "no clicks detected within X minutes" (could be more sophisticated logic/configuration, but at least having timer would help a lot)

If it was there and say I have set it to 60 - then after step 5, after an hour the controller is disconnected and no drain happens

[jonasbark]

Yes, I think 60 minutes is reasonable, but another idea came to my mind:

After 30 minutes of inactivity create a new "reminder" notification that the device is still connected.

Not sure if inactivity disconnection or reminder is the better approach

[zerkms]

Reminder won't work: if you forgot to disable it right after the session - it's ~0% chance you ever return to the tablet before the next riding session.

At the moment I created a tasker task that text-to-speech says "Disable Bluetooth" every 5 minutes if: screen is off & bluetooth is on. This works for me, but wouldn't for those that have their bike station organised in a dedicated part of the house (eg garage).

[jonasbark]

True! I just thought about iOS, which also transfers the notifications to e.g. your iPhone, but on Android or other devices in general it won't work