METNO Update Failed due to HTTP 403 (not 404)
Hello,
The RainMachine MET.NO is no longer able to retrieve weather data.
On the RainMachine Web application, I have this error:
Retrying: URL open fail
And, in LOG files, I have these errors:
2020-11-29 15:59:13,006 - ERROR - rmParser:136 - *** Error in parser 'METNO Parser' while downloading data from https://api.met.no/weatherapi/locationforecast/2.0/classic?lat=48.8872692&lon=2.5213365&altitude=60, error: HTTP Error 403: Forbidden 2020-11-29 15:59:13,023 - WARNING - rmParserManager:181 - * Parser METNO Parser returned no values
Is it possible to have a solution in order to resolve the problem?
Thanks,
Arnaud
-
Hi, Arnaud
Yes, thank you for reporting it.
It is a known issue and we have an workaround for it already.
You can add the fixed METNO weather service by yourself following these steps:
https://support.rainmachine.com/hc/en-us/community/posts/360049587394-MET-NO-weather-service-fix-is-available
It is also available as fix into our latest BETA firmware update.
Thank you for your understanding, Arnaud
Julian
RainMachine Support -
I think this is a new bug. I am seeing the same 403 error when my RainMachine attempts to retrieve data. But if I enter the URL from the log file in Chrome I get back an XML response with the data.
This was working after the Fall 2020 update. It stopped working sometime after that.
-
The manual fix in the message you linked to includes the statement "Update: With Fall 2020 Firmware Update this is no longer necessary". I installed the Fall 2020 update and MET.NO started working again. It then stopped working again sometime later (I'm not sure when since I don't check it every day during the winter).
If it is still broken you should remove the statement that it is fixed in the Fall 2020 update. That is part of what made me believe that it is a new bug.
The original bug (the MET.NO API change) returned 404 errors. It is now returning 403 errors. Again, that different behavior made me think it is a new bug.
Please sign in to leave a comment.
Comments
5 comments