JSON Array and MQTT Temperature-Control Access
This page is organized from an existing operations manual as an online operations reference. Operations marked as expected or not executed in the original must still be verified against the actual environment.
Verify item by item the send/receive, independent properties, history, and stop/recovery specified in this guide; after the send/receive, separately check the current publish synchronization.
Before starting: you have product, device, model, publish, control, and history permissions; the local application, single-node FMQ, and FMQX Web are available; and the connection parameters for this device have been obtained
Before You Start
This guide uses MQTT with JSON array to verify temperature reporting, setpoint control, independent status reporting, historical data, and stop/recovery.
The first-time configuration screenshots follow the original tutorial; this round reuses the retained product, device, and session. The connection parameters and existing subscriptions are read-only checks performed after the send/receive ended; nothing was re-imported, re-saved, or re-subscribed.
This round's samples came first, and the current publish synchronization supplementary check came after; the two pieces of evidence are described separately. A full business re-verification after the current publish is still pending, so do not claim that this draft has been fully accepted.
FMQX Web is used to demonstrate device send/receive and execution replies; whether the physical device actually actuates still needs confirmation on the device side.
Replace These Parameters Before Copying the Templates
The code in this guide uses plain template names; the screenshots retain the actual historical resources. Complete the following checks before saving as a UTF-8 file or sending a message.
- A JSON array element id is a property identifier and stays the same for the same property; only modify value, and do not change the property id for each message.
- temperature and setpoint are the template property identifiers for temperature and setpoint temperature; they can be kept when generating a Thing Model for the first time, but must be replaced with the real identifiers of that product when reusing an existing product, and all messages and initialState keys must be updated accordingly.
- demo-device is the Device Number template. Replace the device number in clientId, the device number in every send/receive topic, and the clientId of TCP reporting together with the platform's device number for this device; the product ID and tenant ID in the MQTT identity must also be replaced with the current device connection parameters.
- The host, port, and listen direction in the connection file must be changed to the actual addresses of the current environment; 127.0.0.1 means the local machine running FMQX. When MQTT is involved, also check the product ID, username, subscription topics, and responseRoute; the password is entered securely only on the connection page.
- Group, session, and subscription ids are internal references of the import file; if renaming is needed, groupId must match the corresponding group id. Check before importing, and do not create a connection with the same name again on a retained session.
- The code blocks are customer templates rewritten from existing password-free assets or original code; this version of the template has not yet been proven to import successfully. Historical screenshots, send times, and the scope of business passes still follow the records of each step; do not treat template names as the actual resource names in old evidence.
1. First-Time Creation and Configuration Example
If the resources of this guide already exist, reuse them directly without recreating. The following eight steps retain the screenshots and boundaries of the original first-time configuration.
Object sample used by the wizard to extract fieldsjson
{
"temperature": 20,
"setpoint": 30
}Used only for the wizard to generate two fields; formal device reporting uses the bare array below. Replaceable customer template names are used here; check against the replacement list in this section before importing or sending.
1. First-Time Configuration · Example: Create the Array Temperature-Control Product
Location: IoT*→Device Access→*Access Source Steps: Select New Product, fill in FastBee_数组温控, and enter Collection Fields.

This image retakes the creation entry; creation was not submitted repeatedly, and subsequent devices and history follow the resources of this guide.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Access Source | Create a new independent product for this guide; re-verification does not create it again. Required · Fill in: New Product |
| Product Name | Give this kind of temperature-control device a concise business name. Required · Fill in: FastBee_数组温控 |
Expected result (not executed): as shown in the historical screenshot: this guide's independent product; re-verification directly uses product 877 without recreating. Risk and recovery: stop repeated commands, check this device's MQTT parameters, the formal JSON array format, model identifiers, and subscriptions; after recovery, report the new state first.
2. First-Time Configuration · Example: Generate Fields from a JSON Object Sample
Location: Device Access*→Collection Fields→*Generate Fields from a JSON Sample Steps: Expand the sample area, fill in the object sample below, and click Parse and Preview.

The retake reproduces the actual object-sample path and did not recreate the product or device; formal device reporting switches to a bare array.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Wizard JSON Sample | First extract the two models with the object sample; after creation, change the data format to JSON array, and formal reporting uses a bare array. Required · Fill in: {"FastBee_temperature":20,"FastBee_setpoint":30} |
Expected result (not executed): as shown in the historical screenshot: the retake reproduces the actual object-sample path and did not recreate the product or device; formal device reporting switches to a bare array.
3. First-Time Configuration · Example: Check the Two Collection Fields
Location: Device Access*→*Collection Fields Steps: Check the identifiers, integer type, ℃, and JSON paths.

The two properties correspond to FastBee_temperature and FastBee_setpoint; this image is a separate retake of the field table.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Fields, Types, and Paths | Generate two integer properties, temperature and setpoint. Required · Fill in: FastBee_temperature/FastBee_setpoint; integer; ℃ |
Expected result (not executed): as shown in the historical screenshot: the two properties correspond to FastBee_temperature and FastBee_setpoint; this image is a separate retake of the field table.
4. First-Time Configuration · Example: Fill in the Independent Device Identifier
Location: Device Access*→*Add Device Steps: Fill in this guide's Device Identifier and Device Name, then enter the access overview.

Device number FastBee_ArrayMQTT_Tutorial_01; subsequent MQTT identity and topics must correspond to it.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Device Identifier | Both the MQTT identity and topics use this device number. Required · Fill in: FastBee_ArrayMQTT_Tutorial_01 |
| Device Name | Both the platform and FMQX use a clear business name for locating. Required · Fill in: FastBee_数组温控 |
Expected result (not executed): as shown in the historical screenshot: device number FastBee_ArrayMQTT_Tutorial_01; subsequent MQTT identity and topics must correspond to it.
5. First-Time Configuration · Example: Check the Initial Access Overview and Create
Location: Device Access*→*Access Overview Steps: Check 1 device, 2 fields and finish the creation.

