No more then any other VDB phone app. Like all apps its up too you how much access you feel conferrable giving it. On the plus side the video feed (or saved video files) is nothing more then some one driving by your house would see.
New RCA HSDB2A 3MP Doorbell IP Camera
- Thread starter fleece
- Start date
No more then any other VDB phone app. Like all apps its up too you how much access you feel conferrable giving it. On the plus side the video feed (or saved video files) is nothing more then some one driving by your house would see.
I don't have Synology but several here do. @alexdelprete would be able to help you, he will Chime in...
Disable video encryption? Only thought...
i think video encryption is only in regards to the microsd card. The stream itself isn't protected by this feature.
The only time i had a grey screen in synology was when i had the capabilities of the camera set wrong. That or a weak connection that dropped a lot.
Only reason I mentioned it is you have to disable video encryption for Echo or Google to work. Just not sure how Synology gets its RTSP feed.
Sent from my SM-G930P using Tapatalk
alexdelprete
Getting comfortable
You have several options: using SAGE zigbee sensor or firefly electronix doorbell sensor (wifi+MQTT). I have both. They work perfectly.
This is interesting, but I see no specific characteristic of the button press event. You should trace all common events (motion detection, etc.), capture those requests, so we can understand if there is something in that request that allows us to distinguish the various events. Cool finding.
alexdelprete
Getting comfortable
Yes, encryption has to be disabled. The RTSP stream is encrypted if that option is turned on. That's why to work with Alexa/Google Home, etc. you need to disable it.
alexdelprete
Getting comfortable
Nope. The RTSP stream is encrypted. In order for other NVR (hw or sw) or systems (Alexa/Google Home) to receive the stream in clear is to disable the option.
alexdelprete
Getting comfortable
RTSP is a standard. There's only one way to get it. The same one for every NVR system, SSS included.
alexdelprete
Getting comfortable
Not true. We intercept the button press with sensors on the electrical wires since a long time. SAGE doorbell sensor, or Fireflyelectronix doorbell sensor are the ones I personally tried, and they both work fine.
True, i saw those solutions. But i could not get over it that i would have to buy an other piece of hardware for such a simple task. Thats why i was looking for a solution with what i have on hands.
Hey guys, new here. Recently got the camera here in Canada.
Do you guys know if this one will work with any of the firwmares out there?
It is listed as a NDB313-W.
www.infinitecables.com
I have had it working directly with the Hikvision software, but in the wifi settings when setting it up, it has an EZVIZ access point.
However, that being said, I seem to have an OEM version of the EZVIZ without the EZVIZ faceplates.
On the hikvision app, there is no update available, and it is a the 5.2.4 191216 build.
Do you guys know if this one will work with any of the firwmares out there?
It is listed as a NDB313-W.
OPEN BOX - Video Doorbell 3MP HD Resolution - WiFi - Two-Way Communication - 2.2mm Lens - IR Night Vision - IP65
Overview This 3MP Wi-Fi video doorbell has a 180° vertical and 105° horizontal field of view and notifies you when someone is at your door on your smartphone or tablet. The doorbell can be motion activated or pressing the doorbell button. Two-way communication lets you hear and speak to people...
www.infinitecables.com
I have had it working directly with the Hikvision software, but in the wifi settings when setting it up, it has an EZVIZ access point.
However, that being said, I seem to have an OEM version of the EZVIZ without the EZVIZ faceplates.
On the hikvision app, there is no update available, and it is a the 5.2.4 191216 build.
alexdelprete
Getting comfortable
Someone disassembled the doorbell and placed a couple of wires directly on the button.
Our Doorbell 101 should help in a lot of your questions...Hey guys, new here. Recently got the camera here in Canada.
Do you guys know if this one will work with any of the firwmares out there?
It is listed as a NDB313-W.
OPEN BOX - Video Doorbell 3MP HD Resolution - WiFi - Two-Way Communication - 2.2mm Lens - IR Night Vision - IP65
Overview This 3MP Wi-Fi video doorbell has a 180° vertical and 105° horizontal field of view and notifies you when someone is at your door on your smartphone or tablet. The doorbell can be motion activated or pressing the doorbell button. Two-way communication lets you hear and speak to people...
I have had it working directly with the Hikvision software, but in the wifi settings when setting it up, it has an EZVIZ access point.
However, that being said, I seem to have an OEM version of the EZVIZ without the EZVIZ faceplates.
On the hikvision app, there is no update available, and it is a the 5.2.4 191216 build.
True but that is not detecting a trigger event in the ONVIF stream like the "remote trigger event" it can pass to NVRs and BlueIris for the PIR.
So I've read that thoroughly but the list doesn't happen to list the camera that I have from that specific vendor.
Is it safe to say I have a Nellys Security version since I don't have the ezviz badging on the faceplates?
But when trying to connect it to HIK-Connect, it shows up as an EZVIZ hotspot.
alexdelprete
Getting comfortable
That depends on the firmware, and it doesn't provide that functionality, so there's no waiting for news in this thread for that, it depends on EZVIZ/Hikvision not from some tweak or finding.
alexdelprete
Getting comfortable
So if you know the DNS name that is being called, then you have 2 additional options to actually intercept the call.. 1- In your DNS server setup, create a manual entry for that DNS address that points to a server on your local subnet which overrides the external DNS forward. OR in your firewall itself, override the routing of the DNS name/IP address to a local IP.
pfSense can help figure out which port by doing some packet captures, then open that port on your local server and set up a listener than then does "X" action on the ping from the doorbell. Honestly, you probably don't even need to decode the packet if the only thing it's being used for is the doorbell button.
Family members are heading out of town for a bit next week, so I'll have some time to experiment and break things, so I will see what I can do. My problem is that I still can't use an app to configure, BCT only, so I'm not sure my doorbell is configured to try to contact anyplace on push.
pfSense can help figure out which port by doing some packet captures, then open that port on your local server and set up a listener than then does "X" action on the ping from the doorbell. Honestly, you probably don't even need to decode the packet if the only thing it's being used for is the doorbell button.
Family members are heading out of town for a bit next week, so I'll have some time to experiment and break things, so I will see what I can do. My problem is that I still can't use an app to configure, BCT only, so I'm not sure my doorbell is configured to try to contact anyplace on push.
Hey everyone. I have Ezviv DB1 wired up in my livingroom, trying it out before I install it (I'll have to run wiring for it).
It's powered by an 18v plugin power supply right now, with the Power Kit and Honeywell Wired to wireless converter.
Everything works great initially but the doorbell goes from Solid blue to the flashing red light after many hours of being powered on.
Any ideas as to what may be causing this?
Thanks
Craig
It's powered by an 18v plugin power supply right now, with the Power Kit and Honeywell Wired to wireless converter.
Everything works great initially but the doorbell goes from Solid blue to the flashing red light after many hours of being powered on.
Any ideas as to what may be causing this?
Thanks
Craig