Anyone building a local-first companion for Google Fitbit Air straps?

There's no widely known or official "Google Fitbit Air straps" product as of now—you might be referring to Fitbit's existing wearables or a hypothetical/emerging product. However, if you're asking about local-first companion apps for general Fitbit devices (or similar wearables), here's the landscape and potential approaches:

Key Considerations for Local-First Fitbit Companions:

1. ·

   Fitbit's Ecosystem Constraints:

   • ·Fitbit devices traditionally sync data to the cloud via Fitbit's servers. Local access is limited unless you use unofficial APIs or reverse-engineer the Bluetooth protocol (which may violate terms of service).
   • ·The official Fitbit Web API requires cloud syncing; local-only solutions are not natively supported.
2. ·

   Local-First Alternatives:

   • ·Gadgetbridge: An open-source project (github.com/Freeyourgadget/Gadgetbridge) that supports local sync for some wearables (Pebble, Amazfit, etc.), but Fitbit support is experimental/nonexistent due to proprietary protocols.
   • ·BLE Reverse Engineering: Some developers have reverse-engineered Fitbit's Bluetooth for local data extraction, but this is fragile and legally risky.
   • ·Export & Local Processing: You could pull data from Fitbit's cloud API periodically and store/process it locally (e.g., with a script using Python/R).
3. ·

   Why Local-First Matters:

   • ·Privacy: Avoid sharing health data with third parties.
   • ·Offline Use: Useful for environments with unreliable internet.
   • ·Longevity: Cloud-dependent services can shut down (e.g., Google's history of killing products).

What You Can Do Today:

• ·For Existing Users:
  • ·Use tools like SyncSolver (third-party Fitbit data exporter) to dump cloud data locally.
  • ·Explore Home Assistant integrations for Fitbit to bridge data to a local server.
• ·For Developers:
  • ·Focus on BLE sniffing/local protocols for newer open wearables (e.g., PineTime, Coros) instead of Fitbit if local-first is a priority.
  • ·Advocate for open standards like FHIR or Open mHealth to pressure Fitbit/Google toward local-access options.

Bottom Line:

A true local-first companion for Fitbit doesn’t exist officially, but workarounds (or alternative devices) may meet your needs. The lack of support reflects broader industry resistance to decentralizing health data—so realistic options are limited unless you’re willing to tinker or switch platforms.

If you clarify the specific use case, I can refine recommendations (e.g., sleep tracking, step counts, or heart rate analysis).