Error: Windy: invalid API key

[Churchtownweather]

HI anyone
having problems with windy upload
Error: Windy: invalid API key
Thanks in advance

[Platokidd]

Yes I am too. Started after updating to 6.0.

[Valdrin]

I have the same problem with the Windy API since May 16th, and now I see that CWOP is also having issues.

[Platokidd]

Wondering if this also was related to some far-out wacky numbers on the MIN/MAX.
Posted here viewtopic.php?t=18023

Since removing Windy the MIN/MAX numbers seem to be normal, fingers crossed. That said, there is a whole lot of bad numbers in the min/max.
Years worth all corrupted.

[admin]

HI anyone
having problems with windy upload
Error: Windy: invalid API key
Thanks in advance

I didn't touch Windy upload code for a long time. Can you please give me remote access? Please send credentials to "info(at)smartbedded.com".

[Churchtownweather]

Will do many thanks

[admin]

Thanks, I was able to login. Your uploads to Windy sometime work, sometimes Meteobridge receives a HTTP Error 400. Looks like network routing or timing issues to me:

Code: Select all

2024-05-31 10:49:03 Success: 2024-05-31 10:48:53
2024-05-31 10:44:03 Success: 2024-05-31 10:43:53
2024-05-31 10:39:02 Success: 2024-05-31 10:38:53
2024-05-31 10:36:05 Error: 2024-05-31 10:33:52  https://stations.windy.com/pws/update/xxx?station=0&ts=1717148032&temp=14.7&wind=2.7&winddir=300&gust=4.3&rh=70&dewpoint=9.3&mbar=1019.6&precip=0.0&uv=3.6: 2024-05-31 10:36:05 ERROR 400: Bad Request.  (no more tries)
2024-05-31 10:29:02 Success: 2024-05-31 10:28:52
2024-05-31 10:24:04 Error: 2024-05-31 10:23:52  https://stations.windy.com/pws/update/xxx?station=0&ts=1717147432&temp=14.7&wind=2.9&winddir=302&gust=5.2&rh=70&dewpoint=9.3&mbar=1019.5&precip=0.0&uv=2.3: 2024-05-31 10:24:04 ERROR 400: Bad Request.  (no more tries)
2024-05-31 10:19:04 Success: 2024-05-31 10:18:52
2024-05-31 10:14:01 Success: 2024-05-31 10:13:52
2024-05-31 10:09:02 Error: 2024-05-31 10:08:52  https://stations.windy.com/pws/update/xxx?station=0&ts=1717146532&temp=14.5&wind=1.9&winddir=0&gust=4.7&rh=70&dewpoint=9.1&mbar=1019.5&precip=0.0&uv=2.2: 2024-05-31 10:09:02 ERROR 400: Bad Request.  (no more tries)
2024-05-31 10:04:01 Error: 2024-05-31 10:03:52  https://stations.windy.com/pws/update/xxx?station=0&ts=1717146232&temp=14.3&wind=1.8&winddir=331&gust=3.3&rh=71&dewpoint=9.1&mbar=1019.5&precip=0.0&uv=3.2: 2024-05-31 10:04:01 ERROR 400: Bad Request.  (no more tries)
2024-05-31 10:01:07 Success: 2024-05-31 09:58:52
2024-05-31 09:56:05 Error: 2024-05-31 09:53:51  https://stations.windy.com/pws/update/xxx?station=0&ts=1717145631&temp=14.2&wind=1.9&winddir=319&gust=4.3&rh=71&dewpoint=9.0&mbar=1019.4&precip=0.0&uv=2.7: 2024-05-31 09:56:05 ERROR 400: Bad Request.  (no more tries)
2024-05-31 09:51:06 Success: 2024-05-31 09:48:51

Similar but less often with AWEKAS:

Code: Select all

2024-05-31 09:37:55 Success: 2024-05-31 09:37:51
2024-05-31 09:32:53 Success: 2024-05-31 09:32:51
2024-05-31 09:27:53 Success: 2024-05-31 09:27:51
2024-05-31 09:23:06 Error: 2024-05-31 09:22:51 Read error (Connection timed out) in headers.  (no more tries)
2024-05-31 09:17:53 Success: 2024-05-31 09:17:51
2024-05-31 09:12:52 Success: 2024-05-31 09:12:50
2024-05-31 09:07:52 Success: 2024-05-31 09:07:50
2024-05-31 09:02:54 Success: 2024-05-31 09:02:50
2024-05-31 08:57:53 Success: 2024-05-31 08:57:50
2024-05-31 08:52:54 Success: 2024-05-31 08:52:50
2024-05-31 08:47:52 Success: 2024-05-31 08:47:50
2024-05-31 08:42:52 Success: 2024-05-31 08:42:50
2024-05-31 08:37:52 Success: 2024-05-31 08:37:50
2024-05-31 08:32:52 Success: 2024-05-31 08:32:49
2024-05-31 08:27:52 Success: 2024-05-31 08:27:49
2024-05-31 08:22:51 Success: 2024-05-31 08:22:49
2024-05-31 08:17:50 Success: 2024-05-31 08:17:49
2024-05-31 08:12:50 Success: 2024-05-31 08:12:49
2024-05-31 08:07:51 Success: 2024-05-31 08:07:49
2024-05-31 08:03:04 Error: 2024-05-31 08:02:49 Read error (Connection timed out) in headers.  (no more tries)
2024-05-31 07:57:50 Success: 2024-05-31 07:57:49
2024-05-31 07:52:49 Success: 2024-05-31 07:52:48
2024-05-31 07:47:50 Success: 2024-05-31 07:47:48
2024-05-31 07:42:50 Success: 2024-05-31 07:42:48
2024-05-31 07:37:50 Success: 2024-05-31 07:37:48
2024-05-31 07:32:49 Success: 2024-05-31 07:32:48

