Apple Watch “Windy Wind” Complication
The “Windy Wind” complication that displays a directional arrow along with a wind speed is not updating with my current location. It appears to be stuck at 5mph with the arrow facing WSW, which is what is displayed in the example for the setting.
Also, I updated my unit setting on the phone and have the iCloud setting set to sync the watch unit setting with the phone, but it will not update.
SimonUrbanek last edited by
Hello @Matthew-Moskal ,
Please could you post a screenshot of what the watch app shows in Forecast and then what complication? Is the location in Forecast ok?
@simonurbanek yes, the location in Forecast is correct. See attached photos.
SimonUrbanek last edited by SimonUrbanek
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.
@simonurbanek the Windy watch face appears to show the correct wind speed and direction (tough to tell, but the arrow is pointing in the correct direction.) Also, the forecast in the bottom left took a few mins to update to the proper forecast. See both photos, cloudy and 50 degF was incorrect. Sunny and 73 degF is correct.
Once the bug is fixed, will I notice it working right away or will it start working after the next app update?
@simonurbanek it appears that the complication on the Apple Watch face now updates properly. Maybe adding the Windy watch face forced it to refresh? If so, still not ideal, but hopefully that helps you troubleshoot further.
SimonUrbanek last edited by
Thank you very much for your help, this will make fixing the bug much easier for me.
The refresh one is a bit more complicated with the watch. Our forecast data is downloaded on the backend and the watch manages it itself ( when they have the resources, iPhone has good connectivity, time of day, etc). So it's hard to predict their refresh. When the data is downloaded, the backgroud thread will ask the system to refresh complications.
From my observation, the watch refreshes all complications in the morning ( the system has a prediction of when the user gets up ) so that when you put on the watch you have actual information. Then the refresh depends on what watchface you are currently using and gives priority to that.
I'm not sure if I'll push this through to the next release as it's already ready in the testing phase, but I'll look at it today and do my best.
Thanks again for your time and I'll let you know when it's fixed.
@simonurbanek excellent, thank you!