Common issues and misusages

> Error -300 (HTTPS)

The -300 error, is described by Garmin to be a timeout error. But, if the error appears instantly after launch, you are probably facing something else. As described in this thread, depending of the version of IOS or Android, Garmin doesn't permit anymore to communicate in HTTP with something other than localhost. You must use HTTPS.

The error also appears when the certificate is self signed (I didn't do the test to add the CA certificates to the smartphone, perhaps it can solve the issue). You can use free service as Let's Encrypt to create a certificate which the smartphone will approve. If you configure apache, don't forget the "SSLCertificateChainFile" parameter in addition of "SSLCertificateFile" and "SSLCertificateKeyFile".

If HTTPS is really not an option and your device have WiFi and/or LTE, because HTTPS is not required with WiFi or LTE, force sending request throught WiFi could be a solution. Take a look on "media" option.

> Memory

For supported watches which only have 60kb of memory, namely :

  • Fēnix® 5, Fēnix® 5s, Fēnix® Chronos
  • Forerunner® 245, 645, 935
  • Quatix® 5
  • Venu™
  • Vìvoactive® 3
    • Note: "music" versions are not affected.

You can configure about 8 to 15 actions on these watches depending on their complexity, then memory could be full.
If the yellow exclamation mark appears, try to limit the number of configured actions.

> Garmin Express vs ConnectIQ

Many users reported issues when configuring the settings from Garmin Express. It's not related to my widget but due to GarminExpress. Please prefer to use ConnectIQ app to configure the settings of the widget.
Is also seems that upgrading from GarminExpress could alter already configured settings, please also prefer ConnectIQ to upgrade the widget.

Supported devices

  • Approach® S62, Approach® S70 (42 and 47mm)
  • D2™ Air, AirX10, Charlie, Delta, Delta PX, Delta S, Mach1
  • Dark Vader™, Rey™
  • Descent™ Mk1, Mk2, Mk2i, Mk2S, Mk3
  • Edge® 1050, 1030, 1030 Bontrager, 1030 plus, 840, 830, 540, 530, 520Plus, Explorer, Explorer2
  • Enduro™, Enduro™3
  • Epix™2, Epix™2pro (42, 47 and 51mm)
  • Fēnix® 5, 5 plus, 5S, 5S plus, 5X, 5X plus
  • Quatix® 5, 6, 6X, 6X Solar, 6X Dual Power
  • Tactix® Charlie, Delta Sapphire, Delta Solar
  • Fēnix® 6, 6 Solar, 6 Dual Power, 6 Pro, 6 Sapphire, 6 Pro Solar, 6 Pro Dual Power
  • Fēnix® 6S, 6S Solar, 6S Dual Power, 6 Pro, 6S Sapphire, 6S Pro Solar, 6S Pro Dual Power
  • Fēnix® 6X Pro, 6X Sapphire, 6X Pro Solar, 6X Pro Dual Power
  • Fēnix® 7, 7S, 7X, 7pro, 7Spro, 7Xpro (WiFi and nonWiFi)
  • Fēnix® 8 (all)
  • Fēnix® Chronos, e
  • First Avenger
  • Forerunner® 55, 165, 165 Music, 245, 245 Music, 255, 255s, 255 Music, 255s Music, 265, 265s, 645, 645 Music, 745, 935, 945, 945lte, 955, 965
  • MARQ™ Adventurer, Athlete, Aviator, Commander, Driver, Expedition, Golfer
  • MARQ® Captain
  • MARQ2™ Adventurer, Athlete, Aviator, Captain, Golfer
  • Venu™, Venu™ Sq, Venu™ Sq. Music Edition, Venu™ 2/2S/2+, Venu™ Sq2, Venu™ Sq2 Music Edition, Venu™ 3/3S
  • Vìvoactive® 3, 3 Mercedes, 3 Music, 3 Music LTE, 4, 4S, 5

Obviously I don't have all the physical devices. I do a test for each reference with the simulator, but it does not always perfectly reflect the real rendering. Thank you for being indulgent and do not hesitate to send me pictures of the rendering or requests for improvements.

Roadmap

  • Add wifi support to send the request. From now, I perhaps find a way but it may take about 20s/30s to launch the query... OK
  • Add PUT method support. OK
  • Add support or array in resDisplay. OK
  • Add support of older devices. Honestly not the priority, it will take lot of time and complexify the code for a probably poor visual result...
  • Add option to add custom http headers to the query.
  • Add option to send POST as plain-text.
  • Always try to optimize memory.

v1.6.x release notes

  • 1.6.0 (02/09/2024) :
    • Change SDK major release. From 6.4 to 7.3.
    • Add support of Enduro™3, Fēnix® 8, Fēnix® e, Edge® 1050

v1.5.x release notes

  • 1.5.2 (06/03/2024) :
    • Add support of Forerunner® 165, 165 Music
    • Add support of Descent™ Mk3
    • Add support of nonWiFi version of Fēnix® 7pro and 7Xpro
  • 1.5.1 (27/10/2023) :
    • Fixed issue with headers option, "Content-type" was not correctly handled.
    • Add support of Vìvoactive® 5
  • 1.5.0 (26/09/2023) :
    • Change SDK major release. From 4.2.4 to 6.4.4.
    • Add support of Venu™ 3 and 3S

v1.4.x release notes

  • 1.4.4 (03/07/2023) :
    • Add support of Approach® S70 (42 and 47mm), Edge® 520plus, 540, 840, Epix™2pro (42, 47 and 51mm), Fēnix® 7pro, 7Spro, 7Xpro
  • 1.4.3 (11/03/2023) :
    • Display fixes.
  • 1.4.2 (10/03/2023) :
    • Add support of Forerunner® 965, 265, 265s, MARQ2™, Edge® Explorer2
    • Code change due to new SDK version.
  • 1.4.1 (18/10/2022) :
    • Add support of Edge® 1040, Venu™ Sq2, Venu™ Sq2 Music Edition
  • 1.4.0 (07/06/2022) :
    • Add custom headers option
    • Remove support of basicAuth option (automaticaly modified to the new "headers" option when already configured).
    • Add support of Forerunner® 955, 255, 255s, 255 Music, 255s Music
    • Code optimization and minor bugs fixes.

v1.3.x release notes

  • 1.3.7 (11/04/2022) :
    • Add support of D2™ AirX10 and D2™ Mach1. Some cosmetic improvements for Edge® series. Code optimization.
  • 1.3.7 (31/01/2022) :
    • Add support of Epix™2 and Fēnix® 7, 7S, 7X
  • 1.3.6 (13/01/2022) :
    • Add full support of glance-view, specially for new devices.
  • 1.3.5 (10/01/2022) :
    • Add support of Venu™ 2 plus
  • 1.3.4 (04/10/2021) :
    • Display enhancements and code optimization. The resDisplay is now written on multiple lines.
  • 1.3.3 (11/06/2021) :
    • Add support of Forerunner® 55, Forerunner® 945lte, Descent™ Mk2S, Venu™ 2 and Venu™ 2S
  • 1.3.2 (16/04/2021) :
    • Add PUT method.
    • POSTcontent is now always sent as the request content regarless of the method (GET, PUT or POST).
    • resDisplay now supports arrays in jsonPath.
  • 1.3.1 (12/04/2021) :
    • Add a json option to force to launch the request through a specific media.
    • Memory optimization.
  • 1.3.0 (02/04/2021) :
    • Add Wifi/LTE support to launch request if BLE connexion not available. Could be desactivated in options.
    • Add support of Enduro™.
    • Remove support of Approach® S62, D2™ Charlie, Descent™ Mk1 and Vìvoactive® 3 Mercedes Edition. The reason is they don't support SDK3.1 which is needed for WiFi/LTE support.
    • Multiple display enhancements.
    • Code optimization and minor bugs fixes.

v1.2.x release notes

  • 1.2.3 (25/03/2021) :
    • Settings are now reloaded when changes appear during the widget is executing.
    • A new setting permit to disable tap to launch the action on touch devices (last line in Connect IQ settings of widget).
  • 1.2.2 (17/03/2021) : Optimize the time to loading settings if there is no change.
  • 1.2.1 (11/02/2021) :
    • Add new features : autolaunch, POST method, display a result and basic auth
    • Many many huge memory optimizations
    • Rotating menu entry on button devices
  • 1.2.0 (19/01/2021) : Complete overhaul of the settings (json format) to allow the addition of new features

v1.1.x release notes

  • 1.1.5 (30/12/2020) :
    • Add support of Venu™ SQ and Venu&™ SQ Music.
    • Add long press for menu for touching device.
  • 1.1.4 (25/10/2020) :
    • Add support of Approach® S62, D2 Air/Charlie/Delta/DeltaS/DeltaPX, FR745, DescentMK1 and MARQ™ Golfer.
    • Add the possibility to launch with a tap for touch watches (specialy for vivoactive 3 because some people report that the button doesn't work)
  • 1.1.3 (05/11/2019) : Adding support of Venu™, Fēnix® Chronos, "Marvel" series and "Starwars" series. As all touch watches (Vivoactive), it seems there is a bug if you press the right/up button during selection of device or action. If someone could try it on physical watch because I cannot find why and I have no log on the developement tool...
  • 1.1.2 (18/10/2019) :
    • Adding VivoActive® 3, 3music 3musicLTE and 4S.
    • Memory optimizations to support Vivoactive3
  • 1.1.1 (17/10/2019) : Adding VivoActive4 support.
  • 1.1.0 (10/10/2019) :
    • Add line of error icons at the bottom (BT connexion missing and error on loading parameters)
    • Error codes are now more readable
    • Better display for all resolutions, and other display enhancements
    • Code optimization and minor bugs fixes
    • Add "auto-next" option.
    • Add icons for devices and actions.
    • Options "auto" and "icon" can be used together. Ex : "My device name;;icon1;;auto"

v1.0.x release notes

  • 1.0.4 (04/10/2019) : Correct bug on Fēnix 6, the 'back' button didn't exit the widget
  • 1.0.3 (04/10/2019) : Add auto selection of action, as previously done for device
  • 1.0.2 (04/10/2019) : When only one device is configured, pass to action choice directly
  • 1.0.1 (30/09/2019) : Add Fēnix 6 support as asked by a user. I cannot test it, tell me if it's right.
  • 1.0.0 (15/08/2019) : First version, just for me and testing.