this just started happening today. If I remove the forecast library and contact forecast.io directly, I get the correct data back.