Fit Contributor datafield not working on Fenix3

Garmin:

I'm using the FitContributor to write out summary values and a graph to Garmin Connect/GCM. It works on the simulator and monkeygraph for all devices with minSDKversion 1.3.0 and it works on my 920XT:
https://apps.garmin.com/en-CA/apps/ded87d46-5477-4ca7-a247-847b896393e0

I'm having reports that it is not working on a Fenix3 and a Fenix3 HR:
https://forums.garmin.com/showthread.php?220947-Data-Field-Surf-Tracker&p=910050#post910050

This is impossible for me to debug on devices I don't own when it works on the simulator - should it work, and any ideas why it wouldn't work on the F3's? Hopefully it is something I am doing wrong. I can post some code, or send it if needed, but perhaps someone can test it out...

Thanks,
Dave
  • Now sent a mail to the address, please put pressure on connect team to implement an else branch instead of only to rely on unitid when identifying the product.
  • Thanks Mathias and Coleman... hopefully this will sort out the Elevation corrections enabled issue too... please keep us posted. I suspect we'll have to provide our device/unit IDs at some point to correct the backend database?
  • Nice find, Mathias. I tried the same and it worked. I used the 'Fit File Repair Tool' to increment my Device ID and then uploaded the resulting fit file to GC. The first two tries were not recognised (unknown device), but the third was (i.e. my Device ID + 3).

    Result: Connect IQ fields recognised (from DozenRun datafield), and elevation corrections disabled. See .

    So apparently the problem is with the Garmin Connect backend not properly recognising our Device IDs.
  • I did the same... modified the serial number and uploaded; elevation corrections are now disabled and Connect IQ info is now showing correctly ;)

    Hope Garmin can "clear" or serial numbers in their database.
  • I also tried changing the Unit ID in GarminDevice.xml and DEVICE.FIT. Unfortunately, FFRT cannot modify device.fit, so I could do nothing about that, and changing GarminDevice.xml only gives strange results, probably because in that case it contradicts device.fit. I did manage to add a new (2nd) Fenix 3 to Garmin Express and GC though. Only GCM was not cooperating.
    If anyone has a tip on how to edit the Unit ID in device.fit, I'd be happy to do some more experimenting. My goal was to have GC/GCM also show the correct device under 'Last Used Device' (it is Unknown currently).

    BTW, you have to set these files to read-only after modifying to prevent the device from replacing them with the originals from the ROM when you disconnect from USB. When you are done experimenting, just delete them, and the device will restore the originals.
  • Working!

    OK, this morning I checked my activity from yesterday afternoon and elevation corrections are correctly disabled again AND connect IQ data graphs are present (for the first time ever without manipulating my device serial number!)
  • Same here: my run yesterday had elevation corrections disabled, and Connect IQ fields recognised! :) (Seems like our messing with Device IDs finally woke someone up :rolleyes: )

    Just in my GCM profile under Last Sync my device is still unknown.
  • I just got my new 935 and tested my data field => the summary fit contributor data is still not being written out to Garmin Connect!! I posted this issue back in October 2016 and it is still broken. There are reports that it doesn't work with the 5S either. Will this ever be fixed or do I give up? My old 920 worked better than this and I'm tired of having to answer users emails and complaints.
  • Garmin Connect IQ team please wake up. This issue now exist on 5S, 935(and most likely all new watches).

    It's blocking core functionality and for some of us the main usage of the watch. The only reason I got a Garmin was to run Surf Tracker IQ app. The data field is perfect but without the connect app summary the usability is half baked and not as useful.

    Please let us know what is being done to resolve this. If this is really a question of IDs getting blocked then all new watch ids need to be fixed!

    Thanks to the mods that have attempted to fix this but I think we need to start posting this to the various social forums and Garmin connect support channels as it seems that this thread alone is not enough to get traction on a final resolution.
  • Former Member
    Former Member over 8 years ago
    I tried to open a support ticket (Reference ID: 9512104K0 and #4508) at different Garmin support channels, but either there is no response or the problem is not understood by the first level support.