Hi,
All my Amcrest & Dericam cameras are normal but one. Normal cams, http or https right in, no problem. A while back I picked up an Amcrest ASH camera, & it sends video ok, I can ping it, but Amcrest disallows web u.i.
And so, the question becomes, "Why does Amcrest (and likely other ASH makers) omit web U.I.?"
Let me guess,
#1 - LABOR INTENSIVE, too hard to write the firmware source code
#2 - Consumer-grade camera users would never think to use web U.I. anyway
Anyone know if there's any way to telnet in or SSH in, in order to diddle with the firmware, and maybe it flash it to another Amcrest model's firmware?
All my Amcrest & Dericam cameras are normal but one. Normal cams, http or https right in, no problem. A while back I picked up an Amcrest ASH camera, & it sends video ok, I can ping it, but Amcrest disallows web u.i.
And so, the question becomes, "Why does Amcrest (and likely other ASH makers) omit web U.I.?"
Let me guess,
#1 - LABOR INTENSIVE, too hard to write the firmware source code
#2 - Consumer-grade camera users would never think to use web U.I. anyway
Anyone know if there's any way to telnet in or SSH in, in order to diddle with the firmware, and maybe it flash it to another Amcrest model's firmware?