New RCA HSDB2A 3MP Doorbell IP Camera
- Thread starter fleece
- Start date
Sorry, what aspect of the image quality you think is disappointing apart from the nightvision. Did you try to improve by using the hikvision batch configuration software? What resolution do you use? What exactly don’t you like in the nightvision? What do you use to watch the picture/video? What brand do you refer to? Latest firmware? ( EZViz did some finetuning in the app lately?
So in short could you eloborate? Thanks
I usually ignore blank statements like these. Not having any experience with the Yoosee, being a 1080p camera, it was not even on my search list when I purchased our 3MP 1536 Res. Doorbell. Only one closest to our our res., at the time I purchased mine in July, 2019, was the Nest Hello at 1200. The Rings are 1080p, with their first Ring 720p. The eufy sports 1920 res., which is nice, but lacks all our flexibility. Not putting down the Yoosee, it seems to have a lot of our flexibility, but definitely not the video quality we have.
YooSee SD-M5 doorbell: 1080p, PoE, RTSP, Onvif, only $66
Hi, I think this is a new doorbell from YooSee (model SD-M5) and on paper it looks too good to be true: 1080p app controlled smart doorbell camera PoE wireless Wi-Fi AC 8-24V DC 9-36V built-in PIR motion sensor Yoosee app Yoosee 1080p smart video doorbell/intercom HD camera wireless/Wi-Fi...
Last edited:
Something weird happened this weekend on the backend cloud service. My RCA HSDB2 doorbell had been running fine since January 2019 but suddenly went into "offline" state in the various mobile apps and on hikcloud website. However, it was still recording to my NVR and I can still view live feed via tinycam/motioneye/gdmss like normal. In the past few times where it went "offline" due to power outage, I would quickly remote into it via iVMS4200 and force reboot the doorbell to not have to go through reset procedure. This time, it didn't come back online status even after half dozen reboots. Everything still worked fine except no PIR push notifications nor video doorbell call due to offline status in the cloud server.
After 30min of troubleshooting to rule out network and manually adding back doorbell in all the branded apps(it allows you to add doorbell fine but more like shared views without alerts), I gave up and performed multiple hard resets of doorbell trying various combinations. That didn't resolve it and caused more issues with password and WiFi SSID name mismatch because I had Laview 190716 FW installed on my RCA unit as I wanted ONVIF when it released. Again, manually assigning WiFi via iVMS tool still only gets it on the network but wouldn't let me register it successfully via any of the mobile apps. So now it's still offline status but also deleted from cloud in both app and website.
Left with no choice, I upgraded to latest Ezviz DB1 191211 FW yesterday morning to get past the mismatched SSID/password issue. After another reboot just to be sure, it allowed me to successfully register my RCA HSDB2 doorbell to Ezviz/Hikvision cloud service in the app. It's been stable since then BUT I knew that 191211 FW didn't have ONVIF so kind of bummed that I was forced to upgrade and lose my ONVIF feature from 190716. Since it's operating fine via RTSP, I didn't want to push my luck and downgrade to 190716 to get ONVIF back. Also still no access to Alexa nor Google in 191211...
After 30min of troubleshooting to rule out network and manually adding back doorbell in all the branded apps(it allows you to add doorbell fine but more like shared views without alerts), I gave up and performed multiple hard resets of doorbell trying various combinations. That didn't resolve it and caused more issues with password and WiFi SSID name mismatch because I had Laview 190716 FW installed on my RCA unit as I wanted ONVIF when it released. Again, manually assigning WiFi via iVMS tool still only gets it on the network but wouldn't let me register it successfully via any of the mobile apps. So now it's still offline status but also deleted from cloud in both app and website.
Left with no choice, I upgraded to latest Ezviz DB1 191211 FW yesterday morning to get past the mismatched SSID/password issue. After another reboot just to be sure, it allowed me to successfully register my RCA HSDB2 doorbell to Ezviz/Hikvision cloud service in the app. It's been stable since then BUT I knew that 191211 FW didn't have ONVIF so kind of bummed that I was forced to upgrade and lose my ONVIF feature from 190716. Since it's operating fine via RTSP, I didn't want to push my luck and downgrade to 190716 to get ONVIF back. Also still no access to Alexa nor Google in 191211...
Got any images from that Yoosee SD-MD5 you're willing to post here?
If so, please do share them, and let us decide for ourselves.
TechBill
Known around here
- Nov 1, 2014
- 1,826
- 1,186
I found your post in this thread amusing after reading all of your other posts on this forum which is a total of 18 posts and most of your posts are in the Yoosee thread where you are expressing your disappointment on the Yoosee camera quality and its poor framerate.
, Cloud 10, etc.
TechBill
Known around here
- Nov 1, 2014
- 1,826
- 1,186
I noticed and learned something today.
I was working on my network. I took my wifi offline for a bit while I worked on it. The Ezviz doorbell was flashing red when it couldn't find the wifi and as soon I put the wifi back in service, it changed back to solid blue.
I was working on my network. I took my wifi offline for a bit while I worked on it. The Ezviz doorbell was flashing red when it couldn't find the wifi and as soon I put the wifi back in service, it changed back to solid blue.
Did you expect a different behaviour?
This sounds like standard behaviour for a wifi client.
TechBill
Known around here
- Nov 1, 2014
- 1,826
- 1,186
Yes, I don't expect it to be blinking red telling the world "Hey! It's okay come steal the package, I won't tell the owner that you stopped by".
They could always use the heartbeat method.
Have the doorbell send a heartbeat to the cloud every 10 minutes and if the cloud doesn't get a heartbeat in 10 minutes time span then send an alert to the owner's app. I am a field technician for a very large communication company and we use heartbeat to check if the connection is still alive.
Agreed, so wonder if there is a way to do that in home assistant or Blue Iris? I know we get push notifications when our SmartThings hub goes down or when our Google Voice (ObiTalk) goes offline.
alexdelprete
Getting comfortable
Looks nice. Do you have the specs/measurements of the finished backplate so I can try to have one made for me from the local shop? Thanks.
It would be great to also have the face-plate like that.
in Home assistant you can add the doorbell as a Device Tracker. There are several intergrations for tracking a device based on IP. I have an asus router, so I use that integration, but there are many other options. You can then set an automation to notify you if the device goes to not_home
Curious to see what the various re-branded doorbells display for your "Panel Version" and "Hardware Version" under device information. My RCA HSDB2 is at "V0" for panel and "0x0" for hardware versions. Even though I've upgraded it to 191211 firmware, I notice the disable outdoor bell sound isn't available in my mobile app.
The outer dimensions were dictated by the imprint of my old doorbell (diameter=60 mm). As i wanted a more or less uniform edge around the db1 i choose 145 mmx60 mm as outer dimensions. But you can go really nuts and choose every shape you like.Looks nice. Do you have the specs/measurements of the finished backplate so I can try to have one made for me from the local shop? Thanks.
It would be great to also have the face-plate like that.
The 2 mounting holes are 89 mm apart (think this is 3.5 inch). The diameter of these i choose 8 mm so there is some wiggle room during mounting.
And in the center there is a 30 mm hole for the connection cable. This could be a bit bigger as the db1 is around 45 mm wide.
Hope this is clear enough; also see the ordering page.
bob2701
Getting comfortable
OK, this is what you mean.
The db1, as a stand alone device, can only communicate to the outside world through wifi and the red/blue ring (also potentially through a connected doorbell but this outside the control of the db1).
When wifi is down/not connected/not available it can only signal this through the ring.
I agree it could send the "wrong message" as this behavior is not configurable at the moment.
I didn't check this but maybe RGB leds are used and after a firmware upgrade different colors and patterns for the ring can be chosen. The non availability of wifi wouldn't be that obvious and more important user specific.
Thanks for the confirmation that we are still the same hardware between RCA and Ezviz. Must be Ezviz locking out the disable outdoor bell sound feature on my RCA via firmware like they are doing with preventing Alexa/Google.