Swapped out two cameras, now getting several NO SIGNAL error messages

propman07

Young grasshopper
Jul 5, 2014
40
20
Long Beach, CA
Hi-

I'm running into some issues with my BI setup after swapping out a few of my older cameras. I keep getting no signal errors on several cameras. The system was working fine before, so I'm assuming that the addition of the higher bitrate cameras is the issue. I'm looking for ways to resolve it. I've run this through AI and received a few suggestions, but wanted to run things by the experts here to see if I'm on the right track.

Here is my current setup.

Dell Optiplex 5070 SFF i5 9th Gen 16GB RAM, 250 GB SSD, 4TB 7200 RPM (for saved videos) running Blue Iris Ver 5.9.9.67
Some POE cams connected via Linksys SRW224P 24 Port POE 10/100 Switch
Some POE cams connected via TP-Link TL-SG1005P 5 Port POE Switch

Running the following POE cameras with the corresponding MPixel / Bitrate settings as noted below.
9 Reolink CX810s, 1 Hikvision Hikvision NC-KBU32201, and 2 Hikvision DS-2CD2132
Reolinks running at 15fps, Hikvisions running at 10fps

Before swapping out the two Hikvision DS-2CD2132s for two Reolink CX810s, the total traffic was 86.8 MB/s and the setup was stable. Afer the swap, the traffic is now at 92.3 MB/s with several of the cameras showing no signal.

Thanks for any troubleshooting tips you can provide.

1754322150340.png
 
Did you just swap them out or did you delete the cameras in BI and re-add?

In BI hit the find/inspect button and post what shows up in the pop-up window.
 
Did you just swap them out or did you delete the cameras in BI and re-add?

In BI hit the find/inspect button and post what shows up in the pop-up window.
wittaj-

Cameras were deleted in BI, then re-added using an existing Reolink camera (known working config) setup that was copied for the two replacement cams. The setup worked for a few minutes, but then the no signal error messages started to appear.

Thanks.
 
Last edited:
Checked the PC running BI and found out that it had "updated" to Win11. Downloading the latest updates. Will inspect the cameras later today and post back. Thanks.
 
Hi-

I'm running into some issues with my BI setup after swapping out a few of my older cameras. I keep getting no signal errors on several cameras. The system was working fine before, so I'm assuming that the addition of the higher bitrate cameras is the issue. I'm looking for ways to resolve it. I've run this through AI and received a few suggestions, but wanted to run things by the experts here to see if I'm on the right track.

Here is my current setup.

Dell Optiplex 5070 SFF i5 9th Gen 16GB RAM, 250 GB SSD, 4TB 7200 RPM (for saved videos) running Blue Iris Ver 5.9.9.67
Some POE cams connected via Linksys SRW224P 24 Port POE 10/100 Switch
Some POE cams connected via TP-Link TL-SG1005P 5 Port POE Switch

Running the following POE cameras with the corresponding MPixel / Bitrate settings as noted below.
9 Reolink CX810s, 1 Hikvision Hikvision NC-KBU32201, and 2 Hikvision DS-2CD2132
Reolinks running at 15fps, Hikvisions running at 10fps

Before swapping out the two Hikvision DS-2CD2132s for two Reolink CX810s, the total traffic was 86.8 MB/s and the setup was stable. Afer the swap, the traffic is now at 92.3 MB/s with several of the cameras showing no signal.

Thanks for any troubleshooting tips you can provide.

View attachment 225903
Any update?
 
How was the "swap" done?

Did you assign a unique, static IP address to each "new" camera, all in the same subnet as the BI server's LAN, then plug in and configure BI with the cam's username, password and that assigned IP address then click on "Find/Inspect"....and got each cam working, one at a time, before moving to the next camera?

if not, what procedure DID you follow?
TonyR-

I connected the new cam with a new/unique static IP. Configured by copying a known working camera profile. Performed find/inspect as described. Verified new cam working and configured overlays within camera settings. Disconnected old cam and mounted new cam in its place. Revised static IP to the IP address of the cam being replaced. Performed find/inspect to verify camera functionality. Cameras will initially work, but eventually the new cam (or others in the system) will start to drop off with the no signal error message.
 
TonyR-

I connected the new cam with a new/unique static IP. Configured by copying a known working camera profile. Performed find/inspect as described. Verified new cam working and configured overlays within camera settings. Disconnected old cam and mounted new cam in its place. Revised static IP to the IP address of the cam being replaced. Performed find/inspect to verify camera functionality. Cameras will initially work, but eventually the new cam (or others in the system) will start to drop off with the no signal error message.
Here's a shot in the dark. Insure this feature is disabled, I don't know where it is located because my BI is v5.4.7.11 from 6/11/21 (shame on me; new server planned soon). Maybe someone else will point it out and you can check it, as this feature has produced similar results for other users if left enabled and a cam's IP was changed, even by the user, IIRC.

