Seems like I have found the answer myself. Windy had, again, changed the API Key and further, even after I started to use the new API key, the station data were screwed up at Windy, so I had to add a new Station 1 with same parameters, change my script to specify station 1 in the URL and NOW it seems to work again.

https://www.windy.com/station/pws-1f071b2f3?55.944,12.337,8

@marekd I have a suggestion for the My Stations page. As shown here, there is free space right to the Status column. Maybe you could insert a "Last updated" column and show, for each station, the timestamp of the latest valid data you have received from the station, fx 26-01-2026 17:05:24.

In that way station owner can quickly see if data is very delayed etc.

@SY-GRACE I have no experience into updating my PWS using the new API v2, but I am sending regular data. What if you ONLY include the lat / lon fields in the json and omits all the other? Then you have thin and simple call to update the position. And I assume your plugin can save the previous reported position and if it has not changed significant the simply omit the position update at all? Just a way I would look at it. :-)

Yes, I agree now. But they have been missing for a period. There was a very sharp edge at the right side of my red circle. It was a vertical line of 200 km or so. I will keep an eye on it next time we have a "rain carpet" covering that whole area.

@Remini-2 I had the same issue. I had to get my CWOP (MADIS) number deleted to get the problem fixed. Now my PWS data are updated every 5 minutes. I have checked my log. Less than a few seconds after my little .NET program has sent the data to Windy API it is visible on the map. Fantastic... :-)

@Suty Okay. Just wanted to point out there is a minor problem.

I have checked OpenStreetMap. Actually it is correct, meaning the station, placed in Paradise Residence, is within the area of Hurma as you can see from the arrow. So why does Windy show it as being in the neighbor area?

@Oleksandr-Honcharov Hi Oleksandr and Suty. Thanks for you fast response. I will now switch back to Pascal pressure unit and include my own timestamp (data from WeatherLink are a few minutes old). I am eager to see how it presents. :-)

I will write you here again if I run into other issues. Have a great day.

BR,
Roland from Denmark

@Oleksandr-Honcharov Hi again. I have to tell you that I still don't see my stations on the public website. I am including two screen dumps. First is the overview of my stations. All say "Offline". Yesterday, with the old profiles and before I changed to API v2, they all said "Online".

Next is that I look in Windy at my home location for stations. I sort on distance. Normally I see "Hillerød Vejr" with a distance of "0 km". But as you can see it is not shown in the overview.

So what can I do now or do you still have things to fix at the server side? :-)

Overview of My Stations on https://stations.windy.com when I am logged in:

My station at home is not shown in the local area. WMO 06188 is the official station from Danish Meteological Institute (DMI).

@Oleksandr-Honcharov Hi Oleksandr. I have done another test. I tried with a direct URL like this:

https://www.windy.com/station/pws-YZjgOxm

that returned the image you can see below. So it shows that data IS coming to Windy, just as you said. We can also see the missing data from the night, which is not so important. But right now status in My Stations is offline and search for the station is missing. I will now let it stay like this for some time. Let us see what happens over the weekend.

Will solar radiation and air quaility values show up later fx. when the "buffer" on Windy is exceeded? Right now I only see UV in the left side. I want to understand how solar radiation and PM values are presented. :-)

@WeatherMan10 The total data (using API v1) goes back as far as possible. The we had a "drop out" for one night when I created the API v2 version.

Very strange, but I just checked again. Since my report som hours ago something has changed. Now it shows the right number of minutes, but the information in the About box is a bit strange (yellow).

It is the same for all 3 stations now - a few minutes in the "ago field" and NaNm in the reporting time fields...

@SY-GRACE I have no experience into updating my PWS using the new API v2, but I am sending regular data. What if you ONLY include the lat / lon fields in the json and omits all the other? Then you have thin and simple call to update the position. And I assume your plugin can save the previous reported position and if it has not changed significant the simply omit the position update at all? Just a way I would look at it. :-)

@marekd Good answer. I saw it when I started on API v2 but did not give it much attention. :-)

@marekd Thanks for your nice comments and feedback.

Yesterday I decided to delete my old stations that reported under API v2 and create new stations. I was surprised that my old station ids were reused and now, because I created them in a new order, the ids were mixed so fx. Paradise Residence got the old Helligsø Drag id. That was not so good as I really wanted to get rid of them including their old data. Then I created a total of 6 ids - the 3 old + 3 new and that gave me complete new ids for my stations. Now there is only left to ask you to 100% remove my old ids and their data from your system. The ids we talk about are these:

It has been a pleasure to help improve Windy. :-)

Maybe you can write in the documentation not only about parameter names and what values you expect but also how they are used later on in app and website. Fx. I expected solar radiation to be shown on the website (and in the app) but as I understand you dont use it. So in my mind "why should I send it to you if you dont use it?".