This stage genuinely shows JSON/MQTT, not yet the formal JSON array; continue modifying the format after creation.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Access Overview | The wizard starts with JSON/MQTT, one device, and two fields; change to the formal format in the next step. Required · Fill in: 1 device, 2 fields; initial JSON/MQTT |
Expected result (not executed): as shown in the historical screenshot: this stage genuinely shows JSON/MQTT, not yet the formal JSON array; continue modifying the format after creation.
6. First-Time Configuration · Example: Switch to the Formal JSON Array and MQTT
Location: Product Management*→Array Temperature Control→*Product Information Steps: Select JSON Array for Data Format, select MQTT for the transport protocol, and save.

Formal protocol JSON_ARRAY/MQTT; the image has a post-save toast and a gray background, and the data format is still readable.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Data Format | This guide's formal format is JSON array; do not keep the initial JSON object format. Required · Fill in: JSON Array |
| Transport Protocol | The product uses MQTT; the underlying transport in the FMQX import file is TCP. Required · Fill in: MQTT |
| Network Type | Keep this guide's actual WIFI setting; it is not the TCP/UDP transport choice. Required · Fill in: WIFI |
Expected result (not executed): as shown in the historical screenshot: formal protocol JSON_ARRAY/MQTT; the image has a post-save toast and a gray background, and the data format is still readable.
7. First-Time Configuration · Example: Complete the Writable Setpoint and History Parameters
Location: Product Management*→Function Definition→*Setpoint Temperature Steps: Fill in Setpoint as the English name, uncheck Read-only Data, enable History Storage, and click Modify.

Setpoint 16~35℃, step 1; the old required-field hint is still present in this image, meaning it is pending submission after completion, and it cannot be treated as a save-success image. The final save is verified by the model record and downlink verification.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Model Translation | Fill in the required English names, then click Modify. Required · Fill in: Temperature/Setpoint |
| Model Identifier | Must match the array element ids verbatim; the id is not a message number. Required · Fill in: FastBee_temperature/FastBee_setpoint |
| Model Category | Both the reading and the writable setpoint are properties. Required · Fill in: Property |
| Read-only Data | Temperature checked; setpoint unchecked to provide a control entry. Required · Fill in: Temperature checked; setpoint unchecked |
| History Storage | Enabled for both properties, recording subsequent independent state reports. Required · Fill in: Checked |
| Chart Display/Real-time Monitoring | Temperature on, setpoint off; check the read-only linkage after saving. Required · Fill in: Temperature on; setpoint off |
| Share Permission | Demoed within this tenant; sharing is not opened. Required · Fill in: Unchecked |
| Integer Range, Unit, and Step | Temperature -40~100℃; setpoint 16~35℃; step 1. Required · Fill in: Temperature -40~100; setpoint 16~35; ℃; 1 |
| Modify/Cancel | Complete the required fields, then Modify to save; Cancel does not submit. Required · Fill in: Modify |
Expected result (not executed): as shown in the historical screenshot: setpoint 16~35℃, step 1; the old required-field hint is still present in this image, meaning it is pending submission after completion, and it cannot be treated as a save-success image. The final save is verified by the model record and downlink verification.
8. First-Time Configuration · Example: Save the Read-only Temperature and Range
Location: Product Management*→Function Definition→*Temperature Steps: Fill in Temperature, keep read-only and history, set -40~100℃ with step 1, and click Modify to save.

Temperature read-only, history enabled, chart and real-time monitoring enabled; the formula is left empty.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Model Translation | Fill in the required English names, then click Modify. Required · Fill in: Temperature/Setpoint |
| Read-only Data | Temperature checked; setpoint unchecked to provide a control entry. Required · Fill in: Temperature checked; setpoint unchecked |
| History Storage | Enabled for both properties, recording subsequent independent state reports. Required · Fill in: Checked |
| Chart Display/Real-time Monitoring | Temperature on, setpoint off; check the read-only linkage after saving. Required · Fill in: Temperature on; setpoint off |
| Share Permission | Demoed within this tenant; sharing is not opened. Required · Fill in: Unchecked |
| Integer Range, Unit, and Step | Temperature -40~100℃; setpoint 16~35℃; step 1. Required · Fill in: Temperature -40~100; setpoint 16~35; ℃; 1 |
| Calculation Formula | This example uses integers directly without formula conversion. Optional · Fill in: Leave empty |
| Modify/Cancel | Complete the required fields, then Modify to save; Cancel does not submit. Required · Fill in: Modify |
Expected result (not executed): as shown in the historical screenshot: temperature read-only, history enabled, chart and real-time monitoring enabled; the formula is left empty.
2. Reuse and Check the Device Session
**First-time import configuration template (no password)**json
{
"schemaVersion": 3,
"groups": [
{
"id": "tutorial_array_mqtt_group",
"name": "数组教程",
"sortOrder": 54,
"isSystem": false
}
],
"sessions": [
{
"id": "array_mqtt_tutorial",
"groupId": "tutorial_array_mqtt_group",
"name": "数组温控",
"protocol": "MQTT",
"transport": "TCP",
"host": "127.0.0.1",
"port": 1883,
"mqttProtocolVersion": "3.1.1",
"clientId": "S&demo-device&877&1",
"username": "admin",
"autoReconnect": false,
"qos": 1,
"subscriptions": [
{
"id": "platform_downlink",
"topic": "/877/demo-device/function/get",
"qos": 1,
"active": true
},
{
"id": "legacy_default",
"topic": "S&demo-device&877&1/function/get",
"qos": 1,
"active": false
}
],
"jsonDevice": {
"format": "JSON_ARRAY",
"responseRoute": "/877/demo-device/property/post",
"initialState": {
"temperature": 29,
"setpoint": 30
}
}
}
]
}This round did not re-import; the password is obtained by authorized personnel from the device connection parameters and entered securely, and is not written into the manual. Replaceable customer template names are used here; check against the replacement list in this section before importing or sending.
9. First-Time Configuration · Example: Import This Guide's Session
Location: FMQX Web*→Configuration File→*Import Configuration Steps: On first use, open the import entry and select the configuration file; if this guide's session already exists, reuse it directly.

