Blue Iris not retaining IP address after power loss

Sonnie

Sonnie

IPCT+ Member
Oct 31, 2022
349
166
Lower Alabama
I have all our cameras on a reserved IP address through our Omada Controller, and the camera itself never loses that IP address that I assigned it in the Config tool.

However, when any camera loses power, updates, restarts, etc, BI adopts its original IP address and I have to enter the IP address and run the configuration again.

Is there any way to get BI to retain the IP address... am I missing a setting or have it setup incorrectly?

1722553763193.png
 
It is probably a router issue more than BI issue. Maybe you need to assign the static IP in the router.
 
The router shows the same IP address after a power loss. If it were losing its IP address, I wouldn't be able to access it via the IP address reserved for it. IOW... the camera is not losing the IP, BI is.
 
Every device should have a static IP (cameras, NICs, switches, router, controller, etc) and those static addresses should all be set on each of the devices not in the controller. This ensures anytime you lose power the device requests the same IP again before it reconnects to your network. The controller should simply mirror what you have set up on the devices. Then you go into BI and setup each camera to match the static IP you have set on the camera.
 
Last edited:
Yes... the Ethernet port is static, as are all the switches with the subnet mask and default gateway.

The controller's purpose is to control all the devices in one location. The IP addresses are set through the controller. If I try to log in to a device, it tells me it is controlled by the controller. If I want to set the IPs in the switch, I have to forget the switch in the OC, which defeats the purpose of the OC. The static IP being set in the OC is no different than setting it in the switch... as the OC sets it in the switch just like I would. The switches and cameras have never changed IP addresses; they always remain the same because they are static, except in BI.

The cameras are not being assigned an IP address via DHCP... they are falling back to their manufacturer IP address, but ONLY in BI, because again, I can access the camera via their static IP address even when BI is showing their manufacturer IP address. None of the devices in the OC are losing power, so their IP would not change if they weren't static, but they are static, so I believe it would be irrelevant. We are only talking about the cameras losing power due to a restart, firmware update or me unplugging it from the POE port temporarily, which causes it to lose power.

To clarify, the device, in this case the camera, does not lose it's IP address. When it reconnects, it keeps the same IP address, but for some reason BI is not picking up that IP address, but instead is reverting back to the manufacturer IP.

Maybe I don't have something set up correctly in BI.
 
Sounds like the BI machine is coming online faster than the controller can negotiate the cameras and is causing issues. So I would unplug one of your cameras, plug it into just a stand alone dumb switch, then plug a PC/laptop into the switch and login to the camera directly. If the camera is still set to the default IP, then change it to what the static IP should be on your network. Now plug the camera back into your network and retest the power failure scenario again to see if that camera is functioning properly. If it does, now you know how to fix it.
 
On startup dahua and hikvision cameras have a different ip. This is due to tftp recovery process. After a few secs the normal OS is booting and it will use the ip which you have in config.

You can watch this process if you plug in the cam directly into a computer and power it with 12v dc up you will notice that the ethernet adapter will be up, then down after a few secs and up again.

But not sure why blueiris is changing the config. Autodiscovery function?
 
  • Like
Reactions: MTL4
  • Like
Reactions: JDreaming
duplo said:
On startup dahua and hikvision cameras have a different ip. This is due to tftp recovery process. After a few secs the normal OS is booting and it will use the ip which you have in config.

You can watch this process if you plug in the cam directly into a computer and power it with 12v dc up you will notice that the ethernet adapter will be up, then down after a few secs and up again.

But not sure why blueiris is changing the config. Autodiscovery function?
Click to expand...

That’s what I was thinking too but wasn’t sure if the cameras were also left at the original IP and the controller was having to renegotiate all the IPs at startup. If not then I don’t know how you would shut that situation down (assuming Mike’s suggestion didn’t work nor did setting static IPs on each camera directly) besides either a time delayed restart for the BI machine or removing them from the controller.
 
Last edited:
Never had such an issue but then again, I don't use a Omada controller. I wouldn't have the need for the Omada but I guess the OP must..... :idk:

What are some benefits it provides? Call me curious.
 
Omada Controller is a device or software solution which controls and monitors the network.

Unifi has the same thing. If you have multiple access points or switches it really handy. Also you see which device is connected to which accespoint etc.

I dont believe it has anything to do with the network itself. The controller does nothing if you dont use DHCP.

For me its blueiris. It makes no sense that config changes in blue iris. That should never gonna happen.
 
To me the test would be to take a camera out of the controller and see how it works during a power failure situation. If you get the same issue, then it's not the controller (likely a BI config issue) but if it does work on that camera while others have issues then it's likely the controller causing the problem.
 
  • Like
Reactions: JDreaming and TonyR
Mike A. said:
Under individual camera settings > Video tab > Configure... > check the box for Skip initial MAC, HTTP, DNS reachability checks.
Click to expand...
This worked. Andy sent me a firmware update and it restarted the camera... IP address was retained. Thanks!

I do have the static IP set in each camera, and I was using a dumb switch when those were set. Even with the managed switch I use now, when I access the camera directly via IP address, the controller is out of the picture.
 
  • Like
Reactions: JDreaming, Mike A., MTL4 and 1 other person
Yeah, that one got a lot of us when Ken made that 'improvement' to BI at one point. Just check it to be skipped/off whenever you set up a new cam. I have Omada too so I'm familiar with it.
 
  • Like
Reactions: JDreaming
The Omada Controller is very nice for someone like me that doesn't want to have to login to each device and manage it. I can manage every device in the network from my controller, and see all the clients in one place. I can create my own network topology from the controller and view it. It allows me to monitor and manage the entire network. You can also use their clound to manage it remotely. I don't, but if someone wanted to, they could.

TonyR said:
Very well could be.

@Sonnie , what is BI's version?
Click to expand...
I keep it updated everytime I get a notice that there's a new version. Just updated it again tonight. It was previously on the last version update, which I want to say was within the last few days.

1722656844418.png
 
Do keep in mind that updating BI for every version means you are essentially a beta tester and you will be bound to have problems at some point.

If you want to be a beta tester, that is great as it is needed, but there will be headaches along the way.

Many of us once our system is stable, we leave it alone and we do not update until BI adds something that we want or need. The updates are providing new features and are not addressing security vulnerabilities...the last update notes that mentioned security was version 5.2.5 - April 9, 2020
 
  • Like
Reactions: JDreaming and Sonnie
You must log in or register to reply here.
Top Bottom