# UDP sensor\_status 655871
**URL:** https://community.tempest.earth/t/udp-sensor-status-655871/23807
**Category:** Developers
**Tags:** tempest
**Created:** [February 18, 2024, 5:08pm UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807 "2024-02-18T17:08:19Z")
**Posts on this page:** 15
**Page:** 1
### Author:  [@Julian](https://community.tempest.earth/u/Julian)
#### Post date: [February 18, 2024, 5:08pm UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/1 "2024-02-18T17:08:19Z")
Hello, as of yesterday I’ve been receiving `"sensor_status":655871` in the UDP device status packets.
The Tempest app says “Sensor Status: Good” and the actual reported values — in both the app and UDP packets — seem to be sane.
The problem is a value of `655871` does line up with having `true` set for every single sensor failure: `0b10100000000111111111` (plus some extra bits set higher, which are ignored as per documentation). So software that respects the failed sensor readings from UDP is confused and thinks I have no valid readings.
---
### Author:  [@Julian](https://community.tempest.earth/u/Julian)
#### Post date: [February 18, 2024, 5:09pm UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/2 "2024-02-18T17:09:29Z")
Tempest firmware 173
Hub firmware 194
I’ve tried disconnecting / reconnecting the hub a few times.
---
### Author:  [@vinceskahan](https://community.tempest.earth/u/vinceskahan)
#### Post date: [February 18, 2024, 8:10pm UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/3 "2024-02-18T20:10:03Z")
Sounds like you need to open a ticket with @WFsupport
---
### Author:  [@Julian](https://community.tempest.earth/u/Julian)
#### Post date: [February 18, 2024, 9:29pm UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/4 "2024-02-18T21:29:31Z")
will do! (adding characters to make sufficient length to say so)
---
### Author:  [@wimleers](https://community.tempest.earth/u/wimleers)
#### Post date: [February 19, 2024, 10:11pm UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/5 "2024-02-19T22:11:14Z")
I’m seeing similar problems: [[Weatherflow Tempest] Bizarrely reporting 0ºC, even though the Tempest app does not · Issue #288 · naofireblade/homebridge-weather-plus · GitHub](https://github.com/naofireblade/homebridge-weather-plus/issues/288#issuecomment-1953205525).
---
### Author:  [@wimleers](https://community.tempest.earth/u/wimleers)
#### Post date: [February 22, 2024, 8:41am UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/6 "2024-02-22T08:41:50Z")
I’m seeing `sensor_status` `672255`. Created a support ticket too.
Note that over at [[Weatherflow Tempest] Bizarrely reporting 0ºC, even though the Tempest app does not · Issue #288 · naofireblade/homebridge-weather-plus · GitHub](https://github.com/naofireblade/homebridge-weather-plus/issues/288#issuecomment-1957325802), there now is a third person reporting sensor failures — but on a whole different level: no observations are being broadcast at all anymore.
I live in Belgium, and it looks like Julian and that third person both live in Silicon Valley.
---
### Author:  [@wcfieselerw](https://community.tempest.earth/u/wcfieselerw)
#### Post date: [March 21, 2024, 11:44pm UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/7 "2024-03-21T23:44:46Z")
Did you get a resolution to the problem of the status reporting all sensors failed? In the last couple days, I’ve had the same issue although data values for the sensors still appear valid. The phone app from WF doesn’t flag anything wrong. It’s as if WF decided to invert their logic on reporting sensor status via the REST interface. The firmware version of my Tempest is 156. The hub firmware is revision 194.
---
### Author:  [@Julian](https://community.tempest.earth/u/Julian)
#### Post date: [March 22, 2024, 12:19am UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/8 "2024-03-22T00:19:11Z")
No, I have not. I’ve bumped the thread with support a few times but have only heard that they’re still looking into it.
---
### Author:  [@wcfieselerw](https://community.tempest.earth/u/wcfieselerw)
#### Post date: [March 22, 2024, 12:52am UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/9 "2024-03-22T00:52:44Z")
Oops, I didn’t realize a response could be too short!
Thanks for responding. For now, I’ll simply invert my logic to avoid nuisance messages in my app.
Wayne
---
### Author:  [@rainer.pohle](https://community.tempest.earth/u/rainer.pohle)
#### Post date: [March 22, 2024, 4:11pm UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/10 "2024-03-22T16:11:51Z")
I have the same problem, but with a different value of 656383, because I use a Power Booster.
Tempest firmware 165
Hub firmware 194
it looks that the problem started with the new Hub firmware.
---
### Author:  [@Lux4rd0](https://community.tempest.earth/u/Lux4rd0)
#### Post date: [July 28, 2024, 3:40am UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/11 "2024-07-28T03:40:58Z")
Dragging this up a few months later - I, too, am getting 655871 even though my sensors are working as expected. Did you discover why that’s the case with your support tickets?
---
### Author:  [@Julian](https://community.tempest.earth/u/Julian)
#### Post date: [July 28, 2024, 6:28am UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/12 "2024-07-28T06:28:14Z")
Nope. Still an issue for me too.
---
### Author:  [@Julian](https://community.tempest.earth/u/Julian)
#### Post date: [March 10, 2025, 9:22pm UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/13 "2025-03-10T21:22:25Z")
Hey just wanted to follow up — I emailed support yet again, and this time they updated my hub to v212. I now get a `sensor_status` of 4 (“lightning disturber”) instead of 655871 (“every sensor is broken”). Tempest app still reporting “Sensor Status: Good”.
---
### Author:  [@ericwaynedavis](https://community.tempest.earth/u/ericwaynedavis)
#### Post date: [April 11, 2025, 12:23am UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/14 "2025-04-11T00:23:13Z")
Same here on firmware version 181. A bit annoying since I can’t find a good way to filter evt\_strike events that are caused by a disturber. Also, anyone know why firmware would not be the same everywhere? It seems control of upgrades is beyond our ability but why would they not push the same firmware across the entire network?
[Logs] [2025-04-10T23:54:28.132Z] DEBUG:root:msg: {‘serial\_number’: ‘ST-00126288’, ‘type’: ‘device\_status’, ‘hub\_sn’: ‘HB-00030739’, ‘timestamp’: 1744329267, ‘uptime’: 10648602, ‘voltage’: 2.658, ‘firmware\_revision’: 181, ‘rssi’: -57, ‘hub\_rssi’: -57, ‘sensor\_status’: 655871, ‘debug’: 0}
---
### Author:  [@ericwaynedavis](https://community.tempest.earth/u/ericwaynedavis)
#### Post date: [April 11, 2025, 12:26am UTC](https://community.tempest.earth/t/udp-sensor-status-655871/23807/15 "2025-04-11T00:26:50Z")
And another strange thing is that outside times when there is an actual thunderstorm going, like right now, I get evt\_strike messages about every 6-10 seconds. Now that I am in a thunderstorm, I’m not seeing any evt\_strike messages. Meanwhile, the app is showing correct data. Note I’m snooping the UDP broadcasts and not looking at the webhook messages.