TetherX vs KGateway

TetherX puts your entire physical infrastructure at your fingertips. Monitor video surveillance, control access systems, track sensors, and manage alarms across all your sites from a single, beautifully designed app. UNIFIED MONITORING - Live video feeds from all your cameras - Real-time sensor data and environmental monitoring - Alarm status and instant notifications - Access control management POWERFUL FEATURES - Push notifications for critical alerts - Secure biometric authentication (Face ID / Touch ID) - Fast, native performance BUILT FOR PROFESSIONALS - Control room operators - Security managers - Facility managers - System integrators TetherX connects to your existing infrastructure through our secure gateway, giving you complete visibility and control whether you're on-site or on the go. Requires a TetherX account. Visit tetherx.io to learn more.

KGateway is a configuration app, through which you can configure the BLE/Wi-Fi gateway launched by KKM. This app supports configuration of the following parameters: 1. Wi-Fi connection information. 2. BLE scan parameters, filter parameters. 3. HTTP or MQTT server information connected by the gateway. After provision by the app, the gateway(BLE/Wi-Fi) can connect the BLE Beacon/Sensor devices, and can report the sensor data from Beacon/Sensor devices to the cloud. Why does this app need location permission? Because the app needs to scan the SSID information of the KGateway when configuring the KGateway for the first time, and the location permission is required for IOS to scan the Wi-Fi SSID information. Why does this app use the HTTP not HTTPs protocol? This app only uses HTTP protocol to connect to the KGatway(WiFI-BLE gateway) for provision. Because the KGateway's internal resources are limited, the device only supports the HTTP protocol. In addition, because the app will only perform provisioning when the KGateway is used for the first time, and the app and the KGateway device must be under the same Wi-Fi router during provisioning, the security risk of using the HTTP protocol for Provisioning is controllable.