Hello,
Is any body using this doorbell ?
It seams nice and the price is correct.
Is that possible to acces to the doorbell button ?
Best regards and thanks for your reply !
Thierry
Hello,
Is any body using this doorbell ?
It seams nice and the price is correct.
Is that possible to acces to the doorbell button ?
Best regards and thanks for your reply !
Thierry
Did you ever find out if we can access the doorbell button?
Yes, plz let us know if you found out something more!
I use it in Openhab and it works great if you donât mind the fish eye look and non standard aspect ratio. The fish eye allows you to see parcels left on the ground, yet have the camera at eye level to see peoples faces if they wear a hat. Cheap and easy to get it up and running.
No you cant get button push events, but you can do the usual zwave sensor hacks to a bell or tap into the lines with DIY electronics.
You can get PIR sensor movements sent separately from the motion alarm so you can write automations that both sensors need to agree before sending an email or triggering an auto doorbell before people even push the button. Works great.
Same camera gets sold under these names:
HIKVISION DS-HD1, RCA HSDB2A, EZVIZ DB1, LAVIEW LV-PDB1630-U, NELLYâS NSC-DB2, LTS LTH-7132-WIFI
Created some wall brackets for the camera here:
I installed a DS-HD1 a few days ago. The device is ONVIF compliant, so I enabled the ONVIF integration in HA. It was a pleasant surprise that the camera was immediately detected, and a live view appeared in my default lovelace screen.
Several entities are added:
(1) Front Doorbell camera.ds_hd1_mainstream
(2) MyFieldDetector1 Field Detection binary_sensor.myfielddetector1_field_detection
(3) MyMotionDetectorRule Cell Motion Detection binary_sensor.mymotiondetectorrule_cell_motion_detection
(4) VideoSource_1 Motion Alarm binary_sensor.videosource_1_motion_alarm
I havenât experimented with these yet, but none of them sounds like âbutton pushedâ. HA does see state changes when the doorbell motion is triggered, but Iâm not sure exactly what the different entities are tracking.
However⌠the doorbell is intended to be used with the HIK-Connect app, which I have on my phone. When the button is pushed, the doorbell initiates a âcallâ to the app, which results in a display of the live video feed on the phone screen, and a button to toggle on a two-way audio stream. So something comes out of the doorbell when the button is pushed.
It is also possible, using the app, to access the stored video clips, which includes quite a bit before the actual trigger occurred. The app talks to the camera over wifi to access the video files stored on the SD card in the camera.
So it might be possible to add something to the HA world which looks like the HIK-Connect app, and reacts to the button-push âcallâ over the Wifi connection.
Hey, very good news!
For my part, i havent already buy a doorbell, some othe projects was more important.
About the DS-HD1:
Are you happy with this device ?
What about the video quality ?
Where did you buy it ? Aliexpress ?
Can you explain the differences in term of behaviour between the first two binaries values ?
Can you send a mail in automation when on captor change ?
I am very intersted to have more info from your experiance !
Best regards
Thierry
Iâve only had the DS-HD1 a few days, but Iâm very happy with it so far. I didnât get it for HA use; the associated app (Hik-connect) had all the features I needed. So the HA compatibility is an unexpected bonus.
The doorbell was amazingly easy to install. The hardest part is getting the app onto your phone (needs to be sideloaded). You just supply power to the doorbell, then use the app to scan a QR code printed on the doorbell manual. The app then finds the doorbell and configures it to join your LAN (the same LAN the phone is using). Takes a few seconds and itâs done.
Video quality is excellent. You get to select from 3 levels: SD, HD, and Ultra HD. Plenty of pixels even when displayed on a desktop monitor. The camera lens is fisheye, so you get that typical distortion. But since itâs designed for wide view, so you can see things like packages left on the floor below the doorbell. The only problem I noted was that I have a covered porch so itâs always âin shadowâ and the image there can be pretty dark if thereâs a sunny background; but thatâs a problem with all cameras, and I mostly care about events at night anyway. It works fine at night with just âporch lightsâ on (which my HA motion sensor turns on; probably I could get the doorbell motion to do that tooâŚ)
I bought the device from Amazon. I didnât see it at Aliexpress. Also I was wary of getting a non-US model which could mean problems with things like upgrading firmware later.
Iâve only played a little with the HA interface. When I walk up to the device, the âcell motionâ and âvideo motionâ sensors both change state, and there are two HA events for each sensor, one for detecting and one for motion ceased. There appears to be only a little âhysteresisâ in the sensors. Each one stays on for just a few seconds. So when you walk by the sensors areas, you get multiple on/off sequences.
I use NodeRed for automation, and it should be simple to have the motion events send email. But I havenât actually tried that yet. The HA logic would have to be just a little complicated to avoid getting too many emails. It may even be possible to do things like send a JPEG with the email - the image is somewhere in HA since the UI is displaying it.
In my walk-up tests, the âfieldâ sensor doesnât ever change, so Iâm not sure what that is monitoring. The âcellâ and âvideoâ sensors both trigger, at slightly different times, perhaps a second or two apart. The device has both a PIR sensor and a camera built-in motion detector, so the different events are probably from the different sensors.
Using the app, you can (1) set the motion detector range and sensitivity - I assume this means the PIR sensor. You can separately also (2) set the specific area of the camera image where motion is to be detected. The app puts the image on the screen with an overlay of a grid (like large pixels), and you drag across those âcellsâ to select which ones should cause detection events. Thatâs useful for blocking out things like cars going by on the street. With the fisheye lens, there can be a lot of area in the image so you can get it to alarm on a smaller area.
I suspect that the âcellâ and âvideoâ entities in HA are reporting the 2 different sensorsâ detection events, so itâs likely that you could get different results depending on the way you set it up. E.g., the PIR sensor might report motion that the video detector ignores because youâve blocked it out of that area of the image.
The HA ONVIF integration seems to do a lot, which Iâm still discovering. Iâm just using the default behavior in HA, which adds the entities and an image to the default UI. The entities behave like other entities - e.g., you double click and you get a history graph, or you use the Logbook and see the event triggers. The image behavior is interesting. You can get a large image by double clicking. You can get a live view, or a view which looks like itâs capturing an image every 10 seconds.
I configured my device to use a 128GB SD card for storage. With the app, you can view a history of events, and then playback stored video clips, which includes video from time before the trigger. Thereâs lots you can do with the app. Since the app communicates with the doorbell over wifi, it seems likely that a 3rd-party app (like HA) could do the same things the app does.
Coincidentally, I have a Synology NAS on my LAN, which is also running an add-on called âSurveillance Stationâ. That add-on knows how to talk ONVIF; it can connect also to the doorbell device and capture video. So I could have the NAS store a continuous video stream from the doorbell (probably in addition to or instead of the SD card). Since the camera is powered through the old doorbell wires, it can be on all the time.
HA also has a âSynologyâ integration, which Iâve done no more than install. It also adds a bunch of entities. So much to exploreâŚ
Hope this helps,
/Jack
How did you get the cameras stream working? i click on the static picture and the stream opens and just keeps trying to load forever with no picture just a black display. Same thing happens with my other hikvision cameras but my Instar and Amcrest are working. All setup with ONVIF via the UI.
Sorry, but I didnât do anything special, just installed the configuration and it set up pretty much by itself. FWIW, the âsystem optionsâ are -pred 1 for ffmpeg, and transport is tcp. I didnât set those, thatâs how it came up on install.
The camera feed appeared in the Lovelace default view for the camera.ds_hd1_mainstream entity. Itâs a pseudo-static image, i.e., a âsnapshotâ which updates about every ten seconds, as indicated by the clock overlay at the bottom.
Double-clicking on the image brings up a larger window, which can be made full-screen. I clicked the âPreloadâ box too. The view then shows a realtime video feed. As long as you keep the window up, a timeline at the bottom keeps growing, as it records the video. By clicking to some earlier point on the timeline, you can ârewindâ the view to see what happened earlier.
This is with HA running on an RPi3B+ using hassio. Iâm viewing it using Firefox on Ubuntu 20.04. I get the same behavior viewing on an Android phone running the HA app.
I have another, several years older, Hikvision camera on the same LAN, but HA does not find it. Havenât investigated that yet.
This is all on a LAN, so all devices are on the same network. Maybe that makes a differenceâŚ
HTH,
/Jack
Thanks for reply. I updated to 0.114.4 and tried adding it again and now it adds 2 streams to the default love lace and 1 of them works (mainstream) and the other one marked as HD does not.
My main Hikvision cameras are still broken here also, but at least now 3 out of the 4 cameras I have are âsortâ of âworkingâ. If you figure out what is wrong with yours then please post.
My camera is now an âobsolete productâ. Although I can get to its GUI web interface, most things donât work. I get âno plug-in detectedâ.
I havenât been good about keeping the camera firmware up to date. The Hikvision site lists 9 firmware versions that Iâve missed, and there may be more. Unfortunately the firmware update tool doesnât work. I suspect itâs likely that the camera ONVIF implementation isnât compatible with HA, if it even has ONVIF in its current firmware.
Despite all that, the camera works fine for live view from other apps. E.g., Hikvisionâs IVMS-4500 app on my phone works fine to see the live view.
Iâm not confident that Iâll ever get this âobsolete productâ to work with HA. For yours, Iâd suggest making sure the firmware is up to date first.
You may need to remove any newer plug-ins that was installed from newer version nvr/camera firmware from your add/remove programs.
What tool are you referring to?
Hi, Iâm new here.
I just purchased a DS-KD8003-IME1/EU and stared playing with it couple of hours ago. I want to add it to HA. But it looks like there are a lot of missing things.
Reading the posts here, the button press cannot be recognized. I think that button initiates a SIP call. Maybe a SIP server could be installed in a docker and recognize the event from the SIP server.
Also some feedback and a request for help. I try to do this:
curl --digest -u admin:passgoeshere http://192.168.1.XX/ISAPI/VideoIntercom/capabilities
and the output is:
<?xml version="1.0" encoding="UTF-8"?>
<ResponseStatus version="1.0" xmlns="http://www.std-cgi.com/ver10/XMLSchema">
<requestURL>/ISAPI/VideoIntercom/capabilities</requestURL>
<statusCode>4</statusCode>
<statusString>Invalid Operation</statusString>
<subStatusCode>invalidOperation</subStatusCode>
<errorCode>1073741830</errorCode>
<errorMsg>invalid operation</errorMsg>
</ResponseStatus>
Do you know what could happen?
I have also this problem:
curl -i --digest -u admin:passgoeshere http://192.168.1.XX/ISAPI/VideoIntercom/callStatus?format=json
HTTP/1.1 401 Unauthorized
Date: Fri, 14 May 2021 21:33:21 GMT
Server: webs
Content-Length: 0
Connection: close
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store
Pragma: no-cache
WWW-Authenticate: Digest qop="auth", realm="DS-C02EB361", nonce="NzU1YTg0MDhmZTcxYzJkNTI4YTY2ZmNiMmRkNzU3OWE=", stale="false", opaque="", domain="::"
Content-Type: application/json
HTTP/1.1 401 Unauthorized
Date: Fri, 14 May 2021 21:33:21 GMT
Server: webs
Content-Length: 0
Connection: close
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store
Pragma: no-cache
Content-Type: application/json
Iâm running firmware 2.2.3 and tested 2.2.45, but after uploading and restarting the device it sais it has 2.2.3 build 201202
Iâm a bit lost. Maybe tomorrowâŚ
Thanks in advance!