@Matthew-Moskal
Thank you for quickly adding the screenshots. From this I can conclude that this is a bug. I will try to fix it as soon as possible.

Could I ask you to add your Windy Watch face, if the bug appears there as well? It is possible to add it directly from the Windy Watch app.
All the complications use one data model, so it would help me a lot in debugging.

Thank you.

Hello @Garik-Peter :),
thank you for creating this topic. I am currently responsible for the watchOS application, so I would like to ask a few questions.

What is the most important information you want to see in corner complications or generally in your watch faces?

Why do you want settings in your WatchOS application? Isn't easier to have this setting synchronized with the application in your iPhone (as the widgets for example)?

Thank you for the answers. This topic and your ideas are really important for me.

I have investigated this issue for your location ( Port Augusta, South Australia, Australia) and there was an error in processing the data.
This problem may occur in another location, so I am giving it a high priority.
Thank you again for your report and I apologize for the inconvenience and it will be fixed in the new version.

@Kez77 Thank you for letting us know what helped you. It was probably some kind of system problem. I'm glad to hear that your complications are now working as they should :) .

@bbary
Ahoj, predovšetkým ďakujem za nahlásenie chýb.
Ikona s aktuálnym počasím je podľa príspevku chybová, to opravím do nasledujúcej verzie.
Krivka s počasím je "konštantná" pretože komplikácia ( graf ) nemá dostatok dát na jej zobrazenie. Jedná sa o predpoveď počasia, takže večer sa už "nepredpovedá" na aktuálny deň. Presnejšie predpoveď sa nerobí dozadu. O 20:54 máme najaktuálnejšiu predpoveď z 18:00 ( veľmi približne ), takže predpoveď obsahuje 18:00, 21:00 a pod. ( 1H predpoveď v hodikách pre premium pripravujeme ). Riešením by bolo ten "začiatok" nezobrazovať vôbec. Takto by to dávalo pre vás zmysel?
Nesúlad medzi hodinkami a iOS applikáciou vychádza z toho, že hodinky nepodporujú (zatiaľ) premium, takže ako premium máte v applikácii presnejšiu a aktuálnejšiu predpoveď, ako v hodinkách.
Hodinky maju obmedzený zdroje na obnovu dát ( záleží na množstve batérie, ako často sa komplikácia využíva, pripojenie k iPhonu a sieti a pod.. ), tých faktorov je mnoho, preto sa môže stávať, že počas dňa obnova dát klesá. Je zo žiaľ obmedzenie s ktorým nič nezmôžeme.

Dúfam, že som vám odpovedal asoň z časti a ešte raz ďakujem, za nahlásenie.

Hey @John-Honchariw @Steve-Ryan ,
Thank you for your comments, we have the locations in the pipeline and I would like to ask your opinion before implementation.
First option, is to switch by default the location for the watch ( forecast, radar, complications ...), which I find but limiting.
The second option is to add a location ( either from favorites or new ) in settings and it would be displayed as a new page in the forecast. But for complications, you would have to select the specific site you want to display in the settings.

Which solution do you like more? Alternatively, if you have another idea, let me know.

Hello @PTarkkonen,
I am a responsible developer for watchOS. Firstly thank you for the bug report. I know about this issue, and it is tough to simulate it. That is a reason why it is still not fixed yet. I have added special logs to catch this error. So, I hope it will be fixed in future versions.

I would lite to ask why it is necessary to reinstall the application? I think just force quit the Windy application and start again should be enough. Can you confirm this, if it couse again?

Thank you again for the bug report :)

@Paw-2
Please try restarting your iPhone and reinstall Windy. Sometimes it happens that iOS does not load new widgets right away, it has to index them first (this also happens with classic widgets).

May I ask if you see the satellite widgets in the iOS widgets gallery?

@tkingham @Obroey Can you please check if the Windy widget is working properly on your device? There may be a similar problem so I can fix both.
Thank you.

Hello @rabard ,
You have set the zoom to 240% in your browser. Change it to 100%. It should fix your problem.

Hello @gdtrfb ,

I hope this message finds you well. As was previously mentioned by @Ondřej-Šutera , I have been occupied with the recent developments surrounding Apple's restrictions, which have rightfully taken precedence in my priorities. However, I wish to assure you that I have not overlooked the matter of implementing locations in widgets.

In contemplating this issue, I have given considerable thought to the approach we should take. One option is to adopt a similar approach as with the old complications, where the default location was chosen due to technical constraints. Nevertheless, I am inclined to explore alternative avenues for widgets. While it would be simpler to follow the default location approach, I believe it may not be the most accurate course of action. Therefore, I have chosen the more intricate path, one that will enable widgets to support all user-defined locations on their respective watches.

I must emphasize that this decision will necessitate more extensive modifications within the application. It will undoubtedly pose challenges and consume more time, but I firmly believe it to be the most correct and comprehensive approach.

Thank you for your understanding and patience as we work towards enhancing the functionality of our widgets.

Hello @carpediemi24 ,
Thank you for reporting the bug. Widgets since watchOS 10 have completely new refresh logic and it is possible that there was a problem with the primary location. I've tried it now on my AW and it also shows me a different current location. I'll try to fix it for the next version.

Hello @seeyou186,
According to your screenshots it seriously looks like a bug. I'll take a closer look. Please let me know what version of the app it is, because in the last update the watch widgets have changed completely ( under the hood )

Hi @Tony-Norris ,
Thank you for the report, this problem also occurred on my iPad ( iPhone is fine ), so I will be able to fix it. I'll keep you posted on the fix, or ask you for more information.

Thanks for the report, there really was a problem in the small lock screen widget and it was fixed. I haven't found a problem with the premium widget yet, but I'll look into it again and let you know.

Hello @Brancis ,
In the last version I modified the switching of 1H and 3H predictions so that it is switched only in 2 cases, namely

1. The user logs out of the iPhone app
2. The user's premium expires.

Previously there was one more option that if I have a non-valid token, it switches, but I have cancelled that. This way it can happen that he has 1H prediction ticked and it shows him 3H, but the build should be quite minimal and it should fix itself. It can happen when you don't turn on either the watch or the iPhone App for a long time, and you have a background task on the watch that refreshes that token blocked by the system.

Please email me, in what situation, does the forecast switch and I will take a look at it again

Hello @Brancis ,
In the last update, I modified the logic regarding 1H settings, the app should no longer switch back to 3H forecast.
If this is still happening, please let me know in what situation it occurs and I will look at it again.
At the moment it changes the 1H forecast to 3H in the following situations:

• The user has logged out of Windy
• User has run out of premium

I have prevented a situation where the validation token has expired, which could just be causing the behavior described ( settings will remain unchanged, but the forecast will be non-premium ). This situation should occur minimally ( when the apple watch or iPhone app hasn't been running for more than 3 days ) and the user has no complication on the watchface and the system won't allow a background update. As soon as it is restarted premium will be restored.

Hi @papauster ,
Which type of widget do you use? Would it be possible to do a short screenrecording and send it to us? It would help us a lot.

Hi @uchidakoichi ,
I am investigating this bug and unfortunately on my iPad it works properly ( and also on iPhone ). Could I ask you for more information? What system version do you have and what version of Windy do you have installed ( you can find this in the menu at the bottom ). This bug hasn't happened to us yet, it could be caused by a number of things. Thank you.

Hello @Brancis,
Thank you for reporting this issue. You are not the only one facing this issue, so I will find out what causes this issue and hopefully fix it in the next version.
I will inform you of the progress.