Doorbird Can't Save Locally? Fix Local Storage Issues

Doorbird Can't Save Locally? Fix Local Storage Issues

One of the powerful features of the Doorbird video doorbell is its ability to save video history and snapshots directly to your own local storage, such as a Network Attached Storage (NAS) device or an FTP server. This gives you full control over your data without mandatory cloud subscription fees. However, setting this up can sometimes be tricky, leading to situations where recordings fail to save.

This troubleshooting guide will help you diagnose and fix the common problems that prevent your Doorbird from saving footage to your local network storage.

Common Symptoms of Local Storage Failure

If you're having issues with local recording, you'll likely encounter one of these problems:

• No History Saved: The history tab in your Doorbird app is empty, even after motion events or doorbell presses.
• Connection Errors: You receive an error message in the Doorbird settings when trying to connect to your NAS or FTP server.
• Login Incorrect: The app reports incorrect credentials, even though you are sure the username and password are correct.
• Incomplete or Corrupt Files: Recordings are saved, but they are zero-byte files, corrupted, or incomplete.
• "Path Not Found" Errors: The system cannot find the network path you have specified.

How to Fix Doorbird Local Storage and Recording Problems

Let's work through the setup and common pitfalls step-by-step.

1. Verify Your NAS/FTP Server Settings

The majority of issues originate from incorrect configuration details. Precision is key.

• Protocol Selection: Doorbird supports saving to an FTP Server or an SMB/CIFS Share (the standard for most NAS devices). Ensure you have selected the correct type in the Doorbird app settings.
• Server IP Address: Double-check that you have entered the correct local IP address for your NAS or server. It's best practice to assign a static IP address to your NAS so it doesn't change.
• Server Path: This is the most common point of error.
  • For an SMB/CIFS Share (NAS): The format must be exact: //SERVER_IP/SHARE_NAME. For example, if your NAS IP is 192.168.1.100 and your shared folder is named Doorbird, the path is //192.168.1.100/Doorbird. Do not add subfolders here.
  • For FTP: Often, you can just use the IP address of the FTP server, and it will save to the user's default home directory.
• Username and Password: The credentials must belong to a user account on your NAS/server.

2. Check User Permissions on Your NAS

This is the second most common problem. The user account you are using for Doorbird needs permission to write files.

1. Log into the administration panel of your NAS (e.g., Synology DSM, QNAP QTS).
2. Go to the User Management or Shared Folders section.
3. Find the user account you entered in the Doorbird app.
4. Edit the user's permissions for the shared folder you are using for recordings.
5. Ensure this user has Read & Write access. Read-only access will cause the connection to fail.

3. Review Doorbird App Configuration

Double-check the settings within the Doorbird app itself.

• Administration Login: To change these settings, you must be logged in as an administrator in the Doorbird app.
• History Settings: Navigate to Settings > Administration > History. This is where you input your server details.
• Recording Schedule: Check the Schedule for Motion Sensor and Schedule for Doorbell settings. If the schedules are empty or disabled, the Doorbird will not record anything, even if the connection to the NAS is successful. Make sure the schedule is active for the desired times (e.g., all blue for 24/7).

4. Test Network and Firewall Rules

A network issue could be preventing the Doorbird from reaching your NAS.

• Same Subnet: Ensure your Doorbird and your NAS/server are on the same local network and subnet (e.g., both have IP addresses starting with 192.168.1.x).
• Firewall: A firewall on your NAS or your router could be blocking the connection.
  • NAS Firewall: Check the security or firewall settings on your NAS. Temporarily disable it to see if the connection works. If it does, you need to create a rule to allow access from the Doorbird's IP address on the correct port (e.g., port 445 for SMB, port 21 for FTP).
  • Router Firewall: This is less likely to be an issue for internal traffic, but check that there are no "client isolation" or internal firewall rules on your router that would prevent devices from communicating with each other.

By carefully verifying these four areas—server details, user permissions, app settings, and network rules—you can resolve almost any issue preventing your Doorbird from saving footage locally.