@marekd Sorry for the late reply. Yes everything is working now with the new API.

@Suty Sorry. I just realized you have to go to Menu, then down toward the bottom it says Air Quality Stations. You add them to your map or pin it.

@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 [image: 1769291083672-0ed3f6d4-2df2-4df9-8c1c-8b4110f31825-image.png] 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?

@Francois-Lacroix It should now throttle by station PASSWORD. Also, a 429 status code is returned when the limit is hit, to make it clearer what is going on. I hope this solves your issue.

@cfrank01 Thank you for the report. It seems that code.gs is not an official Windy implementation, so unfortunately we are not able to help with it directly. Based on the error you shared, it appears that code.gs is trying to use the legacy API together with the new API payload, which cannot work. Please see https://stations.windy.com/api-reference for more details. I would recommend contacting the author of code.gs and kindly asking them to update the script to support the new API.

@cfrank01 I am not familiar with code.gs, and it does not appear to be an official Windy implementation, so unfortunately I am not able to help with it directly. I recommend contacting the author of code.gs and asking them to update the script to the new API specification described here: https://stations.windy.com/api-reference As a temporary workaround, you may continue using the previous API. However, please note that I cannot recommend this approach, as the legacy API will be shut down at the end of 2026.

@xd1936 I have been unable to successfully send data to Windy from my Tempest using the newest version of your script. This is the error that shows up in the Executions list Jan 19, 2026, 1:13:09 PM Error ReferenceError: windyStationPassword is not defined at updateWindy_(Code:1258:29) Prior to this, I was getting a completely different error in the previous script. I was only able to get my station to show up once for few days and then never again. Any ideas?

@Suty said in Remove incorrect Weather Station Data: @WeatherMan10 Hello, we can't handle this manually on our end, however, if you wait for a week, this data will be gone then. I usually do that. But I thought I would ask

@MarkNagy Yes indeed it works on hourly basis that's why I got nothing updated until the next hour. I apologize about the misunderstanding. Best regards, Guillaume