Reolink updates Learn More
Meet Reolink at IFA 2024! Learn More
Reolink Q&A Learn More
Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
Hello Cynthia,I provided the link above. Can you please pass it on to your support team and let us know what their proposed solution is? If you read the article, there is mention that Reolink was aware of and had corrected the issue. If this is the case, you certainly haven't fixed it on the 3816 cameras as there is no new firmware.There is no point in asking individual users to contact support for an individual update when this is an issue that affects all of us that have 3816 cameras. Please provide a response here where all of us can see it.
Sorry to bump an old thread, but the users who have posted in here would likely be interested in the security vulnerabilities posted here: nozominetworks(.)com/blog/new-reolink-p2p-vulnerabilities-show-iot-security-camera-risks. Question for you Reolink: The new HTML5 firmware versions you have released apparently include a patch for this P2P issue per the article. What are you doing for those of us with the 3816 Cameras? We are exposed to this same security holes AND we have been abandoned when it comes to HTML5 support. Are you going to patch the 3816 firmware to eliminate this security risk? If so you should give us HTML 5 support at the same time. Your latest firmware is older than the release of the article.I will be awaiting your response. You need to step up and address this and the HTML5/flash issue. As an absolute minimum you should give 3816 users the same security patch. You are aware of both and you could find yourselves liable for future breaches if bad actors are exploiting a vulnerability you are aware of.
Cynthia, I'm not sure why your approach here is to direct those of us with many IPC_3816 cameras to contact support. Is it so you can dismiss us without an audience? They are providing the same answer you are, that there is no plan to support these discontinued cameras which is not what Reolink has been telling us since 2019. You've conveniently discontinued these now 'unsupported' cameras and replaced them with a new model, thereby abandoning support for those of us who have purchased both old and new.Two questions for you. You said above that the problem is hardware and that the IPC_3816 cannot support HTML5. What about the C2 Pro? This is a camera you have discontinued recently. It is a IPC_51516, just as the new HTML5 supported camera revisions are. Do you have HTML5 support for this camera? Surely it can't be a hardware issue, since the hardware revision is the same. Please advise.Secondly, what ever happened to the earlier beta version of the IPC_3816 HTML5 firmware, back in 2019? Those that had it said it worked pretty well. Why was that beta not completed and why are you now claiming the hardware cannot support HTML5?Let me know about the C2 Pro. Since the hardware version is the same, the only reason I can see you not supporting that camera would be if you've made the decision to abandon customers who are using your older equipment (and by older, we're talking 1-2 years). I sincerely hope this isn't your final position on the matter.
The fact is Cynthia, Reolink stated that HTML5 support was forthcoming. Now the story has changed. Your organization has now waited until the 11th hour, and you're directing users to contact support, who are trying to quietly push the bad news to those of us who have been loyal customers and have old as well as new Reolink products. Reolink's communication with your customers has been piss poor up to this point, and users are rightfully annoyed that you have left them in the dark, discontinued products, replaced them with newer versions and abandoned those of us who have been loyal to your brand.Directing users to a different method of connecting to their cameras is nonsense. Provide HTML5 support as you originally stated you would. There was an earlier version of the IPC_3816 in HTML5 that was beta. Your organization was close to having this done. You've chosen to abandon support hoping that we will buy newer hardware. That is a dishonest approach.There are plenty of budget cameras available out there. It would be wise to not take your customer base for granted. It will cost you in the long run.
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!