A small nightly job that syncs the weigh-ins of a Renpho smart scale to Garmin Connect, body composition included. No manual entry required.
Garmin Connect is the platform I use the most to track training and health, but my scale is a Renpho Wi-Fi scale, and Renpho does not integrate with Garmin. Neither of them offers a public API for personal use, so I built a small script that reads the weigh-ins from the Renpho cloud and uploads them to Garmin Connect every night.
Main features:
- At most one weigh-in per day: the first (usually fasted) or the last one of the day
- A day is uploaded only if Garmin has no weigh-in for that date yet: no duplicates and no local state file, Garmin itself is the source of truth
- The metrics to share with Garmin are chosen in a YAML file
- Backfill of past weigh-ins from any date with
--date - Supports Garmin MFA: the first run asks for the code, then the saved tokens are reused and refreshed
- Runs every night at 2:00 via cron and checks the last 3 days, so weigh-ins that reach the Renpho cloud late are not lost
Weight is always sent. Every other metric can be switched on or off in config/metrics.yaml.
| Garmin | Renpho | Unit |
|---|---|---|
| weight | weight | kg |
| percent_fat | bodyfat | % |
| percent_hydration | water | % |
| bone_mass | bone | kg |
| basal_met | bmr | kcal |
| metabolic_age | bodyage | years |
| visceral_fat_rating | visfat | level |
| bmi | bmi | |
| muscle_mass | muscle | kg, computed as weight × skeletal muscle % |
Metrics that Renpho reports as 0 (e.g. when weighing with socks on, so no impedance is measured) are not sent.
flowchart LR
S[Renpho scale] -- Wi-Fi --> R[Renpho cloud]
R -- renpho-api --> J[sync.py<br/>Docker + cron]
G[Garmin Connect] -- days already weighed --> J
J -- FIT upload<br/>garminconnect --> G
The system is composed of four main components:
- Renpho cloud: the scale uploads every weigh-in over Wi-Fi. The script reads them with the unofficial
renpho-apilibrary. sync.py: keeps one weigh-in per day, asks Garmin which days already have a weigh-in, and prepares the metrics enabled in the config.- Garmin Connect: each weigh-in is uploaded as a FIT "weight scale" file with the unofficial
garminconnectlibrary, so it shows up exactly like a weigh-in from a Garmin Index scale. - Docker + cron: the job runs in a container started by the host crontab, does its run and exits.
renpho2garmin/
├── app/
│ ├── sync.py # Renpho -> Garmin sync (--date for backfill)
│ ├── requirements.txt # Python dependencies
│ └── Dockerfile
├── config/
│ └── metrics.yaml # weigh-in to pick and metrics to send
├── secrets/ # Garmin tokens (not committed)
├── docker-compose.yml
├── .env.example # Renpho and Garmin credentials template
├── LICENSE
└── README.md
To set up this system you need:
- A Renpho Wi-Fi scale, linked to a Renpho Health account
- A Garmin Connect account
- Docker with the Compose plugin, on an always-on machine (e.g. a Raspberry Pi)
- Clone the repository and create the
.envfile with your credentials:git clone https://github.com/GppCalcagno/renpho2garmin.git cd renpho2garmin cp .env.example .env - Choose the weigh-in to keep and the metrics to send in
config/metrics.yaml. - Build the image:
docker compose build
- Run the first sync from a terminal to upload your past weigh-ins. It logs in to Garmin, asks for the MFA code if enabled and saves the tokens in
secrets/:docker compose run --rm sync python sync.py --date 2026-01-01
- Schedule the nightly run with
crontab -e:0 2 * * * cd /path/to/renpho2garmin && docker compose run --rm sync >> sync.log 2>&1 - ⚖️ Step on the scale and forget about it!
docker compose run --rm sync # last 3 days up to yesterday
docker compose run --rm sync python sync.py --date 2026-01-01 # from a date up to yesterday- Both libraries are unofficial and rely on internal APIs, so an update from Renpho or Garmin can break them.
- When the Garmin tokens expire, the script logs in again with your credentials. If MFA is enabled it needs the code, so the cron run fails: run the sync once from a terminal.
- During a full login you may see messages like
mobile+cffi returned 429: ... IP rate limited by Garmin. They can be ignored if the sync goes on:garminconnecttries several login strategies in a row, and only the last one needs to succeed. If every strategy fails, wait a while before retrying, because repeated logins make the rate limit last longer. - Days are computed in the Europe/Rome timezone: change
LOCAL_TZinsync.pyandTZindocker-compose.ymlif you live elsewhere.
This is a personal project, but suggestions and ideas are welcome! Feel free to open an issue or a pull request if you spot something that could be improved.
Released under the MIT License.