App version 5.27.0 · July 2026
This release focuses on profile-creation reliability, Bluetooth pairing security, and a number of interface and copy refinements — including a redesigned, step-by-step visitor creation flow.
New Features and Enhancements
| Name | Description |
|---|---|
| Updated Visitor Creation Flow (Create Visitor 2.0) | Visitor creation has been redesigned as a guided, step-by-step flow. It adds a clearer explanation of the value of adding a visitor, better guidance for connecting the visitor’s phone to the correct home network, a clearer confirmation once the visitor’s presence device is detected, an updated details step for name, photo, description, and phone number, and a modern dark (Nightlight) theme consistent with the app’s new design direction. |
| Improved Alert Feedback | You can now mark any presence alert as correct or incorrect using a thumbs-up or thumbs-down control. Responses are captured to help improve alert accuracy. |
| Optimized Sensor QR Scan Instructions | Scan instructions and error messaging during sensor setup now clearly direct you to the QR code on the back of the presence sensor and clarify the conditions needed for a successful scan. |
| Added Third-Party Licenses Info | A new Third-Party Licenses section at the bottom of the More tab lists the open-source libraries used in the app, along with license details for each. |
| Support Contact Options (Trial Accounts) | The in-app call-support option is now hidden for trial accounts. It will return once each provider’s dedicated support line is available. |
Resolved Issues
| Name | Description |
|---|---|
| Residents’ Onboarding Blocked with Text Accessibility Enabled | Resolved an issue where Residents’ onboarding screens were not adapted for larger system text sizes, which could prevent Residents using larger text or accessibility settings from completing onboarding. |
| Profile Creation Not Enforced After Hard Close | Resolved an issue where a primary user without a profile could hard-close and reopen the app to reach the Home screen instead of being returned to profile creation. |
| Bluetooth Pairing Could Match Unrelated Devices | Resolved an issue where in-app Bluetooth pairing identified sensors by device name only, which could cause the app to match unrelated nearby devices during setup. |
| Email Verification Screen Display Issues | Resolved minor visual inconsistencies on the email verification screen, including spacing, link styling, disabled-button contrast in dark mode, and extra empty space within the modal. |
| Untrusted Person Info Modal | Resolved a display issue with the informational modal for Untrusted Person opened from the profile creation screen. |
Known Issues in This Release
| Name | Description |
|---|---|
| Alert Feedback Not Shown After Selection | After selecting thumbs-up or thumbs-down on the “Was this correct?” alert feedback prompt, the feedback message and icons no longer display, and the prompt does not reappear if the alert is closed and reopened. |
| Formatting Issues at Large Text Scaling | Formatting issues occur when the mobile device text size is dynamically scaled to Large. |
| Missing Error Message Off Home Wi-Fi | When the primary user is not connected to their home Wi-Fi network, the expected error message does not display in place of the QR code. The correct message appears if the device is on a non-home Wi-Fi network; on a cellular network, the loading icon displays instead. |
| Sensors Bouncing Online/Offline | Sensors have been reported bouncing between online and offline status with no environmental change. A firmware update addressing this has tested successfully and is coming soon. |
| Notifications Stopped Displaying | Push notifications have been reported as not received even when notifications are set to active. |
| Inaccurate Alert Notifications | Location status reported in notifications (for example, left home / arrived home) has been reported as inaccurate. |
Platform Characteristics
These are known platform behaviors that apply across releases.
| Name | Description |
|---|---|
| Account Deletion Requires All Residents to Delete First | A primary user cannot delete the account on their own. Each resident must first delete their own account; only then can the primary user delete the account. |
| Account Deleted Outside the App | If an account is removed outside the in-app delete-account flow, the app can be left in a broken state on next launch, including a crash, a stuck loading screen, or an unresponsive sign-out button. Deleting your account from within the app is unaffected and safe to use at any time. A fix is planned for an upcoming release. |
| Halo Connect Requires a 2.4 GHz Network | The Halo Connect plug works only on a 2.4 GHz network. Nearly all homes have a 2.4 GHz band, but it is required. |
| Split 2.4 GHz / 5 GHz Wi-Fi Networks | eSphere’s Halo presence sensors are designed for single-SSID networks. Split 2.4 GHz and 5 GHz SSIDs typically work correctly, though additional customizations such as network-isolation features (guest networks, VLANs, client isolation, or separate subnets) may reduce accuracy or prevent presence detection. |
| Mesh Wi-Fi Systems May See Performance Impact | On mesh Wi-Fi systems with a large number of assigned IP addresses (such as Eero), the sensor’s Wi-Fi device-scanning can generate enough additional network traffic to affect Wi-Fi performance, particularly when the mesh satellites connect to one another wirelessly rather than by Ethernet. Scan behavior is being tuned to reduce this impact while preserving Wi-Fi-based presence detection. |
| MAC Address Rotation Can Cause Presence Inaccuracies | MAC address rotation can cause presence inaccuracies for Wi-Fi-only visitor profiles on devices that do not have a fixed MAC address on the home network. |
| Force Quit or App Update May Cause Presence Reliability Issues | If you force quit the eSphere mobile app, or if the operating system or an app update forces it to close, you may experience presence reliability issues on your device. |
| Disabling Wi-Fi or Bluetooth Triggers a False Exit | If you disable Wi-Fi or Bluetooth on your mobile device, or turn the device off, this can cause a “false exit” that makes it appear your profile has left the home. |
| Rejected App Permissions May Prevent Setup or Reduce Accuracy | If you decline any of the prompted mobile app permissions, this may prevent sensor setup or reduce presence detection accuracy. |
| Building Materials Can Reduce Sensor Range | Dwellings built with materials such as metal, thick concrete, or brick will likely reduce the RF range used by Halo Connect. Large objects placed in front of Halo Connect sensors will also reduce performance. |
| Account Limited to 4 Halo Connect Plugs | A single account is currently limited to four Halo Connect plugs. |
| Samsung Extreme Battery Saver Causes Unreliable Presence | Samsung users who enable extreme battery-saver mode may experience unreliable presence unless the app is allowed to run in the background. |
| “Offline” Notifications Do Not Always Mean Disconnected | An “offline” notification for a sensor does not always mean the sensor has disconnected from Wi-Fi. It means the sensor’s connection to the cloud service is briefly timed out, which can happen under degraded network conditions. The sensor remains connected to the home network throughout and reconnects to the cloud shortly after, at which point the notification clears. |