Creating a bug to track this - about 9 hours ago the forecast API used by this integration stopped working. From quickly looking at this I believe it's a MIME type issue, as the forecast API now returns a content type of application/octet-stream instead of application/json; charset=UTF-8. It's unclear if this change is intentional or not, but my guess is that it was done on accident and will be fixed eventually.
Creating a bug to track this - about 9 hours ago the forecast API used by this integration stopped working. From quickly looking at this I believe it's a MIME type issue, as the forecast API now returns a content type of
application/octet-stream
instead ofapplication/json; charset=UTF-8
. It's unclear if this change is intentional or not, but my guess is that it was done on accident and will be fixed eventually.