Product To Device Closed Loop

fastbeeAbout 2 min

Page Guide

ScenarioUse this flow when a new user needs to understand how FastBee organizes products, devices, thing models, and device messages.

PrerequisitesThe demo environment can be opened, and MQTTX or an equivalent MQTT client is available.

GoalCreate a product, define properties and functions, create a device, report data, and verify command delivery.

Create a product first. The product determines the device type, protocol, networking mode, and thing-model template used by devices.

Recommended fields:

Field	Recommendation
Product name	Use a business-readable name, such as `Demo Temperature Sensor`.
Device type	Choose direct device, gateway, sub-device, video device, or other types according to the scenario.
Protocol	Use MQTT for the first verification.
Data format	Keep the platform default format unless the project has a custom protocol.

Define properties, functions, and events before releasing the product.

Type	Purpose	Example
Property	Device status or telemetry	Temperature, humidity, switch status
Function	Platform command delivered to device	Turn on relay, set threshold
Event	Important device event	Alarm, fault, offline notice

After the product is released, create a device and copy the MQTT credentials.

Pay attention to product ownership, device number, device secret, and status. Device credentials must match the MQTT access document exactly.

Use MQTTX to connect to the platform, report a property, and subscribe to command topics.

After reporting data, check the device running status, logs, and latest property values in the console.

Problem	Check
Device cannot connect	Product status, device credentials, MQTT host, port, and firewall.
Data is not displayed	Topic format, payload format, thing-model identifier, and product protocol.
Command is not received	Device subscription topic, online status, and function identifier.
Device belongs to wrong tenant	Department, tenant, and product visibility settings.