protocol is MQTT and transport is TCP; after the first import, securely fill in this device's Password and save.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Import Configuration | Import the UTF-8 JSON below that contains no password. Required · Fill in: 数组教程/数组温控 |
Expected result (not executed): the historical entry image is used to show the location; this session's parameters are checked separately in the next step. Risk and recovery: stop repeated sending, check this guide's device identity, data format, and target address; after reconnecting, independently report the current status first, then decide whether to control again.
10. Check the Current Connection Parameters
Location: FMQX Web*→This Guide's Session→*Connection Configuration Steps: Open the connection configuration and check the name, address, port, and device identity.

Connection parameters of this guide's retained session
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Connection Name | Identifies this guide's retained session. Required · Fill in: per the deployment plan · Example: FastBee_数组温控 |
| Host / IP | Fill in FMQ's MQTT entry; use 127.0.0.1 on the same machine. Required · Fill in: per the deployment plan · Example: 127.0.0.1 |
| Port | This guide's plain MQTT TCP listen port. Required · Fill in: per the deployment plan · Example: 1883 |
| Client ID | Use this device's fixed connection identity; do not replace it randomly. Required · Fill in: per the deployment plan · Example: S&FastBee_ArrayMQTT_Tutorial_01&877&1 |
| Username | Obtained from the same device's connection parameters. Required · Fill in: per the deployment plan · Example: admin (subject to this device's parameters) |
| Password | After the first import, securely fill in this device's password and save; it is not written into the configuration or the manual. Required · Fill in: per the deployment plan · Example: This device's credential, not echoed |
| MQTT Version | 3.1.1 verified in this guide. Required · Fill in: per the deployment plan · Example: 3.1.1 |
| Auto Reconnect | Off; stop and recover manually per the tutorial. Required · Fill in: per the deployment plan · Example: false |
| Session Name | Locate by this guide's name to avoid mixing in other sessions. Required · Fill in: FastBee_数组温控 |
| Address and Port | This round's local FMQ entry; for other environments, provided by the administrator. Required · Fill in: 127.0.0.1:1883 |
| Device Identity | Must correspond to this guide's product and device. Required · Fill in: S&FastBee_ArrayMQTT_Tutorial_01&877&1 |
11. Check the Existing Downlink Subscriptions
Location: FMQX Web*→This Guide's Session→*Subscription Panel Steps: Expand the subscription panel and check the existing topics and QoS one by one.

Downlink subscription topics and QoS of this guide's device
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Downlink Subscription Topic | The correct downlink topic is enabled. Required · Fill in: per the deployment plan · Example: /877/FastBee_ArrayMQTT_Tutorial_01/function/get |
| Wrong Default Topic | The automatic default entry is retained but active=false; do not treat the two unsubscribe buttons as proof of enablement. Required · Fill in: per the deployment plan · Example: S&FastBee_ArrayMQTT_Tutorial_01&877&1/function/get; active=false |
| QoS | Reporting and subscription are configured as 1; the card for the actual downlink received shows 0. Required · Fill in: per the deployment plan · Example: Report 1; downlink actually received 0 |
| Platform Downlink Topic | Platform control commands are sent to this topic. Required · Fill in: /877/FastBee_ArrayMQTT_Tutorial_01/function/get |
| Legacy Default Topic | Do not treat the legacy default topic as this guide's platform downlink entry. Required · Fill in: S&FastBee_ArrayMQTT_Tutorial_01&877&1/function/get; disabled |
| Subscription QoS | Check against the existing list. Required · Fill in: 1 |
12. Connect This Guide's Device Session
Location: FMQX Web*→*This Guide's Session Title Bar Steps: Click Connect and wait for Connected.

Restore this guide's independent device session
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Session | Connect only this guide's retained session. Required · Fill in: FastBee_数组温控 |
3. Report Ten Samples from 61 to 70
First complete messagejson
[
{"id":"temperature","value":61},
{"id":"setpoint","value":30}
]After that, only change the temperature in sequence from 61 to 70, keeping the setpoint at 30; the array element ids stay unchanged. Replaceable customer template names are used here; check against the replacement list in this section before importing or sending.
13. Prepare the First 61/30 Sample
Location: FMQX Web*→This Guide's Session→*Send Content Steps: Fill this section's first complete message into the send box.

Independent property reporting: 61, 30
Screenshot Key Points
| Field / Control | Description |
|---|---|
| First Message | The complete JSON must not omit the top-level structure or the device identity. Required · Fill in: [ {"id":"FastBee_temperature","value":61}, {"id":"FastBee_setpoint","value":30} ] |
| Reporting Topic | The reporting entry for this device's properties and demo replies. Required · Fill in: /877/FastBee_ArrayMQTT_Tutorial_01/property/post |
14. Send and Check the Ten Temperature Samples
Location: FMQX Web Send Content; platform device details*→*Running Status Steps: Send the ten samples with temperatures 61 to 70 and setpoint 30 in sequence, then view this guide's device Current Value.

