### Payload Structure and Example Message

Source: https://doc.mocreo.com/faq/general/device/hub/mqtt-topic

Defines the JSON structure for messages, including fields for node status, battery level, signal strength, and probe status. Also provides an example of a typical message.

```json
{
    "found": true,                    // Node status: true: Node online, false: Node offline
    "battery": 72,                   // Battery level (0-100%)
    "signal": -15,                   // Signal strength (dBm)
    "probe": 1                      // Node probe status: 1: probe connected, 0: probe disconnected
}
```

```json
{
    "found": true,
    "battery": 72,
    "signal": -15,
    "probe": 1
}
```

--------------------------------

### Payload Structure and Field Descriptions

Source: https://doc.mocreo.com/faq/general/device/hub/mqtt-topic

Details the structure of the data payload received for node status updates, including field descriptions and an example.

```APIDOC
## Payload Structure and Field Descriptions

### Description
This section describes the structure and fields of the data payload that represents the current status of a node.

### Payload Structure
```json
{
    "found": true, 
    "battery": 72, 
    "signal": -15, 
    "probe": 1 
}
```

### Field Descriptions
*   **found** (boolean) - Current online status of Node. `true` indicates the Node is online, `false` indicates the Node is offline.
*   **battery** (integer) - Battery level percentage (0-100).
*   **signal** (integer) - Signal strength in dBm.
*   **probe** (integer) - Node probe status. `1` indicates the probe is connected, `0` indicates the probe is disconnected. This field may not be present in all payloads.

### Example Message
```json
{
    "found": true,
    "battery": 72,
    "signal": -15,
    "probe": 1
}
```
```

--------------------------------

### MQTT Integration

Source: https://doc.mocreo.com/faq/general/server/developer-integration-options

Configure the H5Pro Hub to act as an MQTT client, publishing data to your own MQTT broker. Refer to topic definitions for correct channel subscriptions.

```APIDOC
## MQTT (H5Pro Hub as Client)

### Description
Allows the H5Pro Hub to function as an MQTT client, enabling it to publish data to an external MQTT broker. Developers should consult the provided MQTT topic definitions to ensure proper subscription to relevant data channels.

### Method
N/A (Configuration)

### Endpoint
N/A (Broker connection details configured within H5Pro Hub)

### Parameters
N/A

### Request Example
N/A

### Response
N/A (Data is published to an external broker)
```

--------------------------------

### Node Configuration Query Request and Response Topics/Payloads

Source: https://doc.mocreo.com/faq/general/device/hub/mqtt-topic

Outlines the MQTT topics and message formats for querying node configuration. The request topic is `mocreo/<hub sn>/node/<node id>/config/get` with an empty JSON object as the message. The response topic is `mocreo/<hub sn>/node/<node id>/config`, returning device model and unit information.

```json
{}
```

```json
{
    "model": "LS1",                    // Device model
    "units": {                       // Unit information
        "battery": "%",
        "signal": "dBm",
        "temperature": "℃",
    }
}
```

```json
{
    "model": "LS1",
    "units": {
        "battery": "%",
        "temperature": "℃",
        "signal": "dBm"
    }
}
```

--------------------------------

### OpenAPI Schema

Source: https://doc.mocreo.com/faq/general/server/developer-integration-options

Retrieve the full public OpenAPI schema to discover available endpoints, authentication methods, and understand request/response formats.

```APIDOC
## GET /v1/public/openapi

### Description
Provides the full public OpenAPI schema, allowing developers to explore available endpoints, authentication methods, sample requests, and response formats.

### Method
GET

### Endpoint
https://api.mocreo.com/v1/public/openapi

### Parameters
#### Query Parameters
None

### Request Example
None

### Response
#### Success Response (200)
- **schema** (object) - The OpenAPI schema definition for the API.
```

--------------------------------

### Node Dynamic Information Synchronization Topic

Source: https://doc.mocreo.com/faq/general/device/hub/mqtt-topic

Defines the MQTT topic used for synchronizing real-time status information of a Node. The topic is `mocreo/<hub sn>/node/<node id>/state`. This topic is published by the Hub device and subscribed to by third-party servers for monitoring purposes.

```mqtt
mocreo/<hub sn>/node/<node id>/state
```

--------------------------------

### Node Measurement Data Reporting Topic and Payload

Source: https://doc.mocreo.com/faq/general/device/hub/mqtt-topic

Defines the MQTT topic for reporting node measurement data and the JSON payload structure. The topic is `mocreo/<hub sn>/node/<node id>/data`, published by the Hub and subscribed to by third-party servers. The payload includes measurement details like ID, timestamp, model, and temperature.

```json
{
    "measureId": 1,           // Measurement data counter
    "timestamp": 1760682172,  // Timestamp when Hub received data (Unix timestamp)
    "model": "LS1",             // Node device model
    "temperature": 2850       // Temperature data (actual temperature = value/100, unit: Celsius)
}
```

```json
[
    {
        "measureId": 1,
        "timestamp": 1760682172,
        "model": "LS1",
        "temperature": 2850,
    }
]
```