Alink JSON and UDP Wireless Terminal 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. This guide is a supplementary reference with applicability limits; the missing-item status in the original manual remains in place.
Complete device reporting, downlink actual receipt, FMQX demo reply, independent state, actual history, and stop/recovery.
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 suits UDP devices that report with the standard Alink JSON envelope. Complete creation, publish, ten samples, downlink actual receipt, demo reply, independent state, history refresh, and stop/recovery. The account needs product, device, model, publish, control, and history permissions.
The id of an Alink report is the message number, kept unique for each new message; params is the property object whose keys are Thing Model identifiers. This differs from the fixed element id meaning of the JSON array.
FMQX sends from local port 15023 to FMQ at 127.0.0.1:8889, and each datagram carries the clientId. After recovery or a source endpoint change, report first to register the return address, then control.
FMQX Web plays the demo terminal; after it auto-replies, the operator manually and independently reports the property state; it does not prove physical actuator action or automatic continuous telemetry.
1. Create Independent Resources
Create a new independent product, generate two fields from the object sample first, then save this guide's formal protocol. Reuse existing resources for re-acceptance.
Wizard object samplejson
{
"FastBee_temperature": 20,
"FastBee_setpoint": 30
}The wizard generates only two fields first.
1. Select New Product
Location: IoT*→Device Access→*Access Source Steps: Select New Product and fill in the name of this guide; for re-acceptance, directly reuse the retained 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 / Control | Description |
|---|---|
| Access Source | Create an independent resource the first time; use the retained resource for re-verification. Required · Fill in: New Product |
| Product/Device Name | Locate this guide with a concise business name. Required · Fill in: FastBee_Alink无线 |
2. Generate Two Fields from the Object Sample
Location: Device Access*→*Collect Data Steps: Create the product of this guide and parse the object sample.

Generate plain object fields first, then save the formal Alink JSON.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Access Source | Create an independent resource the first time; use the retained resource for re-verification. Required · Fill in: New Product |
| Product/Device Name | Locate this guide with a concise business name. Required · Fill in: FastBee_Alink无线 |
| Wizard Object Sample | The wizard first parses a plain object to generate two fields; switch to Alink JSON later in the product details. Required · Fill in: {"FastBee_temperature":20,"FastBee_setpoint":30} |
3. Check Field Types and Units
Location: Device Access*→*Collection Fields Steps: Check the two fixed identifiers, integer type, and ℃.

The params keys of the formal Alink reporting match the model identifiers.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Field/Type/Unit | Two integer ℃ fields; the identifiers match the params keys. Required · Fill in: FastBee_temperature/FastBee_setpoint; integer; ℃ |
4. Fill in the Independent Device Number
Location: Device Access*→*Add Device Steps: Fill in the number and name of this guide.

Retain this device for re-acceptance.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Device Identifier | The platform number matches the device identity used by this session. Required · Fill in: FastBee_AlinkUDP_Tutorial_01 |
| Product/Device Name | Locate this guide with a concise business name. Required · Fill in: FastBee_Alink无线 |
5. Check the Initial Access Overview
Location: Device Access*→*Confirm Steps: Check 1 device, 2 fields and then create.

Initial JSON/MQTT; change to this guide's formal format in the next step.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Initial Overview | 1 device, 2 fields; the wizard starts with JSON/MQTT, and the formal protocol is saved afterward. Required · Fill in: 1 device, 2 fields |
2. Configure the Model and Protocol, Then Publish
6. Save the Formal Alink JSON and Transport
Location: Product Management*→*Product Information Steps: Select Alink JSON, UDP, and WIFI, then save.

The formal configuration matches the connections and messages of this guide.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Data Format | Alink JSON is formally adopted; reporting is an id/version/method/params object. Required · Fill in: Alink JSON |
| Transport | Choose per this guide; changing only the connection port is not enough. Required · Fill in: UDP |
| Network Type | WIFI for this guide; the actual endpoint is configured separately. Required · Fill in: WIFI |
7. Save the Writable Setpoint and History
Location: Product Management*→Function Definition→*Setpoint Steps: Add Setpoint, uncheck read-only, enable history, then click Modify.