@marekd I have a suggestion for the My Stations page. As shown here, there is free space right to the Status column. Maybe you could insert a "Last updated" column and show, for each station, the timestamp of the latest valid data you have received from the station, fx 26-01-2026 17:05:24.

In that way station owner can quickly see if data is very delayed etc.

@marekd The only reason I am sending the ts value is that I read data from Davis WeatherLink cloud API and I dont know how old they are. My WeatherLink devices (I have one on each location) reports to WeatherLink cloud and from that I get "the current values". If they have some delay, these values could theorecially be very old. So I decided it is best I tell you the timestamp of the data and thereby "how old is the milk". ;-) If you want I can remove the ts-parameter. But my log shows that data is normally 45-60 seconds old when I report it to you and that is good, right? Yes, to ts - it is Unix seconds (not milliseconds) since 1970, so just one long integer value.

I see all my 3 stations (the new Hillerød Vejr and the two others) are online again. I agree with you that a 1-2-3 hours without data should say "offline", but several days is all too long.

I can also confirm that my station with the NEW ID is showing again since 9:55 this morning, so it is fine now.

If you dont want the ts parameter I will recommend you remove it from API documentation to avoid confusion about it. Until further I will let it stay in the URL. Let us see what happens.

@marekd The list of problems since I switched to API v2 is "endless".

Now I get another problem this morning. I am reporting as I have done for a week or more now. Suddenly your server rejecs my ts-timestamp as being in the future as seen here:

2026-01-26 09:31:08 : Windy URL: https://stations.windy.com/api/v2/observation/update?id=EWtLHK4&ts=1769416250&temp=15.7&dewpoint=13.3&humidity=86&wind=3.9&gust=8.9&winddir=138&pressure=101497&precip=0.0&uv=1.0&solarradiation=299&softwaretype=WLL2Windy_3.0.2.406
2026-01-26 09:31:08 : Windy Error: BadRequest - {"message":["ts must not be in the future"],"error":"Bad Request","statusCode":400}

We can see that reporting time is 2026-01-26 09:31:08 and the ts-value is 1769416250. I have decoded this value and it is this timestamp: 2026-01-26 09:30:50. That is NOT in the future.

Where are we now? I see my 3 stations as offline, my reported data does not show up on windy.com and now I also get ts-errors. Finally a new station I created 2-3 days ago also shows offline. Should I stop reporting or switch back to API v1 until all problems have been fixed? I am ready to help you if you want.

@Oleksandr-Honcharov @marekd Hi guys, I think we are back to the original problem. The reason I think this is that all my stations stopped reporting to Windy on 22nd at 10:46 CET. They went offline, later online, and now offline again. I have created a NEW station (using the Hillerød Vejr to report data) and it never shows up on Windy.com. It shows exactly the same error page that I saw first time I started to use API v2.

https://www.windy.com/station/pws-VtofQu2

It is a strange window at the bottom of www.windy.com. I have even tried to run the above URL in MS Edge in a in-private window where I am not logged into Windy.com. It looks like two windows are on top of each other. Notice the small "close" button at the left, the text "Loading observation data..." and that some other window is shown behind this.

I hopw you can take a look at it soon. I would love to continue having API v2 working correctly. And when I create a new station it should show up without problems, right?

@marekd I dit not change anything at the time of the failure. The stations are online again. I had no error codes during all reporting in the time when they were offline.

Unfortunly my stations (I have just checked them all but only uses Hillerød Vejr as a reference) are no longer shown in the list of PWS stations. I have sorted on distance it it normally shows up at the top of the list.

Red arrow points to my station. The list shows stations around me up to 30 kms aways, but not my station. So there is still something wrong.

Using the direct link to the station, shown here:

https://www.windy.com/station/pws-YZjgOxm

we can see it worked until Thursday 22nd at 10:46 CET... Does that tell you anything? I will check my logs for that time.

As you can see 10:46 and 10:51 in my logs I have NOT changed anything on my side. The application is same verison and only a few values inside the parameters have changed. So I must conclude the problem is caused by something outside my reach. :-) The bottle points to Windy... :-)

2026-01-22 10:46:02 : Reading data from WeatherLink station 'Hillerød Vejr'
2026-01-22 10:46:03 : WeatherLink Success: 122515
2026-01-22 10:46:03 : Sensor Community Success: esp8266-92238877
2026-01-22 10:46:03 : Windy URL: https://stations.windy.com/api/v2/observation/update?id=YZjgOxm&ts=1769075122&temp=-1.6&dewpoint=-3.9&humidity=84&wind=5.3&gust=8.9&winddir=90&pressure=100986&precip=0.0&uv=0.0&solarradiation=19&softwaretype=WLL2Windy_3.0.2.406
2026-01-22 10:46:03 : Windy Success: YZjgOxm - Data timestamp: 22-01-2026 10:45:22

