@idefix37
I’ve seen this advice several times now and is at best partially helpful.
And you nail the problem to the head - what if I DO start the app from the widget? For some strange reason I get defaulted to ECMWF, instead to MBlue, which is much better model here.
Also in my experience, even if I do start the app with the icon, not via the widget, the forecast always defaults to the inaccurate ECMWF.

And to top it up - how about not only retaining that choice in the app when opened (widget or not) but actually display the chosen model in the widget?
Currently the widget is so wrong, always!

The difference in the mountains where I am currently between MBlue and ECMWF is a huge 6 degrees in favor of the former, same with rain forecast, ECMWF is just very wrong.
How about choosing one model, forget about it and actually see the data in the widget, app and web consistently?
Why do you insist to default to a model users may not want to use?

@idefix37
Ok. I understand.
In this case the original request is even more valid, as the WBT has nothing in common with how it really feels outside, nor how you must prepare for exercise outdoors.
Although I see value for it the extremes, basically, set an alert if it goes over 35 and don’t go outside then, It cannot be seen as a replacement for the “real feel”.

@idefix37

In theory that looks like a good answer. In practice - the wet-bulb layer is laughably inaccurate.
Today it showed 18 degrees here :)
I wish, as outside was 34 degrees with a real fee two above.

It would be dangerous is the forecast was mildly wrong, but now it’s so much off, that I just smille looking at it. Until that becomes usable (now isn’t), the simpler calculation for “real feel” offered in other apps would be much better (compared to nothing now)

See if you don’t believe:

@emilw No. The last version didn’t touch the widgets nor allowed default model selection.
The widget still has only a limited set of models available. Opening through it opens with the model used on the widget, which is often wrong and not the one I want to use (MBlue)
Opening directly with the icon defaults to ECMWF, regardless which model I’ve chosen before leaving the previous time.

Frustrating in the app and misleading in the widgets.

@idefix37

I also did similar for the humidity map.

@idefix37
You literally wrote it :)
Sunshine with cloud coverage of 90% is… surprise, surprise… 10%.
And so on.

This is a very useful tool in the forecast and a great for short glances:
Here is a great implementation in Weather Pro:

By the way - this, real feel, and the precipitation probability - things that Windy stubbornly preaches that we “don’t need”, keep WeatherPro as my go-to weather app.
I’m going to continue its subscription and discontinue Windy once it expires, as Windy is unwilling to improve UX and misses key usability (above).

@jasons47 Slight bump of this thread. A reply if that's planned (as part of is is a clear bug, the missing models selection, I guess... feature) would be appreciated.
Same has been requested before - https://community.windy.com/topic/34557/meteoblue-as-an-option-for-forecast-on-the-app-widget

Please add Meteoblue as an option for forecast on the app widget.
If it’s not available as a current location (if there are such locations), should fall back to another model.

Currently it’s not available:

@Jamitt same on iPhone

By the way - time now is not 7:45, but 22:45

@Dan_P

I hate to sound sarcastic, but they said it was on their to-do list over 5 years ago.
So - any moment now…
But then I also saw the date of the post and now I understand that it was just an April Fool’s joke…

idefix37 contunues to suggest in various threads “use last overlay” which has NO effect over the forecast (nor the widget) and they continue to default to ECMWF

@Suty yes

@Suty MBlue, Aladin are much better regional models.. For forecast I’m switching between them, depending on my location.
I’m sure Australia, Japan, US can benefit from their own regional models. I see no reason why any model that can display a forecast for a location would be missing from the widget option.
Today is a great example.
I’m in the mountains, between 1200 and 1700 meters. Hiking. Alone.
ECMWF shows heavy snow starting at 14:00. ICON shows moderate snow at 12:00 and heavy after 15:00
Only the detailed Aladin and MBlue show heavy snow starting at 11:00, as they make difference between 1700 meters and the plain below. Guess when the heavy snow started.
So do you think the difference matters? Three hours of heavy snow? I head out looking at the wrong forecast (like what the widget was showing), in this case later than I should’ve, it would’ve been quite worse experience than the pleasant hike I got.