Setpoint 16~35℃, step 1; chart and monitoring disabled.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Model Translation | Complete the English names. Required · Fill in: Temperature/Setpoint |
| Model Identifier | The keys of the params object match these identifiers verbatim. Required · Fill in: FastBee_temperature/FastBee_setpoint |
| Model Category | Both fields are properties. Required · Fill in: Property |
| Read-only Data | Temperature checked, setpoint unchecked. Required · Fill in: Temperature read-only; setpoint writable |
| History Storage | Enabled for both fields. Required · Fill in: Checked |
| Chart Display/Real-time Monitoring | Temperature on, setpoint off. Required · Fill in: Temperature on; setpoint off |
| Share Permission | Disabled in this guide. Required · Fill in: Unchecked |
| Range/Unit/Step | Temperature -40~100℃, setpoint 16~35℃, integer step 1. Required · Fill in: Integer; ℃; step 1 |
| Modify | Save after completing the required items. Required · Fill in: Modify |
8. Save the Read-only Temperature and History
Location: Product Management*→Function Definition→*Temperature Steps: Add Temperature, keep read-only, history, and chart monitoring, then click Modify.

Temperature -40~100℃, step 1.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Model Translation | Complete the English names. Required · Fill in: Temperature/Setpoint |
| Read-only Data | Temperature checked, setpoint unchecked. Required · Fill in: Temperature read-only; setpoint writable |
| History Storage | Enabled for both fields. Required · Fill in: Checked |
| Chart Display/Real-time Monitoring | Temperature on, setpoint off. Required · Fill in: Temperature on; setpoint off |
| Share Permission | Disabled in this guide. Required · Fill in: Unchecked |
| Range/Unit/Step | Temperature -40~100℃, setpoint 16~35℃, integer step 1. Required · Fill in: Integer; ℃; step 1 |
| Modify | Save after completing the required items. Required · Fill in: Modify |
9. Confirm Publishing the Product
Location: Product Management*→*Publish Confirmation Steps: Check the saved result and click Confirm.

After submitting, keep checking the actual APPLIED status and real send/receive.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Publish/Confirm | Publish after saving the formal configuration, and keep checking APPLIED. Required · Fill in: Confirm Publish |
10. Confirm the Access Node Has Applied
Location: Product Management*→*Access Configuration Sync Steps: Check APPLIED and an empty failure reason.

Success 1, failure 0; continue with the device closed loop.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Access Configuration Sync | Judge whether it is applied by the actual node receipt. Required · Fill in: APPLIED; success 1, failure 0 |
Publish after saving; confirm that snapshot 1845 is APPLIED before performing real send/receive. Continue after checking the actual application result.
3. Import and Connect FMQX Web
This guide's formal connection configurationjson
{
"schemaVersion": 3,
"groups": [
{
"id": "FastBee_tutorial_FastBee_AlinkUDP_Tutorial_01",
"name": "FastBee_AlinkUDP教程",
"sortOrder": 55,
"isSystem": false
}
],
"sessions": [
{
"id": "FastBee_import_FastBee_AlinkUDP_Tutorial_01",
"groupId": "FastBee_tutorial_FastBee_AlinkUDP_Tutorial_01",
"name": "FastBee_Alink无线",
"protocol": "UDP",
"transport": "UDP",
"host": "127.0.0.1",
"port": 8889,
"clientId": "FastBee_AlinkUDP_Tutorial_01",
"autoReconnect": false,
"tcpLineMode": false,
"udpLocalPort": 15023,
"udpTargetAddress": "127.0.0.1",
"udpTargetPort": 8889,
"jsonDevice": {
"format": "ALINK_JSON",
"responseRoute": "",
"initialState": {
"FastBee_temperature": 29,
"FastBee_setpoint": 30
}
}
}
]
}UTF-8 JSON. Credentials such as the password are provided separately by the administrator; the import file does not carry a password.
11. Import the Independent FMQX Session
Location: FMQX Web*→*Configuration File Steps: Import this guide's JSON configuration below.