Real-time values after reporting ten temperatures 61 to 70
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Current Value | Comes from the device's independent property reporting; do not substitute a pending slider or a reply. Required · Fill in: per the deployment plan · Example: 32; final 34 |
| Temperature Sequence | The setpoint stays at 30; the array element ids are fixed to the corresponding property identifiers, and only the temperature value is changed in sequence. Required · Fill in: 61, 62, 63, 64, 65, 66, 67, 68, 69, 70 |
| Sample Time | Shanghai time; record a new window during re-verification. Required · Fill in: 2026-10-15 23:20:24 ~ 2026-10-15 23:20:48 |
The current value only shows the last state; whether the ten samples are complete must also be checked line by line against the actual history later.
4. Deliver 32 and Report Independently
15. Deliver Target 32
Location: Platform device details*→Running Status→*Setpoint Steps: Adjust the setpoint target to 32, check the overlay, and send once.

Setpoint 32℃ pending delivery
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Pending Target | Check the overlay; do not treat the current value as the pending target. Required · Fill in: 32 |
16. Check That the 32 Command Was Actually Received
Location: FMQX Web*→This Guide's Session→*Receive Records Steps: Expand the 32 command and check the target value, message id, and message structure.

Device actually received setpoint 32
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Actual Receive Record | Check the correct topic, command id, and the target value in the params array. Required · Fill in: per the deployment plan · Example: 32/34; 143 bytes |
| This Command id | The subsequent demo reply must correspond to the same id. Required · Fill in: 80d5d43805034ced803b0e869850b99c |
| Target Value | Follow the message received by the device. Required · Fill in: 32 |
17. Check the 32 Demo Reply
Location: FMQX Web*→This Guide's Session→*Send Records Steps: Expand the demo reply with the same id and check the success code, target value, and execution count.

Same-id reply, setpoint 32, 3 cumulative executions
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Demo Auto-reply | Check the same id, code 200, data, request summary, and actual execution count; each increment is 1, which does not prove physical actuation. Required · Fill in: per the deployment plan · Example: 32: 2→3; 34: 3→4 |
| Execution Count | Use this round's actual baseline; do not treat the cumulative value as the number of executions this time. Required · Fill in: 2 → 3 |
| Command id | Same as the actual receive record. Required · Fill in: 80d5d43805034ced803b0e869850b99c |
Independent 29/32 property reportingjson
[
{"id":"temperature","value":29},
{"id":"setpoint","value":32}
]This is a new property message, checked separately from the downlink demo reply. Replaceable customer template names are used here; check against the replacement list in this section before importing or sending.
18. Independently Report 29/32
Location: FMQX Web*→This Guide's Session→*Send Content Steps: Fill in this section's independent property message and send once: temperature 29, setpoint 32.

Independent property reporting: 29, 32
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Independent Property Message | Use the JSON array property reporting structure; the array element ids are fixed to the Thing Model identifiers, and value carries this round's actual state. Required · Fill in: [ {"id":"FastBee_temperature","value":29}, {"id":"FastBee_setpoint","value":32} ] |
19. Check the Platform's Current 29/32
Location: Platform device details*→*Running Status Steps: Refresh and check this guide's device temperature and setpoint.

Platform current 32℃ after independent status reporting
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Current Value | Comes from the device's independent property reporting; do not substitute a pending slider or a reply. Required · Fill in: per the deployment plan · Example: 32; final 34 |
| Current Status | Not the pending slider target. Required · Fill in: Temperature 29; setpoint 32 |
This round's execution count increased from 2 to 3; the cumulative value does not mean multiple executions this time.
5. Verify 34 After Stop and Recovery
20. Stop This Round's Session
Location: FMQX Web*→*This Guide's Session Title Bar Steps: Stop sending and disconnect this guide's session.

This guide's session disconnected, configuration and data retained
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Resource Retention | Finishing only stops sending and disconnects; retain the product, device, model, session, and history. Required · Fill in: per the deployment plan · Example: Last 29/34; disconnected |
21. Restore the Same Device Session
Location: FMQX Web*→*This Guide's Retained Session Steps: Reconnect this guide's session and wait for Connected.

Restore this guide's connection with the original identity
After recovery, reuse the same 29/32 property message from the previous section and send it independently once more, then continue with delivering 34. This round actually completed this state report; it is not a re-execution of the 32 command, so a second 32 appears in the history. The same format follows the earlier description; no duplicate-content image is added.
22. Deliver the Post-recovery Target 34
Location: Platform device details*→Running Status→*Setpoint Steps: Adjust the target to 34, check the overlay, and send once.

Setpoint 34℃ pending delivery
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Pending Target | Do not write the current value 32 as the pending target. Required · Fill in: 34 |
23. Check That the 34 Command Was Actually Received
Location: FMQX Web*→This Guide's Session→*Receive Records Steps: Expand the 34 command and check the target value and the message id of the same round.

Device actually received setpoint 34
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Actual Receive Record | Check the correct topic, command id, and the target value in the params array. Required · Fill in: per the deployment plan · Example: 32/34; 143 bytes |
| This Command id | The subsequent demo reply uses the same id. Required · Fill in: e4f07619486c459fb861b987eaabe316 |
24. Check the 34 Demo Reply
Location: FMQX Web*→This Guide's Session→*Send Records Steps: Expand the demo reply with the same id and check the success code, target value, and execution count.

