Device Viewing and Control
The Mini Program and app share the main device workflow. WeChat authorization and page access do not grant control permissions. Available actions depend on the device Thing Model and the account's permissions.
1. Before You Start
| Item | Details |
|---|---|
| Entry point | Home → Device card → Device Details |
| Permissions | Device viewing permission; check control permission separately before sending a command |
| What to prepare | Device number, a property that reports data, an authorized test device, and the expected feedback |
2. View the Device and Its Data
- Select the device group on Home. If you cannot find the device, switch to All and clear filters. Open the card and check the device number, product, and online status.
- Check the status and timestamp in Overview, then open the monitor tab to verify the property and unit. For history, choose the appropriate time range and property in History Statistics. No Data is not a zero value.
- To add a device, follow Login Authorization and Binding. For camera, Wi-Fi, or BLE, verify permissions and provisioning on a supported physical device.
What to check: The final figure will show the Device Details tabs. If a card is online but has no reading, check the last report in Device Details and whether the property is collected.
3. Send a Command and Verify Feedback
- In Overview, find an action provided by the product and confirm the device number, parameters, and physical effects. Do not trigger actions when you only need to inspect the device.
- Send once on an authorized test device and wait for the result. If there is no response, check the online status and runtime connection before retrying.
- Check the command or service execution record in Records and verify actual execution from device feedback or observed state. Ask an administrator to check permissions instead of switching environments to bypass them.
4. Example: Verify Read-only and Control Accounts Separately
- Use a read-only account to open an authorized test device. Check the device number, live property, unit, and latest report. When comparing with the management console, use the same environment, device number, and time range. The read-only account should be able to view authorized data without being able to send a command successfully.
- Switch to an account authorized to control the device. If the test device exposes a switch or service that is safe to test, record its initial state, send one command, and check the command log and device feedback. Stop at viewing if the device is offline, permission is unclear, or the physical state is unknown.
- If the Mini Program and app show different results, compare the signed-in accounts and device numbers first, then check data timestamps and permissions. Do not use the result from one platform to sign off on another.


