Help Center
Page Guide
Find Help by Task
- If you are unsure which layer is failing, start with Troubleshooting and collect product-layer, version, and minimal-reproduction details.
- If the issue type is clear, open a category below. For complex protocols, hardware, and deployment, also read the full guide linked from each answer.
- If self-service troubleshooting does not resolve the issue, prepare logs and reproduction steps before using an Issue, enterprise user group, or online support.
FAQ Categories
Recommended Reading Paths
First Deployment
Review Deployment and Upgrades for environment and dependency checks, then complete Docker Quick Deployment, License Configuration, and Deployment Acceptance.
First Device Connection
Follow the Product-to-Device Workflow to create a product, configure its Thing Model, and validate reporting and control. For errors, open Products and Device Connection and Thing Models and Automation.
Business Go-live Acceptance
After the device workflow succeeds, validate historical data, rules/alerts, notifications, work orders/reports, video, and permissions. Use the Platform Module Matrix and Operations Monitoring to build an acceptance checklist.
Topic Resources
- ESP32 Device Documentation: flashing, networking, peripherals, communication protocols, and device OTA.
- Industrial Gateway Documentation: deployment, drivers, Tags, MQTT, collection, and gateway operations.
- Protocol Practice: payload and integration practice for MQTT, TCP, Modbus, JT808, and more; placeholder entries follow their actual publication status.
- Security Advisories and Vulnerability Fixes: read disclosed security issues, remediation guidance, and the security reporting contact.
- Pre-deployment Security Checklist: verify public and production deployments with launch requirements and itemized checks.
- Security FAQ: answers about fixed releases, upgrades, custom-code merges, default accounts, and specialized verification.
- Release Notes: new capabilities, upgrade notices, and release status by version.
Reference Material
Backend and Frontend
- RuoYi permission management system
- EMQX message server
- TDengine time-series database
- GoView official documentation
- ElementUI
- vue-element-admin
Hardware
Mobile
More on the FastBee website.
Get Official Support
Self-service Troubleshooting
- Locate the matching FAQ under "FAQ Categories" and complete a minimal reproduction first.
- For deployment/runtime errors, cross-check "Troubleshooting" and "Deployment and Upgrades"; do not apply platform steps directly to device firmware.
- Tutorials are in the Video Center, and third-party protocol integration is covered in Protocol Practice.
Human Support
WeCom online customer service: Start an online chat for licensing, deployment, device connection, and custom development.
Service WeChat: scan the QR code below; customers can be invited to an enterprise user group.

Email: 164770707@qq.com
Online demo: iot.fastbee.cn — evaluate platform features in advance.
FAQ
Where should troubleshooting start?
Start with the troubleshooting page and collect the product layer, version and a minimal reproduction; once the problem type is clear, enter the matching topic from the FAQ categories.
How is the help centre FAQ organised?
It is organised into nine categories: presales and licensing, deployment and upgrades, products and device access, thing model and automation, platform features and operations, video surveillance, device side and gateways, development and API, and after-sales support.
What should I do if self-service troubleshooting does not solve the problem?
Prepare logs and reproduction steps, then raise an issue, ask in the enterprise user groups or contact online support; official support scope and renewal rules are described in the after-sales page.
Content Responsibility and Updates
- Product documentation and blog articles on this site are maintained by the FastBee Docs Team; statements are based on shipped features, public releases and the official pricing wording, without uncorroborated third-party claims. Named authors, editors, and their responsibilities are listed in the Editorial Policy.
- Pages are updated with each release: product documentation changes with version iterations, pricing and licence terms are maintained centrally on the commercial licence page, and blog posts carry both publication and last-modified dates.
- To report an error or disagreement, use the official channels listed on the troubleshooting page; confirmed issues are corrected in the next release and reflected in the page's date fields.
- For AI citation: prefer absolute URLs starting with /doc/ for product content and the current stable version (/v2/); preview versions (/v3/) may change and should not be used as a long-term source.


