Is it normal for model to default to ECMWF every time?
-
This is a topic that has been discussed many times but I've been away for a bit so I don't know if it's me or the app has changed again.
I use the Android widget. I use HRDPS as the model in the widget. But when I open the app (from the widget) it goes back to ECMWF and I have to change it. This is my only real complaint about the app.
I thought this had been "fixed" a long time ago ie so that the model didn't switch from what was set in the widget...but now I'm not sure.
Anyone care to set me straight?
Kevin
-
@hulakai Hello, I tested the behavior in our production app which is now available in Google Play. I created a widget with Ottawa as a location and selected HRDPS as model, than I opened Windy with this widget and it showed me the detail of Ottawa and provided HRDPS forecast data.
May I ask what version of WIndy you have installed?
-
@Suty It isn't working on mine either.
Samsung Galaxy S23 FE
Android v15
Wind v47.1.4I've checked, GFS, ICON, NAM, HRDPS, HRRR
I tried each one multiple times and made sure Windy was closed before trying but it always seems to open with ECMWF as the model.
I really hope you folks are working on the ability to allow users to just identify which model they want it to open with...
-
@Wheats Thank you for sharing this info with us. I will check this behavior on more devices to replicate it.
-
Yes, it’s a known issue — the app often defaults back to ECMWF when launched from the widget. It happens because the widget and app use separate model preference states. Try re-saving HRDPS as your default under ‘Settings → Forecast Model’ and then recreate the widget. If it still resets, it’s a bug in the latest update — developers are aware and working on a fix.
-
@Suty no worries.
It worked today. I have HRRR on the widget, opened using the widget and it opened with HRRR.
Strange intermittent behaviour... -
@Wheats Is it possible that you received the update to our latest version already? Can you please check it?
-
I have the same problem and have always wondered why I can't preset my preferred weather model. It's not in the settings. Every time I open the app, ECMWF is displayed. My location: Hamburg, my preference: ICON D2.
-
@Suty This morning when I opened it using the widget (Windy Detail Widget), with HRRR showing on the widget, it opened with the ECMWF model, not the HRRR.
Samsung Galaxy S23 FE
Android v15
Wind v47.1.4Same version as before so I didn't get an update yet.
I do want to take this time to reiterate how amazingly useful it would be to allow users to select what model they want to see on startup. Please work on this.
-
@Wheats Could you please update Windy to the latest version? It should be v.47.2 and it should be already out for all users.
-
@Suty
This morning I opened using the widget set to HRRR - the app opened with HRRR.
Still running v47.1.4 and manually (it's set to auto-update Windy) checked the play store and there are no updates available.
It says Windy last updated on October 29, 2025.
I have restarted the device and no change to available updates. -
@Wheats Hi, can you please check it once again? We have progressive release, so it usually takes about one week to fully release the new version.
-
@Suty
This morning I tried to open via app, and there was "no data" on any of the layers.
I've rebooted my phone, have HRRR set on the widget, opened via the widget and it opened with HRRR, but there's still no data on layers. When I zoomed way out from my starting location, the layer data appeared. It shows I'm running v47.2.1 now.My mobile shows this one error in the error console.
If you need the stuff I blacked out, please let me know.
-
@Wheats Okay, unfortunately, this message is not related to the issue, you mentioned. Does it happen with every new start of the app?
-
@Suty That is unfortunate haha.
This morning I opened the widget, set to HRRR, and Windy opened with HRRR.
I saw the error message again.
I deleted messages, closed everything, restarted phone, opened via app (it opened with HRRR again) and the same error is in fact present.So I'd say yes, it happens with every new start of the app.
