Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    p0wderhornIT
    @p0wderhornIT
    awesome, thank you!
    Lex-MT
    @Lex-MT
    Hi @jeremywall-davis . I have added a third station recently and noticed that the API response being generated are not all in the same format. Basically there are 4 sections under sensors: the data from outdoor sensors, indoor sensors, atmospheric pressure and some health info. These sections seem to be arranged randomly for each which is an issue when I am doing some automation. Is there a way so that the sections under sensors are always the same. I'll be adding more stations in the coming weeks. Can you please advise. Thanks in advance. Username: Innovation
    Geoff
    @ditch_the_Barn_twitter
    @jeremywall-davis - Hi I msgd last night for an API key for WLL - I know have the user name it is: charlesd - cheers
    Jeremy Wall
    @jeremywall-davis
    @Lex-MT The problem with trying to organize the order is that it would require a predictable means of sorting because trying to do so by concepts like inside/outside will not work in the future as new sensor types are added that could be inside or outside and be changed at any moment. Sorting sensors by a static and unchanging field is the only way.
    So the 2 options are:
    1: sort by lsid
    2: sort by sensor_type with ties sorted by lsid
    Jeremy Wall
    @jeremywall-davis
    @mcrossley Sorry, forgot about your request for info on DIDs for WLL. The DID range for WLL starts at 0x700000 (7,340,032 in decimal), this hex value represents the last 6 characters of the 12 character hex DID.
    Mark Crossley
    @mcrossley
    @jeremywall-davis Thanks, no rush I already work around the existing return values. Did you ever dig out the range of possible WLL station IDs?
    Mark Crossley
    @mcrossley
    @Lex-MT isn't that one of the features of JSON, everything is referenced so the internal order does not matter, nor indeed should be assumed?
    Sorry @jeremywall-davis my phone did not update the forum with your response for some reason.
    Jeremy Wall
    @jeremywall-davis
    @mcrossley @Lex-MT JSON objects or maps (however you think of the curly brace items in JSON) are where order of fields is not guaranteed, but the sensors field @Lex-MT is asking about is an array where order can be controlled.
    Mark Crossley
    @mcrossley
    @jeremywall-davis Ah, you have given me a DID range, but it was the Station-Id range I was really after. Or did they just start at 1 and work up?
    Jeremy Wall
    @jeremywall-davis
    @mcrossley it's just an auto increment integer so all numbers are potentially valid
    wsantos70
    @wsantos70
    Hello everybody, my name is William.
    How to obtain a key to use v2 API?
    Jeremy Wall
    @jeremywall-davis
    @wsantos70 You need a WeatherLink Live or EnviroMonitor weather station and I need to know your WeatherLink username
    Lex-MT
    @Lex-MT
    Sorting by sensor type did work. @jeremywall-davis is there a list of sensor type? Like in my case I am referring to 43 and 48 for the outdoor sensors for Vantage Pro 2. Plus regarding the issue where rain 24 hours rain data was not being stored when there was a power cut, any update on when the fix will be available. Right now I'm managing to counter this problem by adding the 15 min rainfall over a period of 24 hours but there is still a discrepancy in the calculated value doing it this way.
    Jeremy Wall
    @jeremywall-davis
    @Lex-MT Have you seen the sensor catalog available at /v2/sensor-catalog in the API? There's a docs page about it at https://weatherlink.github.io/v2-api/sensor-catalog
    The sensor catalog doesn't change all that often so if you are just using a WeatherLink Live so you can download it once and cache it because the API response is a large 2+ MB JSON document listing all sensors for all types of weather stations, including our agriculture focused EnviroMonitor station.
    Jeremy Wall
    @jeremywall-davis
    In the sensor catalog response look at the sensor_types array (it's also a somewhat randomly sorted array for now) and find the sensor with the "sensor_type" that you are interested. Next, you can use the data_structure_type from the current or historic API response to look inside the sensor information from the sensor catalog to find out information about the fields and unit types that are in the historic and current conditions data.
    Jeremy Wall
    @jeremywall-davis
    @/all API General Availability and Enforcement of Rate Limits:
    The WeatherLink v2 API Rate will be released for general availability on 2020-03-11; at which time the rate limits documented at https://weatherlink.github.io/v2-api/rate-limits will be enforced.
    Mark Crossley
    @mcrossley
    Yeah! Does that mean users will also be able to get their APIv2 key/secret via wl.com like APIv1 now?
    Jeremy Wall
    @jeremywall-davis
    @mcrossley yes, a new v2 API section and key generation button will be added to the user account page on WeatherLink.com
    Hendrik Röhm
    @HendrikRoehm
    @jeremywall-davis When will this button be available?
    Jeremy Wall
    @jeremywall-davis
    @HendrikRoehm this week
    Brian Hamilton
    @mewindy_twitter
    good news on the api keys becoming public in a few days :)
    soils164
    @soils164
    I'm struggling with getting the station ids (response is either 400 or 401), could someone post an example link of the request?
    Jeremy Wall
    @jeremywall-davis
    @soils164 401 means your API key is missing or unknown to the API or your api signature did not match what it should be. You can start a private chat with me and discuss what API calls you are sending and the parameters sent and I can guide you to correcting the issue.
    Jeremy Wall
    @jeremywall-davis


    As the primary engineer who monitors this chat room I will be on vacation March 12-18. I will be offline for the entire time.
    Any questions can be directed to my colleague Anthony @anthonyz-davis

    Anton Olsson
    @anton.j.olsson_gitlab
    Would it be possible to increase the limit on 24h the historic endpoint. Im looking into getting a few years of data. With the 300 calls per hour and 24 h at a time i would have to do it manually. Can you somehow export the historic data with the new api v2 datamodel? I know you can export the data from the portal but the data is structured differently.
    Anthony J Zepezauer
    @anthonyz-davis
    @anton.j.olsson_gitlab the 24 hour limit is based on the size of the responses, which can get quite large. Why would you need to do it manually? I would suggest building a delay between requests into your code that will keep you within the limits. You could get a year's worth of data in a little over an hour.
    Brian Hamilton
    @mewindy_twitter
    great to see you can now get the v2 api keys via your weatherlink.com account :)
    agmgr
    @agmgr
    In the v2 API, is there a difference between device-id (DID) and station-id? Looking at WeatherlinkLive, it seems my station-ID's are a single decimal. Should I use the device-id when making calls for historic data from the API? -TY
    Mark Crossley
    @mcrossley
    They are different, you need to use the station-id.
    Jeremy Wall
    @jeremywall-davis
    soils164
    @soils164
    I'm trying to convert the temperature data downloaded via the api into celcius. However, after conversion it is not the same as on the WL portal. For instance: "temp_out" on 2019-12-31 00:00:00 = 31.1, converted this would be -0.55 C. On the portal it shows -3.1 C. Did anyone manage to convert the data accurately?
    Jeremy Wall
    @jeremywall-davis
    What API call are you getting the data from /current or /historic? Also, what part of the WL web site are you seeing -3.1 C on? Is it the bulletin screen, the charting screen, the data table screen?
    soils164
    @soils164
    @jeremywall-davis I'm using the historic API call. On the WL website I'm looking at the data table screen.
    Jeremy Wall
    @jeremywall-davis
    @soils164 you didn't say which station?
    Jeremy Wall
    @jeremywall-davis


    If anyone had private chat questions with my colleague Anthony I'm sad to say he's no longer with Davis Instruments. Since I am not able to join those private chats to continue to answer your questions I'm afraid I have to ask anyone in this situation to start a new private chat with me and repost your questions. Sorry for the inconvenience.

    Jeremy Wall
    @jeremywall-davis
    @soils164 And can you also give me the exact Unix timestamp that's in the API response in the "ts" field.
    Hendrik Röhm
    @HendrikRoehm
    Hi, I am trying to read the wind and rain however it is not clear to me, which fields are appropriate: There are a lot of possible choices. What is the difference between rain_rate_last_mm and rainfall_mm for instance. How do I get the rain since the last measurement?
    And it would also be interesting to get to know the update intervall of the current endpoint data
    Any helps is appreciated. Thank you very much :)
    Jeremy Wall
    @jeremywall-davis

    @HendrikRoehm
    rain_rate_last_mm = the rain rate (mm per hour) that was observed during the reporting interval
    rainfall_mm = the depth of the rain collected (in mm) during the reporting interval

    If you are asking about how often current conditions are transmitted from the station to the WeatherLink service that depends on the type of device you have. A WeatherLink Live sends data every 60 seconds and EnviroMonitor is based on the cellular service plan of 5, 15, or 60 minutes. But if you are asking about what data is available via the API that depends on the subscription level. This documentation page https://weatherlink.github.io/v2-api/data-permissions discusses what data is available.

    Jeremy Wall
    @jeremywall-davis
    @soils164 I checked the timestamp 1577750400 as you mentioned and the API returns 31.1 F and 31.1 F when I set the WL website to Fahrenheit. When I set the WL web site to Celsius it shows me -0.5 C as expected. I don't see any sign of the -3.1 C that you mentioned seeing.
    Igor Usoltsev
    @IgorUsoltsev
    Hello dear team, how can I apply to get test API credentials to test your API and see potential integration possibilities with our service? We have a weather forecast startup
    Jeremy Wall
    @jeremywall-davis
    @IgorUsoltsev the API is intended for station owners and not the general public. Do you own a station?
    Igor Usoltsev
    @IgorUsoltsev
    I will ask my client for this data. So you have no test access so I can f.e. test your API with sample station data?
    Jeremy Wall
    @jeremywall-davis
    @IgorUsoltsev I'm afraid there's no sample data. The station owner can create a v2 API key and secret at www.weatherlink.com/account
    Hendrik Röhm
    @HendrikRoehm
    @jeremywall-davis I have a weatherlink live station where rainfall_last_15_min_mm is available but not rainfall_mm. I was wondering why this can happen.
    Jeremy Wall
    @jeremywall-davis
    What values are you seeing in the json?