Weather updates - background process - connectivity issues

Hi gents,

I have a few users of my skytracker face that are reporting that since 2-3 weeks the weather stopped updating for some unknown reasons. Used to work perfectly fine before that. I don’t have this issue on my fenix 6pro nor my fenix 5x plus. Some experienced this drop when running both connect and connect iq app. Other are reporting having this issue right after charging their devices.

A few have a vivoactive 4 or variant... not sure if that helps

I didn’t do any updates recently so I’m wondering if anyone else have users reporting this?

cheers

Top Replies

jim_m_58 over 5 years ago +1

What is your source for weather? Darksky seems to be going through changes (they got bought by Apple)

All Replies

jim_m_58 over 5 years ago

What is your source for weather? Darksky seems to be going through changes (they got bought by Apple)

PlayItLoud over 5 years ago in reply to jim_m_58

Not using Darksky, their model can become quite expensive if you offer the weather data for free in your app.

jim_m_58 over 5 years ago in reply to PlayItLoud

So what provider are you using? Are you sure the issue isn't on their end?

PlayItLoud over 5 years ago in reply to jim_m_58

Same message back with same data and data structure. No changes coming from the weather provider. So now I’m looking at other reasons

Shent-Aurkhan (SHN) over 5 years ago

Hi mate,

Do you initiate the weather update with '' onExitSleep ''?

If yes, see in the report bug, there is an issue on Va4 with it.

Shent-Aurkhan (SHN) over 5 years ago in reply to Shent-Aurkhan (SHN)

forums.garmin.com/.../onexitsleep-not-being-called-on-va4

jim_m_58 over 5 years ago in reply to PlayItLoud

What do you see? Is the background not running or are you getting an error on the makeWebRequest?

Adding println calls is can be a pain except for sideloads, so what I do, is in the background, in the case of an error, I return the error (a Number) while if I get data, I return that. Then in onBackgroundData, do a instanceof for "Number" and save off the last error.

That way the error is available to the WF and can be an option for a field in the WF. And by displaying Background.getLastTemporalEventTime() as another option for a field, you can see the last time the background ran. (without need for println calls or setting up a log file)

Between displaying the status and the last time, it's easy to walk a user through seeing what happening

If the background is running but you're always seeing a -104 it means something different than seeing a -402 or a -2, and that can be really helpful.

PlayItLoud over 5 years ago in reply to Shent-Aurkhan (SHN)

Yes... That's exactly what's happening! I'll implement a workaround
Thanks!!! Shent-Aurkhan (SHN)

PlayItLoud over 5 years ago in reply to jim_m_58

Debug Field on watch face.... That's just a BRILLIANT idea!!!!!
Thanks jim_m_58

jim_m_58 over 5 years ago in reply to PlayItLoud

Trust me it comes in really handy when a user has a problem.

    function onBackgroundData(data) {
    	if(data instanceof Number) {
    		wuStatus=data;
    	} else {
    		wuData=data;
    		wuStatus=200;
    	}
    	WatchUi.requestUpdate();
    }
    
    //and in the background
    
    function onReceive(responseCode, data) {
        if(responseCode!=200) {Background.exit(responseCode);}
        else {Background.exit(data);}
    }

and then make the display of the status an option.