Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Met Eireann weather integration using deprecated URL, which is now broken #131223

Closed
gdude2002 opened this issue Nov 21, 2024 · 8 comments · Fixed by #131860
Closed

Met Eireann weather integration using deprecated URL, which is now broken #131223

gdude2002 opened this issue Nov 21, 2024 · 8 comments · Fixed by #131860

Comments

@gdude2002
Copy link

The problem

As of this afternoon, the Met Eireann integration fails to pull any data. This is because the URL it's polling times out: http://metwdb-openaccess.ichec.ie/metno-wdb2ts/locationforecast?lat=<SNIP>;long=<SNIP>;alt=<SNIP>;from=2024-11-21T19:00

According to the Irish Government website:

Announcement: The upgrade of the api will result in termination of the old 'metwdb-openaccess.ichec.ie' URL by 15th September. This is replaced with 'openaccess.pf.api.met.ie'.

URLs of the form:
http://metwdb-openaccess.ichec.ie/metno-wdb2ts/locationforecast
should be replaced with
http://openaccess.pf.api.met.ie/metno-wdb2ts/locationforecast

Disclaimer This API services and data offering is scheduled for upgrade starting Q1 2024. Every effort will be made to maintain data access during the upgrade period, and services/data will be provided on a best effort basis.

Seems we may be a little behind with this one! Any chance of a quick fix?

Thanks!

What version of Home Assistant Core has the issue?

core-2024.11.2

What was the last working version of Home Assistant Core?

core-2024.11.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Met Eireann

Link to integration documentation on our website

https://www.home-assistant.io/integrations/met_eireann

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-11-21 21:21:33.696 ERROR (MainThread) [meteireann] http://metwdb-openaccess.ichec.ie/metno-wdb2ts/locationforecast?lat=[SNIP];long=[SNIP];alt=[SNIP];from=2024-11-21T19:00 returned

Additional information

No response

@home-assistant
Copy link

Hey there @DylanGore, mind taking a look at this issue as it has been labeled with an integration (met_eireann) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of met_eireann can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign met_eireann Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


met_eireann documentation
met_eireann source
(message by IssueLinks)

@crowbarz
Copy link

A hack that got the integration running again for me is to override the DNS entry for the old site metwdb-openaccess.ichec.ie with the IP address of openaccess.pf.api.met.ie (== CNAME az.openaccess.pf.api.met.ie == 137.116.252.12)

There are a few ways to do this. I have added this DNS override to my internet router, how to do that is completely router dependent. If your HA instance resolves DNS through pi-hole, then you might be able to add the override in Local DNS > DNS Records. It might also be possible to add an override (ie. 137.116.252.12 openaccess.pf.api.met.ie) in /etc/hosts within the homeassistant container, though I have not tried this, and this change may be overwritten on each HA restart.

Note that this hack depends on the web server of the new site not looking at the site name in the request URL. If they fix this to serve only requests to openaccess.pf.api.met.ie, then this hack will stop working.

@gdude2002
Copy link
Author

You haven't noticed any loss of functionality with this approach? If that's the case, maybe we should just PR the change, I imagine it's a one-liner

@crowbarz
Copy link

It got my temperature and humidity back :) I have not tested this extensively in the ~20 mins since I made the change.

The PR for the URL change will need to be submitted against https://github.com/DylanGore/PyMetEireann . However, note that the owner has not submitted anything to GitHub since 8-Aug-2023, over a year ago. Only after that package has been updated and re-released can the HA integration be updated to pull the new version of the package.

@gdude2002
Copy link
Author

I noticed that as well, but the author has been active on LinkedIn, so I remain hopeful! Maybe it'd be worth bugging them there? It does seem like that repo is basically unmaintained.

@crowbarz
Copy link

PR DylanGore/PyMetEireann#8 submitted

@gdude2002
Copy link
Author

I've been trying to figure out a way to contact the guy - it looks like he's made himself quite difficult to contact, unfortunately.

  • Dev.to - seems abandoned
  • LinkedIn - wants me to pay an eye-watering 120 euro/month to send messages to people I don't know
  • Twitter - private account

His website does contain an email address, which I'll try contacting shortly and get back to you.

DylanGore pushed a commit to DylanGore/PyMetEireann that referenced this issue Nov 23, 2024
@CaptInsano
Copy link

@crowbarz @gdude2002

Will this fix to the DylanGore/PyMetEireann repo be merged automatically into Home Assistant or is a pull request needed?

Thanks for flagging and helping fix the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants