How to get a list of the watches that have a compass ?

Is there a way to know which watch have which feature ?

Like https://developer.gar https://developer.garmin.com/connect-iq/compatible-devices/min.com/connect-iq/compatible-devices/

but with more information.

The goal is to be able to write and maintain the manifest.xml file (the products list) accordingly.

Regards,

Jean

Top Replies

Travis.ConnectIQ over 4 years ago +2 verified

In case it wasn't clear from FlowState's comment, the documentation for functionality that is conditionally available *should* list the devices that have support. If you look at the docs linked above…
FlowState over 4 years ago in reply to jim_m_58 +1 verified

If the docs are to be believed, then the at least the original Vivoactive does not have a magnetic compass. (I'm assuming that in this context, "compass" means magnetic compass and not GPS compass.)…
jeansch over 4 years ago in reply to FlowState +1

Thank you !

All Replies

0 jim_m_58 over 4 years ago

I'm actually trying to think of any CIQ devices that don't

+1 FlowState over 4 years ago in reply to jim_m_58

If the docs are to be believed, then the at least the original Vivoactive does not have a magnetic compass. (I'm assuming that in this context, "compass" means magnetic compass and not GPS compass.)

https://developer.garmin.com/connect-iq/api-docs/Toybox/Sensor/Info.html#mag-var

It seems that this could be verified in the sim with the following code (assuming the sim returns the correct values):

System.println("device has magnetic compass: " + (Sensor.Info has :mag));

When I tried this with a watch app in the sim, it returned "false" for Vivoactive and "true" for Vivoactive 3.

0 jeansch over 4 years ago in reply to FlowState

Thank you !

+1 Travis.ConnectIQ over 4 years ago

In case it wasn't clear from FlowState's comment, the documentation for functionality that is conditionally available *should* list the devices that have support. If you look at the docs linked above, you'll see a Supported Devices section. You can click Show/Hide to see the list.

0 jeansch over 4 years ago in reply to Travis.ConnectIQ

Yes, the "View devices" link is useful, thanks.

Having the product id in that list could be even better.

0 jim_m_58 over 4 years ago in reply to jeansch

Understand that for a device like the f6, it has more than one part number. World Wide and APAC.

006-B3289-00

006-B3514-00

006-B3770-00

0 FlowState over 4 years ago in reply to jim_m_58

I'm guessing that by "product id", they mean the Connect IQ identifier (like "fr245m" and "fenix6s"), which is literally referred to as "deviceId" in compiler.json, not the part number.

If you want to play around with jq (for example) to aggregate, parse and reshape compiler.json files, you could output JSON that maps/groups a displayName (like "Forerunner® 245 Music") with deviceId (like "fr245m").

e.g. If I use the following command with WSL bash in the CIQ devices folder:

jq '{ displayName, deviceId }' */compiler.json | jq --slurp > devices.json

I get this:

[
  {
    "displayName": "Approach® S60",
    "deviceId": "approachs60"
  },
  {
    "displayName": "Approach® S62",
    "deviceId": "approachs62"
  },
  {
    "displayName": "D2™ Air",
    "deviceId": "d2air"
  },
  ...

But it would be nice to have in the docs, too.

0 jeansch over 4 years ago in reply to FlowState

Yes, exactly, (but that id is refered as product in the manifest.xml file).

Thanks for the tip about the compiler.json.

I don't have the devices directory yet in my setup, it looks like monkeyc is working nicely with.

I'll have a look at that.

0 jeansch over 4 years ago in reply to jeansch

Found...