This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

weather forecast has wrong zip code. How do I change it?

Former Member
Former Member

weather forecast has wrong zip code... were is this info being taken from?  How do I change it?

  • Hello! If you are referring to the weather widget on the device. The Garmin Connect app pulls from the location settings of the phone. If the weather is pulling from the wrong zip code you would need to look at your phone location settings.

  • Former Member
    0 Former Member over 4 years ago in reply to Garmin-AmberD

    Hello Amber, Thank you for replying... actually I was referring the calendar item that shows up when I scroll down from the clock. it shows me a "forecast" for today and tomorrow for an old zip code I used to live in.  My Garmin Connect is setup with my current address/zip. Sorry if I am asking a "rookie question",  I just purchased this to replace my Fitbit that I was NOT happy with the HR  and sleep data.

  • Post a picture of where you see zip code.  You won't see this on the Garmin weather widget.  Are you running a CIQ watch face that uses zip code by any chance?

  • Former Member
    0 Former Member over 4 years ago in reply to jim_m_58

    Hi Jim, thanks for replying to my query.  My weather widget shows proper weather forecast for where I live... it looks like a calendar display of daily appointments that shows a "forecast for 32169" which is my old address of two years ago. I cannot find anywhere how to remedy or remove it! My Google account has my current address as my "home".  I am not sure what a CIQ watch face is... I am using one of the ones that comes with Garmin versus a 3rd party one. Thanks for looking into this.

  • Do you maybe have a Samsung phone with it's own calendar app. I had a similar issue with my last watch (Galaxy watch) and it was because the watch was displaying the Samsung calendar instead of the Google calendar - and the Samsung calendar had the wrong location.