This article covers troubleshooting for the Latch Camera from the property-manager and installer perspective. It assumes the camera is physically installed, powered, and paired to an Intercom Door.
Status LED reference
The status LED is on the side of the mounting base (not on the dome). Use it as the first diagnostic when something is wrong. This table is sourced directly from the Mini Dome IP Camera Installation Guide:
| Color | Behavior | Meaning |
|---|---|---|
| Green | On (solid) | Powered on |
| Green | Off | No power — camera is not receiving PoE |
| Green | Slow blinking | System is booting up |
| Green | Fast blinking | System is downloading (firmware or configuration) |
| Amber | On (solid) | Firmware upgrade failure, or the built-in heater is on (ambient < 42°F / 6°C) |
| Amber | Slow blinking | Device firmware is updating |
| Amber | Fast blinking | System has reset to default |
| Blue | On (solid) | Powered on |
| Blue | Slow blinking | Data is transmitting / receiving via the network |
DOOR does not publish other LED patterns for the Latch Camera. If a pattern outside this table is observed, capture a short video and escalate to support@door.com.
Camera is completely unresponsive (status LED off)
The camera has no battery — a dark LED means no power.
Quick fix
- Confirm PoE delivery at the switch port:
- If using a PoE switch: check that the switch port for the camera is configured to deliver PoE and that the switch's PoE budget is not exhausted.
- If using a non-PoE switch with a PoE injector: confirm the injector is powered, the data side is connected to the switch, and the PoE side is connected to the camera.
- Confirm cable integrity: Ethernet cable terminated correctly, no kinks, no breaks. Swap with a known-good cable if available.
- Confirm UL-listed PoE supply: the camera requires UL-listed I.T.E. PoE rated 48 Vdc, 0.25 A minimum. A non-compliant injector may fail to power the camera.
When to escalate
Contact support@door.com if power is confirmed at the camera end (multimeter or injector LED indicates PoE active) but the status LED still does not light up — the camera's internal electronics may have failed.
Camera shows no feed in the DOOR app (LED is on, network looks OK)
The most common cause is a firewall blocking outbound traffic from the camera to DOOR cloud.
Quick fix — firewall configuration
If the camera is behind a firewall, confirm:
| Setting | Required state |
|---|---|
| TCP outbound to ports 443, 3478, 5349, 8883 | Open |
| UDP ports 1025–65535 (inbound and outbound) | Open |
Domain *.latchaccess.com | Allowed |
Domain *.latch.com | Allowed |
Domain *.amazonaws.com | Allowed |
| NAT mode | Full cone NAT recommended; at minimum, some NAT is required |
| Enable Fragmented Packet Handling | Checked |
| Ignore DF Bit | Unchecked |
| Enable NAT Traversal | Checked |
If the video feed is still not loading after the above, all ports to the camera may need to be opened as a diagnostic measure.
SonicWall firewalls
If the property uses a SonicWall firewall and video feeds are loading less than 90% of the time (or not at all), contact DOOR Support — there are known SonicWall-specific configurations to apply.
SIP transformations (when using a PBX receiver)
If the PBX that the SIP server communicates with is located behind the firewall, SIP transformations should be disabled in most deployments. Consult with the VoIP vendor before changing this setting.
When to escalate
Contact support@door.com if all firewall ports and domains are confirmed open, the camera has a valid DHCP lease, and the feed still does not appear.
Pixelated, frozen, or laggy feed
The feed is reaching the DOOR app but quality is degraded.
Quick fix
- Check network speed: the camera requires a minimum of 10 Mbps as tested by a network testing device. Anything less can produce pixelation, especially during call hours when multiple devices share the link.
- Check switch utilization: a saturated switch port can drop video frames. Verify the camera is on a switch port that isn't sharing bandwidth with high-traffic devices.
- Confirm PoE is stable: an undersized PoE budget can cause power dips that reset or stall the camera. The status LED briefly going off or returning to green slow-blink (booting) is a hint.
- Take a property-manager test image: from a PM DOOR app account, open Devices → select the door → Camera → take a test image. This is the only on-demand way to view the camera outside an active call. If the test image quality is fine but call-time video is degraded, the bottleneck is during the call (resident's phone connection or call-path bandwidth). If the test image itself is degraded, the issue is at the camera or the property network.
When to escalate
Contact support@door.com if network speed and PoE are confirmed adequate but the feed is consistently degraded across multiple residents and call sessions.
Camera cannot pair to the Intercom Door
The DOOR app's Pair Camera flow fails (rejected MAC, paired-to-another-door error, no response).
Quick fix
- Confirm the MAC address matches the label on the camera (and on the back of the camera). Re-enter without typos.
- Confirm you are entering the MAC address and not the serial number. The two are different values printed on the label — the Pair Camera flow requires the MAC address. Entering the serial number is rejected.
- Confirm you are pairing the camera to the Door, not activating it. The Latch Camera joins through the Pair Camera flow on the Intercom Door — it is not added through the standard "activate a device" flow used for locks. If you are in the device-activation flow, exit and use Pair Camera on the Building Entrance door instead.
- Confirm the door has door type Building Entrance in DOOR OS — Camera pairing requires Building Entrance.
- Confirm the Latch Intercom is selected in the door's Intercom dropdown in DOOR OS — without an Intercom, the Camera has nothing to pair with.
- Confirm the door's lock device is activated. The camera cannot be paired to a door that has no activated lock device. Activate the Latch R first, then retry the camera pairing.
- Confirm the camera is online: status LED solid blue (booted and connected). Pairing will most likely fail until the LED is solid blue. If the LED is off, see "Camera is completely unresponsive" above.
- Confirm the camera is not already paired to another door. A camera can be paired to only one door at a time. If the camera was previously installed elsewhere, factory-reset it (hold the reset button for over 15 seconds) and retry pairing.
Factory reset the camera
Used when the camera is unresponsive to pairing, joined a wrong network, or returned from a previous install.
- Locate the reset button on the side of the mounting base (adjacent to the status LED).
- Press and hold the reset button for more than 15 seconds.
- The camera reboots and the status LED transitions through boot patterns (green slow blink → green solid → green slow blink again when ready).
- After reset, the camera obtains a new DHCP lease and is ready to pair fresh.
A factory reset clears all settings — re-pair the camera in the DOOR app after the reset completes.
When to escalate
Contact support@door.com if:
- The status LED is off and PoE delivery is verified at the camera end.
- The status LED is amber-solid and no firmware update is in progress (firmware upgrade failure that doesn't clear with a power cycle).
- The DOOR app shows no feed and all firewall ports, domains, NAT, and DHCP are confirmed correct.
- A SonicWall firewall is in use and the troubleshooting above does not restore reliable feed.
Include with every escalation: the property name in DOOR OS, the door name, the Camera MAC address, the firmware version (visible in the DOOR app under the Intercom Door's Settings — TODO confirm exact UI path), the network topology (PoE switch model + firewall model), and a description of the issue with steps already taken.
Related articles
- Latch Camera overview
- Installing Latch Camera
- Viewing your Latch Camera feed
- Latch Camera specifications
- Cleaning the Latch Camera