Sweet! LTS is releasing an ONVIF compatible doorbell with SD card slot and 940nm IR

The nest doorbell won't be able to integrate with any of the other Clare solutions. That may or may not be a deal breaker for you.

I am not too worried about the integration with Clare's systems if it comes down to using a better camera, but at the same time, the monthly cost of the Nest subscription service is a huge turn off.
 
  • Like
Reactions: spoonek
I have the RCA version and to be honest, the camera is not bad at all. Night vision is acceptable for me.
 
  • Like
Reactions: katamara
I have the RCA version and to be honest, the camera is not bad at all. Night vision is acceptable for me.

Thanks for the reply. I love the fact that the Clare Doorbell doesn't have the subscription fee and don't mind having to try to setup a NVR such as Blue Iris or even the Clare NVR to get it to record at all times. I had a Ring Stick up Camera for a bit near the front door, but hated the missed notifications, or the notifications that occurred, but you missed the person because by the time the app connected, the person was gone.
 
So went through my first night with the cam... unfortunately it seem my RCA IR LED glare is more like VorlonFrog's example rather tan Spoonek. Will try cleaning the lens next... anyway to clean the inside of the lens? i noticed mine have a piece of lint inside the dome lens.

still trying to get the cam to trigger the motion detection/alarm recording on my NVR.... any one with any help on that I would be forever grateful
 
So went through my first night with the cam... unfortunately it seem my RCA IR LED glare is more like VorlonFrog's example rather tan Spoonek. Will try cleaning the lens next... anyway to clean the inside of the lens? i noticed mine have a piece of lint inside the dome lens.

still trying to get the cam to trigger the motion detection/alarm recording on my NVR.... any one with any help on that I would be forever grateful

They usually cover the lens with a protective film, I assume you removed it. It looks like you could take it apart, been tempted to look at the insides.

I'm not familiar with NVRs, but if you are getting a live view, I would think you would be able to use the NVR's motion detection ability on the live view stream. With Blue Iris, I had to use the port 8000 with rtp/udp option to get a good recording (not rtsp). Using a browser, access the camera and go into, I think, the Network section to check what management port is set at (usually defaults to 8000). If you have another camera using the same port, try changing it to 9000 or something and then try that on your NVR.
 
They usually cover the lens with a protective film, I assume you removed it. It looks like you could take it apart, been tempted to look at the insides.

I'm not familiar with NVRs, but if you are getting a live view, I would think you would be able to use the NVR's motion detection ability on the live view stream. With Blue Iris, I had to use the port 8000 with rtp/udp option to get a good recording (not rtsp). Using a browser, access the camera and go into, I think, the Network section to check what management port is set at (usually defaults to 8000). If you have another camera using the same port, try changing it to 9000 or something and then try that on your NVR.

yes removed both the one over the dome lens and the ring IR led film.

The IP NVR Motion detection relies on notification from the IP Camera instead of doing its own image analysis. My front door camera will trigger the NVR motion detection via a built in PIR alarm linkage over ONVIF so I know it can be done, but so far, no luck with the doorbell. These new budget Dahua NVR may have removed the Hikvision protocol... I can't get it to connect to the doorbell on port 8000 even after trying several different protocol beside ONVIF on port 80. ONVIF Device manager is reporting the doorbell as ONVIF v2.20
 
I'm not familiar with NVRs, but if you are getting a live view, I would think you would be able to use the NVR's motion detection ability on the live view stream. With Blue Iris, I had to use the port 8000 with rtp/udp option to get a good recording (not rtsp). Using a browser, access the camera and go into, I think, the Network section to check what management port is set at (usually defaults to 8000). If you have another camera using the same port, try changing it to 9000 or something and then try that on your NVR.
What were your settings in blue iris for this?
 
What were your settings in blue iris for this?

When originally adding the cam, the only thing I entered was rtsp://login:passwd@192.168.0.1xx:554/Streaming/Channels/101 and pressed the Ok button. This worked somewhat, but it was skipping every 1 to 3 seconds on the recordings. Someone here stated that they had to use RTP/UDP option instead. So, I went in and turned off Send RTSP keep alive and Use RTPS/stream code. Then turned on Use RTP/UDP ports and changed it to 8000. Now the recordings are good. From what I read, I assume that RTP is encapsulated within RTSP with some control signals or something?...
 
  • Like
