If OWM city data changes: results in "There is something wrong with your Internet connection"

[troyengel]

At some point in the past when setting up Forecastie, I had my city - San Antonio, TX, USA - configured. A little while ago (not sure how long, I wasn't actively paying attention - maybe 2 months?) it appears OpenWeatherMap changed their metadata to simply "San Antonio, US" now that I've debugged it. There are now 5 results, Forecastie just picked the first one it seems (good thing that's what I needed!): https://openweathermap.org/find?q=san+antonio%2C+us

When refreshing data, I would just get the erroneous error about my internet connection - when in fact I'm sure it's just a bad API call return value for what the previous setting was - I didn't think to save the name, but I'm guessing it was "San Antonio, TX" or whatnot. Or maybe the city code changed? I had wiped out all my data and reconfigured it and through trial and error discovered the problem. Now that I test it, if I simply type "San Antonio, TX" into the search box the internet connection error appears incorrectly, instead of telling me "not found" or similar. https://openweathermap.org/find?q=san+antonio%2C+tx

Can we get (a) a better debug log, and (b) a better error message when there's an API return failure that helps more? It wasn't obvious at all what was wrong, better app output could have saved me a lot of time. Re-searching for my city was something I never thought to try...

[robinpaulson]

Some of this will be fixed with #315 , the remainder by #316 . Closing