P.S. and don’t forget the watch app and complications. Same issue with the three inadequate global models there.

@Suty Of course my joy, reading this was premature.
I got 44.01.0213, released the other day, and there is no difference in the widgets.
Again available are just the completely useless ECMWF and GFS and the almost completely useless ICON…

@idefix37
But widgets have nothing to do with the maps.
Your answer practically says also that you don’t plan to offer Meteoblue as a default forecast, something that was asked multiple times and promised already!
And to finish it off - be bold and offer us a view without the map.
I myself find it distracting and much prefer to look at the data I want in a tabular manner

@idefix37 You know - that’s the problem with Windy. And the fact that it misses the key measurements like real feel, precipitation probability and sunshine duration.
Someone from the team always comes and explains “how’s in meteorology”!

I had a long discussion here about “real feel” and wet-bulb temp, in which I was explained that I don’t understand meteorology and windy is so precise in providing not (the “unscientific”) real feel, which was not “meteorological” enough, but just wet-bulb - what turned out to be in the end a useless measure for 99.9999% of the users and occasions.

Frankly, I couldn’t care less what’s “in meteorology”. I’m not a meteorologist. I don’t want raw data to spend 15 minutes with, creating my own forecast. I want a single glance to show me before a run at 7am are the 4 degrees outside going to feel bloody freezing for me or pleasant. I risk my health if I get this wrong!
Sunshine duration, real feel and precipitation probability give me that in other apps. Windy, stubbornly - refuses to do that simple thing.

Even the data that it has, it provides it with a horrible UX - always changing the model to an incorrect one (the bloody ECMWF), refusing to provide tables and graphs, only maps, impossible to see several parameters together.
In the end it provides a wealth of data with very little practical use - one because of the bad UX, and second - refusing to calculate parameters for the common folk - not the professional meteorologist.

@idefix37
You literally wrote it :)
Sunshine with cloud coverage of 90% is… surprise, surprise… 10%.
And so on.

This is a very useful tool in the forecast and a great for short glances:
Here is a great implementation in Weather Pro:

By the way - this, real feel, and the precipitation probability - things that Windy stubbornly preaches that we “don’t need”, keep WeatherPro as my go-to weather app.
I’m going to continue its subscription and discontinue Windy once it expires, as Windy is unwilling to improve UX and misses key usability (above).

Just as the iPhone widget, the Apple Watch app shows just the three global models ECMWF, ICON and GFS.
Is that because MBlue, ALADIN and others - the way more accurate ones - are not global (although as per my knowledge MBlue is global)? Is it because they are not 5 days?
What can be the reason for this restriction?
Makes the Apple Watch app (just like the widgets) much less useful, as these global forecasts are just not accurate.

Can we get the option for a selection of any model (even local) and only if that one has no data, fall back to a global?

Currently the Apple Warch app and the widgets are such a wasted opportunity. A local model availability will make them… useful.

@idefix37
I know. But I DO use the widget. It’s supposed to give you reliable information without opening the app - right on the homescreen. Widgets are incredibly useful - if the forecast is correct that is.
I speculate that because the more accurate Aladin and MBlue models don’t have the 5 days forecast usually visible in the widget, they are missing and only longer models are given as options. Yet why and who would make that choice I cannot understand.

@Jamitt same on iPhone

By the way - time now is not 7:45, but 22:45

@Suty yes.
And none of the accurate models for my area is available when I open the app.
Is it because Meteoblue and Aladdin do not cover all 5 days, you’re setting the widget to?
Then just show less.
I very much prefer three days of accurate forecast, than 5 of the only mildly accurate ICON on my widget
Your favourite ECMWF is laughably inaccurate as soon as you put a mountain nearby, so I never, ever use it.