The root cause is a poor decision in the old implementation: the station ID contains the userId combined with the station index. We removed this in the new implementation, but it must be kept for backward compatibility. As a result, when you remove a station and create a new one, the ID is composed of your userId and the first available station index. After API v1 is dropped, this will be removed and the ID will be randomly generated.

Sorry about that, but we are not going to change it at the moment. It is quite an edge case, and hopefully you will not need to create stations anymore. And it will be fixed at the end of 2026.

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?".

Your idea regarding the last observation is great, we will add that feature.

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

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.

It was confusing because we have 68 other stations reporting via the new API and they work without any problems. However, those stations do not report the ts property. We expect this property to be in seconds, but our systems were treating it as milliseconds. In a previous deployment, this property was skipped. When we fixed the handling of this property, we accidentally broke it for you. Sorry about that.

We hope no further development will be needed and that everything is stable now. Thank you again. Your feedback is very valuable to us and we are glad you tested this API with us. And of course, sorry for all the complications we caused.

Regarding the online or offline status on stations.windy.com, toggling it likely distracted you from the real issue. We recently changed the threshold for showing a station as online or offline from hours to two days. Sorry about that. We will probably switch it back to hours.

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.

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?

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.

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

Do you have any clue what happened?

• Millimeters or inches, it does not matter. Feel free to send whichever you prefer. The data is consolidated into millimeters in our database and then served on Windy.com in the user’s preferred units.
• Showing the station name somewhere is a great idea. @suty will probably know more about this, or at least can trigger the right people to handle it.
• The reporting time issue is a bug. Thanks for reporting it (again). We will fix it ASAP. (cc @weatherman10)

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...

2026-01-21 21:21:06 : Windy Success: YZjgOxm - Data timestamp: 21-01-2026 21:20:22

As you can see from the log, I report to Windy at 21:21:06 and the data has timestamp 21:20:22, so it is about 44 seconds old data.

I need to understand how 5 minute intervals and delay of data is as shown but it seems Windy tells other information?

Not a answer per say. But my PWS only updated that highlighted bit once the full 10 days of data was there, Then it changed to Reporting: 5m

How far back does the data go?

As you see next to the picture showing the location of the station, I have placed a yellow arrow. It is the name of the station. Could we also have the name just below "About this station"?

The marked text in yellow: What does reporting time and avg. delay mean in this context?

I report every 5 minutes and the reporting time is withing 1 minute of the timestamp of the data:

2026-01-21 21:21:06 : Windy URL: https://stations.windy.com/api/v2/observation/update?id=YZjgOxm&ts=1769026822&temp=-0.1&dewpoint=-1.9&humidity=88&wind=3.0&gust=6.7&winddir=66&pressure=101084&precip=0.0&uv=0.0&solarradiation=0&softwaretype=WLL2Windy_3.0.2.406

2026-01-21 21:21:06 : Windy Success: YZjgOxm - Data timestamp: 21-01-2026 21:20:22

As you can see from the log, I report to Windy at 21:21:06 and the data has timestamp 21:20:22, so it is about 44 seconds old data.

I need to understand how 5 minute intervals and delay of data is as shown but it seems Windy tells other information?

I am ready to go back and report in millimeters. I fetch data from Davis WeatherLink API and I can get any of these values: since midnight, last hour and both in mm or inches:

• rainfall_daily_in
• rainfall_daily_mm
• rainfall_last_60_min_in (should I use this?)
• rainfall_last_60_min_mm (or this?)

So do you prefer mm or inches? I dont feel I should convert it one way and then you will convert it back. Then I will prefer to send you the value that fits Windy best with less convertion and rounding errors. :-)

My stations rain tipping device measures in mm and in steps of 0,2 mm.

If you notice anything else, please let us know. Your feedback is very helpful and helps us significantly with fine-tuning the new API.

This information is regarding sending precipitation information via the new API v2.

The old API required precipitation to be the amount of rain within the last 15 minutes. The new API requires the value to cover the number of millimeters since midnight. I follow this new rule via the precip-parameter.

As seen from the graph (left - API v1) and right (API v2) something does not work correctly. We had 2.6 mm today, but that was in the night. Now it stays as a horizontal line where under v1 it showed more like a hill.

Can you confirm that you want the rain since midnight or is it a display or documentation error?

This is information in the API v2 documentation:

as the rain was many hours ago I report the same value again and again until Midnight, where it is zeroed. It seems like Windy adds the value to the total accumulated rain of the day all time... Where does 27.9 mm acc 24 hours come from? Not from my station. :-)

For the moment being, since Sunday 18th 08:50 I have been replacing the "precip" parameter with "hourlyrainin", which is more close to the way it is done in API v1. I will watch if that fixes the error in the Windy display.