SOLVED: Dahua IPC-HDW2231R-ZS loosing the plot!

Rick daVida

Rick daVida

n3wb
May 21, 2018
29
21
Gondwanaland
I have a Dahua IPC-HDW2231R-ZS which has begun to 'disappear' from the BI interface after a system power failure; all other cameras return to their defaults on power resume.

When I delete and add the camera in the BI interface, it reappears with all presets in place, except for the time and date. The local timezone is however still correct.

This is recent behaviour. There have been no camera FW updates, BI is current and all other camera perform as expected.

Any help appreciated.
 
Sounds like you are caught up in one of the updates that was trying to make life easy for those that don't understand IP addresses and was tying the camera to the MAC address instead and then would potentially give you a different IP address that BI didn't see.

In theory it should be a good feature because many people use DHCP. Most consumer cams are dhcp by default.
So blueiris is able to follow the camera if the dhcp lease get revoked, but it can also cause problems.

Make your camera a static IP address and then check the Skip Initial MAC, HTTP, DNS reachability tests

1733965455226.png

Here are a few threads that discuss it.

5.6.2 - September 23, 2022​

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...
ipcamtalk.com
ipcamtalk.com

Blue Iris is changing IP addresses randomly​

Hello All I have a system with 4 cameras and recently 2 squares in BI are displaying the same camera. I change it back and a few hours/days there will be 2 the same again. Here you can see that at 12 noon two changed to 192.168.2.50. There is no cameras here. then about 40 min later they...
ipcamtalk.com
ipcamtalk.com

BI changed camera IP addresses​

Updated to BI 5.6.2 the other day on one of my BI systems. Last night, the IP addresses of 2 of the cameras was changed in the BI configuration. I usually reserve .50-.200 for DHCP and the addresses in BI was configured for IP addresses in the DHCP range but I would never have put my cameras in...
ipcamtalk.com
ipcamtalk.com

New BI doesn't return the signal for some cameras after router/switch reboot, gets stuck at no signal, was fine on old BI​

Hello! I am having an issue that I didn't have with BI 5.4.4 before upgrading to latest (5.7.9.4 and now on 5.7.9.7), when I for example restart the router or switch (for troubleshooting purposes) or disable the ethernet adapter, all my cameras go no signal (obviously) but the problem is that...
 
Thanks wittaj, checking the 'Skip initial MAC . . . ' box seems to have fixed the issue.

I have all my cameras on a separate NIC with static addresses, so I couldn't understand why the LIVE camera view was only available via the camera / browser, and not via the BI interface.

Thanks for taking the time to post those links as well; very useful.

Rick

​

 
wittaj said:
Sounds like you are caught up in one of the updates that was trying to make life easy for those that don't understand IP addresses and was tying the camera to the MAC address instead and then would potentially give you a different IP address that BI didn't see.

In theory it should be a good feature because many people use DHCP. Most consumer cams are dhcp by default.
So blueiris is able to follow the camera if the dhcp lease get revoked, but it can also cause problems.

Make your camera a static IP address and then check the Skip Initial MAC, HTTP, DNS reachability tests

View attachment 209499
Click to expand...
It would be interesting to know if this BI feature has caused more problems than it has prevented. I just don't see any real benefit from it.. :idk:
 
TonyR said:
It would be interesting to know if this BI feature has caused more problems than it has prevented. I just don't see any real benefit from it.. :idk:
Click to expand...

Based on posts here, I would say it has, but we don't know how many it has saved and they didn't know and thus didn't report it.

I am guessing BI must have got enough complaints from people who would lose their cameras in BI with a power outage that they felt the need to add this feature.
 
wittaj said:
Based on posts here, I would say it has, but we don't know how many it has saved and they didn't know and thus didn't report it.
Click to expand...
True.....

wittaj said:
I am guessing BI must have got enough complaints from people who would lose their cameras in BI with a power outage that they felt the need to add this feature.
Click to expand...
Could be.
IMO, assigning unique static IP's at the start can save some hair pullin' but some don't want to do it or don't want to know how. :idk:

For me, it's been a long time habit. I remember when some routers didn't have IP reservation ability to help with DHCP. And PC's would lose track of network print servers unless the IP was static. Just making many device IP's static took care of the problem.

Now routers have IP reservations. And print servers are pretty much autonomous...but old habits can be hard to break. But I firmly believe in using what works best for you and what cranks your tractor. :cool:
 
Last edited:
  • Like
Reactions: looney2ns
Well, what threw me of the scent was the fact that only one of my cameras has this problem, the rest are fine.

Similarly, this camera routinely reverts to a previous password, even though I've reset the user and ONVIF passwords on multiple occasions.

If this camera was a PC motherboard, I'd reflash the last available FW, but I've decided to leave well enough alone, and replace it when I have the funds.

Thanks again to All for this great resource.

Rick
 
After literally days and days of uniformed 'fault finding', I discovered that two of the Dahua cameras had the same IP address !?!?

No idea how this happened. I'm reasonably network-savy when it comes to addresses etc, and Blue Iris itself did not display this address conflict on camera discovery.

I found the problem but setting up a router and PC at the PoE switch, then running the Dahua config utility which showed the conflict.

As soon as the conflict was resolved, the two cameras in question went from displaying multiple and random error messages, with only occasional 'live' signal, to behaving like when they were new.

I got a new Netgear PoE switch out of the process, so there are some positive here.

Thanks again for all the input.

Rick
 
  • Like
Reactions: bigredfish, Mike A. and SpacemanSpiff
TheWaterbug said:
Is it 192.168.1.108? Or 192.168.1.251?
Click to expand...
The default is 192.168.1.108. I have all my IP cams on a seperate NIC at 10.x.x.x

But after posting 'SOLVED' above, the problem returned!

I had to do a hard reset several times to stop the cam from reverting to the original IP address and password.

It's been rock solid for a few days now so hopefully the issues is resolved and I can get back to Christmas!

Rick
 
You must log in or register to reply here.
Top Bottom