Will do guys. So I just set it and will check it in 10 days. This has been a hard year, we lost our Mother back in January and our Father just passed away this past Sunday, busy week. Both our my parents in same year, wow what a year to remember.
New RCA HSDB2A 3MP Doorbell IP Camera
- Thread starter fleece
- Start date
Interesting; I can confirm I have had No disconnects recording 24/7 to Blue Iris (est. 10 months), other than when I was working on changing from an Asus AP to a TP-Link EAP Managed AP, I have a LaView running LaView's FW 190716.
So question, when did you get your RCA? Ran Nelly's FW? We had a major issue with newer RCA's bricking running on Nelly's FW earlier this year.
I found that too. My DB runs Much better on 2.4 instead of on 5Ghz band. I run 2 streams through Blue Iris, one 24/7, the other only motion. Also I have had a few VLC streams run while testing. Found out 3 RTSP streams is pretty much the limit for tis DB though.
I am still very new to BI, You might need to reach out to another Thread that focuses on BI issues. I just recently turned on Logging, you may try that to look at what the logs say. It is under Status
TechBill
Known around here
- Nov 1, 2014
- 1,826
- 1,186
alexdelprete
Getting comfortable
Condolences dear friend. It's been a tough and strange year. Be strong, I send you a big hug from Italy.
alexdelprete
Getting comfortable
Atari guy here. First computer was Atari 400 (which I still have) with a cassette player attached to save the basic programs I typed from Antic Magazine articles, one day hope to showcase it. And no I did not type on the bubble keyboard, I replaced the keyboard so in a way turning it into an Atari 800. Networking through the Atari XL/ST machines was through the MIDI port back then. Also had the first 8088 procs IBM PCs, and many clones. ARCNET? Remember that networking, BNC connectors
I've used 10BASE-2 networks, cabling, crimping BNC connectors, the taps. When the network failed you had to find which of the connected nodes was the problem: a total pain in the ass. When you have to do any kind of maintenance, the whole network went down.
But you learn the foundations of networking and basics that let you understand how networks really work at low level (physical). When we switched to 10BASE-T ethernet and I saw the first hub it was incredible. Many years have passed.
Last edited:
@alexdelprete
I like your use of the Shelly Uni device. Here was testing a modded Sonoff basic with a few soldered taps to GPIO pins, relay and temperature sensor and customized Tasmota firmware to the garage door. (up and down sensors, button and one temperature sensor). This worked fine with MQTT until last week when I decided to upgrade the firmware. It was a test devices as the current alarm panel is hard wired to the garage door. That said do you think the Shelly Uni device would serve my needs for the garage door (two analog sensors wired to it, button and temperature sensor). Analog sensors are just reed switches on the garage door up and down position, DS18xxx temperature sensor and a open/close button (which is an analog to digital conversion button).
Here too started with the Commodore 64 in the early 1980's. I did have a BBS configured here with a Pet Computer and then tapped in to a phone box outside for multiple phone lines using multiple Ventel modems with a customized hardware modem switcher running on the Commodore. Also had a Kaypro CPM "portable" computer that I used for bean counting at the time. In the 1970's played Star Trek on computer terminals in one building at school (very slow) and would use the teletype machines in water closets to play during long physics classes at the time. (6 hours of lab time). I remember in the 1960's never wanting anything to do with punch card programming. It was tedious. In the 90's went to using an Amiga computer / Toaster and helped a TV station migration over to using the Amiga Toaster for a business / stock reporting program that.
I like your use of the Shelly Uni device. Here was testing a modded Sonoff basic with a few soldered taps to GPIO pins, relay and temperature sensor and customized Tasmota firmware to the garage door. (up and down sensors, button and one temperature sensor). This worked fine with MQTT until last week when I decided to upgrade the firmware. It was a test devices as the current alarm panel is hard wired to the garage door. That said do you think the Shelly Uni device would serve my needs for the garage door (two analog sensors wired to it, button and temperature sensor). Analog sensors are just reed switches on the garage door up and down position, DS18xxx temperature sensor and a open/close button (which is an analog to digital conversion button).
Here too started with the Commodore 64 in the early 1980's. I did have a BBS configured here with a Pet Computer and then tapped in to a phone box outside for multiple phone lines using multiple Ventel modems with a customized hardware modem switcher running on the Commodore. Also had a Kaypro CPM "portable" computer that I used for bean counting at the time. In the 1970's played Star Trek on computer terminals in one building at school (very slow) and would use the teletype machines in water closets to play during long physics classes at the time. (6 hours of lab time). I remember in the 1960's never wanting anything to do with punch card programming. It was tedious. In the 90's went to using an Amiga computer / Toaster and helped a TV station migration over to using the Amiga Toaster for a business / stock reporting program that.
Hi, There is a Chime available for the Ezviz DB1 Ezviz DB1 + Chime
Attachments
Interesting, thanks for the find/share, wonder how they communicate with each other, more so how do they pair. Have not seen any option in their App.
LOL this DB1 gets more and more weird with BI.
Now I noticed if I start video in the ezviz app, the screen splits into three in BI, and shows three images. It has to be reset, then sometimes it goes to a closeup view of the very top portion of the image, necessitating ANOTHER reset on BI.
I really wanted this DB1 to work specifically with BI, but it's really hit and miss. It seems any action in the ezviz app, someone pressing the bell or motion threshold being crossed starts a lockup in BI.
Starting to regret losing the Ring; if no one here knows how to solve this, I don't know who can!
Resetting the BI image every time someone approaches the DB1 is getting to be a real chore.
Now I noticed if I start video in the ezviz app, the screen splits into three in BI, and shows three images. It has to be reset, then sometimes it goes to a closeup view of the very top portion of the image, necessitating ANOTHER reset on BI.
I really wanted this DB1 to work specifically with BI, but it's really hit and miss. It seems any action in the ezviz app, someone pressing the bell or motion threshold being crossed starts a lockup in BI.
Starting to regret losing the Ring; if no one here knows how to solve this, I don't know who can!
Resetting the BI image every time someone approaches the DB1 is getting to be a real chore.
Last edited:
Maybe it relates to BI sending ONVIF commands to the camera at the same time as the EZViz cloud application? Disconnect one or the other and see what happens?
Here do not utilize BI rather utilize RTSP on Zoneminder on Ubuntu Linux.
Looking at the doorbell camera here with the Onvif viewer see all kinds of uneditable ONVIF commands that state mobile at the top.
I have tried to tinker with the ONVIF mobile verbiage even though it is ghosted out and always debends the application in Windows 2016 server.
Here do not utilize BI rather utilize RTSP on Zoneminder on Ubuntu Linux.
Looking at the doorbell camera here with the Onvif viewer see all kinds of uneditable ONVIF commands that state mobile at the top.
I have tried to tinker with the ONVIF mobile verbiage even though it is ghosted out and always debends the application in Windows 2016 server.
THAT did it! You, SIR, are a steely-eyed Missile Man!
Once I disabled onvif in BI (because EZVIZ doesn't support it), everything was fixed.
THANK YOU. You just solved a 10 hour mystery.
Very much appreciated for your suggestion.
Good news. Can you switch BI to using RTSP?
I am playing here with two open board Hikvision cameras. Everytime I change the location of country/china to America/Chicago it changes back to country/china on one of two cameras. The second on is a bit different and it stays in Chicago.
Here is some of the ONVIF code (I think that is what I am seeing) that EZViz is probably using to talk to your Video Doorbell).
Everytime I have tried to edit this stuff the ONVIF program locks up.
I am playing here with two open board Hikvision cameras. Everytime I change the location of country/china to America/Chicago it changes back to country/china on one of two cameras. The second on is a bit different and it stays in Chicago.
Here is some of the ONVIF code (I think that is what I am seeing) that EZViz is probably using to talk to your Video Doorbell).
Everytime I have tried to edit this stuff the ONVIF program locks up.
I bought the unit in early Dec 2019. I installed between Christmas and New Years. I bricked it with the Nelly's FW in Jan or Feb, but revived with a trick I found on here. The video was so yellow, but after thinking I totally hosed the doorbell with the Nelly's FW I put up with the bad video color. In Early March or April I was willing to risk re-flashing to get away from the yellow tint and flashed the Hikvision FW (with zero issues) and the problems with Blue Iris disconnecting started about a month later. When it happens the Guarding Vision app still works, so I know the camera still works. The problem is with the method Blueiris uses to access the video.
Based on my theory the issues is how BlueIris access the video stream, this week I changed my camera type in Blue Iris from DS-2CD6... to "Other RTSP". The streaming path is different, so hoping this might help the reliability. If "Other RTSP" hangs I'll work my way through all of the Hikvision options to see if I find one path that is stable. The top option worked with the RCA and Nelly's FW so I did not change when I went to Hikvision.
I won't feel confident this "fixes" my problem for at least two months. I'll report back what I find.
Guys - Not sure if I just bricked my RCA or not.
After installing with the default RCA Security App, I then upgraded it to the stock latest firmware available successfully before doing anything else.
Then I downloaded the Batch Config, and the HikVision firmware, and hit upgrade.... of which I got the following screen:
However, then I go out to the doorbell, and it's just a constant red led light on the button. Can't connect to the IP address, and can't ping it either. I took it apart, and manually disconnected the battery and it hooked it back up again, and goes right to red led light. There's no SSID or anything being broadcast from it.
Just looks like this.
Is this thing bricked??? What the heck did I do wrong?
After installing with the default RCA Security App, I then upgraded it to the stock latest firmware available successfully before doing anything else.
Then I downloaded the Batch Config, and the HikVision firmware, and hit upgrade.... of which I got the following screen:
However, then I go out to the doorbell, and it's just a constant red led light on the button. Can't connect to the IP address, and can't ping it either. I took it apart, and manually disconnected the battery and it hooked it back up again, and goes right to red led light. There's no SSID or anything being broadcast from it.
Just looks like this.
Is this thing bricked??? What the heck did I do wrong?
Had the same thing happen to me.
After reading through the 101 and various posts I did the following and it recovered.
Turn off power and wait for the red LEDs to go out
disconnect power kit box and chime if connected
remove sd card and format to FAT32
copy the HIK firmware to the card as downloaded
copy the HIK firmware to the card renamed to digicap.dav (so you have 2 files on the card)
reinstall SD card
press and hold reset button
apply power
LEDs will flash once, do not release reset button
continue to hold the reset button until LEDs turn blue and doorbell announces reset successful
This is a combination of various suggestions on here so not sure if all are necessary as I was trying different things as I read them.
The above is the combination I had when it came back to life..
After reading through the 101 and various posts I did the following and it recovered.
Turn off power and wait for the red LEDs to go out
disconnect power kit box and chime if connected
remove sd card and format to FAT32
copy the HIK firmware to the card as downloaded
copy the HIK firmware to the card renamed to digicap.dav (so you have 2 files on the card)
reinstall SD card
press and hold reset button
apply power
LEDs will flash once, do not release reset button
continue to hold the reset button until LEDs turn blue and doorbell announces reset successful
This is a combination of various suggestions on here so not sure if all are necessary as I was trying different things as I read them.
The above is the combination I had when it came back to life..
Last edited:
Just turned around my car from dropping this off to amazon. Am going to try this and will report back shortly!
Good luck
this is another variation that did not work for me
post 4519 by Skinah page 226
ipcamtalk.com
this is another variation that did not work for me
post 4519 by Skinah page 226
New RCA HSDB2A 3MP Doorbell IP Camera
That's not true, I live in Italy, and we have transformers of any kind in use in all houses. Those are limits for your country probably. Thats why I said "all", should say most. Thats why ring provide a transformer for european customers as most, probably not all in europe use 8-12, while in...