Same-id reply, setpoint 34, 4 cumulative executions
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Demo Auto-reply | Check the same id, code 200, data, request summary, and actual execution count; each increment is 1, which does not prove physical actuation. Required · Fill in: per the deployment plan · Example: 32: 2→3; 34: 3→4 |
| Execution Count | Use this round's actual baseline; do not treat the cumulative value as the number of executions this time. Required · Fill in: 3 → 4 |
| Command id | Same as the actual receive record. Required · Fill in: e4f07619486c459fb861b987eaabe316 |
Independent 29/34 property reportingjson
[
{"id":"temperature","value":29},
{"id":"setpoint","value":34}
]Report the final state with a new property message. Replaceable customer template names are used here; check against the replacement list in this section before importing or sending.
25. Independently Report 29/34
Location: FMQX Web*→This Guide's Session→*Send Content Steps: Fill in this section's independent property message and send once: temperature 29, setpoint 34.

Independent property reporting: 29, 34
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Independent Property Message | Use the JSON array property reporting structure; the array element ids are fixed to the Thing Model identifiers, and value carries this round's actual state. Required · Fill in: [ {"id":"FastBee_temperature","value":29}, {"id":"FastBee_setpoint","value":34} ] |
26. Check the Platform's Current 29/34
Location: Platform device details*→*Running Status Steps: Refresh and check this guide's device temperature and setpoint.

Platform current 34℃ after independent status reporting
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Current Value | Comes from the device's independent property reporting; do not substitute a pending slider or a reply. Required · Fill in: per the deployment plan · Example: 32; final 34 |
| Current Status | Not the pending slider target. Required · Fill in: Temperature 29; setpoint 34 |
This round's 34 execution count increased from 3 to 4, only 1 more this time.
6. Query and Refresh Historical Data
Temperature window: 2026-10-15 23:20:24 ~ 2026-10-15 23:20:48. Setpoint window: 2026-10-15 23:20:54 ~ 2026-10-15 23:21:18. All times below are Shanghai time.
27. Set the Complete Temperature Query Time
Location: Data Center*→Historical Data→*Date and Start/End Time Steps: Open the date panel, fill in the complete temperature start/end time, and confirm.

Complete date and start/end time: 2026-10-15 23:20:24 to 2026-10-15 23:20:48
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Time Range | Fill in this round's actual complete date and time: temperature 2026-10-15 23:20:24 ~ 2026-10-15 23:20:48; setpoint 2026-10-15 23:20:54 ~ 2026-10-15 23:21:18; other re-verifications must use that round's actual window. Required · Fill in: per the deployment plan · Example: Temperature 2026-10-15 23:20:24 ~ 2026-10-15 23:20:48; setpoint 2026-10-15 23:20:54 ~ 2026-10-15 23:21:18 |
| Complete Start/End Time | Re-verification should use that round's actual send window. Required · Fill in: 2026-10-15 23:20:24 ~ 2026-10-15 23:20:48 |
28. Select This Device and the Temperature Field
Location: Data Center*→Historical Data→*Filter Conditions Steps: Select the temperature field of FastBee_数组温控 and query.

Query after checking this guide's device, property, and time range
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Device and Property | Select this guide's array temperature control and temperature or setpoint temperature. Required · Fill in: per the deployment plan · Example: FastBee_数组温控/temperature, setpoint temperature |
| Device and Field | The device identity matches this guide's session. Required · Fill in: FastBee_数组温控; temperature |
29. Refresh the Temperature Query
Location: Data Center*→Historical Data→*Refresh Steps: Click Refresh and wait for loading to complete; if the filter conditions are cleared, restore the same device, field, and complete window and query again.

Refresh and re-query this guide's history
30. Check the Temperature History Results
Location: Data Center*→Historical Data→*Results Table Steps: Read the refreshed temperature history results and check line by line.

Check this guide's actual history records after refresh
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Device and Property | Select this guide's array temperature control and temperature or setpoint temperature. Required · Fill in: per the deployment plan · Example: FastBee_数组温控/temperature, setpoint temperature |
| Result Order | Follow the actual table within this round's window. Required · Fill in: 61, 62, 63, 64, 65, 66, 67, 68, 69, 70 |
31. Set the Complete Setpoint Query Time
Location: Data Center*→Historical Data→*Date and Start/End Time Steps: Open the date panel, fill in the complete setpoint start/end time, and confirm.

Complete date and start/end time: 2026-10-15 23:20:54 to 2026-10-15 23:21:18
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Time Range | Fill in this round's actual complete date and time: temperature 2026-10-15 23:20:24 ~ 2026-10-15 23:20:48; setpoint 2026-10-15 23:20:54 ~ 2026-10-15 23:21:18; other re-verifications must use that round's actual window. Required · Fill in: per the deployment plan · Example: Temperature 2026-10-15 23:20:24 ~ 2026-10-15 23:20:48; setpoint 2026-10-15 23:20:54 ~ 2026-10-15 23:21:18 |
| Complete Start/End Time | Re-verification should use that round's actual send window. Required · Fill in: 2026-10-15 23:20:54 ~ 2026-10-15 23:21:18 |
32. Select This Device and the Setpoint Field
Location: Data Center*→Historical Data→*Filter Conditions Steps: Select the setpoint field of FastBee_数组温控 and query.

Query after checking this guide's device, property, and time range
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Device and Property | Select this guide's array temperature control and temperature or setpoint temperature. Required · Fill in: per the deployment plan · Example: FastBee_数组温控/temperature, setpoint temperature |
| Device and Field | The device identity matches this guide's session. Required · Fill in: FastBee_数组温控; setpoint |
33. Refresh the Setpoint Query
Location: Data Center*→Historical Data→*Refresh Steps: Click Refresh and wait for loading to complete; if the filter conditions are cleared, restore the same device, field, and complete window and query again.

