UDP API Documents Out of Date?

Developers
,
1

Hello, I have been implementing some code to parse and process UDP packets from my Tempest, and the documentation mentions the following for the radio status in radio_stats:

Radio Status (0 = Radio Off, 1 = Radio On, 3 = Radio Active, 7 = BLE Connected)

However, I am getting this packet:

{
  "serial_number":"HB-00165152",
  "type":"hub_status",
  "firmware_revision":"309",
  "uptime":369830,
  "rssi":-58,
  "timestamp":1729483645,
  "reset_flags":"POR",
  "seq":18671,
  "radio_stats":[28,1,0,2,60272],
  "mqtt_stats":[2,4],
  "freq":906000000,
  "hw_version":2,
  "hardware_id":0
}

Which appears to have an undocumented radio status: "radio_stats":[28,1,0,2,60272]

Is there a v179 API somewhere? Or have I misread the docs?

2 Likes
2

a radio status of 2 is a bit strange indeed.
If I were an engineer, this would be a bit value.
Like the last bit indicating radio on/off , the second last bit indicating radio activity and the third last bit indicating ble on.
A value of 2 would then be, radio is off, but activity.

3

Yeah, it just doesn’t make sense as a value based on any theory about bit masks. If that is what they’re doing, then it would be great if they could document the bits so that they can be extracted and used individually.

2 Likes
4

is this value of 2 reproducable, or was it just a glitch? i seems odd that the radio is active and off.

5

I am not doing any kind of analysis to see what states I am getting over time, but what little I have observed, I have never received a hub status that didn’t have this value for the radio state.