Hi!
I’ve been trying to setup Virtual IP Camera devices in the new experimental release 2.2.0-rc.7 and my Hikvision cameras without success. Access to the cameras is working just fine, also trying the URL in curl or browser gets a still image but when I try to add my cameras as Virtual IP Cameras i get the error “Content-Type “image/jpeg;charset=UTF-8” not allowed.”
Have anyone successfully added hikvision cameras as virtual ip cameras?
These are the models that I have tried, both with same result.
DS-2CD2542FWD-IS
DS-2CD2032F-I
There is a setting “System -> Authentification”
It’s default digest only but I guess Homey does only support basic authentification. You have to switch it to basic to work with Homey. Also had that same issue with showing the cams on my Fritz Phone. So it’s not only Homey which doesn’t support digest.
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.
Okay with the NVR it works fine and direct with the camera not.
I see the differences. The NVR sends Content-Type: “image/jpeg” and the cameras Content-Type: “image/jpeg;charset=UTF-8” - but Homey ony allows Content-Type: “image/jpeg”
This is, in my opinion, a Homey bug. It should not care if any parameters are added to the header, as long as it is declared to contain image/jpeg data. A charset parameter doesn’t make much sense for binary data, but OTOH, RFC2046 states that “MIME implementations must also ignore any parameters whose names they do not recognize”.
I have the Hikvision DS-2CD3145F-I. When i generate the Url i got rtsp://user:password@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?
Nothing done wrong, Homey protocol to use camera’s like Hikvision have to be updated.
That’s all, therefor, be patience! Dozens of Hikvision users are in the same