Weather from Garmin in watchface

Hi,

Is there a problem with the Weather provide by Garmin? Some users are saying that the current temperature is not displyed on the watchface after a Garmin software update.

Top Replies

surfr.dsign over 1 year ago +1

I am having this issue with my watchface, and I cannot reproduce the error on the emulator... But... can you confirm that we have to check that it is a Lang.Number in some fw/dev and Lang.Float in others…

All Replies

jim_m_58 over 1 year ago

Which device do the users have, and are they Android or iOS? It's working for me with Android. I have noticed the weather no longer updates as frequently - It's now every hour or more. I display observationTime along with the other stuff.

jim_m_58 over 1 year ago

Have users check what they see in the native weather widget. Are they seeing any data at all?

Bruno Bragança over 1 year ago

Hi, good day. I had a similar issue report since this update. Apparently Garmin changed the temperature from integer to float (I had 2 user feedbacks saying that my watchface was showing a "huge" number of decimal cases in the temperature field. Maybe there's chance this is related to your error (say if you check if the temperature is of type integer instead of not null, whatever)

Tak79 over 1 year ago in reply to Bruno Bragança

In API i see that temperature from current condition is still Number, not Float

Bruno Bragança over 1 year ago in reply to Tak79

By "API" you mean the reference? If so, you can ignore that, maybe it's not updated yet. I couldn't reproduce the error on my watch because it's a Venu 2 and didn't got any update recently. The report came from a Venu 3, I solved the issue "blindly" by adding the .format("%02d") to the temperature reading because these decimals cases didn't show on the simulator either.

jim_m_58 over 1 year ago in reply to Bruno Bragança

If you are display the temp in F, you'll already be doing something like this, or should be, as the result of a proper conversion will be a float.....

Bruno Bragança over 1 year ago in reply to jim_m_58

Yeah, exactly. I had this .format("%02d") only inside the if(system temp is F), outside (if the system temp is C) I displayed as it came from the watch system, and it displayed as an integer without issues. After the update it became a float and I had to format both cases.

surfr.dsign over 1 year ago

I am having this issue with my watchface, and I cannot reproduce the error on the emulator... But... can you confirm that we have to check that it is a Lang.Number in some fw/dev and Lang.Float in others??? I am also checking if it is Null... BTW...Thanks

Bruno Bragança over 1 year ago in reply to surfr.dsign

Hi, I only check if it's null and trust the return type of the api reference... anyway, do a .format("%02d") and you're safe from displaying a lot of decimal cases

surfr.dsign over 1 year ago in reply to Bruno Bragança

Thank you! I was already formatting the output, but I was cheking null and type... so it ended up displaying nothing... Thanks a lot!