I wanted to update this thread in order to keep the momentum going -

I reached back out to support with the very latest camera and they were able to pass on to me what I can only assume is a beta firmware - coded specifically to my hardware revision and it seems to *finally* address the dhcp issue as the device is now showing up properly and identifying itself with the proper static ip address, and monitoring seems to be fine. I tried to use that same firmware on a handful of other E1 outdoors but it failed due likely to a hardware revision issue. Hopefully support can resolve this issue so I can patch the rest of my E1 outdoors. My assumption being that if its patchable on this specific hardware revision it should be doable on the rest, and hopefully across the rest of their product line (I don't know if it exists outside the E1's as I haven't used any of the other products).

I did raise another issue which I am sure most of you are already familiar with - the Camera's WIFI name should match the camera name variable that you set in the administrative interface - having 5, 10, 15 camera's show up in your WIFI management with the same ubiquitous Camera1 isn't particularly helpful. Small steps though. I appreciate *whoever it is* that is finally taking this issue seriously at @ Reolink but its past time. The hardware is good, better than the most of the amcrest or dahua stuff I've touched at the same price scale but your firmware has been holding you back for quite some time.

@fdcastel_709084875846370 keep it going, what camera's and hardware revision do you have??

Having the exact same issue here 



 - as you can see all 3 of them for some reason decided they should be using dhcp and all of them grabbed the exact same ip address which of course isn't pingable and is causing all sorts of issues and alarms on my network. 
All these camera's are set to static ip addresses, I have this with a dozen others - We will be returning all of them and never buying another Reolink product again until this issue is resolved. 

Going to support yielded absolutely nothing useful - 

"In general, the wifi camera will send a DHCP request to detect the network connection status in order to check whether there is a wifi connection issue in time.
Attached is the latest firmware of the camera to this email, please upgrade it to see if it helps. Note: there's no need to unzip the file.

Sufficed it to say the update didn't fix anything. 

I just received one of their very latest E1 outdoor's, problem still very much exists. 

Build No. build 23021701
Hardware No. IPC_566SD85MP
Config Version v3.1.0.0
Firmware Version v3.1.0.1789_23021701
Details IPC_566SD85MPS10E1WA1100000001


#1306248 exists for tracking the non resolution.  


@joseph_1979 - Please note that this is happening across the board.

@latez1_702748087968371

I can now happily confirm that a fixed firmware exists for IPC_523SD8 & IPC_566SD85MP (I am using both now) for a couple dozen cameras.

@joseph_1979 Appreciate your response, will keep pushing both here and via email, and via linkedin if I have to do find a director or vp of development. The only thing truly holding back a lot of their low end cameras is the quite frankly poorly implemented firmware.

I wanted to update this thread in order to keep the momentum going -

I reached back out to support with the very latest camera and they were able to pass on to me what I can only assume is a beta firmware - coded specifically to my hardware revision and it seems to *finally* address the dhcp issue as the device is now showing up properly and identifying itself with the proper static ip address, and monitoring seems to be fine. I tried to use that same firmware on a handful of other E1 outdoors but it failed due likely to a hardware revision issue. Hopefully support can resolve this issue so I can patch the rest of my E1 outdoors. My assumption being that if its patchable on this specific hardware revision it should be doable on the rest, and hopefully across the rest of their product line (I don't know if it exists outside the E1's as I haven't used any of the other products).

I did raise another issue which I am sure most of you are already familiar with - the Camera's WIFI name should match the camera name variable that you set in the administrative interface - having 5, 10, 15 camera's show up in your WIFI management with the same ubiquitous Camera1 isn't particularly helpful. Small steps though. I appreciate *whoever it is* that is finally taking this issue seriously at @ Reolink but its past time. The hardware is good, better than the most of the amcrest or dahua stuff I've touched at the same price scale but your firmware has been holding you back for quite some time.

@fdcastel_709084875846370 keep it going, what camera's and hardware revision do you have??

@joseph_1979 Understood, just assumed you had some insight as a global mod - does the dev team peruse the board or is it exclusively through the ticketing system? I think clearly enough of us out here are seeing this distinct problem that needs to be resolved. Saying that this is normal when its clearly not the normal behavior for any cam or quite frankly any wifi device I've ever had is not a valid response.

Any special insight @Cynthia_124785627824270 ?

Having the exact same issue here 



 - as you can see all 3 of them for some reason decided they should be using dhcp and all of them grabbed the exact same ip address which of course isn't pingable and is causing all sorts of issues and alarms on my network. 
All these camera's are set to static ip addresses, I have this with a dozen others - We will be returning all of them and never buying another Reolink product again until this issue is resolved. 

Going to support yielded absolutely nothing useful - 

"In general, the wifi camera will send a DHCP request to detect the network connection status in order to check whether there is a wifi connection issue in time.
Attached is the latest firmware of the camera to this email, please upgrade it to see if it helps. Note: there's no need to unzip the file.

Sufficed it to say the update didn't fix anything. 

I just received one of their very latest E1 outdoor's, problem still very much exists. 

Build No. build 23021701
Hardware No. IPC_566SD85MP
Config Version v3.1.0.0
Firmware Version v3.1.0.1789_23021701
Details IPC_566SD85MPS10E1WA1100000001


#1306248 exists for tracking the non resolution.  


@joseph_1979 - Please note that this is happening across the board.