Hi everyone,
A new test version of Net Scan is available.
This release contains significant improvements to device detection, reachability presentation, Insights, Advanced Flows, pairing and application stability.
Install the test version here:
As this is initially a test release, feedback about device detection, migration and Probe Time measurements is appreciated.
Clear network reachability status
Devices now have a dedicated Network reachability status:
- Reachable
- Not reachable
This uses a network-specific icon instead of presenting the device as a normal on/off switch.
The reachability status is also available as the device quick action. Although Homey may present it similarly to a toggle, it is a read-only status controlled by Net Scan. Pressing it cannot make a network device online or offline; Net Scan restores the detected state.
Backwards compatibility
The legacy onoff and alarm_offline capabilities are retained internally so existing Flows remain compatible.
The legacy on/off status is hidden from the normal device interface where possible and is synchronized with the new reachability status.
You should not need to delete or re-pair existing devices.
For new Flows, use the new reachability status and duration condition instead of the legacy on/off condition.
ARP device detection
IP devices now support three detection methods:
- Automatic – ARP, then TCP
- ARP only
- TCP response – legacy method
Automatic detection first checks for the device using ARP. If ARP cannot confirm the device, Net Scan falls back to its existing TCP response check.
New IP devices use Automatic detection by default.
Existing IP devices remain configured for the legacy TCP response method after upgrading. This prevents their detection behaviour from changing unexpectedly. Automatic or ARP detection can be enabled manually from the device’s Advanced Settings.
ARP is intended for numeric IPv4 addresses on the same local network as Homey. It may not work across routers, VLANs or other separated networks. Hostnames and non-local targets use the TCP fallback.
ARP confirms that a device is present on the network. It does not confirm that a particular service on that device is operational.
- ARP: Better for detecting local devices without a usable TCP service, but can briefly produce stale online results.
- TCP response: Better when rapid crash detection matters.
- TCP port: Best when the monitored service itself must be operational.
Probe Time Insights
Net Scan now records the duration of successful device probes in milliseconds.
The new Probe time capability:
- Is available in Homey Insights
- Supports both ARP and TCP detection
- Uses a dedicated stopwatch icon
- Updates at most once per minute to avoid unnecessary Insights entries
- Updates immediately when a device recovers
- Is cleared when the device is confirmed offline
Probe time is not an ICMP ping measurement. It represents how long the currently selected ARP or TCP detection method took to receive a valid response.
Improved pairing
The IP and TCP pairing dialogs have been redesigned with clearer fields, validation, feedback and connection testing.
Before adding a device, press Test connection.
For an IP device, the test uses the same ARP-first and TCP-fallback process as Automatic detection.
For a TCP device, Net Scan attempts to connect to the specified TCP port.
The result is informational:
- A successful test is displayed in green.
- A timeout, unreachable device, unresolved hostname or closed TCP port is displayed as a warning.
- Devices can still be added after a warning. This allows devices that are currently offline or whose service is stopped to be configured in advance.
- Invalid IP addresses, malformed hostnames and invalid TCP ports are rejected.
- Changing the host or TCP port requires running the test again.
The device name is optional. If it is left empty, Net Scan creates a name from the host or host and TCP port.
Online/offline duration Flow condition
A new Advanced Flow condition is available for IP and TCP devices:
Device has been online or offline for at least a specified duration
You can select:
- Online or offline
- Duration
- Seconds or minutes
Net Scan stores the last state transition time, allowing duration tracking to continue across application restarts.
This is a condition, not a delayed trigger. It evaluates the device state when the Flow runs. Use it together with a suitable trigger or periodic Flow.
For upgraded devices without existing duration history, tracking starts when this version first initializes the device.
Logging changes
The Send Log function has been removed, together with its email-related dependencies. Logs can still be viewed, copied and cleared manually from the app settings.
Two logging levels remain:
- Errors Only: Only actual errors are recorded.
- Basic Information: Includes scanning and Probe Time diagnostics.
When reporting a Probe Time problem, select Basic Information before collecting the log.
Stability and maintenance improvements
This version also includes:
- Improved socket and timer cleanup
- Protection against outdated scan results
- Safer handling of settings changes, app restarts and device removal
- Improved capability migration for existing devices
- Better error handling for Flow triggers and device state updates
- Improved host and TCP-port validation
- Updated Homey SDK and supporting dependencies
- Refreshed device, quick-action and App Store artwork
- Updated English, German and Dutch translations
Instructions for existing users
- Install the test version using the link above.
- If Network reachability or Probe time is still missing, restart the app once more. Newly added capabilities may require another initialization.
- Do not delete or re-pair existing devices.
- Existing IP devices continue using the legacy TCP response method.
- To test ARP, open the IP device’s Advanced Settings and select Automatic – ARP, then TCP.
- Check Homey Insights for Network reachability and Probe time.
- Test your existing Flows after upgrading.
Reporting problems
When reporting a problem, please change the reporting to Basic, let it run few cycles and then include as many details as possible in the diagnostic report.
Thank you for testing and providing feedback.