Do not borrow sessions from other tutorials.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Import Configuration | Import this guide's independent session and group; credentials are provided separately by the administrator. Required · Fill in: FastBee_连接配置.json |
12. Check the Formal Connection Parameters
Location: FMQX Web*→*Connection Configuration Steps: Fill in per the adjacent parameters and save this guide's session.

The local endpoint parameters match the real verification; account credentials are provided by the administrator.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Local Listen Address | The NIC bound by FMQX; 0.0.0.0 means the local interfaces. Required · Fill in: 0.0.0.0 |
| Local Port | FMQX source port and the port where downlink returns. Required · Fill in: 15023 |
| Remote Target Address | FMQ UDP listen address. Required · Fill in: 127.0.0.1 |
| Remote Target Port | FMQ UDP entry; do not swap it with the local port. Required · Fill in: 8889 |
| Enable Broadcast | This guide explicitly unicasts to FMQ. Required · Fill in: Off |
| Connection Timeout | In milliseconds. Endpoint reachability still requires full uplink/downlink verification. Required · Fill in: 5000 ms |
| Auto Reconnect | Disabled in this guide; stop/recovery is verified manually. Required · Fill in: Off |
| Test Connection/Save Configuration | Save and then reuse this guide's session; Test Connection does not replace the business closed loop. Required · Fill in: Test Connection; Save Configuration |
13. Connect This Guide's Device Endpoint
Location: FMQX Web*→*This Guide's Session Steps: Click Connect and check the endpoint and Connected status.

Connected still requires full uplink/downlink verification.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Connect/Disconnect | Open after checking this guide's endpoint; close when finished. Required · Fill in: Connected/Disconnected |
4. Send Ten Different Alink Samples
The first complete Alink messagejson
{
"clientId": "FastBee_AlinkUDP_Tutorial_01",
"id": "FastBee_AlinkUDP_Tutorial_01_sample_1",
"version": "1.0",
"method": "thing.event.property.post",
"params": {
"FastBee_temperature": 20,
"FastBee_setpoint": 30
}
}Temperature goes 20~29 message by message, setpoint 30; each id is different, and the params keys stay unchanged.
14. Prepare the First Complete Report
Location: FMQX Web*→*Send Data Steps: Fill in the complete message as shown, check the identity, fields, and target address, then send.

This image retakes the complete send form and did not resend old samples; the actual send and processing results are in the separate records that follow.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| clientId Device Identity | The top-level clientId of the report matches this device number and is carried by every UDP datagram. Required · Fill in: FastBee_AlinkUDP_Tutorial_01 |
| Alink Message id | Each new sample/independent state uses a different number; do not reuse a downlink id as a new property id. Required · Fill in: FastBee_AlinkUDP_Tutorial_01_sample_1…10 |
| version/method/params | version 1.0; the property method is thing.event.property.post; params is an object. Required · Fill in: 1.0; thing.event.property.post; params object |
| Remote Target Address | FMQ UDP listen address. Required · Fill in: 127.0.0.1 |
| Remote Target Port | FMQ UDP entry; do not swap it with the local port. Required · Fill in: 8889 |
| JSON/Text/Send | Complete UTF-8 JSON; wait for the platform to receive each message before continuing. Required · Fill in: Complete message; Send |
15. Send Ten Different Samples
Location: FMQX Web*→*Send Records Steps: Temperature 20~29, setpoint 30; send ten messages one by one with new ids.