2026-01-22 10:46:05 : Reading data from WeatherLink station 'Helligsø Drag'
2026-01-22 10:46:05 : WeatherLink Success: 122252
2026-01-22 10:46:05 : Windy URL: https://stations.windy.com/api/v2/observation/update?id=FDbhSie&ts=1769075133&temp=-0.4&dewpoint=-3.3&humidity=81&wind=3.8&gust=7.6&winddir=95&pressure=100969&precip=0.0&uv=0.0&solarradiation=18&softwaretype=WLL2Windy_3.0.2.406
2026-01-22 10:46:05 : Windy Success: FDbhSie - Data timestamp: 22-01-2026 10:45:33

2026-01-22 10:46:07 : Reading data from WeatherLink station 'Paradise Residence'
2026-01-22 10:46:08 : WeatherLink Success: 124735
2026-01-22 10:46:08 : Windy URL: https://stations.windy.com/api/v2/observation/update?id=EWtLHK4&ts=1769075151&temp=8.7&dewpoint=7.4&humidity=92&wind=0.0&gust=1.3&winddir=310&pressure=101328&precip=3.6&uv=0.0&solarradiation=53&softwaretype=WLL2Windy_3.0.2.406
2026-01-22 10:46:08 : Windy Success: EWtLHK4 - Data timestamp: 22-01-2026 10:45:51

2026-01-22 10:51:02 : Reading data from WeatherLink station 'Hillerød Vejr'
2026-01-22 10:51:03 : WeatherLink Success: 122515
2026-01-22 10:51:03 : Sensor Community Success: esp8266-92238877
2026-01-22 10:51:03 : Windy URL: https://stations.windy.com/api/v2/observation/update?id=YZjgOxm&ts=1769075422&temp=-1.5&dewpoint=-3.9&humidity=84&wind=5.3&gust=9.4&winddir=85&pressure=100982&precip=0.0&uv=0.0&solarradiation=19&softwaretype=WLL2Windy_3.0.2.406
2026-01-22 10:51:04 : Windy Success: YZjgOxm - Data timestamp: 22-01-2026 10:50:22

2026-01-22 10:51:06 : Reading data from WeatherLink station 'Helligsø Drag'
2026-01-22 10:51:06 : WeatherLink Success: 122252
2026-01-22 10:51:06 : Windy URL: https://stations.windy.com/api/v2/observation/update?id=FDbhSie&ts=1769075433&temp=-0.4&dewpoint=-3.2&humidity=82&wind=3.8&gust=7.6&winddir=87&pressure=100965&precip=0.0&uv=0.0&solarradiation=19&softwaretype=WLL2Windy_3.0.2.406
2026-01-22 10:51:06 : Windy Success: FDbhSie - Data timestamp: 22-01-2026 10:50:33

2026-01-22 10:51:08 : Reading data from WeatherLink station 'Paradise Residence'
2026-01-22 10:51:08 : WeatherLink Success: 124735
2026-01-22 10:51:08 : Windy URL: https://stations.windy.com/api/v2/observation/update?id=EWtLHK4&ts=1769075451&temp=8.7&dewpoint=7.5&humidity=92&wind=0.0&gust=0.4&winddir=3&pressure=101321&precip=3.6&uv=0.0&solarradiation=21&softwaretype=WLL2Windy_3.0.2.406
2026-01-22 10:51:09 : Windy Success: EWtLHK4 - Data timestamp: 22-01-2026 10:50:51

The two other stations, Helligsø Drag and Paradise Residence, which is located in Antalya, Türkiye, also stopped after 10:46. Meaning they no longer show data on Windy. Antalya had 241 mm rain in the last 24 hours and that would have been nice to see on the map...

If you cannot find a solution should I then delete and re-create all 3 stations? Then we do a 100% cleanup.

@marekd Did you fix something that made my 3 stations go offline? They worked yesterday but today they are offline. I have no errors in the local logfile, so my reporting works (or at least seems to work).

I have checked station ids and their passwords. Everything is as it should be on my side.

Do you have any clue what happened?

@WeatherMan10 The total data (using API v1) goes back as far as possible. The we had a "drop out" for one night when I created the API v2 version.

Very strange, but I just checked again. Since my report som hours ago something has changed. Now it shows the right number of minutes, but the information in the About box is a bit strange (yellow).

It is the same for all 3 stations now - a few minutes in the "ago field" and NaNm in the reporting time fields...