App version 5.30.0 · October 2026
This release focuses on memory stability and performance improvements, along with interface cleanup. It also adds two-way factory reset sync for presence sensors.
The eSphere mobile app requires iOS 15.2 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 |
|---|---|
| Home Screen Timeline Removed | The Timeline bar has been removed from the Home screen. It caused the app’s memory use to grow over long sessions, particularly with frequent date changes. |
| Activity Bell Red Dot Removed | The red dot indicator on the Activity bell icon has been removed. Alert cards do not track read or unread status, so the indicator could not be cleared. |
| Two-Way Factory Reset Sync | A sensor can now be factory reset from the eSphere mobile app or eDM, and a reset from the sensor’s button now also removes it from the account. Both require the sensor to be online and running firmware 0.38.0 or later. |
| Android API Level 36 Migration | The app now targets Android API level 36, ahead of Google’s deprecation of earlier API levels for Play Store updates (effective October 31, 2026). This has no user-facing impact. |
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 Memory Growth After Connection Timeouts | Resolved an issue where the app’s memory use grew over time after network connection timeouts, particularly while the app was in the foreground. |
| Home Screen Resource Use While Idle | Resolved an issue where the Home screen kept using CPU and memory while idle. |
| Status Bar Contrast on Dark Screens | Resolved an issue where the native status bar always displayed in black, making it hard to read on screens with dark backgrounds. It now switches between black and white to match the current screen. |
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 |
|---|---|
| Sensor Scanning Impact on Mesh Wi-Fi Performance | On mesh Wi-Fi systems with many assigned IP addresses, such as Eero, sensor Wi-Fi scanning can add enough traffic to affect network performance, especially when mesh satellites connect wirelessly rather than by Ethernet. Under active investigation. |
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 |
|---|---|
| Primary User Account Deletion Order | A primary user cannot delete the shared account until every resident has deleted their own account first. |
| eSphere Presence Sensor Requires 2.4 GHz | Similar to many IoT products, the eSphere presence sensor 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 presence sensors are designed for single-SSID networks. With separate 2.4, 5 and 6 GHz SSIDs, the sensor joins the 2.4 GHz network and still detects presence devices on 5 and 6 GHz. Network-isolation features (guest networks, VLANs, client isolation or separate subnets) may reduce accuracy or prevent detection. See Split-Band Network Setups. |
| 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. |
| App Force-Quit Affects Presence | If a user force-quits the eSphere mobile app, or the operating system or an app update forces it to close, presence reliability may be affected for that device. |
| Disabled Radios Cause False Exits | If a user disables Wi-Fi or Bluetooth on their mobile device, turns it off, or its battery runs out, this can cause a “false exit” that makes it appear their profile has left the home. |
| Declined App Permissions | If a user declines any of the prompted mobile app permissions, sensor setup may fail or presence detection accuracy may be reduced. |
| Building Materials Reduce RF Range | Dwellings built with metal, thick concrete or brick will likely reduce the RF range of the eSphere presence sensor. Large objects placed in front of a sensor also reduce performance. See the eSphere deployment guide for sensor placement and quantity recommendations. |
| Four-Sensor Limit per Account | A single account is currently limited to four eSphere presence sensors. |
| 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. |
| ‘Offline’ Notification Does Not Always Mean Disconnected | An ‘offline’ notification means the sensor’s cloud connection briefly timed out, not that it left the home network. The sensor stays connected locally and the notification clears once it reconnects to the cloud. |