Rtsp Camera Hikvision

[Colette]

HelloI am a bit of a newbie, please bare with me. I am trying to enable sub stream for my cameras connected to my HikVision DS-7608NI-E2 configuration. The aim being to get a URL (not rtsp) that I can paste into a browser or VLC to view an...

No progress but I heard in another forum that homey require a pure jpg file and do not support the script page that hikvision cameras provide. Workaround could probably be to get the jpg file from an NVR.

I have the Hikvision DS-2CD3145F-I. When i generate the Url i got rtsp://user:pass...@145.129.???.242//Streaming/Channels/101 and i fill this in Homey virtual ip camera i got the message URL malformed. What i am doing wrong?

This guide isn't definitive, but it is a good reference point as I am wiping out some Hikvision IP cameras I inherited in my new office space. They were all paired with an annoying proprietary Hikvision NVR, and I wanted to wipe them and use them on a new isolated VLAN with my new Raspberry Pi Frigate-based NVR setup.

Obviously, if you want to set a static IP for the camera separately, you can go ahead and do that too. I'm setting all my VLAN and IP configuration on the router, though. Especially as these cameras get older and more outdated (though they still work fine), it's best to separate them off on their own VLAN, since old firmware likely has exploits that could be hacked.

I wish you had demo'd using a Raspberry Pi + Camera module to stream video to your Frigate server.

Would love to see something like that with a Pi Zero 2 + Arducam and the specific of scripting for it with rpicam-vid & ffmpeg or vlc for rtsp or similar.

Hikvision is a huge manufacturer. They make cameras under a lot of brand names. You may be buying Hikvision, and not even know it. Sadly, a lot of other IP cameras have inferior build quality, but better software.

That said, Hikvision is taking the tiger by the tail, a bit. If you prefer a little less international intrigue and/or having the Rawling Virus in-a-jar on your network, I might recommend Reolink or Ubiquiti in a pinch.

Hikvision (Pronounced High-Kay-Vision. Yes, really) is short for Hangzhou Hikvision Digital Technology Co, LTD. partially state-owned Chinese manufacturer and supplier of video surveillance equipment for civilian and military purposes, headquartered in Hangzhou, China.

The vision for robust camera equipment, and the implementation, is massively impressive. The hardware truly is incredible as it is able to, in real time, do face detection, people counting, detect and flag unattended baggage or packages, identify animals and much more.

The software, on the other hand, is not to idealistic American standards. It is apparent the software was not built with hardening or security in mind. The main problem is that the software is a bit opaque and the known security issues in the past have been jaw-droppingly bad.

In an ideal world there would be open firmware for these cameras, ideally from some third party. Some noted security researchers have really put a lot of work into trying to tear these down, and some have lamented that the boot sequence on these cameras seems incredibly obfuscated and needlessly complex. Why go to all the trouble given the past security weaknesses?

The guide is a genuinely helpful guide for securing and configuring your Hikvision gear; they do want you to have secure gear to the extent that the criminals-du-jour are not exploiting the camera hardware to mine cryptocurrency or participate in DDoS attacks.

Almost all of these cameras feature an on-board microSD slot. If you intend to use local storage with the cameras, I highly recommend getting extremely high endurance microSD cards, designed for surveillance apps, which are only just starting to become marketed as such in the west.

If you are not familiar with what TFTP is, it is a trivial file transfer protocol. It is not built for speed, or redundancy, or reliability. Neither is the Hikvision update process. TFTP, and these IP addresses, are the cornerstone of being able to recover these cameras quickly and properly. You will waste a lot of time if you do not perform the firmware recoveries/updates from a hard-wired computer with a manually configured IP address.

Be aware that different regions (US, UK, Netherlands, EU, China/Asia Pacific) all have slightly different firmwares AND slightly different camera builds. It can be super annoying finding the right camera, and the right region, to download the correct version of the firmware.

No matter what camera you have (except the 7+ year old ones) the firmware filename will be digicap.dav but the contents are highly specific to both the camera model and global region where it was sold (in some, but not all, cases).

The second option is to attach a cable to the serial console. As these cameras run Linux under the hood, they do output to a built-in serial console. This may involve soldering or building a special console cable with a header such as:

