Three of my cameras each have exactly the same number of "no signal" errors per 24 hours (hundreds), but the other seven have absolutely none?

Editbear

n3wb
May 7, 2016
3
4
London
I have three IP Cams which "no signal" hundreds of times each day, but my other seven never "no signal" at all?
The 3 culprits show exactly the same number of "no signal" alerts (around 209 in 12 hours - see attached photo).

All 10 cameras are on their own VLAN with no gateway and no DHCP.
They all have fixed IP addresses and the VLAN feeds a second NIC card on my B.I. computer.

I have tried the following with no affect;-
Moved one camera to a different Ubiquiti POE switch - no change.
Powered one camera with its 12v psu rather than POE - no difference

A have set up a repeating ping to the camera IP address from a laptop (temporarily placed on the camera VPN) and watched the direct output of the camera on its browser until the feed in B.I. says "no signal"
Neither the ping nor the direct camera feed on the browser was interrupted?

Two of the cameras are identical Chinese Courtyard Lantern cameras but the third is a Chinese dome camera.
All three have identified as Generic/ONVIF - see attached.

I really need some suggestions from you! Something must be common to those three - and only those three, since they all have exactly the same number of faults?
 

Attachments

  • nosignal.png
    nosignal.png
    494.7 KB · Views: 18
  • nosignal2.jpg
    nosignal2.jpg
    147.6 KB · Views: 18
It sounds like you were doing what I would suggest, which was opening up the Blue Iris interface and watch the cameras and the camera watching the video stream and having the Blue Iris status screen open to the cameras and watch for the No signal and confirm are you actually losing signal or is Blue Iris thinking it is.

In many instances you will see that Blue Iris thinks it is losing signal and it isn't. If that is the case, try either turning Watchdog off or try unchecking the interpret monochome as loss of signal should take care of it. Probably just some issue with the camera signal to BI that doesn't impact anything.

You probably are not really having loss of signal, it is just being interpreted as that. I have a few that were doing that and unchecking the box worked on two of them and I just turned watchdog off for the other camera.
 
  • Like
Reactions: alastairstevenson
Please mark this as solved! It seems the problem was two fold;-

1) Even though my cameras appeared totally different (two were lantern and one globe), I noticed they had similar firmware numbers (T38);-

Garden: T38F006-ONVIF-P2P V2.5.1.8 build 2015-01-12 10:42:48
Porch: T38L-ONVIF-P2P V2.5.1.9 build 2015-02-12 15:20:36
Front Park: T38L-ONVIF-P2P V2.5.0.6 build 2014-01-26 12:19:11

My thanks to this blog New Firmware Version 2.5.1.8 for DM365/DM368 DSP IP Camera - Intermittent Technology
which suggested updating the firmware OR reducing the framerate to 15fps and less than 5Mb/s stream rate.
I did the latter - and problem improved immediately.

2) My brand new Ubiquiti POE switches!;-
I previously powered my 10 cams from a single 250W "old style" Ubiquiti 24 port (12 + 12 POE) switch.
In the interests of being green, I bought two new style 40W (Version 2) Ubiquiti 16 port (8 + 8 POE) switches.
It turns out my cams were taking 39 Watts from one switch and although this should be within rating, it clearly wasn't!
I moved a few cams from one switch to the other to equalise the load to around 30W on each - and problem solved!
Beware! these new Ubiquiti switches may be green, but they can't take as many cams as the old style they replaced - and don't seem to warn you they are failing!

With both fixes above done - I have been running now for a week with no more signal losses - problem SOLVED!
I hope this helps someone!
 
Nothing but issues with Ubiquiti switches in my experience, they have great marketing, but the hardware is trash

2 years ago we ripped out 20 EdgeSwitches from a customer site and replaced them with Dell and Cisco. Endless issues and support was worthless
 
  • Like
Reactions: Editbear