Weather is broken due to Yahoo weather API changes
PeterSumm opened this issue · 28 comments
I loved this for about a week, but then Yahoo changed their API and it died. Before I jump into the code to try to fix it, is anyone working on this?
I can confirm this is working on Versa.
I'm not able to fetch weather data again on my versa. Did the API change again?
Weather data is working for me.
The date still doesn't update at midnight but I can't see why.
OK, thanks. Let me know if I can help with testing. I'm in the +11:00 time zone, so if that's different from you then we may be able to test it twice a day between us.
Any luck?
OK, thanks. I'll watch out for the new code release.
What was the problem? Your code looked right to me.
BTW, I've rewritten my big font code so that it's an option in the settings, so that it works for both Versa and Ionic and so that I can reintegrate it with new releases easily. If you'd like to look at it, please let me know.
Cheers,
Peter
This seems to work on the Ionic, but on the Versa it gives the message:
[11:56:41 AM]Unhandled TypeError: Expected a function.
tempAndConditionLabel at app/index.js:329,7
drawError at app/index.js:301,1
messaging at common/weather/device.js:124,1
? at app/index.js:1133,1
fetchWeather at app/index.js:1227,1
and the weather icon and text are missing.
I can't see why and I've tried copying text between the relevant files and it hasn't helped.
I've spent an hour or so on this and the suddenly I couldn't reproduce the problem any more, even after reloading your code that had previously failed. I'll try it again later.
Most odd - the only thing I can think of that might have changed is the actual weather conditions and so the data that's being returned. Or it could be some ugly bug in Javascript.
BTW, is there a reason that you're using SDK 1?
I can get the message
[5:01:21 PM]Unhandled TypeError: Expected a function.
? at app/index.js:1133,1
fetchWeather at app/index.js:241,1
and the weather icon doesn't show although it displays a temperature, condition and location. I can't see why, but I'll keep looking.
This looks to me like some random location in memory is being corrupted. Can Javascript do that?
I'm not sure.
I find the fact that problems mysteriously come and go when we add or remove perfectly good code really troubling. But I've not a better suggestions, so yes, go for it.
Interestingly, the problem is also apparent in my version with the big font option added.
Does this help at all?