Refresh and re-query this guide's history
34. Check the Setpoint History Results
Location: Data Center*→Historical Data→*Results Table Steps: Read the refreshed setpoint history results and check line by line.

Check this guide's actual history records after refresh
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Device and Property | Select this guide's array temperature control and temperature or setpoint temperature. Required · Fill in: per the deployment plan · Example: FastBee_数组温控/temperature, setpoint temperature |
| Result Order | Follow the actual table within this round's window. Required · Fill in: 32, 32, 34 |
The three setpoint history entries are, in order, the state after the first 32 control, the 32 state after recovery, and the state after the 34 control. All three are independent property history; demo replies cannot substitute for them.
7. Finish and Retain This Guide's Resources
35. Finish Send/Receive and Retain Resources
Location: FMQX Web*→*This Guide's Session Steps: Finish sending and disconnect the session.

This guide's session disconnected, configuration and data retained
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Resource Retention | Finishing only stops sending and disconnects; retain the product, device, model, session, and history. Required · Fill in: per the deployment plan · Example: Last 29/34; disconnected |
For re-verification, record new send times, keep using the fixed property identifiers as the array element ids, judge each increment against the actual execution-count baseline, and do not reuse old conclusions.
8. Post-send/receive Publish Synchronization Supplementary Check
The following four steps occurred after the above send/receive and are used to check the current publish, automatic page updates, node application, and manual refresh. The device send/receive and history closed loop after the new snapshot still need re-verification.
36. Post-send/receive Supplementary Check: Confirm Publishing the Product
Location: Product Management*→This Guide's Product→*Publish Confirmation Steps: Confirm the current product, then click Confirm Publish.

The original screenshot retains this guide's product name, ID, and the complete publish confirmation box.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Current Product | Operate only this guide's independent product. Required · Fill in: FastBee_数组温控; 877 |
37. Observe the Automatic Update of the Sync Summary
Location: Product Details*→Product Summary→*Access Configuration Sync Steps: Stay on the current page and wait for the sync summary to update.

This guide's product access configuration has taken effect
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Access Configuration Sync | The current publish receipt after this round's send/receive; it cannot serve as the snapshot source for the earlier ten samples. Required · Fill in: per the deployment plan · Example: APPLIED; success 1, failure 0; snapshot 1986 |
38. Expand the Current Node Application Receipt
Location: Product Details*→*Sync Details Steps: Open Sync Details and check this guide's product identity, node results, and effective time.

Application receipt for this guide's product and access node
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Access Configuration Sync | The current publish receipt after this round's send/receive; it cannot serve as the snapshot source for the earlier ten samples. Required · Fill in: per the deployment plan · Example: APPLIED; success 1, failure 0; snapshot 1986 |
| Current Snapshot | Only proves this publish synchronization; do not attribute the earlier send/receive to this snapshot. Required · Fill in: 1986 |
39. Manually Refresh the Current Sync Status
Location: Product Details*→Sync Details→*Refresh Status Steps: Click Refresh Status and wait for this check to complete.