Check the platform message by message; the actual history has all ten temperatures.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Alink Message id | Each new sample/independent state uses a different number; do not reuse a downlink id as a new property id. Required · Fill in: FastBee_AlinkUDP_Tutorial_01_sample_1…10 |
| version/method/params | version 1.0; the property method is thing.event.property.post; params is an object. Required · Fill in: 1.0; thing.event.property.post; params object |
| clientId Device Identity | The top-level clientId of the report matches this device number and is carried by every UDP datagram. Required · Fill in: FastBee_AlinkUDP_Tutorial_01 |
| JSON/Text/Send | Complete UTF-8 JSON; wait for the platform to receive each message before continuing. Required · Fill in: Complete message; Send |
The actual inbound time this round was 2026-10-13T02:52:42.004+08:00~2026-10-13T02:52:51.037+08:00; the ten source inputs correspond one by one to actual consumption and history. Do not copy a bare object or JSON array as the complete JSON. Use new ids and a new time window for each re-verification.
5. Deliver 32 and Report Back Independently
16. Deliver Setpoint 32 from the Platform
Location: Device Details*→*Running Status Steps: Adjust from the current 30 to 32 and click Send.

This image shows the operation entry; then check the independent actual receipt and reply.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Setpoint Slider/Send | 32 first, 34 after stop/recovery; the physical device follows the allowed range. Required · Fill in: 32/34 |
17. Adjust the Control Target to 32
Location: Device Details*→*Running Status Steps: Move the setpoint slider to 32, check the overlay target, and click Send on the right.

At the time of retaking, the current value was already 34; the overlay 32 is the target to be sent. This retake did not click Send again.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Setpoint Slider/Send | 32 first, 34 after stop/recovery; the physical device follows the allowed range. Required · Fill in: 32/34 |
18. Confirm the 32 Command Was Actually Received
Location: FMQX Web*→*Receive Records Steps: Check the formal command id, the params object, and 32.

Actually received at 2026-10-13 02:53:06.073; do not mix in earlier commands.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Actual Receive Record | Check the command id, params object, and targets 32/34. Required · Fill in: 32/34; params object |
19. Check the 32 Demo Reply
Location: FMQX Web*→*Send Records Steps: Check the same id, code 200, data 32, and the count.

The demo count this time is 1; the independent property state is still required.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| FMQX Demo Reply | Check the same id, code 200, data object, request summary, and actual execution count. Required · Fill in: executionCount 1/2 |
Independent 29/32 state after executionjson
{
"clientId": "FastBee_AlinkUDP_Tutorial_01",
"id": "FastBee_FastBee_AlinkUDP_Tutorial_01_after32",
"version": "1.0",
"method": "thing.event.property.post",
"params": {
"FastBee_temperature": 29,
"FastBee_setpoint": 32
}
}Use a new property id, keep the method as property.post, and keep params as an object.
20. Independently Report 29 and 32
Location: FMQX Web*→*Send Data Steps: After the demo reply, send a separate complete property message: temperature 29, setpoint 32.

This image retakes the independent property state send box and did not send again; the actual state time and result follow the subsequent platform and history records.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| clientId Device Identity | The top-level clientId of the report matches this device number and is carried by every UDP datagram. Required · Fill in: FastBee_AlinkUDP_Tutorial_01 |
| Alink Message id | Each new sample/independent state uses a different number; do not reuse a downlink id as a new property id. Required · Fill in: FastBee_AlinkUDP_Tutorial_01_sample_1…10 |
| version/method/params | version 1.0; the property method is thing.event.property.post; params is an object. Required · Fill in: 1.0; thing.event.property.post; params object |
| Remote Target Address | FMQ UDP listen address. Required · Fill in: 127.0.0.1 |
| Remote Target Port | FMQ UDP entry; do not swap it with the local port. Required · Fill in: 8889 |
| JSON/Text/Send | Complete UTF-8 JSON; wait for the platform to receive each message before continuing. Required · Fill in: Complete message; Send |
21. Refresh and Confirm Current 32
Location: Device Details*→*Running Status Steps: After the independent report, refresh the platform.

