latest update has been released!

Thank you and great question. There’s already an open issue for this in the repo (#31) and the fix is in dev. Next RC will have it. The Android scanner will use the bundled ML Kit model directly, with no Google Play Services calls at runtime. Same scanning engine.

Thank you so much! I appreciate it!

Yes! Settings → Backup → Nutrition Import. Built-in adapters for MyFitnessPal, Cronometer, LoseIt, and a generic CSV shape. Export your diary from MFP (it’s a CSV in their account settings), upload it, preview, commit. Skip / Merge / Replace per-date semantics, so you can re-import safely without overwriting.

Yes, TLS is left to a reverse proxy (nginx, Caddy, Traefik, Cloudflare Tunnel). The container serves plain HTTP on a port you map; whatever you put in front handles the cert.

No wger integration today. NutriTrace covers food + wellness + workout sync (from Fitbit/Garmin/Withings/Google Health/Health Connect), but doesn’t connect to wger or other dedicated exercise-routine apps. My soon to be released app in the Trace family of apps will be dedicated to lifting, and will include wger integration to name one of its exercise databases (as well as support for custom imports).

It is an android app with Health Connect Support! Android app works with or without the server! :)

For docker, It is only one service. everything else can be setup in app once you are in if you so choose. Android App can be used with or without server.

Open Food Facts (OFF) for barcodes. Free, open license, community-edited. Their API: https://world.openfoodfacts.org/api/v2/product/<barcode>.json

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.

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.

Hey, thanks for trying it out!

For things you don’t measure by weight (eggs being the classic example), the easiest path is to make a local entry once and then reuse it. A few ways to go about it.

The nutrition label on your egg carton is your friend here. It’ll show you the serving size, usually 1 large egg at around 50g, plus the full breakdown (calories, protein, fat, carbs). Tap the + on the Foods page, type those numbers in, set Serving size to 50 and Unit to “grams”. From then on, logging eggs is just typing “Quantity: 2” in the diary and the math takes care of itself.

For irregularly-sized stuff like apples or bananas, a kitchen scale is honestly the easiest path. A medium apple can swing anywhere from 130g to 220g, so weighing it once and typing the gram count gets you accurate numbers without needing a separate per-piece entry for every size.

One thing worth knowing about OFF and USDA results: the “100g” you see is just the per-100g nutrition density. That’s how those databases store everything, it’s a baseline reference, not a forced serving size. So you can either weigh your food and type the grams directly, or edit the entry to change the portion and unit (say to “1 piece” or “1 cup”) and the totals rescale.

Once you’ve dialed in a handful of items you eat regularly, day-to-day logging gets a lot faster. The new Favorites and Most Used sort in rc.19 will float your top items to the top of the Foods page automatically.

Just pushed rc.15 with the fix. Energy unit setting is now respected across the app, and the wizard auto-picks kJ for AU and NZ on first run.

Glad you’re enjoying it.

On the kJ, you’re right. The setting was being respected for goals and storage but a bunch of display spots still had kcal hardcoded. Just pushed the fix to dev and it’ll be in the next public release. Also added auto-detect so if your device locale is en-AU or en-NZ the wizard pre-selects kJ on first run, no toggle needed (but present now in settings).

On AI for coding, yes I utilize it. Claude Code to be specific. It makes me more efficient and helps lift the work I ship.

Will let you know when i push out the update, should be later today.

Glad the workaround clicked. Custom-nutrient “water” plus your own recipes is the cleanest path for comprehensive accounting without waiting on a built-in feature.

The “two lists feels more complicated than one” observation is fair and worth sitting with. Ill add this as a possible future feature

Thanks for the thoughtful feedback.

Thank you! Enjoy the app!

Currently no, there’s no per-food water field in NutriTrace, and food water doesn’t count toward your daily water goal. The water tab tracks drinking water only.

What’s the actual use case for you, comprehensive nutrition accounting, or trying to reduce the explicit drinking water target based on what you ate? They’re different problems and the answer would shape what (if anything) makes sense to add in the future.

Great glad that fixed it!

Thanks for catching this. The Cronometer adapter was treating the parsed gram count as a serving multiplier, so a 750g entry got its calories multiplied by 750. The “NaNg” had the same root cause: the portion was stored as the raw string “750.00 g”, which JS coerces to NaN when the diary tries to multiply it for display.

The layout overlap on the duplicate-day dialog is should now be fixed too (added a divider so the buttons have proper visual separation from the radio options).

Both are hopefully now fixed and pushed in rc.14. Grab the latest package, delete the affected day from your diary, and re-import. Items should hopefully now come in with the right values.

Thanks again for the detailed report.

Thanks for implementing it that fast! Unfortunately I wasn’t able to test it.

I found the new section in the readme. So I followed it. I created an admin account (which confused me a bit - my user already had admin permissions. So why is it necessary to create another admin user?). Then I wanted to logout and login with the admin again. But I wasn’t able to figure out how to log out. So I just deleted the cookies and local storage.

After that I was greeted by the login page. So I logged in as admin, entered the User Management - and found an interface to manage users. Ok, sounds logic to find a user management tool in the “user management” menu entry. But the readme said, that there should be oidc settings. Maybe they got lost in a merge conflict or something like that. I was testing on rc12.

Anyways I would prefer an env variable to configure oidc. I like to separate the technical configuration (like credentials, etc) from the user space configuration.

This comment may sound super negative, but I’m actually very grateful you addressed this feature. Thanks!

Thanks for the detailed walkthrough. A few of the rough edges you ran into are fixed in the latest release:

The admin-account confusion makes sense in hindsight. If you were already running NutriTrace single-user, you genuinely didn’t need an admin account, that step exists because OIDC requires user management to be on. The README now spells that out as a prerequisite up front so it doesn’t feel like surprise paperwork.

Logout has a real home now. Profile lives at the very top of Settings as a card showing your name and photo, and Log Out is right there inside it. No more digging through the cookie jar.

The “where are the OIDC settings” question was on me. They were buried inside User Management. They’re now their own top-level section called Authentication, sitting right under User Management, with presets for Authentik, Keycloak, Authelia, Pocket ID, Auth0, Google, and a generic OIDC option for anything else.

And on your env-var preference, that’s in too. You can configure providers entirely from .env or docker-compose.yml. Single-provider shorthand:

OIDC_ISSUER=https://auth.example.com/ OIDC_CLIENT_ID=nutritrace OIDC_CLIENT_SECRET=… OIDC_DISPLAY_NAME=Authentik OIDC_REDIRECT_URIS=https://nutritrace.example.com/api/auth/oidc/callback/1

Multi-provider works with OIDC_PROVIDER_2_, OIDC_PROVIDER_3_, etc. Anything you define this way shows up in the Settings UI with a lock badge and is read-only there, so it’s clear where the source of truth lives. Full doc in .env.example and the README.

Pull the latest and give it another shot when you have a minute. Please confirm the env-var path actually works for your IdP when you have a chance.

Thanks again.

I gave this a shot, but when I press the “preview” button I just get a little popup that says “Invalid CSRF token”.

Hmm… i think i see the issue. The preview / commit upload was missing the CSRF token, so the server was rejecting it before it even read the file. Just pushed a fix. Once you pull it down, hard-refresh the page (Ctrl+Shift+R / Cmd+Shift+R) to grab the new bundle and try again.