Windy Community
    • Unread
    • Categories
    • Groups
    • Go to windy.com
    • Register
    • Login
    1. Home
    2. docbee
    D
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 6
    • Groups 0

    docbee

    @docbee

    1
    Reputation
    1
    Profile views
    6
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online
    Website meteobridge.com
    Location Germany, Lentföhrden

    docbee Unfollow Follow

    Best posts made by docbee

    • Very poor communication to developers of upload software

      Hi,
      as the developer of the Meteobridge SW which quite a few user use to upload data of their PWS to windy, I am largely disappointed that you do not inform me before doing changes in the upload format. The current issue I was pointed to by my customers is that station IDs are now given as alphanumerics, while it was only numerics before. Looks like a small change, but Meteobridge allowed to use numerics only according to previous specs. As a result I got bug reports and frustrated customers.

      Is it too much to ask to be informed on changes that impact data upload before you implement those? I see this as rather unprofessional and I am not interested to support unreliable services that impact quality and user experience of my product.

      posted in Your Feedback and Suggestions
      D
      docbee

    Latest posts made by docbee

    • RE: Very poor communication to developers of upload software

      Just to leave some hints for others dealing with the changing upload API.

      Current windy account provide 3 credentials:

      1. the API KEY that is used in the legacy API to identify your account. It is just this, no password is needed here. The second parameter is the STATION ID, which is a pure numerical that allows you to enumerate multiple stations if you have that. Default is "0" for the regular case where just one station is registered.

      2. The PASSWORD which is given to make use of the new V2 API. In addition to the password you are also provided a STATION ID which is not just an enumeration of your own stations, but a unique ID to identify your station within all stations on the network. This is no longer pure decimal but alphanumeric (or hex? I don't know and they don't tell).

      3. As mentioned before STATION ID is different, when using legacy API or V2 API. This will give a lot of confusion for users, when they have to change from old to new upload API.

      You can derive the V2 credentials from Windy when calling this URL with your legacy API KEY:

      https://stations.windy.com/api/v2/pws?key=***your_legacy_api_key***&station=0

      The returning JSON text shows new Station ID and PASSWORD

      Caveat on handling the return information on uploads:
      Error and/or success reporting is unclear as before. On some conditions it returns nothing, sometimes lengthy JSON stuff with "success":"true" somewhere in it, sometimes error messages introduced by "message", confusion all over the place and of course no documentation. I understand that it is hard to document things that don't have a proper design apart from "you get something in JSON", sometimes...

      posted in Your Feedback and Suggestions
      D
      docbee
    • RE: Very poor communication to developers of upload software

      I just released a new Meteobridge version that hopefully supports legacy API and the new V2. The lack of support from Windy is rather outstanding compared to other weather networks. There was not any helpful information in this thread given from @Suty, who seems to have the task just to simulate customer or developer support.

      posted in Your Feedback and Suggestions
      D
      docbee
    • RE: Very poor communication to developers of upload software

      @Suty yes, this is what I found myself (as stated in my previous post).

      I received an ID and a PASSWORD for a specific station by calling "https://stations.windy.com/api/v2/pws". When I use these credentials via "https://stations.windy.com/api/v2/observation/update?station=....&password=..." I get this error:

      {"message":"Provide a valid password via the PASSWORD query parameter or a Bearer token.","error":"Unauthorized","statusCode":401}

      Why? The credentials are what windy told me for that specific station.

      posted in Your Feedback and Suggestions
      D
      docbee
    • RE: Very poor communication to developers of upload software

      @Suty looks like I found a rather confusing api upload definition here: https://stations.windy.com/api-reference. Is that the one to use? Why aren't there any examples and what is all this duplicate station id thing good for?

      Can you please explain why the upload below does returns a 403 error (which is btw not defined in your API doc) without any useful information what exactly is the problem?

      https://stations.windy.com/api/v2/pws?key=....&station=....&ts=1775554620&temp=22.2&wind=1.8&winddir=80&gust=2.8&rh=58&dewpoint=13.5&mbar=1020.1&precip=0.0&uv=2.6

      {"message":"Forbidden resource","error":"Forbidden","statusCode":403}

      posted in Your Feedback and Suggestions
      D
      docbee
    • RE: Very poor communication to developers of upload software

      @Suty where do I find the new upload API definition? Do old uploads that just have the key and the station id defaulted to "0" still work or do they need new credentials?

      posted in Your Feedback and Suggestions
      D
      docbee
    • Very poor communication to developers of upload software

      Hi,
      as the developer of the Meteobridge SW which quite a few user use to upload data of their PWS to windy, I am largely disappointed that you do not inform me before doing changes in the upload format. The current issue I was pointed to by my customers is that station IDs are now given as alphanumerics, while it was only numerics before. Looks like a small change, but Meteobridge allowed to use numerics only according to previous specs. As a result I got bug reports and frustrated customers.

      Is it too much to ask to be informed on changes that impact data upload before you implement those? I see this as rather unprofessional and I am not interested to support unreliable services that impact quality and user experience of my product.

      posted in Your Feedback and Suggestions
      D
      docbee