# \#websocket

**URL:** https://community.tempest.earth/tag/websocket/74.md

[Latest](https://community.tempest.earth/latest.md) · [Categories](https://community.tempest.earth/categories.md) · [Tags](https://community.tempest.earth/tags.md)

---

## [Announcements & Updates](https://community.tempest.earth/t/announcements-updates/1933)

<div class="topic-metadata">

**Author:** [@peter](https://community.tempest.earth/u/peter)\
**Replies:** 59\
**Last updated:** [April 29, 2026, 6:58pm UTC](https://community.tempest.earth/t/announcements-updates/1933 "2026-04-29T18:58:23Z")

</div>

The WeatherFlow PiConsole is a Python console that displays the data collected by a WeatherFlow Tempest or Smart Home Weather Station. The console uses either the WeatherFlow REST API and websocket service or the local U…

---

## [Websocket Stops Sending Data - No errors](https://community.tempest.earth/t/websocket-stops-sending-data-no-errors/26375)

<div class="topic-metadata">

**Author:** [@pickusj](https://community.tempest.earth/u/pickusj)\
**Replies:** 3\
**Last updated:** [January 10, 2025, 10:45pm UTC](https://community.tempest.earth/t/websocket-stops-sending-data-no-errors/26375 "2025-01-10T22:45:04Z")

</div>

When i open a websocket, data stops being sent after about 15 minutes. There is no errors being reported, that i can tell. Basically it just hangs. This happens everytime i start a websocket. Data does flow immediat…

---

## [WebSockets - only receiving an ack and a single message](https://community.tempest.earth/t/websockets-only-receiving-an-ack-and-a-single-message/26205)

<div class="topic-metadata">

**Author:** [@rkowieski](https://community.tempest.earth/u/rkowieski)\
**Replies:** 3\
**Last updated:** [December 31, 2024, 3:11pm UTC](https://community.tempest.earth/t/websockets-only-receiving-an-ack-and-a-single-message/26205 "2024-12-31T15:11:53Z")

</div>

I am new to WebSockets, but get the general concepts. I have a simple app where I am trying to use WebSockets rather than pulling from the API on an interval for updates. I am able to successfully open the connection, re…

---

## [WebSocket API issue with obs\_st messages](https://community.tempest.earth/t/websocket-api-issue-with-obs-st-messages/21078)

<div class="topic-metadata">

**Author:** [@tris](https://community.tempest.earth/u/tris)\
**Replies:** 11\
**Last updated:** [August 4, 2024, 6:37pm UTC](https://community.tempest.earth/t/websocket-api-issue-with-obs-st-messages/21078 "2024-08-04T18:37:50Z")

</div>

I’ve stumbled upon an interesting issue concerning the reception of obs\_st messages over the WebSocket API. If one opens a second concurrent connection and issues listen\_start for the same device ID, that connection wil…

---

## [Different lux observations in app and through Web Sockets API](https://community.tempest.earth/t/different-lux-observations-in-app-and-through-web-sockets-api/23157)

<div class="topic-metadata">

**Author:** [@morgan1](https://community.tempest.earth/u/morgan1)\
**Replies:** 2\
**Last updated:** [December 14, 2023, 3:38pm UTC](https://community.tempest.earth/t/different-lux-observations-in-app-and-through-web-sockets-api/23157 "2023-12-14T15:38:59Z")

</div>

I’m working with the web sockets API to retrieve data from a station I installed. Everything is working ok, except that the lux values in the weather flow app are different from what is reported via the web sockets API. …

---

## [WeatherFlow PiConsole](https://community.tempest.earth/t/weatherflow-piconsole/20083)

<div class="topic-metadata">

**Author:** [@peter](https://community.tempest.earth/u/peter)\
**Replies:** 1\
**Last updated:** [August 17, 2023, 8:06pm UTC](https://community.tempest.earth/t/weatherflow-piconsole/20083 "2023-08-17T20:06:00Z")

</div>

The WeatherFlow PiConsole is a Python console that displays the data collected by a WeatherFlow Tempest or Smart Home Weather Station. The console uses either the WeatherFlow REST API and websocket service or the local U…

---

## [LevityDash v0.2.0b1 - UI/UX Update](https://community.tempest.earth/t/levitydash-v0-2-0b1-ui-ux-update/18099)

<div class="topic-metadata">

**Author:** [@noblecloud](https://community.tempest.earth/u/noblecloud)\
**Replies:** 6\
**Last updated:** [December 26, 2022, 9:51pm UTC](https://community.tempest.earth/t/levitydash-v0-2-0b1-ui-ux-update/18099 "2022-12-26T21:51:54Z")

</div>

LevityDash A lightweight, desktop native, multi-source dashboard for macOS, Windows, and Linux The goal of LevityDash is to create a lightweight, modular, metrics dashboard with a drag-and-drop UI for easy cust…

---

## [Websockets Clarification](https://community.tempest.earth/t/websockets-clarification/17290)

<div class="topic-metadata">

**Author:** [@livysdad27](https://community.tempest.earth/u/livysdad27)\
**Replies:** 5\
**Last updated:** [May 1, 2022, 4:20am UTC](https://community.tempest.earth/t/websockets-clarification/17290 "2022-05-01T04:20:25Z")

</div>

Howdy, I was playing around with the Websocket API and am having a bit of a tough time understanding the docs. Specifically in the image below… What is the definition of device\_id and id. I am assuming that device…

---

## [Oauth2 Access Token](https://community.tempest.earth/t/oauth2-access-token/2126)

<div class="topic-metadata">

**Author:** [@peter](https://community.tempest.earth/u/peter)\
**Replies:** 39\
**Last updated:** [October 16, 2021, 7:30am UTC](https://community.tempest.earth/t/oauth2-access-token/2126 "2021-10-16T07:30:30Z")

</div>

Can anyone help me understand how you are meant to use an Oauth2 Access Token in an API/websocket request to access data from a non-public station?

---

## [Websocket rate limit exceeded](https://community.tempest.earth/t/websocket-rate-limit-exceeded/8422)

<div class="topic-metadata">

**Author:** [@peter](https://community.tempest.earth/u/peter)\
**Replies:** 18\
**Last updated:** [May 20, 2021, 2:07am UTC](https://community.tempest.earth/t/websocket-rate-limit-exceeded/8422 "2021-05-20T02:07:12Z")

</div>

@corrineb, over the last couple of weeks I have been noticing that websocket connections have been tending to fail far more frequently due to the rate limit being exceeded: {'status\_code': 5, 'status\_message': 'AUTHORI…

---

## [WS obs summary object precip fields](https://community.tempest.earth/t/ws-obs-summary-object-precip-fields/9773)

<div class="topic-metadata">

**Author:** [@jkf](https://community.tempest.earth/u/jkf)\
**Replies:** 1\
**Last updated:** [October 11, 2020, 7:58am UTC](https://community.tempest.earth/t/ws-obs-summary-object-precip-fields/9773 "2020-10-11T07:58:40Z")

</div>

I’ve read back through past posts and haven’t seen this discussed in awhile. Will the summary object in the obs events received via WS going to be documented or blessed for use? I noticed today the precip\_analysis\_type\_y…

---

## [Heads-up: Forthcoming changes to API (REST & WS)](https://community.tempest.earth/t/heads-up-forthcoming-changes-to-api-rest-ws/3601)

<div class="topic-metadata">

**Author:** [@dsj](https://community.tempest.earth/u/dsj)\
**Replies:** 22\
**Last updated:** [September 20, 2020, 10:16am UTC](https://community.tempest.earth/t/heads-up-forthcoming-changes-to-api-rest-ws/3601 "2020-09-20T10:16:50Z")

</div>

In support of some forthcoming changes to the way rain accumulation is calculated and presented in our apps, we will be pushing an update to the API next week. This message is purposely vague as to exactly what is changi…

---

## [Hub status from API](https://community.tempest.earth/t/hub-status-from-api/6472)

<div class="topic-metadata">

**Author:** [@peter](https://community.tempest.earth/u/peter)\
**Replies:** 12\
**Last updated:** [June 3, 2020, 5:40pm UTC](https://community.tempest.earth/t/hub-status-from-api/6472 "2020-06-03T17:40:55Z")

</div>

I think I know the answer, but does anyone know if there is a way of telling whether a hub is online or not using the REST API? There seems to be a websocket endpoint for this, but in my testing I was unable to get it to…

---

## [WS (web socket) API questions](https://community.tempest.earth/t/ws-web-socket-api-questions/4698)

<div class="topic-metadata">

**Author:** [@vinceskahan](https://community.tempest.earth/u/vinceskahan)\
**Replies:** 13\
**Last updated:** [November 18, 2019, 6:39pm UTC](https://community.tempest.earth/t/ws-web-socket-api-questions/4698 "2019-11-18T18:39:38Z")

</div>

I’m fiddling around with trying to duplicate my python UDP listener via the WS interface, mainly as a learning exercise, and had some questions… I see a development/personal-use key we can use that “has some limitatio…

---

## [Bug or Feature? Missing fields in Websocket AIR summary object](https://community.tempest.earth/t/bug-or-feature-missing-fields-in-websocket-air-summary-object/3695)

<div class="topic-metadata">

**Author:** [@peter](https://community.tempest.earth/u/peter)\
**Replies:** 2\
**Last updated:** [June 11, 2019, 9:10pm UTC](https://community.tempest.earth/t/bug-or-feature-missing-fields-in-websocket-air-summary-object/3695 "2019-06-11T21:10:46Z")

</div>

@dsj Not sure if this is a bug or a feature, but when a new station comes online and no lightning strikes have yet been detected, two fields are missing from the AIR summary object: strike\_last\_dist and strike\_last\_epoch.…

---

## [New fields in websocket messages](https://community.tempest.earth/t/new-fields-in-websocket-messages/3439)

<div class="topic-metadata">

**Author:** [@peter](https://community.tempest.earth/u/peter)\
**Replies:** 5\
**Last updated:** [May 3, 2019, 8:50pm UTC](https://community.tempest.earth/t/new-fields-in-websocket-messages/3439 "2019-05-03T20:50:26Z")

</div>

I haven’t looked in detail at the websocket messages recently, but noticed today that a lot more information is being sent compared to what is documented. For example, the documentation shows that the obs\_air message sho…

---

## [Websocket delay](https://community.tempest.earth/t/websocket-delay/2169)

<div class="topic-metadata">

**Author:** [@peter](https://community.tempest.earth/u/peter)\
**Replies:** 0\
**Last updated:** [September 8, 2018, 5:34pm UTC](https://community.tempest.earth/t/websocket-delay/2169 "2018-09-08T17:34:07Z")

</div>

Is it just me, or is anyone else noticing a delay in the arrival time of the Websocket packages today? Usually the Websocket packet arrives within a few seconds of the observation time, but today there seems to be a 20 s…
