App version 5.26.0 · June 2026
This release is an onboarding-reliability update for the eSphere mobile app. It resolves two onboarding issues — including one that could remove already-added sensors from an account during multi-sensor setup — and improves the sensor setup flow.
New Features and Enhancements
| Name | Description |
|---|---|
| Timeout Recovery Messaging | Added a clearer recovery path with a “sign out / try again” error message when the main controller hits a loading timeout, so you can recover from a stalled load. |
| Sensor View Cleanup | Removed the signal history section from the sensor view under the More tab to reduce noise and simplify the experience. |
| Smoother Camera Permission Step in Sensor Setup | The app now advances automatically to the QR scan screen as soon as camera permission is granted, eliminating the extra tap previously required. |
Resolved Issues
| Name | Description |
|---|---|
| Added Sensors Removed When Multi-Sensor Setup Was Interrupted | Fixed a critical data-loss issue where exiting multi-sensor onboarding early and returning to add a remaining sensor could silently remove already-added sensors from the account. |
| Profile Screen Shown Prematurely During Sensor Setup | Fixed an issue where the “Add/Select Your Profile” screen briefly appeared before the setup success screen. The app now proceeds directly to the success screen, with the profile screen appearing only at its intended point afterward. |
| App Crash on Session Replay Initialization | Fixed a crash caused by a session replay initialization failure. A failed initialization no longer brings down the app. |
| Non-Presence Device Display | Corrected incorrect labeling of non-presence devices on a profile. They now display with a clear status (for example, “No presence detection”) instead of a placeholder. |
| iOS Media Permission Popup | Fixed a repeating “Media permission denied” popup on iOS. The prompt now appears only once and does not reappear after the initial dismissal. |
Platform Characteristics
| Name | Description |
|---|---|
| Account Deletion Requires All Residents to Delete First | A primary user cannot delete an account independently. Each resident must delete their account before the primary user is able to do so. |
| Halo Connect Requires a 2.4 GHz Network | Similar to many IoT products and services, the eSphere Halo Connect sensor requires a 2.4 GHz Wi-Fi network for setup and operation. This requirement is met by the vast majority of home Wi-Fi networks. |
| Split 2.4 GHz / 5 GHz Wi-Fi Networks | eSphere Halo presence sensors are designed for single-SSID networks. Split 2.4 GHz and 5 GHz SSIDs typically function correctly, though further customizations such as network isolation features (guest networks, VLANs, client isolation, or separate subnets) may reduce accuracy or prevent presence detection. |
| MAC Address Rotation Can Cause Presence Inaccuracies | Devices that do not use a fixed MAC address on their home network may produce unreliable presence detection for Wi-Fi-only visitor profiles. |
| Force Quit or App Update May Cause Presence Reliability Issues | If the app is force-quit or closed by an OS or app update, you may experience temporary presence detection issues for that device. |
| Disabling Wi-Fi or Bluetooth Triggers a False Exit | Turning off Wi-Fi or Bluetooth, or powering down the device, will register as the user leaving the home. |
| Rejected App Permissions May Prevent Setup or Reduce Accuracy | Denying any prompted permission may block sensor setup or degrade presence detection accuracy. |
| Minimum OS Requirements: iOS 15.1 / Android 7.0 | The eSphere app requires iOS 15.1 or Android 7.0 at minimum. |
| Account Limited to 4 Halo Connect Plugs | A single account cannot use more than 4 Halo Connect plugs at this time. |
| Samsung Extreme Battery Saver Causes Unreliable Presence | Samsung users who enable extreme battery saver and have not allowed eSphere to run in the background will experience unreliable presence detection. |