I added two cameras to my BI for testing a solar based setup, and I've noticed some strange behavior in BI. When I initially set them up, I set one up, and then I used that one as a base for the second one, just changing the IP after it was set up and everything was fine. Then the next morning, when the cameras went down overnight due to the battery being depleted, I noticed that the image in the 'no signal was the same for both cameras. When I looked in BI, I found that now both had the same IP under the 'Video' tab. Thought maybe, as odd as it sounds, it was related to having 'cloned' the first one to make the second, so I deleted them both and re-created them individually with new names. Last night, when the battery died, same thing. The config in BI changed from one having an IP (last octet) of .107 and the other .114 to both being .114. Change the one back and it's fine for now, but I bet it'll change on its own again tonight if/when the battery goes dead.
This is very odd - has anyone seen this before?
Odd camera behavior
Re: Odd camera behavior
Ok, so this took another weird turn... Since I 'fixed it' this morning, it was fine, and then at some point, the .107 camera got 'copied ' to the other camera, so both had the .107 cameras feed... this is REALLY odd..... The settings for cameras in BI SHOULDN'T CHANGE ON THEIR OWN....
Re: Odd camera behavior
I think Ken fixes things that we didn't know were broken. I think this is a BI5 mechanism to keep the correct camera IP address on a LAN where things keep changing, and my suspect settings are these in the camera Video configuration settings:
The HELP file shows:
- IP settings.png (11.94 KiB) Viewed 3594 times
The HELP file shows:
and:[5.9.4.2] For cameras with changing RTSP URIs, the option is now given to use ONVIF to refresh the stream URIs each time the camera is initialized.
Are they unticked for your cameras ?The software by default first verifies the camera is online by “pinging” its HTTP port before continuing on to video streaming. This allows a check for address redirection, and possibly a session key or cookie as well that may be required for other functionality on some models.
You may elect to bypass this functionality here by selecting Skip initial HTTP DNS and reachability tests.
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
Re: Odd camera behavior
You must be on the 'latest and greatest' as those options don't appear for me.. I'm on 5.9.3.4.
Re: Odd camera behavior
This can be a common problem if the cameras are connecting via an access point or wi-fi bridge. This is due to Blue Iris not being able to reconcile the MAC addresses of the cameras behind such devices to their associated IP addresses in the Blue Iris configurations.
Ticking the 'Skip' box for MAC, DNS, etc. combined with appropriate IP address bindings in the router/dhcp server will usually fix the problem.
Ticking the 'Skip' box for MAC, DNS, etc. combined with appropriate IP address bindings in the router/dhcp server will usually fix the problem.
Re: Odd camera behavior
Well, these ARE connecting through a wireless bridge, but there's no NAT or anything and their MAC address ''should' be properly recognizable by BI... My DHCP server which is on 'this side' of the bridge properly recognizes their MAC addresses and they have reservations.
Re: Odd camera behavior
The bridge is your problem.
I've posted about it several times explaining how this happens. It can be a real pain in the ass trying to figure it out unless you just stumble across the bridge address popping up in a camera config in BI or another device's address behind the bridge being applied to an incorrect device also behind the bridge. The devices still appear on the network as active with their correct IP addresses, just not in Blue Iris.
Try checking the 'skip' box for the MAC, etc. in the affected camera's BI configs and see if that helps.
I've posted about it several times explaining how this happens. It can be a real pain in the ass trying to figure it out unless you just stumble across the bridge address popping up in a camera config in BI or another device's address behind the bridge being applied to an incorrect device also behind the bridge. The devices still appear on the network as active with their correct IP addresses, just not in Blue Iris.
Try checking the 'skip' box for the MAC, etc. in the affected camera's BI configs and see if that helps.
Re: Odd camera behavior
That must have been it. I was blind and didn't see it in the settings initially. After I checked the box, they seem to be behaving now.
Was that a 'feature' that was added at some point in the last year or so? I had been playing with this setup about a year ago and never had this crop up before.
Was that a 'feature' that was added at some point in the last year or so? I had been playing with this setup about a year ago and never had this crop up before.
Re: Odd camera behavior
I believe it's been there since inception.
It's purpose is explained in the help topics for that page in pretty vague terms.
Fortunately it's an effective solution for this particular problem.
It's purpose is explained in the help topics for that page in pretty vague terms.
Fortunately it's an effective solution for this particular problem.