Why does Reolink break functionality and then not recognize they need to fix it?

Adrian

I have four NVRs. 16 port NVRs with about 50 cameras total across three properties. I just updated one NVR from v3.0.0.148_21100910 to version v3.0.0.200_22081549. As soon as it came back up half my cameras disappeared. I don't have my cameras set up connected to the PoE ports, because I want to access them individually so i can check the health of the individual cameras, and access the cameras individually when the NVR take a poop. I have NVRs that are in different buildings from the cameras they record from. The reason for this is if the building burns down, I want the camera footage to be offsite. This means my networks are across different subnets from the cameras. This used to not work with the old style NVR OS (with the old janky interface). Then the new OS came out last year, and miraculously REOLink accidentally fixed it so now I could add cameras across subnets. Now with the newest version, they have "fixed that bug" that allows me to record across subnets. I have opened up a ticket, but I know i'm going to get an entry level technician that is going to make me walk them through my setup and give me advice or recommendations on how to change my setup. When the problem is really, "Why did you break the ability to add cameras across subnets, and can you just fix the damned thing you broke?"

My question to Reolink is this: Are you intentionally breaking this functionality? If so, why? If not, how do we get the bug fix rushed over to your dev teams since it's obvious you know how to do that functionality, since you did it until you broke it.

Thanks!