Independent state at 2026-10-13T02:53:06.878+08:00; the actual history has the same value.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Current Value | Refresh and check after independent property reporting; do not substitute a pending target. Required · Fill in: 32; final 34 |
The downlink command, demo reply, and independent property state are checked separately; do not look only at a successful send.
6. Verify 34 After Stop and Recovery
22. Stop This Guide's Send/Receive
Location: FMQX Web*→*This Guide's Session Steps: Stop sending and disconnect.

Retain the session and business resources.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Connect/Disconnect | Open after checking this guide's endpoint; close when finished. Required · Fill in: Connected/Disconnected |
23. Restore This Guide's Endpoint
Location: FMQX Web*→*This Guide's Session Steps: Reconnect with the original configuration and continue verifying with the new target.

After recovery, prove uplink and downlink with the new 34 command and independent state.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Connect/Disconnect | Open after checking this guide's endpoint; close when finished. Required · Fill in: Connected/Disconnected |
FMQX sends from local port 15023 to FMQ at 127.0.0.1:8889, and each datagram carries the clientId. After recovery or a source endpoint change, report first to register the return address, then control.
24. Confirm the Recovered 34 Was Actually Received
Location: FMQX Web*→*Receive Records Steps: Deliver 34, and check the new id and the params object.

Actually received at 2026-10-13 02:53:13.984.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Actual Receive Record | Check the command id, params object, and targets 32/34. Required · Fill in: 32/34; params object |
| Setpoint Slider/Send | 32 first, 34 after stop/recovery; the physical device follows the allowed range. Required · Fill in: 32/34 |
25. Check the Recovered 34 Demo Reply
Location: FMQX Web*→*Send Records Steps: Check the same id, code 200, data 34, and the count.

The demo count this time is 2, and the platform shows executionConfirmed=false.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| FMQX Demo Reply | Check the same id, code 200, data object, request summary, and actual execution count. Required · Fill in: executionCount 1/2 |
Independent 29/34 state after recoveryjson
{
"clientId": "FastBee_AlinkUDP_Tutorial_01",
"id": "FastBee_FastBee_AlinkUDP_Tutorial_01_after34",
"version": "1.0",
"method": "thing.event.property.post",
"params": {
"FastBee_temperature": 29,
"FastBee_setpoint": 34
}
}After the demo reply, report independently and manually, then refresh the platform.
26. Independently Report 29 and 34
Location: FMQX Web*→*Send Data Steps: After the post-recovery demo reply, send a separate complete property message with temperature 29 and setpoint 34.

This image retakes the independent property state send box and did not send again; the actual state time and result follow the subsequent platform and history records.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| clientId Device Identity | The top-level clientId of the report matches this device number and is carried by every UDP datagram. Required · Fill in: FastBee_AlinkUDP_Tutorial_01 |
| Alink Message id | Each new sample/independent state uses a different number; do not reuse a downlink id as a new property id. Required · Fill in: FastBee_AlinkUDP_Tutorial_01_sample_1…10 |
| version/method/params | version 1.0; the property method is thing.event.property.post; params is an object. Required · Fill in: 1.0; thing.event.property.post; params object |
| Remote Target Address | FMQ UDP listen address. Required · Fill in: 127.0.0.1 |
| Remote Target Port | FMQ UDP entry; do not swap it with the local port. Required · Fill in: 8889 |
| JSON/Text/Send | Complete UTF-8 JSON; wait for the platform to receive each message before continuing. Required · Fill in: Complete message; Send |
27. Refresh and Confirm Current 34
Location: Device Details*→*Running Status Steps: Refresh after the independent report.

Final temperature 29, setpoint 34; the actual history has the same values.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Current Value | Refresh and check after independent property reporting; do not substitute a pending target. Required · Fill in: 32; final 34 |
7. Query History and Refresh
28. Set the Temperature Ten-sample Query
Location: Data Center*→*Historical Data Steps: Select this guide's device, temperature, and the complete time.

