Has anyone noticed that sometimes the Tempest observation data is missing fields? For example, I just received: "status":{"status_code":0,"status_message":"SUCCESS"},"device_id":XXXXX,"type":"obs_st","source":"cache","summary":{"pressure_trend":"steady","strike_count_1h":0,"strike_count_3h":0,"pre…

We’d have to see your device_status and hub_status messages I think, to look for the sensor status. I notice the voltage looks pretty low which might be part of the issue. My recollection the Tempest starts shedding sensors as the voltage gets low on the unit. There was a long post a month or two …

Not sure I follow, my devices is at 2.4v according to the post says I’m in Mode 2 and nothing is disabled? Edit: Also if it’s battery related and not a bug, seems odd that rebooting the tempest fixes it?

Hi @dmeglio , I think there may be some misunderstanding over what observations the nulls correspond to. The first null (index 4 in the obs array; counting starts from 0) corresponds to the wind direction. The wind direction is null because the wind speed is zero. The direction is undefined if the wi…

Yeah I see that now, unfortunately it was because obs_st is undocumented in the WebSocket API… I guess I was supposed to look at the REST API to get the documentation… Anyway, you’re correct about the rain but that doesn’t seem to be the case about wind speed. Right now wind speed is 0 and I get a …

Yea the WeatherFlow team are aware that the documentation for the Websocket is missing, but I think that they are so snowed under at the moment it’s not their top priority. It is interesting that the wind direction is only null sometimes. I wonder whether it is null only when the average 1 minute w…

[image] peter: It is interesting that the wind direction is only null sometimes. I wonder whether it is null only when the average 1 minute wind speed is truly zero, whereas other times the average 1 minute windspeed is very light and rounds to 0.0, but the direction is then defined. It was r…

I’m not sure I know the answer I’m afraid. There is some discussion in this thread: Calculate wind vector-direction and this thread: Wind Direction when winds are calm should not be zero , but I don’t know whether any changes were ever made. As Gary said though, null is definitely a valid value, so t…

[image] dmeglio: And as a note, the article about the battery level changes doesn’t mention the wind sensor ever being disabled. Agree, but it does say the sensor sample period can back off to greater than 60 seconds, so you have a chance of there being no wind reading in a particular obs_st.…

Possible Bug - WebSocket API Missing Data Sometimes

Developers

vinceskahan August 23, 2020, 5:22pm 3

Here it is - Tempest data collectionn during low battery conditions

Topic		Replies	Views
Issue with live wind readings Third-Party Integrations	3	2337	December 30, 2021
Why is the API returning different observations data? Developers api , tempest , observation	6	366	November 20, 2023
Web Socket Retrieving Incorrect Data Developers tempest	5	297	February 9, 2024
Tempest Wind Sensor Failed Tempest Owners	34	2862	October 24, 2020
Only Wind speed/dir on windrose displaying	9	500	November 25, 2020

Possible Bug - WebSocket API Missing Data Sometimes

Related topics