App version 5.28.0 · August 2026
This release completes onboarding accessibility support, resolves the account-deletion issue reported in v5.27.0, and includes a number of interface and copy refinements.
The eSphere mobile app requires iOS 15.1 or later, or Android 7.0 or later.
New Features and Enhancements
Capabilities added or improved in this release. Fixes to existing behavior are listed under Resolved Issues.
| Name | Description |
|---|---|
| Dynamic Text Scaling in Onboarding | Onboarding screens — account creation, sensor setup, and profile creation — now support text scaling up to 200%, so the full onboarding flow can be completed at large accessibility text sizes. |
Resolved Issues
Defects reported or identified in a previous release that are fixed in this one. Defects that remain open are listed under Known Issues.
| Name | Description |
|---|---|
| App Not Redirected to Login After Account Deletion | Resolved an issue where the app could become unresponsive on launch after the account was deleted. The app now signs the user out and returns to the login screen. |
| Excessive Sensor Offline Notifications | Resolved an issue where a sensor offline notification was generated too quickly after a brief connectivity interruption. This is a backend change and requires no app update. |
Known Issues
Identified or reported defects that have not yet been resolved. Behaviors that are expected characteristics of the platform are listed under Platform Characteristics.
| Name | Description |
|---|---|
| Alert Feedback Not Shown After Selection | After selecting thumbs-up or thumbs-down on the “Was this correct?” alert feedback prompt, the confirmation message does not display, and the prompt does not reappear if the alert is reopened. |
| Formatting Issues at Large Text Scaling | Formatting issues occur outside the onboarding flow when the mobile device text size is dynamically scaled to Large. |
| Missing Error Message Off Home Wi-Fi | On a cellular connection, a loading icon displays in place of the QR code instead of the expected error message. The message displays correctly on non-home Wi-Fi networks. |
| Notifications Stopped Displaying | Push notifications have been reported as not received even when notifications are set to active. |
| Inaccurate Alert Notifications | On occasion, location status reported in notifications (for example, left home / arrived home) has been reported as inaccurate. |
| Sensor Wi-Fi Scanning Degrades Mesh Network Performance | On mesh Wi-Fi systems with many assigned IP addresses (such as Eero), sensor Wi-Fi scanning can generate enough additional traffic to degrade Wi-Fi performance, most notably when mesh nodes connect to each other via wireless backhaul rather than hardwired Ethernet backhaul. |
| Sensors Reported Offline During Brief Cloud Timeouts | A sensor may report as offline if its connection to the cloud briefly times out under degraded network conditions, even though the sensor remains connected to the home network. The notification clears once the sensor reconnects. |
Platform Characteristics
Characteristics of eSphere as currently designed. These are not defects and are not scheduled for correction. Defects awaiting a fix are listed under Known Issues.
| Name | Description |
|---|---|
| Halo Connect Requires 2.4 GHz | Similar to many IoT products, eSphere’s Halo Connect sensor/plug works only on a 2.4 GHz network. Nearly all homes have a 2.4 GHz band, but it is required. |
| Single-SSID Network Design | eSphere’s Halo presence sensors are designed for single-SSID networks. Split 2.4 GHz and 5 GHz SSIDs typically work correctly, though additional network setup customizations such as network-isolation features (guest networks, VLANs, client isolation, or separate subnets) may reduce accuracy or prevent presence detection. |
| MAC Address Rotation | 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. This is an industry-standard limitation, and the eSphere team is evaluating technologies to improve detection of these devices. |
| App Closure Affects Presence | 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 for that device. |
| Disabled Radios Cause False Exits | If you disable Wi-Fi or Bluetooth on your mobile device, turn the device off, or the device runs out of battery, this can cause a “false exit” that makes it appear your profile has left the home. |
| Declined App Permissions | If you decline any of the prompted mobile app permissions, this may impact presence detection accuracy. |
| Building Materials Reduce RF 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. See our deployment guide for sensor placement and quantity recommendations. |
| Four-Plug Limit per Account | A single account is currently limited to four Halo Connect plugs. |
| Resident Accounts Must Be Deleted 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. |
| Samsung Extreme Battery Saver | Samsung users who enable extreme battery-saver mode may experience unreliable presence unless the app is allowed to run in the background. |