Hi, I am running a new device that appears to be working well, but when I parse the device status, all of the 9 least significant bits are set to 1. The device is running FW version 173…has something major changed since 171? Raw Message: {‘serial_number’: ‘ST-00127092’, ‘type’: ‘device_status’, …

I am seeing the same thing on a unit running FW version 173. Getting the exact same sensor_status number. App doesn’t show any errors and unit seems to be functioning fine.

I’m also on device firmware v173, hub firmware v194. I’m willing to bet $1 on someone reversing the sense of all of the bits from “fail” to “working correctly”. I just installed a power booster and wanted to ensure it was working, so I wrote some Python code to decode the bits. Here is the output…

[image] dan_bob_spalding: I’m willing to bet $1 on someone reversing the sense of all of the bits from “fail” to “working correctly”. Hmmm - but only if every system worldwide with that firmware and equally all-good sensors showed the same value… All zeroes should be all bits zero per Weathe…

It might be new hardware + the new firmware versions as a combination. I have all new equipment purchased in January, 2024. Note that it may not be the software but the hardware reporting it in reverse as well, or the UDP packet generation is different from what the hub sends to the cloud. It is …

I’m receiving 511 during the day and 10751 during the evening: all sensors should be faulty, if I interpret the UDP API docs correctly. That can’t be possible obviously, since the device is working fine. { "serial_number": "ST-00008550", "type": "device_status", "hub_sn": "HB-00026574", "ti…

I think we should just all assume the sensor status reported is incorrect. As per my above thread, I still receive this kind of reply from customer support every time I check. Considering how long it’s been it’s clearly not a priority, so even if it gets fixed now, it could easily break again in th…

My system is up to v181 and all the bits are still on and the docs indicate that those bits set means failure of the sensor.

I believe it’s the hub version that’s emitting this — my hub is v212 (my Tempest is v181) and I only get an error bit on my lightning sensor, which customer support tells me is relatively expected.

My hub tells me its firmware version is v194 so that is a difference between our setups. Thanks!

Sensor Status bits?

Developers

Julian April 14, 2024, 11:58pm 5

Yes there are a good handful of people who’ve reported similar issues publicly. I started this thread on the topic when it started for me in February. I still have an open customer support issue in which I’m told “they’ll get back to me soon” every couple of weeks when I ask.

Topic		Replies	Views
UDP sensor_status 655871 Developers tempest	14	572	April 11, 2025
Tempest sensor_status field Developers tempest	22	1365	December 3, 2020
Undocumented or incorrect device_status value Developers tempest	1	391	November 10, 2023
Lightning sensor failed light-sensor , tempest	3	591	July 10, 2020
UDP API Documents Out of Date? Developers udp , tempest	4	186	October 22, 2024

Sensor Status bits?

Related topics