Manually refresh the current node application receipt
Field and Parameter Reference
Device Access Wizard
| Field / Control | Fill-in Instructions |
|---|---|
| Access Source | Create a new independent product for this guide; re-verification does not create it again. Required · Fill in: New ProductExisting Product: use an existing model; use an existing model. New Product: create this guide's independent model; create this guide's independent model. Copy Product: copy an existing configuration; copy an existing configuration. Use Template: start from a template; start from a template. |
| Product Name | Give this kind of temperature-control device a concise business name. Required · Fill in: FastBee_数组温控 |
| Wizard JSON Sample | First extract the two models with the object sample; after creation, change the data format to JSON array, and formal reporting uses a bare array. Required · Fill in: {"FastBee_temperature":20,"FastBee_setpoint":30} |
| Fields, Types, and Paths | Generate two integer properties, temperature and setpoint. Required · Fill in: FastBee_temperature/FastBee_setpoint; integer; ℃ |
| Device Identifier | Both the MQTT identity and topics use this device number. Required · Fill in: FastBee_ArrayMQTT_Tutorial_01 |
| Device Name | Both the platform and FMQX use a clear business name for locating. Required · Fill in: FastBee_数组温控 |
| Access Overview | The wizard starts with JSON/MQTT, one device, and two fields; change to the formal format in the next step. Required · Fill in: 1 device, 2 fields; initial JSON/MQTT |
Protocol and Publish Effectiveness
| Field / Control | Fill-in Instructions |
|---|---|
| Data Format | This guide's formal format is JSON array; do not keep the initial JSON object format. Required · Fill in: JSON ArrayPublish after modification. Alink JSON: Alink structure, verified in another guide; Alink structure, verified in another guide. JSON: the wizard's initial object format, not this guide's formal format; the wizard's initial object format, not this guide's formal format. 7E: a supplementary registration and heartbeat scenario, not chosen in this guide; a supplementary registration and heartbeat scenario, not chosen in this guide. JSON Array: the bare-array id/value format verified in this guide; the bare-array id/value format verified in this guide. OPC UA: an OPC UA connection scenario, not chosen in this guide; an OPC UA connection scenario, not chosen in this guide. IEC 60870-5-104: the IEC104 industry protocol, not chosen in this guide; the IEC104 industry protocol, not chosen in this guide. IEC 60870-5-103: the IEC103 industry protocol, not chosen in this guide; the IEC103 industry protocol, not chosen in this guide. JT808 2013: a vehicle terminal protocol, not chosen in this guide; a vehicle terminal protocol, not chosen in this guide. DL/T645 1997: the 1997 meter protocol, not chosen in this guide; the 1997 meter protocol, not chosen in this guide. DL/T645 2007: the 2007 meter protocol, not chosen in this guide; the 2007 meter protocol, not chosen in this guide. Modbus TCP: a TCP register scenario, not chosen in this guide; a TCP register scenario, not chosen in this guide. Modbus RTU: an RTU passthrough scenario, not chosen in this guide; an RTU passthrough scenario, not chosen in this guide. Modbus TCP over RTU: a TCP-over-RTU scenario, not chosen in this guide; a TCP-over-RTU scenario, not chosen in this guide. Modbus JSON HP: another dedicated configuration, not chosen in this guide; another dedicated configuration, not chosen in this guide. JSON Gateway: a gateway device configuration, not chosen in this guide; a gateway device configuration, not chosen in this guide. |
| Transport Protocol | The product uses MQTT; the underlying transport in the FMQX import file is TCP. Required · Fill in: MQTTPublish after modification. MQTT: this guide sends and receives via MQTT identity and topics; this guide sends and receives via MQTT identity and topics. TCP: a separate TCP tutorial, without MQTT topics; a separate TCP tutorial, without MQTT topics. UDP: a separate UDP tutorial, with identity carried per datagram; a separate UDP tutorial, with identity carried per datagram. |
| Network Type | Keep this guide's actual WIFI setting; it is not the TCP/UDP transport choice. Required · Fill in: WIFIPublish after modification. WIFI: the network type saved in this guide; the network type saved in this guide. Cellular (2G/3G/4G/5G): choose per the physical cellular access, not chosen in this guide; choose per the physical cellular access, not chosen in this guide. Ethernet: choose per the physical wired networking, not chosen in this guide; choose per the physical wired networking, not chosen in this guide. Other: when none of the existing network types applies, choose per reality, not chosen in this guide; when none of the existing network types applies, choose per reality, not chosen in this guide. NB-IoT: choose per the physical narrowband cellular access, not chosen in this guide; choose per the physical narrowband cellular access, not chosen in this guide. |
| Publish Product | Unpublish before modifying a published product; republish after saving. Publish after modification. |
| Access Configuration Sync | The current publish receipt after this round's send/receive; it cannot serve as the snapshot source for the earlier ten samples. Required · Fill in: APPLIED; success 1, failure 0; snapshot 1986Publish after modification. |
| Refresh Status | Re-read the current sync summary and node receipts, updating the check time. Publish after modification. |
Function Definition
| Field / Control | Fill-in Instructions |
|---|---|
| Model Translation | Fill in the required English names, then click Modify. Required · Fill in: Temperature/SetpointPublish after modification. |
| Model Identifier | Must match the array element ids verbatim; the id is not a message number. Required · Fill in: FastBee_temperature/FastBee_setpointPublish after modification. |
| Model Category | Both the reading and the writable setpoint are properties. Required · Fill in: PropertyPublish after modification. Property: stores readings and setpoints; stores readings and setpoints. Function: not used in this guide; not used in this guide. Event: not used in this guide; not used in this guide. |
| Read-only Data | Temperature checked; setpoint unchecked to provide a control entry. Required · Fill in: Temperature checked; setpoint uncheckedPublish after modification. Checked: only displays reported readings; only displays reported readings. Unchecked: allows delivering setpoints per permission; allows delivering setpoints per permission. |
| History Storage | Enabled for both properties, recording subsequent independent state reports. Required · Fill in: CheckedPublish after modification. Checked: saves subsequent history; saves subsequent history. Unchecked: subsequent history cannot be checked per this guide; subsequent history cannot be checked per this guide. |
| Chart Display/Real-time Monitoring | Temperature on, setpoint off; check the read-only linkage after saving. Required · Fill in: Temperature on; setpoint offPublish after modification. Checked: the display adopted for temperature; the display adopted for temperature. Unchecked: the display adopted for setpoint; the display adopted for setpoint. |
| Share Permission | Demoed within this tenant; sharing is not opened. Required · Fill in: UncheckedPublish after modification. Checked: sharing decided by tenant policy; sharing decided by tenant policy. Unchecked: keep this guide's scope; keep this guide's scope. |
| Integer Range, Unit, and Step | Temperature -40~100℃; setpoint 16~35℃; step 1. Required · Fill in: Temperature -40~100; setpoint 16~35; ℃; 1Publish after modification. |
| Calculation Formula | This example uses integers directly without formula conversion. Optional · Fill in: Leave emptyPublish after modification. |
| Modify/Cancel | Complete the required fields, then Modify to save; Cancel does not submit. Publish after modification. |
FMQX Web MQTT Connection
| Field / Control | Fill-in Instructions |
|---|---|
| Import Configuration | Import the UTF-8 JSON below that contains no password. Reconnect after modification. |
| MQTT/TCP Connection | protocol is MQTT and transport is TCP; writing transport as MQTT on first import is rejected by the import. Required · Fill in: protocol=MQTT; transport=TCPReconnect after modification. |
| Connection Name | Identifies this guide's retained session. Required · Fill in: FastBee_数组温控Reconnect after modification. |
| Host / IP | Fill in FMQ's MQTT entry; use 127.0.0.1 on the same machine. Required · Fill in: 127.0.0.1Reconnect after modification. |
| Port | This guide's plain MQTT TCP listen port. Required · Fill in: 1883Reconnect after modification. |
| Client ID | Use this device's fixed connection identity; do not replace it randomly. Required · Fill in: S&FastBee_ArrayMQTT_Tutorial_01&877&1Reconnect after modification. |
| Username | Obtained from the same device's connection parameters. Required · Fill in: admin (subject to this device's parameters)Reconnect after modification. |
| Password | After the first import, securely fill in this device's password and save; it is not written into the configuration or the manual. Required · Fill in: This device's credential, not echoedReconnect after modification. |
| MQTT Version | 3.1.1 verified in this guide. Required · Fill in: 3.1.1Reconnect after modification. 3.1: not verified in this guide; not verified in this guide. 3.1.1: verified in this guide; verified in this guide. 5.0: not verified in this guide; not verified in this guide. |
| Auto Reconnect | Off; stop and recover manually per the tutorial. Required · Fill in: falseReconnect after modification. false: manual connect and recovery; manual connect and recovery. true: automatic recovery needs separate verification; automatic recovery needs separate verification. |
| JSON Demo Device | Format JSON_ARRAY; initial 29/30; the reply route is this device's property/post. Required · Fill in: JSON_ARRAY; temperature 29, setpoint 30Reconnect after modification. |
| Connect/Disconnect | Confirm the real status before sending/receiving; retain the session without deleting it. Reconnect after modification. |
Array Reporting, Subscription, and Reply
| Field / Control | Fill-in Instructions |
|---|---|
| Downlink Subscription Topic | The correct downlink topic is enabled. Required · Fill in: /877/FastBee_ArrayMQTT_Tutorial_01/function/getReconnect after modification. |
| Wrong Default Topic | The automatic default entry is retained but active=false; do not treat the two unsubscribe buttons as proof of enablement. Required · Fill in: S&FastBee_ArrayMQTT_Tutorial_01&877&1/function/get; active=falseReconnect after modification. |
| Reporting and Demo Reply Topic | Both the array properties and demo reply objects are published to this device's reporting topic. Required · Fill in: /877/FastBee_ArrayMQTT_Tutorial_01/property/postReconnect after modification. |
| QoS | Reporting and subscription are configured as 1; the card for the actual downlink received shows 0. Required · Fill in: Report 1; downlink actually received 0Reconnect after modification. 0: this guide's actual downlink display value; this guide's actual downlink display value. 1: this guide's reporting and subscription configuration; this guide's reporting and subscription configuration. 2: not verified in this guide; not verified in this guide. |
| Array Element id | Fixed Thing Model identifiers, not message numbers that can be changed at will. Required · Fill in: FastBee_temperature/FastBee_setpointReconnect after modification. |
| Array Element value | The current ten-sample temperatures 61~70 and initial setpoint 30; subsequent independent states are filled per the corresponding steps. Required · Fill in: Temperature 61~70; setpoint 30/32/34Reconnect after modification. |
| Publish Message/Send | Complete UTF-8 JSON; after preparation, send each message once and check one by one. Reconnect after modification. |
| Actual Receive Record | Check the correct topic, command id, and the target value in the params array. Required · Fill in: 32/34; 143 bytesReconnect after modification. |
| Demo Auto-reply | Check the same id, code 200, data, request summary, and actual execution count; each increment is 1, which does not prove physical actuation. Required · Fill in: 32: 2→3; 34: 3→4Reconnect after modification. |
Device Running Status
| Field / Control | Fill-in Instructions |
|---|---|
| Setpoint Slider/Send | Choose the target within the model's 16~35℃ range, then send. |
| Current Value | Comes from the device's independent property reporting; do not substitute a pending slider or a reply. Required · Fill in: 32; final 34 |
Historical Data
| Field / Control | Fill-in Instructions |
|---|---|
| Device and Property | Select this guide's array temperature control and temperature or setpoint temperature. Required · Fill in: FastBee_数组温控/temperature, setpoint temperature |
| Time Range | Fill in this round's actual complete date and time: temperature 2026-10-15 23:20:24 ~ 2026-10-15 23:20:48; setpoint 2026-10-15 23:20:54 ~ 2026-10-15 23:21:18; other re-verifications must use that round's actual window. Required · Fill in: Temperature 2026-10-15 23:20:24 ~ 2026-10-15 23:20:48; setpoint 2026-10-15 23:20:54 ~ 2026-10-15 23:21:18 |
| Advanced Filter/Query/Refresh | Select the field and query; after refreshing, reselect the same conditions and wait for loading to finish. |
Stop and Recovery
| Field / Control | Fill-in Instructions |
|---|---|
| Resource Retention | Finishing only stops sending and disconnects; retain the product, device, model, session, and history. Required · Fill in: Last 29/34; disconnected |
Where to Check First When Problems Occur
| Symptom | Possible Cause | Where to Check First | How to Recover |
|---|---|---|---|
| Connection failure | Device identity, endpoint, or authorization parameters do not match | First check this guide's session name, address, port, and platform device identity | Fix the authorization configuration and reconnect; no connection-fault injection was performed this round |
| Platform submitted but the device did not actually receive | Downlink route or device connection does not match | Check this device's function/get subscription, topic, and current connection | Stop repeated control, locate the route first, then re-verify with a new command |
| Reply succeeded but the current value did not update | The demo reply and the property state are two different messages | Check the independent property reporting and this device's current value | Report the actual state independently first; do not treat a pending target as the current value |
| History entry count mismatch | The device, field, or query time does not correspond to this round | Expand the complete date panel, restore the same device and field, then refresh | Check line by line against the actual window; do not pad samples with old data |
| Sync status needs reconfirmation | The current viewing time is earlier than the new receipt | Check the current product and snapshot, then click Refresh Status | Retry later if reading fails; the browser did not inject this fault this round, and only component tests cover the recovery path |


