olliv / bfree Goto Github PK

Seems to be jumping a lot.

Same as previously somewhere else, the scaling is wrong. Perhaps not scaled tockm/h properly.

The back button on the Title element is horribly unintuitive as it is now.

Create a training session object that has useRef to the selected measurements.

Example:

{
  speedRef: [ cscRef, csRed ],
  powerRef: [ cspRed ]
}

Save config on regular interval by checking if there are changes using setTimeout() and a global flag. Show a notification when the config is stored to local storage.

It's already a JSON blob so we could allow exporting and importing it.

• Calculate altitude data in Free Ride Slope mode
• The trainer is making weird noises, it sounds like it's slipping???

This could be nice addition as it doesn't require internet connection anyway.

One possible solution is here next-pwa.

There should be an useEffect() or something somewhere that would update the user params when something is changed and the trainer is already connected.

Currently there is an empty space and we shift stuff when the controller is added. Instead an empty card should be replaced with the new one.

It would be good to always see whether the sensors are connected and working. This could potentially include battery level warnings.

Currently we only get accumulated wheel revolutions from the speed sensor which can be used to calculate the distance.
The ANT+ FE-C over BLE profile supports calculation of accumulated distance directly.

Basic stats are missing from the recording mode.

Text and lines are missing

(async () => {
  try {
    const isBluetoothAvailable = await navigator.bluetooth.getAvailability();
    log(`> Bluetooth is ${isBluetoothAvailable ? 'available' : 'unavailable'}`);
  } catch(error) {
    log('Argh! ' + error);
  }
})();

if ('onavailabilitychanged' in navigator.bluetooth) {
  navigator.bluetooth.addEventListener('availabilitychanged', function(event) {
    log(`> Bluetooth is ${event.value ? 'available' : 'unavailable'}`);
  });
}

https://googlechrome.github.io/samples/web-bluetooth/availability-async-await.html

Initially it would be probably enough to support the three resistance modes or even just power.
The workouts could even just scripted with JS. This would/should allow an easy access to different lap triggering modes (time, distance, etc.).

but allow in dev mode?

There is no valid reason to start a workout script if the smartTrainer object is not initialized.

It's currently half-done as history.tsx will load all the loggers but isn't able to show any.
There might be also a memory consumption concern. Maybe it shouldn't load all the data permanently but create a new logger when one is actually needed again?

Screen saver will unmount the resistance component which makes the matter worse.

Show target power 🔺🔻🆗 sent by the trainer.

The trainer might be left in undefined state if a calibration run fails.

Read gpx or some other format and sync video speed to the cycling speed.

Missing measurements should either be replaced with the previous measurement or with a zero, or intelligently with and average of the previous and next measurement if existing.

For the first time the app crashed after 30 minutes and lost all data.

Show a question mark and a tool top or model explaining why each thing is asked. E.g. bike type is asked because it's used for calculating the correct wind resistance coefficient.

At least avg speed and probably others too may go NaN if a value is missing or the ride is paused, not sure which one or both.

Making a lap split doesn't fix the issue.

The graph shows the correct speed buy it looks like the speed measurement card is showing m/s while the unit shown is km/h.

Moving the title to the left side of the page and moving the content up in the record page would give more space for the measurements. It would be nice to animate this move if possible.

Currently the log is incomplete after a crash. It should be fairly easy to recover an incomplete log in most of the cases.
We could either show an error and ask the user to press a button or attempt an automatic fix.

The setStates are used incorrectly and that breaks unpairing action after leaving the page and coming back.

This happens when you unpair an already failed connection.

For example a trainer may have a FE-C and a separate power meter in the same device, if one is disconnected the browser will disconnect all active services.

This sometimes results the following error:

Uncaught (in promise) DOMException: GATT Service no longer exists.

Steps to reproduce

1. Connect to the FE-C service
2. Connect to the cycling power service
3. Disconnect the cycling power service

This should result the FEC-C service being dropped as well.

• Persist sessions after riding
• Allow downloading previously persisted rides
• Persist ongoing ride periodically to avoid dataloss

Is there any better way to make it absolutely sure that we don't lose the BLE connections if something happens? Pretty much everything else can be just pushed to the local storage either immediately or periodically. Is it possible to move the data logging to a worker?

Provide the following predefined values as well as manual input.

There is a button and there is already a way to do it from the results page but neither is currently accessible.

Ignore zeroes, avg whatever it's that makes bad cadence sensors less useless. Should be a toggle switch in the sensors setup.

We are probably missing the right bike parameters to calculate speed and distance accurately. The trainer is currently sending a User configuration required flag all the time.

Needs implementation.

Should be a pretty simple script to write.

Add support for Bluetooth blood oximeters. This could be potentially shown along with hr data and the oximeter can also act as a source for HR.

It would be really nice to able to configure the date format used in lists and elsewhere.

The max and avg values for speed are still randomly showing NaN and Infinity for the rest of the session since the beginning.

The graph sometimes fails in the beginning and requires a lap split to start drawing something.

• Avg is showing too many decimals
• power avg is showing unrealistically low values