by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Jeremy Wall
    @jeremywall-davis
    @Erosfaus_gitlab that is it, it's the direction of the prevailing wind direction over the archive period
    you have to understand that the data the device sends to our servers in the current conditions data is not always the same kinds of data in the archive records
    Fausto Amador
    @Erosfaus_gitlab
    OK, thanks @jeremywall-davis *
    Jose Gallardo
    @JLgallardoq_gitlab
    Hello @jeremywall-davis , i'm new to use davis api. i´m working with the historic data. and when i check the wind direction in all the information are the number 9.
    What the meaning of this number?
    because in weatherlink appear the number 250, 235, etc.
    Jeremy Wall
    @jeremywall-davis
    @JLgallardoq_gitlab what is the sensor_type and the data_structure_type in the JSON data you are looking at?
    Jose Gallardo
    @JLgallardoq_gitlab
       'data_structure_type': 9,
       'lsid': 340868,
        'sensor_type': 254,
    @jeremywall-davis
    Jeremy Wall
    @jeremywall-davis
    @JLgallardoq_gitlab sensor type 254 is a soil moisture sensor, it does not report the wind
    what's the sensor type of the JSON data where you see the wind direction is a 9
    Jose Gallardo
    @JLgallardoq_gitlab
    sorry Jeremy
    u'data_structure_type': 7,
    u'lsid': 340753,
    u'sensor_type': 82}
    'wind_dir_of_hi': 7
    'wind_dir_of_prevail': 9
    Jeremy Wall
    @jeremywall-davis

    Ok, that makes more sense. Have you looked into the sensor catalog? It's the list of all sensor definitions possible and provides some information about the data types and the units of the data. There's some information about the sensor catalog at https://weatherlink.github.io/v2-api/sensor-catalog

    But I'll just tell you what is happening to save you some time. First I looked up the sensor catalog section for sensor_type 82. In that sensor information I looked at the data_structures section for data_structure_type 7. Under the section for data_structure_type 7 is the list of fields you will receive in the data records from the API for historic data. When I look at the wind fields I see this:

     "wind_dir_of_hi": {
            "type": "integer",
            "units": "direction code: 0=N, 1=NNE, ... 14=NW, 15=NNW"
    },
    "wind_dir_of_prevail": {
            "type": "integer",
            "units": "direction code: 0=N, 1=NNE, ... 14=NW, 15=NNW"
    },
    Jose Gallardo
    @JLgallardoq_gitlab
    Ok, thanks @jeremywall-davis
    Jeremy Wall
    @jeremywall-davis
    The reason is that the wind direction is not reported in degrees but in a numeric code that represents 1 of 16 possible sections of the compass. On the WeatherLink web site this is converted to the degrees from the center of the compass section. But in the API I give you the raw data value we received from the station. The reason I give you the raw data is because that is what the API was designed to do ... to give you access to the data in it's original form.
    Other sensor types do report the wind direction in degrees, but that is just not the case here.
    deadbyback
    @deadbyback
    Hello! I am interested in the following question: does the API v2 key have a lifetime? If so, which one? Thank you in advance!
    alediazmor
    @alediazmor
    Capture.PNG
    Screenshot 2020-09-13 at 13.55.24.png
    Hi @jeremywall-davis I'm using API v2 to retireve current conditions every 15 min, but most times rain_15_min_mm and rain_rate_mm are not consistent with values shown on our weatherlink main page. In fact, some times I get a randon rain_rate_mm value of 13107 that messes up our calculations. Any idea why this might be happening?
    Jeremy Wall
    @jeremywall-davis
    @deadbyback The API key and secret combination does not have a max lifetime. They combination is good until you use the "Generate New v2 Key" button at https://www.weatherlink.com/account which will only generate a new secret. While the secret can be discarded and replaced the key itself can not be changed.
    Jeremy Wall
    @jeremywall-davis
    @alediazmor You can't really compare the current conditions and archive (also known as historic) data. Depending on what hardware you have for uploading data to WeatherLink.com the data in the current conditions and the data in the archive record can represent completely different time spans. Additionally, time stamps in the API response are UTC unix timestamps while the date and time on the web site is adjusted to show the local date and time according to the selected timezone of the weather station.
    Certified Ag
    @CertifiedAg_twitter
    will the API V2 retrieve data from EM nodes; such as soil moisture sensors?
    Jeremy Wall
    @jeremywall-davis
    yes
    deadbyback
    @deadbyback
    @jeremywall-davis Thanks! :)
    Torben Bernt Henriksen
    @torbeh33_gitlab
    Hi
    Got problems with my weatherlink after I changed the router, it stopped and reported. is there anyone who can help me with this.
    thank you in advance.
    With best regards
    Torben.
    Jeremy Wall
    @jeremywall-davis

    @torbeh33_gitlab Sorry, this is the chat room for people using the WeatherLink v2 API. You need to contact our Tech Support department

    By Phone: +1-510-732-7814 on Monday - Friday from 7:00 AM - 5:30 PM PST
    By Email: support@davisinstruments.com

    950hPa
    @carioca_cari_twitter
    Hey @jeremywall-davis it's possible add the temperature range on API?
    API/or Wllive
    Jeremy Wall
    @jeremywall-davis
    @carioca_cari_twitter what do you mean
    chris123417
    @chris123417
    Hey @jeremywall-davis I'm trying to get my station's ID using the following:
    "https://api.weatherlink.com/v2/stations/api-key={}&api-signature={}&t={}".format( parameters["api-key"], apiSignature, parameters["t"]). However it keeps returning an error "no API key found in request", should there be a '?' before the api-key in the URL?
    Jeremy Wall
    @jeremywall-davis
    yes, remove the "/" between stations and api-key and replace it with a "?"
    chris123417
    @chris123417
    Thanks
    deadbyback
    @deadbyback
    Hey, guys. Can you help me?
    I am trying to send a request: "https://api.weatherlink.com/v2/stations/:station-ids" for a specific station, but I get 400 request status with message "API signature check failed". When compiling this parameter, should I consider ALL parameters or only specific ones?
    METEOshop
    @METEOshop
    Hey guys, I'm another one who need your help :-) I stuck at authentication, because I don't know station ID I tried to get all stations informations by url https://api.weatherlink.com/v2/stations?api-key=xxx&api-signature=zzz&t=yyy, but there is return code 400 with status API signature check failed, I use calculation of signature from example at https://weatherlink.github.io/v2-api/ and also I'm sure my key and secret are correct, any idea what might be wrong? my test site http://www.meteoshop.cz/davis/api.php
    Jeremy Wall
    @jeremywall-davis
    @deadbyback every parameter, either before or after the question mark, must be accounted for in the signature
    @METEOshop only include parameters that are actually defined according to the API reference page at the documentation web site. A call to "/stations" does not define a station-id parameter but you used one from the sample code. Remove it from your signature calculation.
    950hPa
    @carioca_cari_twitter
    it's possible add the temperature range(High T°C - Low T°c ) on API/API Local?
    Jeremy Wall
    @jeremywall-davis
    Sorry, we can't add fields. There are design requirements and limitations you are not aware of and the API can only show the data reported by the device.
    METEOshop
    @METEOshop
    @jeremywall-davis thank you, now it is clear for me
    ran-pelta
    @ran-pelta
    Hi, is there a pdf or some other documentation with a list of all the weather parameters (and their units or agg options- e.g., hourly, daily) Davis stations measure? I could not find it on the official API docs - https://weatherlink.github.io/v2-api/
    Jeremy Wall
    @jeremywall-davis
    @ran-pelta see the sensor catalog https://weatherlink.github.io/v2-api/sensor-catalog
    ran-pelta
    @ran-pelta
    Thanks, it says - "Because the Sensor Catalog is a comprehensive list of all sensor types the JSON in the API response is a large document over 2 MB in size." Can I get this document without using API? do you have it as pdf or as downloadable file?
    Jeremy Wall
    @jeremywall-davis
    No the document is dynamically generated based on what you have access to
    ran-pelta
    @ran-pelta
    Is there a test/demo station for the API?
    Jeremy Wall
    @jeremywall-davis
    no
    ran-pelta
    @ran-pelta
    Thanks
    azwanr
    @azwanr
    hi.. just a bit confuse. does station-id is similar with station_did?
    Jeremy Wall
    @jeremywall-davis
    azwanr
    @azwanr
    thanks @jeremywall-davis