Hello,
recently the observationLocationName returns something like Loca.... and not true location name as before (I only see first 4 letters as I truncate). Has there been any change or new bug? It worked before.
Thanks, Jan
Hello,
recently the observationLocationName returns something like Loca.... and not true location name as before (I only see first 4 letters as I truncate). Has there been any change or new bug? It worked before.
Thanks, Jan
if you mean this function:
Toybox.Weather.getCurrentConditions().observationLocationName
then in a simulator you need to Set Weather -> Observation Location Name
it works fine for me.
Did it stop working after a FW update to your device or an update to GCM on your phone? Make sure both FW and GCM are up to date.
In GCM, under settings>user settings you'll see "weather settings", where you can set a location instead of the phone location. What happens if you change that? (it may take an hour to change what's you see on the watch)
Thank you for advice. I had some more observations. In Google Connect, I tried four different Android systems and on three of them I could not set fixed weather location in Connect settings. After I chose country from pick list it did not propagate to Country line in the form (which has ZIP code below Country name). It only worked on old Android 6 phone.
I have phone without google apps but I it worked before, I use it for long time. It seems to me it stopped working after some Garmin Connect update, I will try to download old APK if it works.
Can you advise how to debug it? Because when I run simulator in Eclipse, it actually shows whatever location I set up in simulator settings. I would need to debug with Google Connect Android application, as it seems to me that weather location name is sent from there.
The localization itself seems to work, weather forecast is in line with other sources for my area.
Do you have their release notes? is this official?
Hello is this weather location that you manually set in emulator settings?
as far as observationLocationName, you really want to use a real device and GCM for testing. It could be an issue with a specific location, If I recall, a while back, Big Ben in the UK was showing a bad observationLocationName for example. Other places worked fine.
So I have reprogrammed my watch face to show whole observationLocationName and instead weather station location as it used to show earlier now it shows Location[ 50****** 14****** ].
Apparently reverse geocoding does not work in Garmin Connect