OpenWeatherMap onecall - api

That could be on OWM's side.  If I recall with the free API. it can be up to an hour before data changes.  There can also be delays based on how often a weather station send it's data to OWM.

I checked with the data from simulator, - a System.println with the data that came from the call to onecall method

The [dt] value is the data is the time the readings were taken.  It's in "unix time".  It doesn't matter when an app requests the data as much as how old the reading is.

I didn't checked that, but when you see on the watchface that the temperature remain the same for an hour and in that time the temperature changed five - six times (increasing), in the call from simulator - you understand that is a problem in the watchface

Let's say you request data at 10:00.  The data could be timestamped at 9:45, request again at 10:10, and it still could be from 9:45.  Same with a request at 10:20, and 10:30.  

Should be the some problem in simulator?

also the watchface based on https://api.openweathermap.org/data/2.5/weather worked correctly 

what you can try, put in onReceive data prinln("responseCode")  and let the simulator runs for long time,

pretty sure you will receive a 403 error. (that what happened to me)

what you should do also is to refract again your code, the one on background and the AppBase, I tried to send an example but the forum does not allow me to put code part.

using Toybox.Application as App;

function onTemporalEvent()
{
var AK = App.getApp().getProperty("WeatherApi");
var a = App.getApp().getProperty("a");
var b = App.getApp().getProperty("b");
if(AK != null && a != null && b != null)
{
Comm.makeWebRequest
(
"">api.openweathermap.org/.../onecall",
{
"lat" =>a.toFloat(),
"lon"=>b.toFloat(),
"exclude"=>"minutely,hourly,daily,alerts",
"appid"=>AK,
"units" => (Sys.getDeviceSettings().temperatureUnits==Sys.UNIT_STATUTE) ? "imperial" : "metric"},
{
:methods => 1,
:headers => {"Content-Type" => 0},
:responseType => 0
},
method(:receiveWeather)
);
}
}