GaryOkie
Pulling my weight
There's a date printed on the box. BTW- what firmware version is shipping with these new RMA units?I know this is probably somewhere in the thread, but how do we find the manufacturing date?
There's a date printed on the box. BTW- what firmware version is shipping with these new RMA units?I know this is probably somewhere in the thread, but how do we find the manufacturing date?
FWIW, The page isn't actually blank. It looks like a potentially functional page but it attempts to load a couple of files (merge.js and a merge.css) that it can't find. I haven't found a way around that... yet.
There's a date printed on the box. BTW- what firmware version is shipping with these new RMA units?
Hi @F1rby - thanks for the mention, and happy to see many posts here were helpful.
When you install the AD410 with the SmartHome app, you choose between no chime or a digital or mechanical chime. The latter 2 options require you install the chime kit first, as if you don't, you can fry your doorbell's 24VAC circuit. Once installed, the SmartHome app does NOT have an option to turn off the external chime - you can only toggle between digital or mechanical chime. I assume this is because if you could select "no external chime " it can't bypass the chime circuit if it actually exists.
There are CGI/firmware configuration settings related to the external chime:
ExternalDoorBell.Enable=true
ExternalDoorBell.Time=3 (digital time delay)
ExternalDoorBell.Type=1 (1=mechanical, 2=digital)
I went ahead and tried <ip_addr>/cgi-bin/configManager.cgi?action=setConfig&ExternalDoorBell.Enable=false which was accepted, but the external chime still clanged its ding donger. It actually makes sense to me now why software can't control it.
Since you are using Home Assistant you should consider using voice or doorbell ring sound broadcasts to smart speakers when the doorbell is pushed based on whatever schedule you want, and just physically disconnect the external chime. This can also be accompanied by streaming video as to who is at the front door to various displays in the house.
You will still get push notifications (if enabled) regardless of the chime settings.
I didn’t get any RMA units yet. I have 5/22 and 6/22, both have issues.
@remlemasi - That's the original version of firmware and it works fine. There was a corrupt manual update a few months back that broke event handling for any 3rd party integrations (like Home Assistant). This update has been replaced by a new version that fixes this, and is only available on the Amcrest firmware download page. The change log for this latest version is sparse - just says the event bug was fixed and there is a new continuous SD recording option.
BTW - the SmartHome app continues to state that 210220 is the latest version.
Well, I don't know of any new issues- because I haven't seen any user experience reports yet with this new version. Since it includes a new feature you want, I think it's OK to proceed with the update. You can always go back if you find some new problem.If I do want to take advantage of the continuous SD recording, any downsides to upgrading?
There is no known way to enable the web UI and it's very unlikely there can be. You can manipulate the configuration via the HTTP API and other software (DMSS, ipconfigtool, NVR). Using software other than that written for the doorbell (SmartHome for the ADxxx) can sometimes cause unwanted side effects, particularly with video settings - requiring a factory default refresh.
Yes, I am. The 2 way audio from DS cam doesn't work for me, however.Hi all. Is anyone using this doorbell cam with Synology Surveillance Station AND using Surveillance Station for the doorbell calls/intercom? It seems configurable for this, but by time I get DS Cam (the Synology iPhone app) open, the person at the door would probably be long gone. Thanks!
Yes, I am. The 2 way audio from DS cam doesn't work for me, however.
Also FYI, DS Cam on iOS loads significantly faster when using IPV6 for some reason. I can open the app, login, and load 5 cams in about 4s when I'm on wifi. Definitely try logging in using your Synology's IPV6 address instead of the normal IPv4.