Feedback board

I did a strength workout 2 hours ago (6am local pt) and now within the app it says I did it yesterday at 6pm. Please fix

Syncing stopped working about a month ago. Neither Strava nor Garmin are updating my exercises

We understand that some users in different areas are having trouble syncing their Freestyle Libre data with Enhance-d. We are investigating this and will keep you in the loop as we gather more information. We are extremely sorry for any inconvenience this is causing, and we are working hard to resolve the issue.

When i try to connect the Hevy app the toggle switch keeps going back to off and hence the wheel just spins

I can’t open link to Guroo’s homepage

App is unable to open the link when toggle is activated

Hi, I'm not sure where the displayed glucose data is coming from on my enhanced-d app, but it’s not my actual glucose in any way, nor is it my HR data. Do I have too many integrations? It is nightscout the issue potentially?

t‘s great that you‘ve started integrating Glooko to get Insulin data into the app. Unfortunately for me with the Omnipod 5 the Insulin data isn‘t transfering yet. I only see parts of the Insulin sometimes and the training view always shows 0 Units… also there is no IOB diagram there for me, which might also be a sign that the Insulin data isn‘t being imoorted correctly yet. Would be great if you could check and fix that! If you need some extra data from how Omnipod 5 is saved in glooko, I‘m happy to help.

There seems to be a big time delay between the Enhance-d and LibreLinkUp or no interaction at all at times. For example I finished a walk earlier today after 7 AM. At time of writing after 9AM still no interaction between Enhance-d, LibreLinkUp and Strava

Garmin integration failed

Hi, I’m getting very frequent (sometimes more than one a day) revoking of my Nightscout integration. Any ideas how I can make the integration more robust? Thanks…

We're currently aware of an issue with the Guardian monitor uploader app for Medtronic data to Nightscout that some users are using. Whilst this app is in no way related to us, we are working closely with the developer to resolve this issue. The uploader does not apply a proper UTC offset value in its upload to nightscout, which in turn means that all values are treated as being UTC. This means that any blood glucose values uploaded via this mechanism may appear several hours in front or behind your local time depending on your offset to UTC. Nightscout applies front-end timezone conversions and stores all data as UTC relative, however, we store data with a UTC value and its UTC offset so that we can display data in the user's local time irrespective of where you are looking. This is important for people who may be having their data reviewed by others but also allows mobile app users to look at activities and glucose data in the other users local time rather than being relative to the onlooker. We hope that guardian monitor app will be updated soon to resolve this issue and correctly store UTC offset values based on the uploader's local time zone.

Hey there! We’ve noticed a few users having trouble getting their data from Komoot to sync. We’re on the case and will keep you posted as soon as we have any updates. Sorry for the hassle, and we’re doing our best to fix this ASAP! Henry & the Enhance-d Team

Integratie failed

Due to local regulations, we do not yet have access to Germany based user's Freestyle Libre data. But we're working on making this possible.

Using nightscout and Medtronic system - the CGM data from my activities often takes ages to come to activities, if it comes at all. All the data is viewable on the desktop dashboard straight away but not on the app for some reason. Example image from run this morning:

Carbohydrate information (or any meals) does not appear to be pulling down with the Nutracheck Integration.

I did activity at 8:37 AM. But this app shows it as 8:07 AM

Due to local regulations, we do not yet have access to France based user's Freestyle Libre data. But we're working on making this possible.

We have noticed a bug in Google Fit activities where the local timezone are not kept and all activities are pulled through in UTC. As such if you have an activity recorded in CEST (UTC +2 in summer) then you will notice the timestamp on this activity being shown as 2 hours earlier than the local time the activity was completed.