Honeywell

Honeywell Geofencing Not Working? Enterprise Fix Guide

Honeywell geofencing fails? Resolve location-based automation issues. Check Resideo App settings, verify firmware channels, and use network diagnostics for quick fixes.

Is this your issue?

Camera shows offline in the VMS dashboard but responds to ping
RTSP stream drops intermittently despite stable network link
PoE negotiation fails — switch port shows Class 0 instead of expected Class 3
Firmware update stuck in pending state in the management platform
Geofencing events fail to trigger despite correct Resideo App settings
Multiple users report inconsistent geofence behavior across devices
VMS logs show geofencing events as 'unprocessed' or 'dropped'

Sound familiar? The guide below will help you fix it.

Verify Your Honeywell Camera’s Network Configuration

If your Honeywell geofencing system is failing, the first step is to validate the camera’s network settings. Ensure the camera is connected to the correct VLAN in the Resideo App → Camera → Network. Confirm the VLAN ID matches the switch port configuration. Use the IP Utility tool to verify the camera’s IP address and subnet. For 60 Series IP Cameras, check the PoE budget allocation on the switch. If the port shows Class 0, the camera may be receiving insufficient power, causing intermittent connectivity. Disable multicast in the VMS if the switch lacks IGMP snooping support to prevent event drops. Ensure the RTSP port in the VMS matches the Resideo App’s Network → RTSP Port setting.

Check VLAN Assignment

Access the Resideo App → Camera → Network menu and confirm the VLAN ID matches the switch port configuration. If the VLAN is misconfigured, the camera may be isolated from the management platform, preventing geofencing events from triggering. Use the IP Utility tool to verify the camera’s IP address and subnet. Ensure the camera’s IP is within the same subnet as the VMS and that the default gateway is correctly configured.

Validate PoE Budget

For 60 Series IP Cameras, check the PoE budget allocation on the switch. Access the switch’s management interface and confirm the port is configured for Class 3 power delivery. If the port shows Class 0, the camera may be receiving insufficient power, causing intermittent connectivity. Adjust the PoE budget on the switch to ensure the camera receives adequate power. Avoid overloading the switch with too many high-power devices, as this can cause power starvation.

Diagnose VMS Integration Issues

VMS integration issues often stem from incorrect stream profiles or licensing. In your VMS (e.g. Avigilon Control Center), verify the camera’s RTSP stream URL matches the Resideo App configuration. Ensure ONVIF profile S is enabled for geofencing events. If the VMS uses a custom RTSP port, check the Resideo App’s Network → RTSP Port setting. Confirm the VMS is licensed for geofencing features and that the camera is registered in the VMS. Use the Resideo App → Camera → Edge Analytics tool to verify geofence event logs and ensure the VMS is receiving event data.

Check VMS Licensing

Access your VMS (e.g. Avigilon Control Center) and confirm that the camera is licensed for geofencing features. If the VMS lacks the necessary license, geofencing events may fail to trigger. Ensure the VMS is running the latest firmware and that the camera’s firmware is up to date. Use the Resideo App → Camera → Firmware menu to check for available updates and ensure the camera is on the stable firmware channel.

Verify ONVIF Profile S

In your VMS, ensure that ONVIF profile S is enabled for geofencing events. Access the VMS’s camera settings and confirm that the ONVIF profile S is selected. If the profile is not enabled, the VMS may not receive geofencing events from the camera. Use the Resideo App → Camera → Edge Analytics tool to verify geofence event logs and ensure the VMS is receiving event data.

Troubleshoot Firmware and Geofence Settings

Firmware incompatibility can disrupt geofencing. In the Resideo App → Camera → Firmware, ensure the camera is on the stable firmware channel. For 30 Series IP Cameras, use the Device Diagnostics tool to check for firmware update errors. If a staged rollout is in progress, geofencing may fail until the update completes. Force a rollback via Resideo App → Camera → Advanced Settings → Firmware Rollback if necessary. Verify ONVIF profile S is enabled in the VMS for geofencing events to ensure compatibility.

Adjust Geofence Radius Settings

In the Resideo App → Camera → Geofencing, ensure the radius is set to 150-200 meters for optimal coverage. Avoid overlapping geofences to prevent conflicts. For multi-user environments, use the Resideo App → Account → Device Management to sync settings across all devices. Verify the geofence center point aligns with the camera’s GPS coordinates in the VMS. If using cloud-managed systems, ensure the geofence data is synchronized with the central management platform.

Sync Geofence Settings Across Devices

If multiple users are involved, confirm geofence radius settings are synchronized across all devices via the Resideo App → Account → Device Management. Ensure that all devices are using the same geofence center point and radius. Use the Resideo App → Camera → Edge Analytics tool to verify geofence event logs and ensure consistency across devices. If discrepancies are found, update the settings on all devices to match the central configuration.

Advanced Diagnostics and Support Escalation

If basic troubleshooting steps fail, perform advanced diagnostics. Use the Resideo App → Camera → Device Diagnostics tool to check for firmware update errors or network issues. If the camera is still unresponsive, consider factory resetting the device. For 30 Series IP Cameras, press and hold the reset button for 12 seconds while the camera is powered on. For 60 Series IP Cameras, disconnect power and press and hold the Reset button with a paperclip while reconnecting power. After resetting, reconfigure the camera’s network settings and firmware channel.

