Learn the product definition (object model), which can help you more accurately and flexibly call the interface to access the device.
Product definition
| 2.1 | State property | |
| 2.2 | Trigger event | |
| 2.3 | Configuration item |
2.1 State property
The status attribute is the basic material model of the product, which determines the function of the product.
By issuing commands, human operations can change these status attributes；
If it is a sensor class or a product with sampling function, the environment will also change the device status attribute.
By issuing commands, human operations can change these status attributes；
If it is a sensor class or a product with sampling function, the environment will also change the device status attribute.
| Property | Options | Value | Description |
|---|---|---|---|
| power | 打开 | 1 | |
| 关闭 | 0 |
2.2 Device command
The device supports the following commands, and can send these commands to the device through the interface.
When private (Broker, gateway, etc. in any way), the command sending method is different, but the content is the same.
When private (Broker, gateway, etc. in any way), the command sending method is different, but the content is the same.
System command（All products support）
| Name | Content | Description |
|---|---|---|
| 网络信息 | {"system":"network"} | View the current network information of the device: network type, signal strength, IP address, etc. |
| Soft reboot | {"system":"restart"} | Restart the device and try to maintain the current state as much as possible |
| Hard reboot | {"system":"reboot"} | Restart the device, abandon the current state |
Commands of this product
| Command | Name | Content | Description |
|---|---|---|---|
|
先通后断 point |
1秒 | {"point":"1000"} | |
| 2秒 | {"point":"2000"} | ||
| 3秒 | {"point":"3000"} | ||
| 5秒 | {"point":"5000"} | ||
|
先断后通 reset |
1秒 | {"reset":"1000"} | |
| 2秒 | {"reset":"2000"} | ||
| 3秒 | {"reset":"3000"} | ||
| 5秒 | {"reset":"5000"} |
2.2 Trigger event
When the device property status value changes because of the following two reasons:
1. Self-state changes (such as the value of a sensor changes);
2. Human operation (pressed the device button)
After the event is triggered, the platform will carry the current status parameter of the device, and report the message in real time,
The specific mechanism is described in "Section 5: Message push"
1. Self-state changes (such as the value of a sensor changes);
2. Human operation (pressed the device button)
After the event is triggered, the platform will carry the current status parameter of the device, and report the message in real time,
The specific mechanism is described in "Section 5: Message push"
Public event（All products support）
| Name | Content | Description | |
|---|---|---|---|
| Power on | {"name":"boot","state":{Current attribute value}} | Device power on, cloud registration after trigger, report with the current status (the value of each function attribute) | |
This product event
| Event | Name | Description |
|---|---|---|
| Press the button | btn1 | |
| 信号输入 | btn2 |
2.3 Configuration item
All configuration items are saved in the Flash of the device, because Flash has a write limit,
So the platform does not open the interface to modify the configuration of the device in batch, you can modify the configuration item in the console.
All configuration items have default values, such as do not understand the meaning of the configuration item, do not modify it randomly;
Modifying the configuration item can only be successfully sent and saved when the device is online, and does not require a restart of the device.
So the platform does not open the interface to modify the configuration of the device in batch, you can modify the configuration item in the console.
All configuration items have default values, such as do not understand the meaning of the configuration item, do not modify it randomly;
Modifying the configuration item can only be successfully sent and saved when the device is online, and does not require a restart of the device.
Configuration item
| Configuration item | Name | Content | Description |
|---|---|---|---|
| relay1 | 通 | 1 | |
| 断 | 0 | 默认 | |
| action1 | 状态反转 | reverse | 默认 |
| 先断后通 | reset | ||
| 先通后断 | point | ||
| 禁用 | dis | ||
| time1 | 1秒 | 1000 | |
| 2秒 | 2000 | ||
| 3秒 | 3000 | ||
| 4秒 | 4000 | ||
| 5秒 | 5000 | ||
| action2 | 状态反转 | reverse | 默认 |
| 先断后通 | reset | ||
| 先通后断 | point | ||
| 禁用 | dis | ||
| time2 | 1秒 | 1000 | |
| 2秒 | 2000 | ||
| 3秒 | 3000 | ||
| 4秒 | 4000 | ||
| 5秒 | 5000 |
Attachment. Firmware list
The principle of firmware update is compatibility upgrade, that is, the new firmware version will retain the original functions and commands.
If the current firmware can meet the business requirements, you can not upgrade the latest version of the firmware.
If the current firmware can meet the business requirements, you can not upgrade the latest version of the firmware.
Last 10
| Version | ID | Size | Release date | Description |
|---|---|---|---|---|
|
V4 p33.20251203.v4 |
id.1407 | 294.1 KB | 2025-12-03 15:16:43 | 无 |
| id.1408 | 294.1 KB | 2025-12-03 15:28:17 | 无 | |
|
V3 p33.20250912.v3 |
id.1267 | 292.29 KB | 2025-09-12 15:08:36 | 无 |
| id.1268 | 292.29 KB | 2025-09-12 16:32:42 | 无 | |
|
V1 p33.20240122.v1 |
id.341 | 339.13 KB | 2024-01-22 19:40:25 | 无 |