Skip to content

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

text
{

  "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.

Create the Array Temperature-Control Product

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 / ControlDescription
Access SourceCreate a new independent product for this guide; re-verification does not create it again.
Required · Fill in: New Product
Product NameGive 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.

Generate Fields from a JSON Object Sample

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 / ControlDescription
Wizard JSON SampleFirst 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.

Check the Two Collection Fields

The two properties correspond to FastBee_temperature and FastBee_setpoint; this image is a separate retake of the field table.

Screenshot Key Points ​

Field / ControlDescription
Fields, Types, and PathsGenerate 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.

Fill in the Independent Device Identifier

Device number FastBee_ArrayMQTT_Tutorial_01; subsequent MQTT identity and topics must correspond to it.

Screenshot Key Points ​

Field / ControlDescription
Device IdentifierBoth the MQTT identity and topics use this device number.
Required · Fill in: FastBee_ArrayMQTT_Tutorial_01
Device NameBoth 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.

Check the Initial Access Overview and Create

This stage genuinely shows JSON/MQTT, not yet the formal JSON array; continue modifying the format after creation.

Screenshot Key Points ​

Field / ControlDescription
Access OverviewThe 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.

Switch to the Formal JSON Array and MQTT

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 / ControlDescription
Data FormatThis guide's formal format is JSON array; do not keep the initial JSON object format.
Required · Fill in: JSON Array
Transport ProtocolThe product uses MQTT; the underlying transport in the FMQX import file is TCP.
Required · Fill in: MQTT
Network TypeKeep 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.

Complete the Writable Setpoint and History Parameters

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 / ControlDescription
Model TranslationFill in the required English names, then click Modify.
Required · Fill in: Temperature/Setpoint
Model IdentifierMust match the array element ids verbatim; the id is not a message number.
Required · Fill in: FastBee_temperature/FastBee_setpoint
Model CategoryBoth the reading and the writable setpoint are properties.
Required · Fill in: Property
Read-only DataTemperature checked; setpoint unchecked to provide a control entry.
Required · Fill in: Temperature checked; setpoint unchecked
History StorageEnabled for both properties, recording subsequent independent state reports.
Required · Fill in: Checked
Chart Display/Real-time MonitoringTemperature on, setpoint off; check the read-only linkage after saving.
Required · Fill in: Temperature on; setpoint off
Share PermissionDemoed within this tenant; sharing is not opened.
Required · Fill in: Unchecked
Integer Range, Unit, and StepTemperature -40~100℃; setpoint 16~35℃; step 1.
Required · Fill in: Temperature -40~100; setpoint 16~35; ℃; 1
Modify/CancelComplete 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.

Save the Read-only Temperature and Range

Temperature read-only, history enabled, chart and real-time monitoring enabled; the formula is left empty.

Screenshot Key Points ​

Field / ControlDescription
Model TranslationFill in the required English names, then click Modify.
Required · Fill in: Temperature/Setpoint
Read-only DataTemperature checked; setpoint unchecked to provide a control entry.
Required · Fill in: Temperature checked; setpoint unchecked
History StorageEnabled for both properties, recording subsequent independent state reports.
Required · Fill in: Checked
Chart Display/Real-time MonitoringTemperature on, setpoint off; check the read-only linkage after saving.
Required · Fill in: Temperature on; setpoint off
Share PermissionDemoed within this tenant; sharing is not opened.
Required · Fill in: Unchecked
Integer Range, Unit, and StepTemperature -40~100℃; setpoint 16~35℃; step 1.
Required · Fill in: Temperature -40~100; setpoint 16~35; ℃; 1
Calculation FormulaThis example uses integers directly without formula conversion.
Optional · Fill in: Leave empty
Modify/CancelComplete 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

text
{

  "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.

Import the Connection Configuration in FMQX Web

protocol is MQTT and transport is TCP; after the first import, securely fill in this device's Password and save.

Screenshot Key Points ​

Field / ControlDescription
Import ConfigurationImport 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

Connection parameters of this guide's retained session

Screenshot Key Points ​

Field / ControlDescription
Connection NameIdentifies this guide's retained session.
Required · Fill in: per the deployment plan · Example: FastBee_数组温控
Host / IPFill 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
PortThis guide's plain MQTT TCP listen port.
Required · Fill in: per the deployment plan · Example: 1883
Client IDUse 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
UsernameObtained from the same device's connection parameters.
Required · Fill in: per the deployment plan · Example: admin (subject to this device's parameters)
PasswordAfter 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 Version3.1.1 verified in this guide.
Required · Fill in: per the deployment plan · Example: 3.1.1
Auto ReconnectOff; stop and recover manually per the tutorial.
Required · Fill in: per the deployment plan · Example: false
Session NameLocate by this guide's name to avoid mixing in other sessions.
Required · Fill in: FastBee_数组温控
Address and PortThis round's local FMQ entry; for other environments, provided by the administrator.
Required · Fill in: 127.0.0.1:1883
Device IdentityMust correspond to this guide's product and device.
Required · Fill in: S&FastBee_ArrayMQTT_Tutorial_01&877&1

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

Downlink subscription topics and QoS of this guide's device

Screenshot Key Points ​

Field / ControlDescription
Downlink Subscription TopicThe correct downlink topic is enabled.
Required · Fill in: per the deployment plan · Example: /877/FastBee_ArrayMQTT_Tutorial_01/function/get
Wrong Default TopicThe 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
QoSReporting 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 TopicPlatform control commands are sent to this topic.
Required · Fill in: /877/FastBee_ArrayMQTT_Tutorial_01/function/get
Legacy Default TopicDo 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 QoSCheck 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

Restore this guide's independent device session

Screenshot Key Points ​

Field / ControlDescription
SessionConnect only this guide's retained session.
Required · Fill in: FastBee_数组温控

3. Report Ten Samples from 61 to 70 ​

First complete messagejson

text
[

 {"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

Independent property reporting: 61, 30

Screenshot Key Points ​

Field / ControlDescription
First MessageThe 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 TopicThe 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

Real-time values after reporting ten temperatures 61 to 70

Screenshot Key Points ​

Field / ControlDescription
Current ValueComes 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 SequenceThe 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 TimeShanghai 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

Setpoint 32℃ pending delivery

Screenshot Key Points ​

Field / ControlDescription
Pending TargetCheck 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

Device actually received setpoint 32

Screenshot Key Points ​

Field / ControlDescription
Actual Receive RecordCheck 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 idThe subsequent demo reply must correspond to the same id.
Required · Fill in: 80d5d43805034ced803b0e869850b99c
Target ValueFollow 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

Same-id reply, setpoint 32, 3 cumulative executions

Screenshot Key Points ​

Field / ControlDescription
Demo Auto-replyCheck 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 CountUse this round's actual baseline; do not treat the cumulative value as the number of executions this time.
Required · Fill in: 2 → 3
Command idSame as the actual receive record.
Required · Fill in: 80d5d43805034ced803b0e869850b99c

Independent 29/32 property reportingjson

text
[

 {"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

Independent property reporting: 29, 32

Screenshot Key Points ​

Field / ControlDescription
Independent Property MessageUse 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

Platform current 32℃ after independent status reporting

Screenshot Key Points ​

Field / ControlDescription
Current ValueComes 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 StatusNot 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

This guide's session disconnected, configuration and data retained

Screenshot Key Points ​

Field / ControlDescription
Resource RetentionFinishing 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

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

Setpoint 34℃ pending delivery

Screenshot Key Points ​

Field / ControlDescription
Pending TargetDo 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

Device actually received setpoint 34

Screenshot Key Points ​

Field / ControlDescription
Actual Receive RecordCheck 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 idThe 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

Same-id reply, setpoint 34, 4 cumulative executions

Screenshot Key Points ​

Field / ControlDescription
Demo Auto-replyCheck 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 CountUse this round's actual baseline; do not treat the cumulative value as the number of executions this time.
Required · Fill in: 3 → 4
Command idSame as the actual receive record.
Required · Fill in: e4f07619486c459fb861b987eaabe316

Independent 29/34 property reportingjson

text
[

 {"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

Independent property reporting: 29, 34

Screenshot Key Points ​

Field / ControlDescription
Independent Property MessageUse 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

Platform current 34℃ after independent status reporting

Screenshot Key Points ​

Field / ControlDescription
Current ValueComes 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 StatusNot 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

Complete date and start/end time: 2026-10-15 23:20:24 to 2026-10-15 23:20:48

Screenshot Key Points ​

Field / ControlDescription
Time RangeFill 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 TimeRe-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

Query after checking this guide's device, property, and time range

Screenshot Key Points ​

Field / ControlDescription
Device and PropertySelect 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 FieldThe 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

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

Check this guide's actual history records after refresh

Screenshot Key Points ​

Field / ControlDescription
Device and PropertySelect this guide's array temperature control and temperature or setpoint temperature.
Required · Fill in: per the deployment plan · Example: FastBee_数组温控/temperature, setpoint temperature
Result OrderFollow 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

Complete date and start/end time: 2026-10-15 23:20:54 to 2026-10-15 23:21:18

Screenshot Key Points ​

Field / ControlDescription
Time RangeFill 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 TimeRe-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

Query after checking this guide's device, property, and time range

Screenshot Key Points ​

Field / ControlDescription
Device and PropertySelect 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 FieldThe 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

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

Check this guide's actual history records after refresh

Screenshot Key Points ​

Field / ControlDescription
Device and PropertySelect this guide's array temperature control and temperature or setpoint temperature.
Required · Fill in: per the deployment plan · Example: FastBee_数组温控/temperature, setpoint temperature
Result OrderFollow 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

This guide's session disconnected, configuration and data retained

Screenshot Key Points ​

Field / ControlDescription
Resource RetentionFinishing 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.

Confirm Publishing This Guide's Product, Product ID 877

The original screenshot retains this guide's product name, ID, and the complete publish confirmation box.

Screenshot Key Points ​

Field / ControlDescription
Current ProductOperate 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

This guide's product access configuration has taken effect

Screenshot Key Points ​

Field / ControlDescription
Access Configuration SyncThe 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

Application receipt for this guide's product and access node

Screenshot Key Points ​

Field / ControlDescription
Access Configuration SyncThe 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 SnapshotOnly 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

Manually refresh the current node application receipt

Field and Parameter Reference ​

Device Access Wizard ​

Field / ControlFill-in Instructions
Access SourceCreate 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 NameGive this kind of temperature-control device a concise business name.
Required · Fill in: FastBee_数组温控
Wizard JSON SampleFirst 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 PathsGenerate two integer properties, temperature and setpoint.
Required · Fill in: FastBee_temperature/FastBee_setpoint; integer; ℃
Device IdentifierBoth the MQTT identity and topics use this device number.
Required · Fill in: FastBee_ArrayMQTT_Tutorial_01
Device NameBoth the platform and FMQX use a clear business name for locating.
Required · Fill in: FastBee_数组温控
Access OverviewThe 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 / ControlFill-in Instructions
Data FormatThis guide's formal format is JSON array; do not keep the initial JSON object format.
Required · Fill in: JSON Array
Publish 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 ProtocolThe product uses MQTT; the underlying transport in the FMQX import file is TCP.
Required · Fill in: MQTT
Publish 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 TypeKeep this guide's actual WIFI setting; it is not the TCP/UDP transport choice.
Required · Fill in: WIFI
Publish 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 ProductUnpublish before modifying a published product; republish after saving.
Publish after modification.
Access Configuration SyncThe 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 1986
Publish after modification.
Refresh StatusRe-read the current sync summary and node receipts, updating the check time.
Publish after modification.

Function Definition ​

Field / ControlFill-in Instructions
Model TranslationFill in the required English names, then click Modify.
Required · Fill in: Temperature/Setpoint
Publish after modification.
Model IdentifierMust match the array element ids verbatim; the id is not a message number.
Required · Fill in: FastBee_temperature/FastBee_setpoint
Publish after modification.
Model CategoryBoth the reading and the writable setpoint are properties.
Required · Fill in: Property
Publish 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 DataTemperature checked; setpoint unchecked to provide a control entry.
Required · Fill in: Temperature checked; setpoint unchecked
Publish after modification. Checked: only displays reported readings; only displays reported readings. Unchecked: allows delivering setpoints per permission; allows delivering setpoints per permission.
History StorageEnabled for both properties, recording subsequent independent state reports.
Required · Fill in: Checked
Publish 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 MonitoringTemperature on, setpoint off; check the read-only linkage after saving.
Required · Fill in: Temperature on; setpoint off
Publish 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 PermissionDemoed within this tenant; sharing is not opened.
Required · Fill in: Unchecked
Publish 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 StepTemperature -40~100℃; setpoint 16~35℃; step 1.
Required · Fill in: Temperature -40~100; setpoint 16~35; ℃; 1
Publish after modification.
Calculation FormulaThis example uses integers directly without formula conversion.
Optional · Fill in: Leave empty
Publish after modification.
Modify/CancelComplete the required fields, then Modify to save; Cancel does not submit.
Publish after modification.

FMQX Web MQTT Connection ​

Field / ControlFill-in Instructions
Import ConfigurationImport the UTF-8 JSON below that contains no password.
Reconnect after modification.
MQTT/TCP Connectionprotocol is MQTT and transport is TCP; writing transport as MQTT on first import is rejected by the import.
Required · Fill in: protocol=MQTT; transport=TCP
Reconnect after modification.
Connection NameIdentifies this guide's retained session.
Required · Fill in: FastBee_数组温控
Reconnect after modification.
Host / IPFill in FMQ's MQTT entry; use 127.0.0.1 on the same machine.
Required · Fill in: 127.0.0.1
Reconnect after modification.
PortThis guide's plain MQTT TCP listen port.
Required · Fill in: 1883
Reconnect after modification.
Client IDUse this device's fixed connection identity; do not replace it randomly.
Required · Fill in: S&FastBee_ArrayMQTT_Tutorial_01&877&1
Reconnect after modification.
UsernameObtained from the same device's connection parameters.
Required · Fill in: admin (subject to this device's parameters)
Reconnect after modification.
PasswordAfter 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 echoed
Reconnect after modification.
MQTT Version3.1.1 verified in this guide.
Required · Fill in: 3.1.1
Reconnect 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 ReconnectOff; stop and recover manually per the tutorial.
Required · Fill in: false
Reconnect after modification. false: manual connect and recovery; manual connect and recovery. true: automatic recovery needs separate verification; automatic recovery needs separate verification.
JSON Demo DeviceFormat JSON_ARRAY; initial 29/30; the reply route is this device's property/post.
Required · Fill in: JSON_ARRAY; temperature 29, setpoint 30
Reconnect after modification.
Connect/DisconnectConfirm the real status before sending/receiving; retain the session without deleting it.
Reconnect after modification.

Array Reporting, Subscription, and Reply ​

Field / ControlFill-in Instructions
Downlink Subscription TopicThe correct downlink topic is enabled.
Required · Fill in: /877/FastBee_ArrayMQTT_Tutorial_01/function/get
Reconnect after modification.
Wrong Default TopicThe 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=false
Reconnect after modification.
Reporting and Demo Reply TopicBoth the array properties and demo reply objects are published to this device's reporting topic.
Required · Fill in: /877/FastBee_ArrayMQTT_Tutorial_01/property/post
Reconnect after modification.
QoSReporting and subscription are configured as 1; the card for the actual downlink received shows 0.
Required · Fill in: Report 1; downlink actually received 0
Reconnect 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 idFixed Thing Model identifiers, not message numbers that can be changed at will.
Required · Fill in: FastBee_temperature/FastBee_setpoint
Reconnect after modification.
Array Element valueThe 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/34
Reconnect after modification.
Publish Message/SendComplete UTF-8 JSON; after preparation, send each message once and check one by one.
Reconnect after modification.
Actual Receive RecordCheck the correct topic, command id, and the target value in the params array.
Required · Fill in: 32/34; 143 bytes
Reconnect after modification.
Demo Auto-replyCheck 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→4
Reconnect after modification.

Device Running Status ​

Field / ControlFill-in Instructions
Setpoint Slider/SendChoose the target within the model's 16~35℃ range, then send.
Current ValueComes 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 / ControlFill-in Instructions
Device and PropertySelect this guide's array temperature control and temperature or setpoint temperature.
Required · Fill in: FastBee_数组温控/temperature, setpoint temperature
Time RangeFill 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/RefreshSelect the field and query; after refreshing, reselect the same conditions and wait for loading to finish.

Stop and Recovery ​

Field / ControlFill-in Instructions
Resource RetentionFinishing 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 ​

SymptomPossible CauseWhere to Check FirstHow to Recover
Connection failureDevice identity, endpoint, or authorization parameters do not matchFirst check this guide's session name, address, port, and platform device identityFix the authorization configuration and reconnect; no connection-fault injection was performed this round
Platform submitted but the device did not actually receiveDownlink route or device connection does not matchCheck this device's function/get subscription, topic, and current connectionStop repeated control, locate the route first, then re-verify with a new command
Reply succeeded but the current value did not updateThe demo reply and the property state are two different messagesCheck the independent property reporting and this device's current valueReport the actual state independently first; do not treat a pending target as the current value
History entry count mismatchThe device, field, or query time does not correspond to this roundExpand the complete date panel, restore the same device and field, then refreshCheck line by line against the actual window; do not pad samples with old data
Sync status needs reconfirmationThe current viewing time is earlier than the new receiptCheck the current product and snapshot, then click Refresh StatusRetry later if reading fails; the browser did not inject this fault this round, and only component tests cover the recovery path