How does ChirpStack handle data isolation for different organizations in a multi-tenant setup?
ChirpStack's multi-tenant application-server integrates user accounts into the MQTT broker authentication. This ensures that each organization can only access and view its own data, maintaining strict data isolation.
Can ChirpStack optimize the data rate and power consumption of LoRaWAN end-devices?
Yes, when Adaptive Data-Rate (ADR) is enabled on an end-device, ChirpStack's LoRaWAN network server actively manages the device's data-rate and transmit power. This not only conserves device energy but also optimizes radio spectrum usage, reducing the risk of collisions.
What kind of debugging capabilities does ChirpStack offer for LoRaWAN frames?
ChirpStack provides a live frame-logging feature that acts like a 'Wireshark for LoRaWAN'. It displays all RX/TX metadata along with the raw LoRaWAN PHYPayload in a readable format, enabling detailed debugging of communication between gateways and devices.
Is it possible to customize the LoRaWAN channels used by devices within ChirpStack?
Yes, the ChirpStack LoRaWAN network server allows for flexible channel (re)configuration. Users can define a subset of LoRaWAN channels (e.g., for the US band) or add additional channels (e.g., for the EU band), and the server ensures devices remain synchronized with the network's configured channels using CFList and/or MAC commands.
What types of APIs does ChirpStack offer for integrating with external systems?
ChirpStack provides both gRPC and REST APIs for integration with external services. Additionally, all application data is published to an MQTT broker by default, and specific integrations are available for various cloud providers, databases, and visualization platforms.