5.6.2 - September 23, 2022

The Camera Discovery window now finds MAC addresses along with IP addresses. You also have the option of using the previous ONVIF discovery, or the new full LAN IP and port
scan. With this, it should no longer be necessary to use the external website service Advanced Port Scanner to search your network.
LAN cameras now automatically pull MAC addresses and they are displayed on the Status/ Cameras page.

If a camera’s MAC was previously determined and the camera experiences connectivity issues, the software with automatically scan the LAN in order to detect an IP address change. If a new address is found, it will be adopted and posted to Status/Log. This provides protection against IP address changes when DHCP is left active on a camera.
 
  • Like
Reactions: looney2ns
Quick update. I haven't had a chance to look into TonyR's suggestion. That's on my list of things to do later today. I have a scheduled task to reboot the PC that runs BI every so often at midnight. The system rebooted earlier today, and all 13 cams were up and running as of 0300 when I was getting ready for work. I checked them a few minutes ago (around 0700 local) and one of them has dropped off and is now reporting the NO SIGNAL error. Note that this cam is NOT one of the ones that was recently added to the system.

Thanks.
 
Results from Inspect command on a couple of cameras that are working in BI:

Opening 192.168.1.33 port 80...
HTTP Get / request...
Timeout
Opening 192.168.1.33 port 8000...
ONVIF GetSystemDateAndTime
HTTP 12002
Checking for common cameras...
Foscam FI86xx/98xx compatible?
Foscam FI89xx compatible?
Foscam FI9821 V2 compatible?
Foscam FI9821 media port compatible?
Cantonk port 34567?
RTSP port open?
No automatic configuration made
Done

Opening 192.168.1.28 port 80...
HTTP Get / request...
Timeout
Opening 192.168.1.28 port 8000...
ONVIF GetSystemDateAndTime
HTTP 12002
Checking for common cameras...
Foscam FI86xx/98xx compatible?
Foscam FI89xx compatible?
Foscam FI9821 V2 compatible?
Foscam FI9821 media port compatible?
Cantonk port 34567?
RTSP port open?
No automatic configuration made
Done

Still looking for the command to disable that TonyR recommended.
 
Here's an update....

I disabled Tailscale that I have running on the PC that is running BI....did another inspect on one of the cameras...results below....

Opening 192.168.1.62 port 80...
HTTP Get / request...
OK
ONVIF GetSystemDateAndTime
2025-08-08T01:00:47.000Z
Requesting device information...
Manufacturer: REOLINK
Model: CX810
FirmwareVersion: v3.1.0.3430_2404191198
GetCapabilities...
Querying services
Has Imaging services: /onvif/imaging_service
Has media services: /onvif/media_service
Has RTP_RTSP_TCP, requesting profiles
profile token 000
profile name Profile000_MainStream
profile source is 000
profile token 001
profile name Profile001_SubStream
profile source is 000
requesting URI for profile 000
RTSP URI: rtsp:/192.168.1.62:554/
requesting URI for profile 001
RTSP URI: rtsp:/192.168.1.62:554/h264Preview_01_sub
Has Event services: /onvif/event_service
Has WSPullPointSupport
RelayOutputs: 0
Has Device IO services: /onvif/deviceIO_service
AudioOutputs: 0
Done

So it looks like it has something to do with Tailscale.....now to try to figure out what....
 
That looks more like it!
Yes...now....all cameras are working as they were before. Not sure what Tailscale was doing....I was trying to get it to work so that I could use the mobile app to view the cameras when away from my home network. I'll bet is has something to do with the fact that the cameras aren't part of the Tailscale network, and that is giving BI issues.

I'll probably run it now without Tailscale enabled until I have time to do more research....hopefully this helps someone else with troubleshooting.

Thanks for the replies to all.
 
Quick update. I haven't had a chance to look into TonyR's suggestion.
Looks like I sent you on a wild goose chase, because in the most recent (online) "Help" file I don't see that radio button to select or de-select as shown in previous software versions.....the software must have been changed and it's no longer available. Sorry about that. :facepalm: :idk:
 
Looks like I sent you on a wild goose chase, because in the most recent (online) "Help" file I don't see that radio button to select or de-select as shown in previous software versions.....the software must have been changed and it's no longer available. Sorry about that. :facepalm: :idk:
TonyR- No worries....I looked through the help file, and could not find a place to make that change....but thanks for the suggestion.
 
  • Like
Reactions: TonyR
TonyR- No worries....I looked through the help file, and could not find a place to make that change....but thanks for the suggestion.
It was a feature in that version 5.6.2 and some later ones, as evidenced by the section of the help file I posted in #9 above but I guess was changed later, which I was unaware of. Next time I'll comb the current help file and if I don't see something that was a feature in past versions I'll assume it has been eliminated or revised. :cool: