Communication issues

I am doing a web request for tide info. Code works fine, API key works fine.

Request comes out as success. (200). I trigger it every 3 hours, to conserve battery.

I then put the watchface in my watch to test it for longer periods, and after a while, it stops communicating successfully. I get error code -104

I think I also found a workaround. I just applied a different watch face, then reapplied mine, and it works again.

My assumption is that the issue is between the watch and the phone (iPhone). After w while the BT connection becomes flaky. When the watch starts the request, the phone does not go through with it, and I get an error code in return. Is this correct? If so, how do I solve it?

I have been trying to post logs but the forum is not allowing me to.

jim_m_58 over 5 years ago

-104 means your phone isn't connected at the time the request is made. It could be connected right before and right after though.

agsurf5 over 5 years ago in reply to jim_m_58

Yes. How do I make it that the watch connects to the phone and "wakes" it so that it connects to the internet? There are no permission that I see to activate. "Background App Refresh", "Cellular data" and bluetooth are all active for Connect on the phone. And I am also on wifi all the time.

I could change the timer to make a web request every 5 minutes, but it seems an overkill, as tides do not change that often and I already grab two days ahead of time.

jim_m_58 over 5 years ago in reply to agsurf5

The watch and phone will be connected when they can. You can't have the watch force it.

Doing it every 5mins could also result in maing out your requests with the provider.

You might consider doing something like if you get a -104, re-register the background for 5 minutes later, and keep doing that until it's not -104, in which case, schedule it for 6 (or whatever) hours later.

agsurf5 over 5 years ago in reply to jim_m_58

that's a great way to do it. thanks a lot.