How do I check if the watch is connected to the phone - Watch App?

The reason I am asking this question is that I would like to use this method: makeWebRequest() , which works when there is a WiFi connection or if connected to a mobile device over Bluetooth. In my case, I am going to use my application mostly outdoors, which periodically initiates a web request. However, I want to be able to store the lost data on the watch to send it in the web request when the Bluetooth connection with the phone is re-established. Therefore, I need to implement an if condition that checks whether the phone is connected via Bluetooth or not.

0 Shent-Aurkhan (SHN) over 1 year ago

hi,

you will find all you need here:

https://developer.garmin.com/connect-iq/api-docs/Toybox/System/DeviceSettings.html#phoneConnected-var

or here

https://developer.garmin.com/connect-iq/api-docs/Toybox/System/DeviceSettings.html#connectionAvailable-var

https://developer.garmin.com/connect-iq/api-docs/Toybox/System/DeviceSettings.html#connectionInfo-var

0 4641850 over 1 year ago in reply to Shent-Aurkhan (SHN)

Thank you very much. Just to make sure, to store said data I should use https://developer.garmin.com/connect-iq/api-docs/Toybox/Application/Storage.html correct?

0 Shent-Aurkhan (SHN) over 1 year ago in reply to 4641850

hi, it depends on which device, see here: developer.garmin.com/.../

0 jim_m_58 over 1 year ago in reply to 4641850

One thing to consider is that you want to try again if there is any error seen in the callback for makeWebrequest(). If the result isn't 200, there was an error, including a -104 if there isn't a phone connection.

This really means you don't have to check for a phone connection before the makeWebRequest, but just handle all errors in the same way in the callback.

0 4641850 over 1 year ago in reply to jim_m_58

That sounds like a good idea but what kind of trigger can I use to make it send the stored data once the connection is re-established?

0 jim_m_58 over 1 year ago in reply to 4641850

Therr's no callback available when a connection is lost or established, so you have to use a timer in any case.

0 Ultra over 1 year ago in reply to jim_m_58

jim_m_58 said:
This really means you don't have to check for a phone connection before the makeWebRequest,

Though it’s more efficient to check first, to minimise -104. Otherwise you’ll be blindly trying then having to wait another 5 mins.

0 jim_m_58 over 1 year ago in reply to Ultra

If you don't have a phone connection, you still wait the same time to retry, Like I said, a timer in either case.

And if you check in your app before you do the makeWebRequest, the overhead would likely be the same if that check was done in makeWebrequest and not your code. Handling all errors the same way would be cleaner code wise.

0 Ultra over 1 year ago in reply to jim_m_58

jim_m_58 said:
If you don't have a phone connection, you still wait the same time to retry, Like I said, a timer in either case.

No you don’t as you can trigger the background temporal event as soon as you have a connection. You don’t have to wait 5 minutes after a failed attempt, you wait till it says you have a connection then trigger the web call. Phone connection blips in and out, it’s the nature of Bluetooth and background on phone as well. You’re better off trying the web call when your device says the connection is there.

0 jim_m_58 over 1 year ago in reply to Ultra

There is no mention that this is being done in the background with a temporal event. Sounds like it's in the foreground to me.