App and Mini Programs
The FastBee mobile client brings devices, scenes, alerts, news, and account features together. Choose the guide for the native app, WeChat Mini Program, or H5 web client. They share some pages, but differ in login authorization, camera, Bluetooth, notification subscriptions, and updates.
Page Guide
| Task | Start here | What to check |
|---|---|---|
| Install the app, sign in, or add a device | Installation, Login, and Binding | Installation source, account environment, and device number |
| Check readings, history, command results, or alerts | Devices, Real-time and Historical Data, Control, Alerts, and Messages | Units, timestamps, device feedback, and alert status |
| Use the mobile client in WeChat | Login Authorization and Binding | Mini Program ownership, platform account, and authorization scope |
| Integrate, build, or release | Source Code, Environment, and API Configuration | Client and backend versions, target platform, and test and release environments |
1. App Guide
After signing in, use Home to find a device by group or open the Add Device menu. Check live readings and history from Device Details, and send commands only with authorization. Alert shows device alerts; Me → Platform Message shows platform notices.
2. Mini Program Guide
Confirm that the WeChat Mini Program belongs to your deployment, complete login authorization, and verify the platform account. Then see Device Viewing and Control and Alerts, Notifications, and Permissions. Verify notifications, scanning, and Bluetooth in WeChat on a physical device.
3. Development and Release
Configure the service endpoints and test the integration first. Then follow App Build, Signing, and Release or Configuration, Review, and Release for your target. Before publishing, review the upgrade order and fallback plan in Frontend-Backend Version Compatibility.
Images and verification scope
Some figures mark where screenshots will be added; they do not depict the current interface. Use H5 to check menus and shared workflows, not as a substitute for WeChat authorization, native installation, device provisioning, or release acceptance.
4. FAQ
Can H5 replace the app or Mini Program?
H5 is suitable for browser integration and checks of shared features. Test native installation, WeChat authorization, scanning, Bluetooth, and notification subscriptions on the target platform.
What should I check if no devices appear after login?
Confirm the service environment, account, and tenant scope, then check Home groups and filters. Being signed in does not grant access to a particular device.
Why is my device still offline after binding?
Binding makes the device visible to your account. It does not connect the device to the platform. Confirm the device number in Device Details, then check power, network connectivity, and device connection settings. After the device comes online, wait for the property you want to check to report a reading.
5. First Use: Verify One Device
- Confirm your identity. Sign in with the app or Mini Program for the target environment and confirm your account under Me. Look for existing devices on Home; add a device only if you need to create an association.
- Verify a reading. Open a device you are authorized to view. Note its number, property, unit, and timestamp. Check real-time monitoring, then query a history range that includes the report. If history is empty, check storage settings separately instead of binding the device again.
- Verify control or notifications when needed. Use a test device to verify one command and its feedback only if you have permission and it is safe to do so. For WeChat, follow the notification subscription workflow to verify the alert record and actual delivery. Stop after step 2 for a read-only check.
6. Find the Right Troubleshooting Guide
| What you see | What to do first | Guide |
|---|---|---|
| A device appears under All but not in a group | Check group membership and Home filters instead of binding it again | Devices, Real-time and Historical Data |
| A device is online but one property has no reading | Use the device number and property to check whether the platform received a report for that measurement | Devices, Real-time and Historical Data |
| There is a command log, but the device state did not change | Stop resending. Check device feedback, the connection path, and the physical state | Control, Alerts, and Messages |
| The Mini Program lists an alert, but WeChat did not receive a message | Check the template and subscriber, then ask an administrator to verify delivery | Alerts, Notifications, and Permissions |
| H5 sign-in works, but the WeChat trial build cannot sign in | Check trial access, AppId, and the actual environment the trial build calls | Configuration, Review, and Release |


