Hello all at WeatherFlow! Today, I want to share with you some feedback (and questions / suggestions) about the REST API. This feedback comes directly from the following use case: I’ve developed an application (as a matter of fact it’s a plugin for a more “wide” application, but that does not chan…

[image] pierre: Why not to have an endpoint, similar to /observations/station/, to retrieve old data with the same “format” as /observations/station/? Do you have it in your backlog? Is it something realistic / feasible? Peter, congratulations: you are the first developer (to my knowledge) to…

I understand what you are asking. The data you receive from /observations/station/ is the data from /observations/device/ for the two main devices, except is also contains data that is calculated from historical records. You can create the same from the stored data. Remember, WeatherFlow has the s…

Hello @GaryFunk ! OK, so now, I’m sure I was definitely unclear, sorry… My main goal is to allow to import in my software old data stored by WF. For now, /observations/station/ doesn’t provides time_start and time_end parameters which allow to control the timeframe of the query. To import old data…

[image] pierre: my only way to do is to go with /observations/device/ which allow time_start and time_end parameters but doesn’t provide an “aggregated view” of the station. Correct. You have to create your own “aggregated view.” [image] pierre: What is the heuristic used by WF to publis…

[image] GaryFunk: That’s easy. Every station has a primary Air and a primary Sky. I will guess the primary is the first added of each. WeatherFlow uses only the primary in the “aggregated view.” Ha. Thanks for all @GaryFunk ! That was the information I haven’t. Just one last question - as you…

Generally it will be the one with the lowest device_id. However, since you are writing the code you can decide the rules. You can ask the user which device to use, pick the latest firmware or the one with the longest uptime.

Wow! Thanks @dsj ! So happy to know that you have already thought about it. I feel less alone :relieved: While waiting for the priority to climb up in your backlog, I will use the method you propose. But I’m impatient to have a full consistent API on this subject :slight_smile: If I have some othe…

Has there been any update to allow the user to change the primary device for Station Observations? I thought I might be able to exclude the first by changing its environment to “inside” but it was still reported in station observations (with observation suffix “xxxxx_indoor” )

Not at this time. It has been suggested that this may be available in the far future.

Thanks Gary. I’ll put in a support request to swap the order of the two airs.

[image] dsj: Peter, congratulations: you are the first developer (to my knowledge) to ask for this “station/observation timeseries” end point, which is something that we perceived as important, and has been on our featuer backlog, since Day 1. [image] [API] The ability to req…

Feedback (and question) about REST API for historical data use case

Developers

GaryFunk May 20, 2019, 6:19am 13

How soon might we expect this feature to come to testing?

Topic		Replies	Views
WeatherFlow REST API -- Station Observations Developers	10	1516	December 1, 2020
Historical Data - REST API Developers	2	583	June 25, 2021
REST API: my wishlist to Santa Claus Developers rest_api	13	1453	April 4, 2019
Federated time series data for a station? Developers	2	492	April 9, 2020
Access full history of data within graphs Feature Requests web , app , database , history , data-access	7	4404	October 14, 2018

Feedback (and question) about REST API for historical data use case

Related topics