Thank you guys for the report and investigation. I have forwarded it to the team responsible for downloading station data. If there is anything we can do about it, we will fix it.

@gptwisted Thanks for letting us know. The bug was in the documentation and it has now been fixed. Previously, it was possible to request 30 days, but we had to limit it to 7 days. It was causing a huge load on our systems as the number of requests increased.

Hi, This is a bit late - but probably not too late. Years ago if i remember correct, it wasn't this hard. It was possible to setup the windbird pioupiou to send the data automatically to windy; or to setup windy to collect the data from openwindmap. Exchanging stationID was almost the only necessary thing. I do not remember at when the functionality got lost - I would guesstimate about a year not seeing my windbird on Windy. Today I investigated (That's also the reason why I'm replying today); and it seems that both services, OpenWindMap/pioupiou and Windy do only serve APIs to collect data - but there is no initiator anymore, this means - you have to create some kind of automatism on your own. In my point of view this has become far too technical for the general audience. Prerequisite: Your dataretrieval URL will be: https://api.pioupiou.fr/v1/live/1605 You have to create a station on windy ( https://stations.windy.com/ ) This will give you a station ID (8 characters) and a password (approx 40-60 characters) for the station. Now the technical part, and this can be done in may ways. Every way I know requires you to have a device or computer running non-stop 24/7. In my case I am using node-red on a raspberry pi to call every 5 minutes https://api.pioupiou.fr/v1/live/{myWindbirdNumber} convert the payload from JSON to javascript object move the msg.payload to msg.windbird set {windy station id} to msg.payload.id set {windy station password} to msg.payload.PASSWORD copy msg.windbird.data.measurements.date to msg.payload.time copy msg.windbird.data.measurements.wind_heading to msg.payload.winddir as integer copy msg.windbird.data.measurements.wind_speed_avg to msg.payload.wind divided by 3.6 copy msg.windbird.data.measurements.wind_speed_max to msg.payload.gust divided by 3.6 pass all this to a http request linked to https://stations.windy.com/api/v2/observation/update with the option to attach payload to query. If you have a Windows computer, you can take and adapt the following powershell code, and call it every 5 or 10 minutes with the task-scheduler: # Pioupiou / Windbird Station ID $windbirdStationId = 1605 # Windy StationId + Password $windyStationId = "abcdefgh" $windyPassword = "approx 40-60 symbols password" # Nothing to adapt below this line # URLs $srcUrl = "http://api.pioupiou.fr/v1/live/$windbirdStationId" $windyUrl = "https://stations.windy.com/api/v2/observation/update" # Retrieve data try { $data = Invoke-RestMethod -Uri $srcUrl -Method GET -ErrorAction Stop } catch { Write-Host "Error retrieving data: $_" exit 1 } # Extract data $winddir = [int]$data.data.measurements.wind_heading $wind = [string]::Format([System.Globalization.CultureInfo]::InvariantCulture, "{0}", $data.data.measurements.wind_speed_avg) $gust = [string]::Format([System.Globalization.CultureInfo]::InvariantCulture, "{0}", $data.data.measurements.wind_speed_max) $ts = $data.data.measurements.date # Form new Query-Parameters $params = @{ id = $windyStationId time = $ts winddir = $winddir wind = $wind / 3.6 gust = $gust / 3.6 PASSWORD= $windyPassword } # GET-Request to Windy try { $upload_result = Invoke-RestMethod -Uri $windyUrl -Method GET -Body $params -ErrorAction Stop Write-Host "Data succesfully sent to Windy." } catch { Write-Host "Error sending to Windy: $_" $params.GetEnumerator() | Format-Table -AutoSize }

@RothwellHeights I can see your station without any issue at https://www.windy.com/station/pws-O47KWNED. Where exactly is your station not shown on Windy?

@idefix37 Ah, thanks! I found this quite by chance a year or so ago (to give evidence to an insurance company of uncharacteristically high wind and gusts) but had been battling to find it again. Appreciated.

@melloil Δημήτρη, δες https://community.windy.com/topic/33054/send-your-station-data-to-windy-and-others-from-wunderground-myacurite-davis-weatherlink-weatherflow-tempest-or-ambient-weather?_=1771079190776 και https://ingallswx.com/2024/10/31/simple-guide-to-forward-your-weather-station-data-to-multiple-sites-online/ Πάντως εγώ βλέπω μια χαρά το σταθμό σου στο windy [image: 1771079858914-1000044314.jpg]

@Amar-Drbala Hi, If you purchase a weather station, you will have the option to report its data to Windy, but it will not influence the forecast. The forecast is provided by weather models, and Windy gives you access to several of them for your region. As the ECMWF states “We routinely process data from around 90 satellite instruments as part of our operational daily data assimilation and monitoring activities. We receive 800 million observations daily, and 60 million quality-controlled observations are available daily for use in the Integrated Forecasting System (IFS)” note: IFS is the model run by the ECMWF and shown in Windy. “ the vast majority of these are satellite measurements, but we also benefit from all available observations from non-satellite sources, including surface-based and aircraft reports. … The so-called conventional data nowadays include observations provided by ground stations, radiosondes, sensors on airliners and commercial vessels or installed on anchored or drifting buoys. But these data now represent only about 10% of the total volume because 90% of the data is now provided by satellites”. Furthermore, the weather stations whose data are integrated into the meteorological model assimilation system are official stations such as those certified by the WMO, airport stations, SYNOP stations, etc. Personal stations can be integrated into the MADIS network, but I don't know how the data from these stations is used. Therefore, there is very little chance that you can influence the model forecasts with your weather station.

@marekd Thanks I think disabling them will be better than removing them, then at least we don't have to go a set up another one

@kostinha Try https://community.windy.com/post/189930 Here you can find a guide for the forwarder https://community.windy.com/post/202512 https://ingallswx.com/2024/10/31/simple-guide-to-forward-your-weather-station-data-to-multiple-sites-online/

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

@Filipe-Cardoso It is okay. I will forward your feedback to our colleague.

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

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

@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