Report your Weather Station Data to Windy

bobeast

@bobeasterday said in Report your Weather Station Data to Windy:

It looks like this API expects the weather station to be at a fixed location. My station is on a boat and as such, the data I send is based on my current location which of course can change.

Ideally I would be able to pass longitude and latitude values as query parameters. Is this possible?

Edit: I figured it out but for the edification of others;

You need to use the POST method (as opposed to GET). That way you can send updated server info (including lat and Lon).

jf_moreira

Hello all.

Again, nothing changed on my side and Windy stopped receiving my data last Monday, April 29th. Does anyone know what changed here?

My PWS is regularly reporting to Wunderground, PWSweather and ThinkSpeak and everything is published.

https://node.windy.com/pws/stats/f052cfed

Others:
https://www.wunderground.com/dashboard/pws/ISOJOS39
https://www.pwsweather.com/station/pws/ISOJOS39

Please help.
Jeffo.

jf_moreira

This post is deleted!

jf_moreira

This post is deleted!

jf_moreira

@jf_moreira

This is what solved it for me. I used a script from a guy in Github:

https://community.windy.com/post/183560

Thanks, @Gkikas-LGPZ

jmunkki

I'm getting relatively frequent errors when I try to send data every 5 minutes. I could extend the period to 6 minutes to fix the issue, but I think it's weird that you say that 5 minutes is OK, but then even a slight amount of jitter in the period will cause error messages.

"Measurement sent too soon, update interval is 5 minutes"

Here are some samples of the measured interval in seconds that show the the variations are around 60 milliseconds and we're still getting errors:

300.001
300.037
299.953
300.035
299.992
300.036
299.943

As an experiment, I'll add a static delay before sending the data. It will not affect the interval in any way, but it might help if the problem is in fact a clock sync issue. I could of course track the interval and add a variable delay, but our station is on a strict one minute clock, so the Windy data would start to drift relative to that clock since there's no way to claw back the added milliseconds.

David Ryzec 3

@jmunkki Hi, how are you measuring those intervals? You should count 5 minutes since you receive response from us. Those issues you are describing are probably caused by network delay. I can maybe lower the interval little bit so we are not so strict about this limit.

jmunkki

@David-Ryzec-3 I placed the timer code just before the HTTP request. Looking at the log, there haven't been any errors in the past 7 hours, so maybe it's fixed, but it could just be luck. We get data every minute, but I'm not in control of that and can not let Windy drive the sample rate. I can of course change the code to send to Windy only every 6 minutes instead of 5 and that will eliminate the issue. I'll switch to a 6 minute send period, if the problem returns.

David Ryzec 3

@jmunkki I lowered the limit a little so you should see no errors now

@Enrique-Alvarez-Jativa

I have been unable to compile . Any ideas?

Enrique Alvarez Jativa

Hi, what compilation error do you see? If you want, send me your email by DM and we will review it.