from TraceApps@lemmy.world to selfhosted@lemmy.world on 10 May 14:18
https://lemmy.world/post/46664426
NutriTrace is a self-hosted nutrition tracker (Docker on the server, PWA in the browser, native Android app). AGPL-3.0, no telemetry, no accounts on external services, your data stays on your hardware.
This release is the biggest one since the Android app shipped: the Wellness layer moves off the legacy Fitbit Web API (which Google is sunsetting in September 2026) onto the new Google Health API, the numeric Stress Score becomes Resilience (Optimal / Balanced / Low), Fitbit’s new Sleep Quality sub-metrics show up under Sleep, and the Diary gets a Cronometer-style Split Recipe action.
What’s new
Google Health migration — Wellness data now flows through Google Health instead of the deprecated Fitbit Web API. Existing Fitbit data still comes from the same device; only the connection method changes. Fitbit users will see a “Re-link required” notice in Settings → Wellness with the migration steps. Old tokens keep working through a transition window.
Resilience replaces the numeric Stress Score — Fitbit retired the 0-to-100 score and renamed it Resilience with three buckets (Optimal / Balanced / Low). The Wellness page reflects the change with a category badge, a one-line interpretation, and a breakdown of the three pillars Fitbit uses (Physical Calmness, Activity Balance, Sleep Patterns). Historical Stress values stay in the database for reference.
Sleep Quality sub-metrics — Time to Sound Sleep, Sound Sleep, Restlessness, and Interruptions appear under the Sleep tab when data is available. Restlessness under-counts vs Fitbit because Google Health doesn’t expose the raw motion data Fitbit’s app uses internally; the others track within a few minutes on most nights.
Split Recipe on the Diary — Long-press a saved recipe in your diary and tap Split Recipe to break it into its component ingredients in place. The recipe stays as the parent (so totals are preserved); a chevron expands to reveal each ingredient scaled by however much of the recipe was logged. Each child is editable (adjust portion, remove one) without touching the saved recipe in your library.
Info button on saved meals and recipes in the Foods picker — tap the i on any meal or recipe row to see the full ingredient list with portions and per-item energy before logging it. Mirrors the existing yesterday-meals expand pattern
Issues, feature requests, and integration test reports are all welcome on GitHub.
#selfhosted
threaded - newest
So this mentions Google fit. Does it also serve as an exercise tracker with counting steps and tracking distance?
For that kind of stuff I just use Gadgetbridge which is amazing at figuring ways to pair with your Bluetooth tracker/smart watch/band/headset/about anything they can figure. Their devices supported list is… Really long these days.
Not directly. NutriTrace doesn’t record steps or GPS itself; it reads them from whatever’s already tracking you (Health Connect on Android, or Fitbit/Garmin/Withings via their cloud APIs). So if Google Fit, Samsung Health, or your watch is counting your steps and logging workouts, NutriTrace will pull those numbers in and chart them alongside your nutrition.
Does it support Health Connect so I could import from other services or just Google Health? I’ve used Samsung Health for long time and want to move to something open.
Yes, Health Connect is supported on the Android app. As long as Samsung Health is set to write to Health Connect (Samsung Health → Settings → Connections → Health Connect), NutriTrace can read steps, sleep, heart rate, weight, and exercise from it.
Honestly though, this path hasn’t had many testers yet, so if you give it a shot I’d really appreciate a heads-up on what works and what doesn’t. Feedback (positive or bug reports) is welcome on GitHub.
It sounds like you’ve put a lot of effort into updating NutriTrace to a significant degree, incorporating Google Health API and making various user experience improvements.
First, let’s talk about the Google Health API migration. This change is likely a strategic move to future-proof your app, considering Google’s sunset of the legacy Fitbit Web API in September 2026. The transition period will help users adjust, and existing tokens will still work during this time.
Introducing Resilience as a replacement for the numeric Stress Score is an interesting decision. This change might provide a more nuanced understanding of users’ overall well-being, with the categorical breakdown of Optimal, Balanced, and Low. However, it’s worth noting that users might miss the old 0-to-100 score.
The addition of Sleep Quality sub-metrics is also a welcome feature. Although there might be some discrepancies with Restlessness tracking due to the underlying data differences between Fitbit and Google Health, the other metrics should provide a more detailed understanding of users’ sleep patterns.
The Diary feature with the Split Recipe action is an excellent addition for users who want to log meals and recipes more efficiently. Breaking down a recipe into its component ingredients will make it easier for users to log and adjust their meals.
Lastly, the info button on saved meals and recipes will provide users with more context and information before logging their meals. This feature mirrors the existing yesterday-meals expand pattern and will likely be helpful for users.
Overall, these updates should provide
This is an AI slop Spam Bot. Every single post it has made in the last two hours stops in the middle of a sentence, with each comment being at best sycophancy, and at worst a total non-sequitur. Everyone should report this spam from an undeclared bot account.