When the date input is truncated, still fill in the complete parameters.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Device and Field | Select the temperature or setpoint of this guide's device. Required · Fill in: FastBee_Alink无线; temperature/setpoint |
| Date and Start/End Time | Temperature and setpoint each use this guide's actual window. Required · Fill in: Temperature 2026-10-13 02:52:40~2026-10-13 02:52:52; setpoint 2026-10-13 02:52:52~2026-10-13 02:53:23 |
| Advanced Filter/Query/Refresh | After refreshing, reselect the same device, field, and complete time, and wait for loading to complete. Required · Fill in: Query, refresh, and re-query |
29. Check 20 to 29 Line by Line
Location: Data Center*→*Historical Data Steps: Wait for loading to complete and check the ten values.

The ten messages are uniquely associated with the actual history.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Advanced Filter/Query/Refresh | After refreshing, reselect the same device, field, and complete time, and wait for loading to complete. Required · Fill in: Query, refresh, and re-query |
30. Query the Independent Setpoint State
Location: Data Center*→*Historical Data Steps: Switch to the setpoint and the corresponding time window.

Check against the actual independent state time.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Device and Field | Select the temperature or setpoint of this guide's device. Required · Fill in: FastBee_Alink无线; temperature/setpoint |
| Date and Start/End Time | Temperature and setpoint each use this guide's actual window. Required · Fill in: Temperature 2026-10-13 02:52:40~2026-10-13 02:52:52; setpoint 2026-10-13 02:52:52~2026-10-13 02:53:23 |
| Advanced Filter/Query/Refresh | After refreshing, reselect the same device, field, and complete time, and wait for loading to complete. Required · Fill in: Query, refresh, and re-query |
31. Re-query the Setpoint History After Refresh
Location: Data Center*→*Historical Data Steps: Refresh, reselect the same conditions, and wait for loading to complete.

The independent 32 and final 34 match the actual storage.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Advanced Filter/Query/Refresh | After refreshing, reselect the same device, field, and complete time, and wait for loading to complete. Required · Fill in: Query, refresh, and re-query |
After refreshing, reselect the same device, field, and complete time, and wait for loading to finish. Check 32 and 34 against the independent state times; the command reply time does not equal the property history time.
8. Finish and Re-accept
Stop sending and disconnect this guide's session; retain the product, device, model, and history. For re-acceptance, record a new time window, send ten different samples, and check the new downlink actual receipt, demo reply, independent state, and history; verify one more round after stop/recovery, then finish and disconnect.
32. Finish Send/Receive and Retain Resources
Location: FMQX Web*→*This Guide's Session Steps: Stop sending and disconnect; retain business resources and history.

