openweather plugin ?

[CatmanV2]

@akbooer this looks great. Despite searching I can't find something as simple as a lookup for my nearest station ID.
Any suggestions?

TIA

C

[akbooer]

@CatmanV2

You’re speaking about Datapoint?

Some documentation for location here…

DataPoint API reference

A consolidated guide to using the DataPoint API and products

[CatmanV2]

@akbooer Thanks, I rather assumed that a list like that would be available without actually having to jump through

C

[akbooer]

Yes, I was surprised. It turns out that there’s far fewer stations which record hourly data, which is what you need. I can’t remember now how I found the one I use, I’m not in front of my development system at this time.

The device panel on openLuup should give a nice brief text summary of current conditions.

[CatmanV2]

Yes. Struggling to find one that's close. They seem to fail silently and I can't see much in the details to indicate which ones might work

I'll crack on. Thanks for the pointer

C

[akbooer]

@CatmanV2

Did you find what you needed in the end?

This query: (along with your API key)

datapoint.metoffice.gov.uk/public/data/val/wxobs/all/T/sitelist?key=...

Gives the relatively short list of stations (140 or so, IIRC) with hourly data, from which it's easy to pick the nearest.

I should build this link directly into the app...

[CatmanV2]

Ooooh thanks!

C

[akbooer]

Just found this too...

Synoptic and climate stations

Their site is not easy to navigate!

[a-lurker]

OpenWeatherMap's API changes: Some time back OpenWeatherMap decided to change their API billing practices. The old "One Call API" arrangements (1,000 API calls per day free) have now ended.

You now have to provide your credit card details, so if you exceed the free 1,000 API calls per day you can be charged. The provided API keys don't work unless you provide these details. Returned error message:

{
  "cod": 401,
  "message": "Invalid API key. Please see https://openweathermap.org/faq#error401 for more info."
}

However, if you just want current weather with no forecasts, you can use the "weather" call:

https://api.openweathermap.org/data/2.5/weather?lat=%s&lon=%s&units=%s&lang=%s&appid=%s

It's possible the Multi Station Weather plugin could be modified to fall back to this call, if it fails on the first call. As suggested here.

In my case, I've hacked the MultiStationWeather plugin code to use the "weather" URL at all times, as I don't use forecasts.

[mrFarmer]

Hi, it is on my to-do list to make the change. Might be this week, no promises.

[therealdb]

I’ve transitioned to https://open-meteo.com/.
It’s free and it have been reliable for me in the latest 5 months.

[mrFarmer]

Hi, I have updated the plugin code. You will have to install it manually as the MIOS App Market nor the ALTUI App Store are working. Get the file from github at https://github.com/reneboer/MultiStationWeather/blob/main/src/L_MsWeather.lua

Note that you will need to get a One Call 3.0 API key. The old one will not work.

Cheers Rene

[akbooer]

@mrFarmer said in openweather plugin ?:

Hi, I have updated the plugin code. You will have to install it manually as the MIOS App Market nor the ALTUI App Store are working. Get the file from github at https://github.com/reneboer/MultiStationWeather/blob/main/src/L_MsWeather.lua

I can put that in the AltAppStore for you.

AK

[akbooer]

Done (for AltAppStore only!) ...

...it might take up to a day for openLuup to show the change (or just reload openLuup if in a hurry.)

Is it the web interface that's not working for updates? I changed the database directly.

[mrFarmer]

Thanks Ak, the Google token refresh does not work unless you run AltUI on a Vera and I do not have those up and running anymore. We did find that before. The token refresh gets stuck in some loop and a luup reload is needed to stop that. It is too deep in ALTUI and some google scripts for me to figure out and @amg0 does not seem to be around any more.

I am on openLuup 23.01.06. When not using MTTQ, Shelly, Zwave stick, any reason for an update to the latest?

Cheers Rene

[akbooer]

Yes, this problem was fixed when it first arose for openLuup, which now takes its App Store information via GitHub, if you use the console App Store page, and not AltUI’s.

In fact, openLuup is now totally independent of AltUI, which I don’t even have installed on my production system.

GitHub’s mirror of the Google database happens via a separate process, hence the delay in updating sometimes.

[akbooer]

@mrFarmer said in openweather plugin ?:

I am on openLuup 23.01.06. When not using MTTQ, Shelly, Zwave stick, any reason for an update to the latest?

To answer the above, most of the changes since then have , indeed, been with MQTT (which now fully supports both * and + wildcards) and Shelly Gen 2+ devices.

It also includes native scene creation, which was the only remaining functionality from AltUI that I needed to replace.

[mrFarmer]

I might update then. I do need ALTUI still because of some of my plugins. Slowly moving to HA, but not totally there yet.

To update a plugin now, How would that work if not via the ALTUI publish function?

[akbooer]

@mrFarmer

I've just tried AltUI on my development system running openLuup, and access to the AltAppStore appears to work just fine.

When hitting the Publish button, I had to go through some authentication step that I've never seen before, but ended up with this from Google:

Screenshot 2024-08-12 at 15.01.53

then went back to AltUI to see this page:

...so all seems good to me.

[mrFarmer]

Hi Ak,
Not sure what the issue is for me then. I first had it running on Pi3 with Debian, now on Pi4 with Ubuntu, same issue of not getting the token. I did copy the user_data.json, so maybe something in that.
As a test I tried on my openLuup clean test install running in a container and that is working. So must be something at my end.
Thanks again anyway, I have a new workaround :-).