Tempest api data project

This is my first attempt to access some data for my new Tempest.

Had a look at
https://github.com/WeatherFlow (perhaps there will be something here eventually)

**Perhaps there is a better way to do this, please let me know **

I only appear to be able to get “type”: “obs_sky”, but I am looking for wpi;d be under type=“obs_st” or type=“obs_air”

lists the results but I don’t appear to be able to change the results type

test API key limit?

I also tried the oauth option but I just get 404 not found.



"status": {

    "status_code": 0,

    "status_message": "SUCCESS"


"device_id": 25854,

"type": "obs_sky",

"source": "cache",

"summary": {

    "precip_total_1h": 0.0,

    "precip_accum_local_yesterday": 0.012043,

    "precip_analysis_type_yesterday": 0


"obs": [






















I would like to pull the last 30 days of data and calculate an absolute humidity to add to a chart.
Personally I am finding the charts vis WF a bit lacking as RH without temperature feels incomplete.
Also gives me a change to play with the API and understand what’s possible

If I understand correctly, you are using the /swd/rest/observations/device endpoint to get the latest device observation from the WF API. The API call you shared was getting the observations from device 25854 which is a Sky device (hence the type is obs_sky). If you want to get observations from a Tempest device (obs_st), or an Air device (obs_air), you need to change the device ID to an appropriate Tempest/Air ID. The format of the URL is:

https://swd.weatherflow.com/swd/rest/observations/device/[DEVICE_ID]?api_key=20c70eae-e62f-4d3b-b3a4-8586e90f3ac8 (obviously replace [DEVICE_ID] with the ID you need).

1 Like

I got that station ID from my tempest weather device webpage

(this is where the docs suggested I get the number from)

I also see in the cards ST-00015285 at the top left of each card but have not tried that number.

Do devices have multiple IDs?

Ah I understand. There is a difference between a Station ID and a Device ID. Your Station ID is 25854, but your Tempest Device ID is 83635. You should be able to see this on the web by clicking on Settings -> Stations -> [station name] -> status.

The API endpoint you are using is for Device IDs not Station IDs. Just by chance though, it seems that there is a Sky device out there that shares its Device ID with your Station ID (25854). That is why you are seeing obs_sky from the API. If you change the device ID to 83635, you will see the observations from your Tempest:



There is an API endpoint that works with Station IDs if you prefer though:


Note how the URL above has changed from /observations/device/ to /observations/station/ Both will return the same data, but the fields returned in the station endpoint are much more verbose.

1 Like

Well thanks for that…


Find a station_id (this is the id of your Station). The easiest way to do this is sign into you Smart Weather account using a browser and go to an observation list view for a Station. You should see a URL that includes a station_id that looks something like this.

You are right I was using the Station ID of my station with the Device API. :man_facepalming:
Funny that about the ID match. If this worked my next question would have been why the data doesn’t appear to match for me.


Becasue you helped so much already do you know how to adjust the “bucket_step_minutes”
This assumes I am correct when I think this means I am getting a datapoint every 180 minutes for the query?

right now it’s “bucket_step_minutes”: 180
for my project every 60 mins would be nice but it shouldn’t stop me.

thanks again

The bucket_step_minutes is limited based on the length of time between time_start and time_end. The longer that period, the longer the bucket_step_minutes has to be.

That being said I think there is an undocumented feature of the API that allows you to specify the bucket step length, as long as you don’t go over the maximum period. There are some details here: REST API: my wishlist to Santa Claus

Thanks, for that.

I will take 30 minutes over 28 days

now that I have the base data comes the hard part, generating the new data and graphing the whole thing

1 Like