How to make an alert when mobile data is not available?

Jack 20 days ago

Hello.

Is there a way to make a short message on the watch when I turn off the connection (mobile data)?

I'm using OWM data, currently I'm using

if (!System.getDeviceSettings().phoneConnected) , but this only solves the problem with BLE.

I still need to solve

var Settings = System.getDeviceSettings();

if (Settings has : connectionAvailable) {.

Or if there is a better way, for example Communications.makeWebRequest?

Then please give an example of how to solve this problem.

Thank you

FlowState 19 days ago in reply to Jack

I see, thank you for the context. To be fair I should've gotten that from "extends WatchUi.Drawable" in the first place.

Can you please show how Weather gets weather data from the background process?

Again, whatever method you used to send weather data to Weather drawable can also be used to send a weather error to the drawable.

If you don't want to change the code too much and you are ok with handling all errors the same way, you could use a weather data value of null to indicate there was an error.

Jack 19 days ago in reply to FlowState

function onBackgroundData(data)

{

System.println("Synch. "+ data);

if(Application.Storage.getValue("updated") == null) {

Background.registerForTemporalEvent(new Time.Duration(Application.Properties.getValue("RefreshRateOWM") * 60));

}

var _data = data as Dictionary;

var time = _data["updated"] as Numeric?;

var temperature = _data["temp"] as Numeric?;

Application.Storage.setValue("updated", time);

Application.Storage.setValue("temp", temperature);

WatchUi.requestUpdate();

requestWeatherUpdate();

}

FlowState 19 days ago in reply to Jack

So to be clear, in your Weather drawable, you call Application.Storage.getValue() in draw() for these values ("updated" and "temp")?

So again, all you have to do is adopt one of the solutions that was already posted in the thread to return the responseCode
- either along with the OWM data or instead of the OWM data (when there's an error).

Then you need to give responseCode to the drawable the same way you're giving the other data to the drawable.

Going back to your comment "I have no experience with this solution" - this isn't really the kind of thing that you need special knowledge for, this is simply generic coding / problem solving skills. You will eventually have to develop these skills on your own, if you want to code your own apps.

It's like driving a car in a new city with unfamiliar roads and neigbourhoods (and no GPS). You have to adapt to the new city, you would not expect someone to teach you to drive all over again, with lessons specifically designed for that city.

It's like being given a new task at school or work that is a combination of tasks that you already know. You don't expect your prof, boss or mentor to teach you exactly how to do the new task, they expect you to apply the knowledge and skills that you already know towards solving the new task.

To be clear:

- you already know how to pass "updated" and "temp" to the Weather drawable

- you asked how to determine if the OWM request failed and the answer was to look at the response code (any value other than 200 is failure). Examples of this were given

- now your challenge is to ALSO pass responseCode to the drawable.

I am really not sure how this is impossible with an example.

FlowState 19 days ago in reply to FlowState

But here's a concrete example anyway, assuming that we use my solution for passing responseCode to the foreground.

I will say that it's not a good idea to call Storage.getValue() in the Weather drawable, because Storage is very slow and battery-intensive.

It's ok to write weather data with Application.Storage, since I assume you want it to persist if the watchface is terminated and restarted (so the user doesn't need to wait for weather information to be downloaded again).

But you shouldn't be constantly reading from Storage in the drawable. The drawable will be rendered once per second in high power mode (for a few seconds while the user is looking at their watch).

A better solution would be to create a method on the drawable which sets the weather data, and to use View.findDrawableById() to get the drawable instance.

I will provide an example in a follow-up comment.

FlowState 19 days ago in reply to FlowState

Solution where:

- onReceive passes both responseCode and OWM data from background to foreground

- foreground passes both responseCode and OWM data to drawable

- weather data is written to storage when it's updated from background (just as before)

- weather data is only read from storage at application startup (when initial view is created)

Jack 19 days ago in reply to FlowState

Thank you very much, I will look at the method you recommend: View.findDrawableById(). Is it possible to call the response Code = 200 this way? I mean error.

FlowState 19 days ago in reply to Jack

You're welcome!

Jack said:
Is it possible to call the response Code = 200 this way? I mean error.

I don't understand the question.

responseCode is the first argument to onReceive, the callback for makeWebRequest.

function onReceive(responseCode, data);

If responseCode is 200, that means makeWebRequest was successful. Any other value means there was an error (and data should also be null).

The possible values for responseCode are listed here:

[https://developer.garmin.com/connect-iq/api-docs/Toybox/Communications.html]

Jack 19 days ago in reply to FlowState

Sorry, I was wondering if it is possible to display an icon as an error when the response Code is other than 200 in View.findDrawableById().

FlowState 19 days ago in reply to Jack

Jack said:
Sorry, I was wondering if it is possible to display an icon as an error when the response Code is other than 200 in View.findDrawableById().

Maybe you don't understand the purpose / function of findDrawableById(). findDrawableById() doesn't do anything except get the drawable object with the given ID.

The point is to get the instance of the Weather drawable class so you can call functions on the drawable.

You said that you have a drawable in your layout.xml with a custom implementation in the Weather class.

That means your layout.xml must look like this:

<layout id="WatchFace">
  ...
  <drawable id="weather_data" class="Weather" />
  ...
</layout>

When you app runs, an instance of the Weather class is created. That's how CIQ code in the watch's firmware can call Weather.draw() to draw your Weather drawable.

In the example I gave above, I showed you how you can change the Weather class to receive the weather data (and responseCode) using the setWeatherData() function.

Again:

- You have a Weather class

- You have a drawable in your layout that is connected to the Weather class, with a given id (pretend it's "weather_data" although of course I have no idea what the id is)

- When your app runs, an instance (object) of the Weather class is automatically created which represents the actual drawable in the layout

- You want code outside of the Weather class to talk to the instance of the Weather class (to set weather data / error)

- findDrawableId("weather_id") will return the instance of the Weather class so that you can call functions on it

I'm sorry, I don't know how else to explain it. If you have any other questions, I'll try to answer them.

flocsy🤠 19 days ago in reply to Jack

@FlowState will get the ChatGPT badge soon