Error Handling
SDK operation failures raiseWujiException or one of its subclasses, such as NodeOfflineError, so catch WujiException at the SDK boundary. Only argument-type or overflow errors that the Python interpreter raises before the SDK call keep their native exception types:
Reconnection Strategy
After disconnection, reconnect and resubscribe:Multi-device Coordination
Collect data from multiple devices simultaneously:Cross-device Merged Data
In multi-device setups, use global resources to get aggregated data from all devices without manual merging:Log Control
Adjust SDK log level for debugging:Device Logging
Device logging access varies by product. See the corresponding device documentation:Data Collection and Privacy
Wuji SDK uploads anonymous usage data by default to help improve the product. It doesn’t collect personal or sensitive information. For more details, see the Privacy Policy. On first use, the terminal shows the following privacy notice:WUJI_TELEMETRY_DISABLE to 1 or true before starting the application.
Recording Best Practices
Choose the Right Compression
- Use
"lz4"for real-time capture (low latency). Use"zstd"for long-term storage (high compression ratio) - For high-frequency channels (>500 Hz), prefer
"lz4"to avoid compression becoming a bottleneck