Reactions: fenderman
When originally adding the cam, the only thing I entered was rtsp://login:passwd@192.168.0.1xx:554/Streaming/Channels/101 and pressed the Ok button. This worked somewhat, but it was skipping every 1 to 3 seconds on the recordings. Someone here stated that they had to use RTP/UDP option instead. So, I went in and turned off Send RTSP keep alive and Use RTPS/stream code. Then turned on Use RTP/UDP ports and changed it to 8000. Now the recordings are good. From what I read, I assume that RTP is encapsulated within RTSP with some control signals or something?...
if you change the rtp/udp ports in your settings to 8001, do you get the stream?
 
if you change the rtp/udp ports in your settings to 8001, do you get the stream?

If I change it to 8001, it looks like it's working, however going back to the settings, it changed it back to 8000. So, BI must be sensing that it should be 8000. That is port set in the cam when accessing it via the browser app.

Also, I have another one that I had to change from 8000 to another number (i.e. 9000) because BI was getting confused. With both set to 8000, it seemed to work but then in a few seconds second cam being displayed in BI would switch to the first cam feed. So I had first cam being displayed twice and then it finally shutdown one of the cam (color bars). Switching the second cam to 9000 using the browser app and changing it in BI, both cams are now shown.
 
If I change it to 8001, it looks like it's working, however going back to the settings, it changed it back to 8000. So, BI must be sensing that it should be 8000. That is port set in the cam when accessing it via the browser app.

Also, I have another one that I had to change from 8000 to another number (i.e. 9000) because BI was getting confused. With both set to 8000, it seemed to work but then in a few seconds second cam being displayed in BI would switch to the first cam feed. So I had first cam being displayed twice and then it finally shutdown one of the cam (color bars). Switching the second cam to 9000 using the browser app and changing it in BI, both cams are now shown.
BI cant sense anything...likely still using 554...8000 is proprietary to hikvision clients..unchecking use rtsp timecode may have solved your issue.
 
  • Like
Reactions: concord
Good news. I think I may have a solution to the buzzing in the chime. At least it worked for me. Most chimes should have 3 terminals. One is common, in the middle. The other 2 are for the front door and the back door. Just bridge the front and back door terminals with a wire.

I have a picture and an explanation on my blog post at the end. Please let me know if this worked for you.

Installing the Nelly Security WiFi Video Doorbell
Thanks for the explanation, I'll give it a try.
 
They usually cover the lens with a protective film, I assume you removed it. It looks like you could take it apart, been tempted to look at the insides.

I'm not familiar with NVRs, but if you are getting a live view, I would think you would be able to use the NVR's motion detection ability on the live view stream. With Blue Iris, I had to use the port 8000 with rtp/udp option to get a good recording (not rtsp). Using a browser, access the camera and go into, I think, the Network section to check what management port is set at (usually defaults to 8000). If you have another camera using the same port, try changing it to 9000 or something and then try that on your NVR.

So wiping/cleaning the outside of the dome lens and IR LED ring helps with cutting down the glare quite a bit.... not perfect but still helps alot. Now I'm wondering if I can somehow take off the dome lens to wipe/clean the inside to further improve night vision............
 
I just installed Nelly's version of the camera. Does anyone know if there is a URL for grabbing a jpg snapshot? Thanks!
 
I have the RCA version. My firmware is V1.4.62 build 171127.

Clare has v2.0.0 Build 171218.
LTS has V1.4.62_171219 1/02/2018

Should I upgrade?

I can't find the firmware on the RCA, Laview nor Hikvision site. :idk:

Be warned that the Clare version sets the 1080p main stream to 12fps only and you can't change it... When Clare pushed out a version, the notification comes up on the phone app and displays a blue dot. Check on the RCA version settings, etc menus for a blue dot to see if there are any updates.
 
  • Like
Reactions: spoonek
Be warned that the Clare version sets the 1080p main stream to 12fps only and you can't change it... When Clare pushed out a version, the notification comes up on the phone app and displays a blue dot. Check on the RCA version settings, etc menus for a blue dot to see if there are any updates.

How about the LTS 17219 version? does it limit to 12 fps also?

spoonek, thanks for the link to the new firmwares
 
I have the RCA version. My firmware is V1.4.62 build 171127.

Clare has v2.0.0 Build 171218.
LTS has V1.4.62_171219 1/02/2018

Should I upgrade?

I can't find the firmware on the RCA, Laview nor Hikvision site. :idk:

I have the Laview version of this doorbell. Pretty happy other than losing motion alerts every couple of days. I figure its easy enough to fix in firmware. ANy changelog info for either of these updates?