How to connect an IP camera to a local network?

Connecting an IP camera to a local network can seem daunting, but with the right guidance, it can be a straightforward process. This article will walk you through the necessary steps to connect your IP camera to a local network, ensuring a seamless integration without any IP conflicts or the need for manual configuration.
Avoiding IP Conflicts and Manual Configuration

Step 1: Preparing Your Network

Before starting the connection process, it's crucial to prepare your local network. Ensure your router is functioning correctly and that you have access to its settings. Additionally, make sure that your network is secured with a strong password to prevent unauthorized access.

Step 2: Connecting the IP Camera to Your Network

Automatic IP Configuration (DHCP):

Most modern IP cameras support DHCP (Dynamic Host Configuration Protocol), which allows the camera to automatically obtain an IP address from your router. This method is the easiest way to connect your IP camera to a local network and avoid IP conflicts.

To enable DHCP, follow these steps:
  • Access the camera's settings menu.
  • Locate the network settings.
  • Select "DHCP" or "Automatic IP configuration."
  • Save the changes and restart the camera.

Manual IP Configuration:

If your IP camera does not support DHCP or you prefer to set a static IP address, you can manually configure the IP settings. However, this method requires more attention to avoid IP conflicts. Here's how to do it:
  • Access the camera's settings menu.
  • Locate the network settings.
  • Select "Manual IP configuration."
  • Enter the desired IP address, subnet mask, gateway, and DNS server information.
  • Save the changes and restart the camera.

Step 3: Verifying the Connection

Once the IP camera is connected to your local network, you should verify the connection to ensure everything is functioning correctly. Access the camera's live feed from a computer or mobile device connected to the same network. If you can view the live feed, the connection is successful.

Step 4: Avoiding IP Conflicts and Manual Configuration

To avoid IP conflicts and the need for manual configuration, consider the following tips:

Use DHCP Whenever Possible:
As mentioned earlier, DHCP is the easiest and most straightforward way to connect an IP camera to a local network. It automatically assigns a unique IP address to the camera, preventing any conflicts.

Reserve IP Addresses:
If you prefer to use static IP addresses, you can reserve specific IP addresses for your IP cameras in your router's settings. This will prevent other devices from using the same IP address and causing conflicts.

Use a Unique Subnet for IP Cameras:
Another way to avoid IP conflicts is to use a unique subnet for your IP cameras. This separates the cameras from other devices on your network, reducing the likelihood of IP conflicts.

Connect the camera to a power source: Most IP cameras require a power source, such as a power adapter or PoE (Power over Ethernet) switch. Use an Ethernet cable to connect the camera to a router or switch on the local network. Some IP cameras also support Wi-Fi, in which case you can connect the camera to the local Wi-Fi network. Once the camera is connected to the network, you may need to configure its settings, such as its IP address, subnet mask, gateway, and DNS server. Consult the camera documentation or manufacturer's website for instructions on how to configure the camera. After configuring the camera, you should be able to access it from a computer or mobile device on the same local network by entering the camera's IP address in a web browser or using a dedicated camera viewing software or mobile app. It's important to ensure that the connection to the camera is secure to prevent unauthorized access. This can be done by using encryption, strong passwords, and other security measures. The exact steps involved in connecting an IP camera to a local network may vary depending on the camera model and your network setup. Consult the camera documentation or manufacturer's website for detailed instructions on how to set up the camera on your specific network.

Telegram Event Notifications

Surveillance events can be delivered directly to the messenger. To configure this feature, a Telegram connection panel has been added to the general system settings.

To activate it, enable the “Use Telegram for events” option, enter your phone number, and input the verification code received in Telegram. After the connection is completed, a group named SmartVision.dev is automatically created where notifications will be sent.
To prevent excessive message flow, several sending control options are available:

Send no more than (N) notifications per minute for each camera. The default value is 2.
Do not send event photos. This option is enabled by default to reduce the amount of transmitted data.
Message sending timeout — 60 seconds by default. Once the timeout is reached, sending is temporarily paused.

If the detector registers a large number of triggers, the system follows the configured limit. For example, if the person detector triggers hundreds of times per minute, only the number of notifications allowed by the settings will be sent to Telegram.

Notifications are processed through a queue. Newer events from each camera receive higher priority. All cameras have equal priority, but within a single camera older events have lower priority. If more than two outdated events accumulate in the queue for one camera, they are automatically removed. Events from different cameras remain independent and are processed separately.

Camera Settings

In the Cloud tab of the camera settings, filters for event types have been added. Users can choose which detected objects should trigger notifications. For example, notifications can be sent only when a person or car is detected, while ignoring animals.

Notifications can be generated for different detection types:
person, dog, car, fire, smoke, sound, specific license plate number, specific face from the database.

As a result, SmartVision allows Telegram to be used as an additional channel for receiving surveillance system event notifications, with flexible configuration of event types and message limits.