I have flashed some Xiaomi cameras replacing the bootloader on the chip (involved a bit of soldering work), but they come nowhere near the image and build quality of the units displayed on your video.

I apologise in advance if this is a dumb question but here goes. I have been looking back through the synology video that goes with the hikvision cameras here and was wondering if I had a nas with 1 eth port could I add one with the USB and still keep them segmented off of my main network?

I have a problem with my NVR after trying to upgrade the firmware. However when i use SADP tool to check my system its showing my IP address as 10.5.33.25 !!!

Does anyone know how I can still use the tftp with that IP address?

i did ask hikvision for a password reset, i can use the xml they sent to reset the password successfully on SADP however literally 5 seconds after i try to make changes via SADP to remove DHCP so i can modify the IP, it says incorrect password.

What even are the regions?

If I start from us[.]hikvision[.]com, UK has no firmware, fw list on the EU site seems completely broken. Are we talking about www[.]hikvisioneurope[.]com/portal ? I see EU/UK here. EU seems to equal NL?

I have 4x DS-2CD2342WD-I that I picked up from auction a long time ago and they have sat because I knew that they would take effort to configure, but dang, I was not expecting THIS level of incomprehensible insanity.

Is it possible to change the internal model number to match a close model?

For example. The DS-2CD5126G0-IZS is a 2mp unit that I think has the same hardware than the 4mp/8mp and even the 12mp camera on the same lineup.

They all use the same V5.6.12 firmware.

The 2mp cameras are going for around $60 on Ebay and would be fun to convert them to a 8mp or 12mp just for fun.

I have the XMEYE DVR system with 16 cameras recorded in a hard drive box. I can see these cameras using the Firestick version of IPCAM Viewer Pro (Robert Chio) but when I bought ROKU, I see your app does not support it.

This is what it takes to load and get output from the XMEYE dvr (see an actual command line below). The Variables for others would be to change the IP Address:192.168.0.240, change the user -:yourname and change the passord -:yourpassword, and the channel=:01 through 15 for the camera number.

This app supports almost nothing. I'm surprised people have not complained to have it removed. The author says 'don't use cheap cameras' but what does that mean? Is a $50.00 camera cheap these days? There's a lot of amazing hardware out there that's cheap. Entire computers I use all day long, Libre computer, $35.00. I have cameras from $50.00 to $150.00 and not one works with this 'app'.

Majority that have problems are trying to use cameras that only have h264/h265 streams. IP Camera Viewer only supports jpeg encoded streams (mjpeg, rtsp), or snapshots directly, or, with extra hardware, supports h264 streams too:

I have 6 hikvisions. Three are old (almost a decade) and three are Of the newer onvif-supporting cameras, even when I turn onvif on only one of the three can be found--but without audio. The other one I can get the app to find it but it displays nothing unless I use the JPEG option, which briefly flashes an image every two seconds or so followed by mostly grey.

Your cameras do not meet the complete ONVIF compliance standards, which results in the absence of a jpeg encoded rtsp stream, a requirement for the application. Moreover, the Roku device has limitations that prevent it from supporting the h264 rtsp stream.

Regarding the jpeg stream, if you intend to showcase the cameras' high resolution, it may lead to slow performance. Transmitting a jpeg (mjpeg) stream entails capturing each frame as a full jpeg image, which can be quite large in size. To achieve a smoother stream, you could decrease the cameras' resolution.

I was hoping to use this channel, or even the pro version, but I have a somewhat unique camera setup. I'm using a battery (solar) powered Reolink Argus 2E wireless camera that does not support RTSP or ONVIF. BUT, I found an open source package named "neolink" that provides an RTSP bridge to NVR's, etc. I can stream the live view now from the camera using VLC with the following, basic URL:

I tried setting up a camera with the IP 192.168.1.10 and the port 8554, but when I try to edit the stream url to add "mycamera" (without the quotes), and save, your channel adds a "?" to the end of "mycamera", which will not work.

@DaBlues I gave up on it. The vendor here said my cameras do not fully support Onvif. This may indeed be the case. However, I'm back to the simple reality that all of the other software I've tried on my smart phone always works, with all of my cameras. I gave up on this particular effort, as it was a waste of time for me. I found a surplus laptop that just pulls them all down instead on windows software.

3a8082e126