... and CWOP:

Code: Select all

2024-05-31 10:53:58 Success: 2024-05-31 10:53:53
2024-05-31 10:48:59 Success: 2024-05-31 10:48:53
2024-05-31 10:43:59 Success: 2024-05-31 10:43:53
2024-05-31 10:38:57 Success: 2024-05-31 10:38:52
2024-05-31 10:36:01 Error: 2024-05-31 10:33:52 connection failed (no more tries)
2024-05-31 10:28:57 Success: 2024-05-31 10:28:52
2024-05-31 10:23:59 Success: 2024-05-31 10:23:52
2024-05-31 10:19:00 Success: 2024-05-31 10:18:52
2024-05-31 10:13:57 Success: 2024-05-31 10:13:52
2024-05-31 10:08:57 Success: 2024-05-31 10:08:52
2024-05-31 10:03:57 Success: 2024-05-31 10:03:52
2024-05-31 10:01:02 Error: 2024-05-31 09:58:52 connection failed (no more tries)
2024-05-31 09:56:01 Error: 2024-05-31 09:53:51 connection failed (no more tries)
2024-05-31 09:51:02 Error: 2024-05-31 09:48:51 connection failed (no more tries)
2024-05-31 09:43:56 Success: 2024-05-31 09:43:51
2024-05-31 09:41:01 Error: 2024-05-31 09:38:51 connection failed (no more tries)
2024-05-31 09:33:57 Success: 2024-05-31 09:33:51
2024-05-31 09:28:56 Success: 2024-05-31 09:28:51
2024-05-31 09:23:56 Success: 2024-05-31 09:23:51
2024-05-31 09:21:02 Error: 2024-05-31 09:18:51 connection failed (no more tries)
2024-05-31 09:13:56 Success: 2024-05-31 09:13:50
2024-05-31 09:10:59 Error: 2024-05-31 09:08:50 connection failed (no more tries)
2024-05-31 09:03:57 Success: 2024-05-31 09:03:50
2024-05-31 09:00:59 Error: 2024-05-31 08:58:50 connection failed (no more tries)
2024-05-31 08:53:55 Success: 2024-05-31 08:53:50
2024-05-31 08:51:00 Error: 2024-05-31 08:48:50 connection failed (no more tries)
2024-05-31 08:43:56 Success: 2024-05-31 08:43:50

[admin]

I did a bit more research, windy has a minimum sent interval of 5 minutes. As you sent every 5 minutes, this might conflict here and there.

Code: Select all

"update":{"update":{"stations":[],"observations":[{"si":0,"time":"2024-05-31T10:23:15.000Z","temp":12.2,"wind":1.5,"wind_dir":312,"wind_gust":4.7,"rh":80,"dew_point":8.9,"pressure":101670,"precip":0,"uv":0}]},"errors":{"observations":[],"stations":[]}},"result":{"0":{"stations":[],"observations":[{"success":false,"value":{"si":0,"time":"2024-05-31T10:23:15.000Z","temp":12.2,"wind":1.5,"wind_dir":312,"wind_gust":4.7,"rh":80,"dew_point":8.9,"pressure":101670,"precip":0,"uv":0},"error":"Measurement sent too soon, update interval is 5 minutes"}]}}}

When you set send interval to 10 min in Meteobridge, all will be fine. As an alternative, you can ask Windy to make it a bit more tolerant on there side.

[Platokidd]

Wondering if this also was related to some far-out wacky numbers on the MIN/MAX.
Posted here viewtopic.php?t=18023

Since removing Windy the MIN/MAX numbers seem to be normal, fingers crossed. That said, there is a whole lot of bad numbers in the min/max.
Years worth all corrupted.

Rolling back to 5.8. Too many issues with 6.0 Corrupt MIN /MAX data. Tried to erase all and start over. Nojoy,
Windy still has issue even set at 10 minutes.

[admin]

This error even occurs on your system when update interval set to 10 mins. Only explanation I have is that you have another PC reporting with same credentials to windy and this causes the rejections.

[Churchtownweather]

Many thanks that did the trick

[zakos52]

Same problem with meteobridge version 5.9!

windy.png (46.81 KiB) Viewed 2894 times

windy1.png (17.79 KiB) Viewed 2894 times

[Platokidd]

This error even occurs on your system when update interval set to 10 mins. Only explanation I have is that you have another PC reporting with same credentials to windy and this causes the rejections.

The meteobridge is the only source that I send data to Windy. Been sending data to Windy for a few years without issue. Just noticed this recently. I know CWOP sends my data to Windy.

[admin]

Your Meteobridge is uploading partly fine to Windy. I have given you my analysis. Windy is rejecting packets with "you send too often" message. Please contact windy to get it fixed on their side.