Please submit your question to the Cassia Support Team
- Which ports need to be opened for router and AC server to communicate?
A: TCP 80, 443, UDP 5246 and 5247
- What factors will affect Cassia router long-range coverage and stable connection of BLE devices?
A: Connection interval, Transmit speed, Noise floor, and BLE device capability
- Which type of profile (Bluetooth SIG standard or User Specific) used by Cassia router?
A: E1000 is supported SIG standard profile
- Is the connectivity up to 40 achieved with bi-direction or uni-direction communication?
A: bi-direction communication is supported today with the Cassia E1000 router, when a device is connected. user can call `writeHandle()` & `readHandle()` for get device data. If the router as a scanning mode for advertised data, hundreds of devices’ data can be captured in `uni-direction` communication.
- Is the API converting the data from BLE device to Cassia router?
A: Cassia router is not altering the BLE payload data from BLE device to the API.
- I’m looking at transmitting an audio signal via Bluetooth to multiple Bluetooth devices. Will this device support that?
A: Cassia long-range Bluetooth hub only supports half-duplex audio/music streaming with BT protocol v3.0 or lower.
- Please provide a little more specific in that where E1000 router with nRF52832 is BT5 compatible we don’t yet support any features of it
A: To clarify BTv5 compatible means this particular nRF52832 chip (http://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF52832) doesn’t support the long-range and the mesh, but it does support the high throughput, improved coexistence, and advertising extension. At this time the Cassia router already has the patented long-range communication (up to 1000 feet), this missing feature doesn’t impact our current capability. Once we are ready to design our next generation of Cassia router solution, the newer Nordic chip with full BT5 features will be used, the range is expected to increase beyond what we have now.