Comparable Projects and Integration Boundaries
This page helps you verify configuration approaches and project positioning. It does not rate quality by star counts, lines of code, or test counts, and it does not present unverified third-party integrations as compatible. Verified on 2026-10-11; refer to each project's official documentation for specific versions and component support.
Configuration Approach
| Project | Configuration and Purpose | Reference |
|---|---|---|
| FastBee-Arduino | Web-based device configuration for peripherals, execution rules, MQTT/MQTTS, and a Modbus RTU master; features must pass compilation, user selection, and resource admission | Feature Overview, Capabilities and Acceptance Boundaries |
| ESPHome | Uses Device Builder or YAML to define components and build device firmware, with Home Assistant integration | Official site |
| Tasmota | Provides web, commands, templates, rules, and extended capabilities through corresponding builds | Official docs |
| WLED | Focused on LED lighting and effects control; verify board models, interfaces, and features per version | Official docs |
| OpenMQTTGateway | A gateway between devices/wireless protocols and MQTT; supported scope depends on components and hardware | Official docs |
Do not mark features unlisted by other projects as unsupported, and do not interpret FastBee's source paths, page options, or test counts as superior to all products.
Current FastBee Capabilities
- Release builds cover nine Flash/PSRAM combinations across ESP32, C3, C6, and S3; specific carrier boards still require individual verification.
- Networking is selected via
networkType: WiFi, W5500, or a cellular adapter. W5500/4G only compile in certain environments and are disabled by default at runtime; there is no general promise of fixed-priority automatic switching from Ethernet to WiFi to 4G. - The main business protocols today are MQTT/MQTTS and a Modbus RTU master. Web services, OTA/time requests, and fixed weather resources do not equal generic HTTP telemetry, Modbus TCP, or arbitrary TCP/CoAP client protocols.
- Web login uses sessions and user passwords. The platform ClientId S/E authentication differs from web sessions; do not collectively call it web "Token + AES authentication".
- Application OTA requires compilation capability, an upgrade slot, and internal DRAM; OTA is disabled in the 4MB release environment, and no standalone filesystem OTA writer is currently provided.
- Configuration recovery uses a whitelist and whole-group validation. Switching boards requires reviewing capabilities, remapping wiring, and disabling outputs; identity/network/protocol settings do not migrate with a reusable plan, so you cannot simply "copy one device's configuration to any N devices".
- Template conversion and command scripts use the current restricted engine; a general-purpose JavaScript runtime is not promised. Compiled, enabled, instance-present, valid business, and physically verified are judged separately.
The 4MB partition layout allocates 3.1875MiB for the app and 768KiB for LittleFS; see Hardware and Environments for other layouts and feature differences.
Third-Party Platform Integration
Standard MQTT provides the transport foundation, but integration also requires verifying the platform's authentication, topics, payloads, device identity, TLS, and received results. The FastBee platform also requires actual configuration and product binding—it is not configuration-free.
| Requirement | Boundaries to Verify Today |
|---|---|
| Generic MQTT Broker | server/port/scheme, authentication, ClientId, topics/payloads, and the data received by the platform |
| Home Assistant | MQTT and external bridging are available; the firmware currently does not promise automatic Discovery generation or a native HA API |
| Data platforms and flow orchestration | Require platform-side protocol/field conversion and real end-to-end verification; device-model compatibility is not automatic |
| Platforms requiring client certificates or proprietary token generation | The current MQTT configuration has no generic mTLS path that accepts an uploaded clientCert/privateKey; you cannot promise integration with AWS and similar platforms just by filling in a TLS address |
Current release reporting uses PubSubClient at QoS 0; subscription QoS, configuration values in topics, and business delivery guarantees are separate matters. On TLS failure or low memory, keep the secure protocol and pause with backoff; do not automatically downgrade to plaintext to gain a successful connection.
For integration steps, see MQTT Configuration. The final choice should be validated with actual board models, feature combinations, resource peaks, and maintenance workflows; this page does not replace Testing and Release Acceptance.