This guide's real session is disconnected; the product, device, configuration, and history are retained for re-acceptance.
Screenshot Key Points
| Field / Control | Description |
|---|---|
| Stop and Retain | Stop sending and disconnect the session; retain business resources and history. Required · Fill in: Disconnected; last 29/34 |
| Connect/Disconnect | Open after checking this guide's endpoint; close when finished. Required · Fill in: Connected/Disconnected |
Field and Parameter Reference
Device Access Wizard
| Field / Control | Fill-in Instructions |
|---|---|
| Access Source | Create an independent resource the first time; use the retained resource for re-verification. Required · Fill in: New ProductNew Product: adopted in this guide; adopted in this guide. Existing Product: re-verification uses the retained resource; re-verification uses the retained resource. |
| Product/Device Name | Locate this guide with a concise business name. Required · Fill in: FastBee_Alink无线 |
| Wizard Object Sample | The wizard first parses a plain object to generate two fields; switch to Alink JSON later in the product details. Required · Fill in: {"FastBee_temperature":20,"FastBee_setpoint":30} |
| Field/Type/Unit | Two integer ℃ fields; the identifiers match the params keys. Required · Fill in: FastBee_temperature/FastBee_setpoint; integer; ℃ |
| Device Identifier | The platform number matches the device identity used by this session. Required · Fill in: FastBee_AlinkUDP_Tutorial_01 |
| Initial Overview | 1 device, 2 fields; the wizard starts with JSON/MQTT, and the formal protocol is saved afterward. Required · Fill in: 1 device, 2 fields |
Protocol and Publish Effectiveness
| Field / Control | Fill-in Instructions |
|---|---|
| Data Format | Alink JSON is formally adopted; reporting is an id/version/method/params object. Required · Fill in: Alink JSONPublish after modification. |
| Transport | Choose per this guide; changing only the connection port is not enough. Required · Fill in: UDPPublish after modification. MQTT: topic messages; topic messages. TCP: the device connects actively; the device connects actively. UDP: identity and return address per datagram; identity and return address per datagram. |
| Network Type | WIFI for this guide; the actual endpoint is configured separately. Required · Fill in: WIFIPublish after modification. |
| Publish/Confirm | Publish after saving the formal configuration, and keep checking APPLIED. Publish after modification. |
| Access Configuration Sync | Judge whether it is applied by the actual node receipt. Required · Fill in: APPLIED; success 1, failure 0Publish after modification. |
Function Definition
| Field / Control | Fill-in Instructions |
|---|---|
| Model Translation | Complete the English names. Required · Fill in: Temperature/SetpointPublish after modification. |
| Model Identifier | The keys of the params object match these identifiers verbatim. Required · Fill in: FastBee_temperature/FastBee_setpointPublish after modification. |
| Model Category | Both fields are properties. Required · Fill in: PropertyPublish after modification. Property: adopted in this guide; adopted in this guide. Function: not added in this guide; not added in this guide. Event: not added in this guide; not added in this guide. |
| Read-only Data | Temperature checked, setpoint unchecked. Required · Fill in: Temperature read-only; setpoint writablePublish after modification. Checked: adopted for temperature; adopted for temperature. Unchecked: adopted for setpoint; adopted for setpoint. |
| History Storage | Enabled for both fields. Required · Fill in: CheckedPublish after modification. Checked: this guide keeps actual history; this guide keeps actual history. Unchecked: does not meet this guide's acceptance; does not meet this guide's acceptance. |
| Chart Display/Real-time Monitoring | Temperature on, setpoint off. Required · Fill in: Temperature on; setpoint offPublish after modification. Checked: adopted for temperature; adopted for temperature. Unchecked: adopted for setpoint; adopted for setpoint. |
| Share Permission | Disabled in this guide. Required · Fill in: UncheckedPublish after modification. Unchecked: authorized per account; authorized per account. Checked: sharing configured separately; sharing configured separately. |
| Range/Unit/Step | Temperature -40~100℃, setpoint 16~35℃, integer step 1. Required · Fill in: Integer; ℃; step 1Publish after modification. |
| Modify | Save after completing the required items. Publish after modification. |
FMQX Web Connection
| Field / Control | Fill-in Instructions |
|---|---|
| Import Configuration | Import this guide's independent session and group; credentials are provided separately by the administrator. Reconnect after modification. |
| Local Listen Address | The NIC bound by FMQX; 0.0.0.0 means the local interfaces. Required · Fill in: 0.0.0.0Reconnect after modification. |
| Local Port | FMQX source port and the port where downlink returns. Required · Fill in: 15023Reconnect after modification. |
| Remote Target Address | FMQ UDP listen address. Required · Fill in: 127.0.0.1Reconnect after modification. |
| Remote Target Port | FMQ UDP entry; do not swap it with the local port. Required · Fill in: 8889Reconnect after modification. |
| Enable Broadcast | This guide explicitly unicasts to FMQ. Required · Fill in: OffReconnect after modification. Off: adopted in this guide; adopted in this guide. On: verified separately; verified separately. |
| Connection Timeout | In milliseconds. Endpoint reachability still requires full uplink/downlink verification. Required · Fill in: 5000 msReconnect after modification. |
| Auto Reconnect | Disabled in this guide; stop/recovery is verified manually. Required · Fill in: OffReconnect after modification. Off: manual recovery in this guide; manual recovery in this guide. On: verified separately; verified separately. |
| Test Connection/Save Configuration | Save and then reuse this guide's session; Test Connection does not replace the business closed loop. Reconnect after modification. |
| Connect/Disconnect | Open after checking this guide's endpoint; close when finished. Reconnect after modification. |
Device Reporting and Demo Reply
| Field / Control | Fill-in Instructions |
|---|---|
| Alink Message id | Each new sample/independent state uses a different number; do not reuse a downlink id as a new property id. Required · Fill in: FastBee_AlinkUDP_Tutorial_01_sample_1…10 |
| version/method/params | version 1.0; the property method is thing.event.property.post; params is an object. Required · Fill in: 1.0; thing.event.property.post; params object |
| clientId Device Identity | The top-level clientId of the report matches this device number and is carried by every UDP datagram. Required · Fill in: FastBee_AlinkUDP_Tutorial_01 |
| JSON/Text/Send | Complete UTF-8 JSON; wait for the platform to receive each message before continuing. |
| Actual Receive Record | Check the command id, params object, and targets 32/34. Required · Fill in: 32/34; params object |
| FMQX Demo Reply | Check the same id, code 200, data object, request summary, and actual execution count. Required · Fill in: executionCount 1/2 |
Device Running Status
| Field / Control | Fill-in Instructions |
|---|---|
| Setpoint Slider/Send | 32 first, 34 after stop/recovery; the physical device follows the allowed range. |
| Current Value | Refresh and check after independent property reporting; do not substitute a pending target. Required · Fill in: 32; final 34 |
Historical Data
| Field / Control | Fill-in Instructions |
|---|---|
| Device and Field | Select the temperature or setpoint of this guide's device. Required · Fill in: FastBee_Alink无线; temperature/setpoint |
| Date and Start/End Time | Temperature and setpoint each use this guide's actual window. Required · Fill in: Temperature 2026-10-13 02:52:40~2026-10-13 02:52:52; setpoint 2026-10-13 02:52:52~2026-10-13 02:53:23 |
| Advanced Filter/Query/Refresh | After refreshing, reselect the same device, field, and complete time, and wait for loading to complete. |
Stop and Recovery
| Field / Control | Fill-in Instructions |
|---|---|
| Stop and Retain | Stop sending and disconnect the session; retain business resources and history. Required · Fill in: Disconnected; last 29/34 |
Where to Check First When Problems Occur
| Symptom | Possible Cause | Where to Check First | How to Recover |
|---|---|---|---|
| Platform does not update after connecting | The identity, formal format, or reporting address does not match. | This device number, Alink JSON, APPLIED, and this guide's endpoint. | Fix the configuration and send the complete envelope with new message ids and a new time window. |
| Reporting exists but no downlink | The MQTT subscription is wrong, or the UDP return address has not been registered yet. | For MQTT, use this device's function/get; for UDP, check the local port and the most recent report. | Enable the correct subscription, or first report completely to register the address, then deliver a new target. |
| Repeated sending still produces no new history | Message ids are reused, or the query window does not match. | Whether each new property id is unique and whether params is an object. | Use new message ids and record new times; do not delete old data to hide the problem. |
| Reply succeeded but the current value did not change | The property state has not been reported independently yet. | Whether there is an independent property.post params after the reply data. | Report independently and manually, then check the real-time value and history. |
| The count starts from 2 | An earlier command was demo-executed and retained. | The command id, receive time, and actual count. | Check separately; do not mix earlier actual receipts with the formal reply. |
| Values missing after refreshing history | The device, field, or complete time does not match. | This guide's temperature and setpoint time windows given by the adjacent parameters. | Reselect the conditions and wait for loading; record a new window during re-verification. |


