Telemetry messages are messages that are sent by the IoT device to the cloud platform every given time, or when a certain event happens. More information is available in the API documentation.
For HDBaseT devices, both the TX and RX of each link can send telemetry messages. Each device can send data about itself (noted with the "local" prefix) and about the remote device (noted with the "remote" prefix). The server will couple the two devices based on their chip_ids.
In order for CloudOS to display HDBaseT related information in a proper way, and send alerts and notifications based on the received data, HDBaseT products must strictly follow the following common fields and data types. Additional fields can be sent if required.
Note: Every telemetry message should include the full DTO (see below).
Periodic Telemetry Messages
Each device must send a telemetry message every 5 minutes or less to notify the server that it is online. If no messages were received by the server for over 5 minutes, the server assumes that the device is offline, and will indicate it to the end-user.
For HDBaseT devices, the server will use the mse, max_err and retransition rate to indicate if the link is good, or if IT admins should be notified of an error.
"telemetries":
{
"status": "online", //Note that this is a mandatory field for every message
"local_gender": "TX",
"remote_gender": "RX",
"port_hdbt_cablelength": 15,
"local_system_chip_id": "04:04:ea:4c:49:fa",
"remote_system_chip_id": "04:04:ea:4c:4a:f5",
"local_hdbt_mse_ch_a_db": -20.169,
"local_hdbt_mse_ch_b_db": -19.359,
"local_hdbt_mse_ch_c_db": -20.763,
"local_hdbt_mse_ch_d_db": -20.631,
"local_hdbt_retransrate": 0,
"remote_hdbt_mse_ch_a_db": -14.735,
"remote_hdbt_mse_ch_b_db": -14.311,
"remote_hdbt_mse_ch_c_db": -13.124,
"remote_hdbt_mse_ch_d_db": -14.436,
"remote_hdbt_retransrate": 8087121,
"local_hdbt_max_err_ch_a_db": 0.42188,
"local_hdbt_max_err_ch_b_db": 0.5,
"local_hdbt_max_err_ch_c_db": 0.42969,
"local_hdbt_max_err_ch_d_db": 0.40625,
"local_hdbt_device_vendor_id": 0,
"remote_hdbt_max_err_ch_a_db": 0.9375,
"remote_hdbt_max_err_ch_b_db": 1.0703,
"remote_hdbt_max_err_ch_c_db": 1.2344,
"remote_hdbt_max_err_ch_d_db": 1.0703,
"remote_hdbt_device_vendor_id": 0
}
Event-Based Telemetry Messages
Event-based telemetry messages should be sent as soon as an event triggers to notify the server of the change. The list below is a mandatory list that ensures that the server is up to date with the most recent information. Additional events can be added as required.
Startup Event
Following a successful registration of the device to the service, or following a software or hardware reset, the device should notify the server with its full status.
When the HDBaseT link is disconnected, immediate notification should be sent to the server, which will alert the end-user. As with all other telemetry messages, the full DTO is required, but these fields below are the relevant fields for the event -
The link status fields (MSE, Max_err etc.) are sent to the server as part of the periodic telemetry messages. However, if a change to these values happens, the device can choose to immediately notify the server.
5V at TX Side (Source Connect/Disconnect)
When a source connects or disconnects to the HDBaseT transmitter, the device should send update for these fields -