openmeteo & openweathermap "API Error" after Upgrade to v7.0

[x86txt]

Description

I upgraded from v6 to v7 and now my openmeteo weather widget reports API error. Upon page load or refresh, it will have on "Updating" and eventually go to API Error. The only thing I see in 'docker logs' is tons of errors like this:

[2023-10-03T10:30:20.746Z] error: undefined [2023-10-03T10:30:40.808Z] error: undefined [2023-10-03T10:31:20.865Z] error: undefined [2023-10-03T10:31:33.765Z] error: undefined [2023-10-03T10:32:16.313Z] error: undefined [2023-10-03T10:33:30.974Z] error: undefined [2023-10-03T10:34:44.299Z] error: undefined [2023-10-03T10:35:32.875Z] error: undefined [2023-10-03T10:35:36.339Z] error: undefined

Screenshot of behavior:

config in widget.yaml:

• openmeteo:
  label: Home
  latitude: 35.22658
  longitude: -80.85283
  timezone: America/New_York # optional
  units: imperial
  cache: 5

I tried to switch to openweathermap (with a register API key) and it fails as well. The container is able to contact external sites, which is verified by opening a /bin/sh shell to the container and performing a wget to https://www.google.com and to the oneweb API ('https://api.openweathermap.org/data/3.0/onecall?lat=33.44&lon=-94.04&exclude=hourly,daily&appid=MyApiKey'), all of which are successful.

Steps to reproduce

1. edit widget.yaml
2. input openmeteo code or openweatherapi code above
3. see api error?

homepage version

v0.7.0 (c18caf9, Sep 29, 2023)

Installation method

Docker

Configuration

- openmeteo:
    label: Home
    latitude: 35.0074
    longitude: -80.9451
    timezone: America/New_York # optional
    units: imperial
    cache: 5

This is in widgets.yaml.

Container Logs

maybe these?

[2023-10-03T10:30:20.746Z] error: undefined
[2023-10-03T10:30:40.808Z] error: undefined
[2023-10-03T10:31:20.865Z] error: undefined
[2023-10-03T10:31:33.765Z] error: undefined
[2023-10-03T10:32:16.313Z] error: undefined
[2023-10-03T10:33:30.974Z] error: undefined
[2023-10-03T10:34:44.299Z] error: undefined
[2023-10-03T10:35:32.875Z] error: undefined
[2023-10-03T10:35:36.339Z] error: undefined

Browser Logs

No response

Troubleshooting

I have other widgets in this file working fine, it's only the openmeteo and openweathermap widgets that do not work.

Other

No response

Before submitting, I have made sure to

• Check the documentation
• Follow the troubleshooting guide (please include output above if applicable).
• Search existing issues and discussions.

[x86txt]

Update: openweathermap is now working, apparently you have to wait a bit for the API keys to activate. OpenMeteo is still failing.

[netstx]

@x86txt I can confirm that using a newly API Key on OpenWeatherMap will cause this issue. For testing, I switched to a key that had already been created for a long time and it worked right away.

[shamoon]

I dont think they're broken as they are used by a huge percentage of homepage users and there have been no reports of this (nor can I reproduce). Just to check, try re-creating your container. Otherwise you can easily see what data is being returned by looking at the call like /api/widgets/openmeteo?latitude=... in your browser tools under the network tab.

[x86txt]

I've recreated the container several times. This started failing as soon as I upgraded to v7, it happens both in k8s and regular docker. (I pulled it out of k8s and into docker to make troubleshooting easier.)

Note, openweather is now working, apparently you have to wait for the API keys to activate. So, it's just openmeteo.

I'll check what the browser call shows and report back. Hopefully it is something unique to my environment.

[x86txt]

Okay, progress - Openmeteo is throwing an HTTP 500 error. I've tried several browsers, my mobile phone, on my home network and off (at work) plus my cellular provider. All throw a 500 error.

Eh, a 500 error is server-side, so I'm not going to bother tracking it any further since openweather is working fine.

Thanks for the help and the AWESOME software. This is one of my favorite tools.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.