Escalate to Enterprise Support

If geofencing issues persist, escalate to Honeywell’s enterprise support team. Visit the official support website for Honeywell at https://www.honeywellhome.com/pages/support-security to submit a support ticket. Provide detailed logs from the Resideo App → Camera → Device Diagnostics tool, VMS event logs, and firmware version information. Include the camera’s MAC address, IP address, and VLAN ID for faster resolution. For UK-based users, mention any Building Regulations Part Q considerations or GDPR retention policy conflicts that may impact geofencing functionality.

Root Causes and Prevention

Enterprise-relevant root causes for Honeywell geofencing failures include PoE power budget exhaustion, DHCP scope exhaustion, VMS licensing issues, and firmware incompatibility. Ensure switches are configured for Class 3 PoE delivery and that the DHCP scope in the camera VLAN is not exhausted. Verify that the VMS is licensed for geofencing features and that the camera’s firmware is up to date. Use the Resideo App → Camera → Edge Analytics tool to monitor geofence event logs and identify recurring issues.

Long-Term Maintenance

To prevent future geofencing issues, schedule regular firmware updates and monitor VMS health via the Resideo App → Camera → Edge Analytics tool. Ensure switches are configured with QoS policies for geofencing traffic and that SNMP monitoring is enabled for network health. Use dedicated camera VLANs to isolate geofencing traffic from other network services. Full disclosure: we built scOS to address exactly this — the complexity of managing enterprise camera fleets across VLANs — using permanently powered cameras connected via Ethernet.

Replacement and Lifecycle Management

If troubleshooting exceeds 30 minutes and basic steps (restart/reset/reconnect) have failed, consider hardware replacement. Honeywell cameras typically have a 5-8 year lifespan for wired models and 3-5 years for battery-powered models. Surveillance-rated HDDs in NVR systems last 3-5 years, while microSD cards degrade after 1-2 years of continuous use. Under the Consumer Rights Act 2015, UK consumers have up to 6 years to claim faulty goods. Replace cameras with 60 Series IP Cameras for better PoE support and 30 Series IP Cameras for advanced firmware features. Use high-endurance microSD cards (e.g. Samsung PRO Endurance) for reliable storage.

What if this wasn't your problem to solve?

scOS detects suspicious activity — not motion. It only alerts you when something matters, like a person would. Designed to be left alone. All features included.

Detects Suspicious Activity

Not motion — actual suspicious behaviour. Like a person would notice.

Designed to Be Left Alone

No settings to tweak. No app to check. It just works.

All Features Included

No subscriptions. No tiers. Everything works from day one.

See why this keeps happening

Works with any wired camera brand. See all features

Frequently Asked Questions

VLAN misconfigurations disrupt geofencing by isolating cameras from management platforms. In the **Resideo App → Camera → Network**, confirm VLAN ID matches switch port settings. Use the **IP Utility tool** to verify the camera’s IP address and subnet. For 60 Series IP Cameras, check PoE budget allocation on the switch. If the port shows **Class 0**, the camera may be receiving insufficient power, causing intermittent connectivity. Disable **multicast** in the VMS if the switch lacks IGMP snooping support to prevent event drops.

Firmware incompatibility can break geofencing. In the **Resideo App → Camera → Firmware**, ensure the camera is on the **stable** firmware channel. For 30 Series IP Cameras, use the **Device Diagnostics** tool to check for update errors. If a staged rollout is in progress, geofencing may fail until the update completes. Force a rollback via **Resideo App → Camera → Advanced Settings → Firmware Rollback** if necessary. Verify **ONVIF profile S** is enabled in the VMS for geofencing events to ensure compatibility.

VMS integration issues often stem from incorrect stream profiles. In your VMS (e.g. **Avigilon Control Center**), verify the camera’s **RTSP stream URL** matches the Resideo App configuration. Ensure **ONVIF profile S** is enabled for geofencing events. If the VMS uses a **custom RTSP port**, check the Resideo App’s **Network → RTSP Port** setting. For 60 Series IP Cameras, disable **multicast** in the VMS if the switch doesn’t support IGMP snooping, as this can cause event drops. Confirm the VMS is licensed for geofencing features.

Battery optimization on mobile devices can block geofencing. In the **Resideo App → Settings → Location**, ensure **Always Allow** is selected for geofencing. For iOS devices, disable **Low Power Mode** and check **Background App Refresh** under **Settings → General → Background App Refresh**. On Android, grant **Location Permissions** via **Settings → Apps → Resideo App → Permissions**. If multiple users are involved, confirm **geofence radius settings** are synchronized across all devices via the **Resideo App → Account → Device Management**. Use the **Resideo App → Camera → Edge Analytics** tool to verify geofence event logs.

Incorrect geofence radius settings can prevent accurate automation triggers. In the **Resideo App → Camera → Geofencing**, ensure the radius is set to **150-200 meters** for optimal coverage. Avoid overlapping geofences to prevent conflicts. For multi-user environments, use the **Resideo App → Account → Device Management** to sync settings across all devices. Verify the **geofence center point** aligns with the camera’s GPS coordinates in the VMS. If using cloud-managed systems, ensure the geofence data is synchronized with the central management platform.

All Troubleshooting Guides