Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a direct Dreeve exporter for BLE Scale Sync.
Dreeve now exposes a bearer-authenticated athlete-weight API. This exporter sends BLE Scale Sync readings directly to a self-hosted Dreeve instance, without requiring an Android/openScale-sync intermediary.
The exporter is deliberately weight-only because Dreeve currently accepts only weight measurements.
This exporter targets the athlete-weight API introduced in
dreeveapp/dreeve#2653.
Changes
dreeveexporter with:POST /api/v1/athlete/weightsdelivery.drv_...API key.GET /api/v1/statushealth check.base_urltokenunit_systemunit_system: metric | imperialhandling:metricsends kilograms.imperialconverts kilograms to pounds before sending..envconfiguration path.config.yaml.example,.env.example, exporter docs, README, site landing page, FAQ, and exporter-count metadata.Test Plan
npm test)npm run lint)npx tsc --noEmit)Focused verification also passed:
git diff --checkpassed.Manual verification was not performed against a live Dreeve instance. HTTP contract tests cover the documented status and weight endpoints, bearer authorization, metric and Imperial payloads, retry behavior, date handling, and error handling.
Notes
unit_systemmust match the Dreeve instance Appearance setting exactly:metricfor kilograms.imperialfor pounds.DREEVE_API_KEY, and the same generateddrv_...key must be configured as the exportertoken.