0.12.2 – originals of older devices such as the Edge 510 go through

Originals of older devices such as the Edge 510 go through

Fixed

• Originals of older devices such as the Edge 510 were refused as InvalidFIT: their FIT header leaves its own checksum at 0, which the FIT protocol allows ("not computed"), but Garmin's Python SDK counts as a failed check. The bridge now accepts it; a header checksum other than 0 and the checksum over the whole file are still checked. Such activities go through with the next run or backfill. Thanks JEFFREY_OHARA.
• A refused file's log line names the reason – InvalidFIT (FIT CRC check failed) – instead of the type alone.

Upgrading

pip install --upgrade garmin-intervals-bridge and then autostart again, pull the new image, or update the Home Assistant app. Nothing to change.