eufy-garmin-sync (deprecated)
This project has moved to eufy-sync. The new package adds Strava support alongside Garmin Connect.
Migrating
pipx uninstall eufy-garmin-sync
pipx install eufy-sync
Your config (~/.garmin-sync/) and sync history carry over automatically - no data loss.
New features in eufy-sync
- Sync to Strava in addition to Garmin Connect
- Configure one or both targets
eufy-sync --setup-stravato add Strava to an existing setup
Metadata
Release files for eufy-garmin-sync 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| eufy_garmin_sync-2.0.0.tar.gz | 2.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eufy_garmin_sync-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.8 kB
Release files / eufy_garmin_sync-2.0.0.tar.gz
| Download URL | eufy_garmin_sync-2.0.0.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
22da47de7dd393f699737c33d69320c78de5853c71584e9516586641d5a48e45
|
|
BLAKE2b-256 checksum How to use checksums |
21b51ec36e723759a0efa0914f6423a562a34a1920b8c20c35f104245ade5013
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 2, 2026.
Transparency logRelease files / eufy_garmin_sync-2.0.0-py3-none-any.whl
| Download URL | eufy_garmin_sync-2.0.0-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87650a499970a587c8665ab3ec50eadcd84d24acc01de96a087fb70b74933652
|
|
BLAKE2b-256 checksum How to use checksums |
6b2cc05e1c36f33a4117e7f56905353dcaaa72a66641af3754490566ef84418e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 2, 2026.
Transparency log