amcrest168 wrote: ↑Wed Jan 15, 2020 8:09 pm
hi @Dingdongditch , i think the replacement doorbell struggles to maintain a solid wireless network connection.
doorbell.PNG
I don't doubt it.
when I upgraded my transformer from 10v to 16v, most of the "doorbell is offline" things went away.
I will keep monitoring wifi/pings.
Find the IP of the doorbell and run a ping -t to it
Mine has said "Successfully connected to wifi" at random times and I see that the pings stopped simultaneously, but I haven't had issues in the past couple hour, will continue to monitor the wifi signal.
My doorbell is " 11ng (2.4 GHz) 92% (-54 dBm)" and among 60 clients, it's in the middle in terms of signal quality, will hope it stays connected. so far so good
Attachments
amcrest doorbell disconnecting.PNG (55.02 KiB) Viewed 2621 times
my first doorbell was installed with an existing 16v 10va transformer and it worked fine with the old transformer but recognizing the ad110 is more than a push button to close the circuit and trigger the door chime, i went ahead and upgraded the transformer to a 30va. the doorbell needs more than 10va to ensure it is getting enough current to operate as a wireless networking device. i was a happy camper until i changed the day/night value from auto to color via the amcrest ip config tool. i highly advise everyone not to change doorbell values with legacy amcrest apps.
@kabon360 How did you change the IP settings? I'm struggling to find a WebUI for the doorbell. I need to change the TCP Port so I can access the doorbell on my Amcrest View Pro app from outside the network by way of port forwarding. I have another Amcrest Home App camera (Deterrent Camera) that has defaulted to the same TCP Port and I've reluctantly kept for port forwarding. I can't access any WebUI for that camera either to change the port.
My other IPM/IPVM Cameras all have unique TCP Ports I've created for forwarding purposes.
Might this be because these smart home cameras are meant to be fed through the Amcrest cloud/server and onto the Amcrest Smart Home app? Seems like a big miss if I can't add multiple Smart Home "AC" series cameras to my View Pro App and be able to view them from outside my network.
I also tried logging in via the Amcrest IP Config Tool, but it denies me login to either of my Smart Home cameras!
amcrest168 wrote: ↑Sat Dec 28, 2019 2:45 pm
i think i have stumbled on something fatal. support ticket 323977.
do not make any attempt to change any of the ad110 preset values using the amcrest ip config tool. making any change to the preset values could render the ad110 to go offline and become unresponsive. factory reset button no longer works when ad110 is unresponsive.
I actually had this issue with the first unit I got. After returning it, it went out of stock for awhile on Amazon, then when back in stock it shipped directly from Amcrest with an updated firmware and STRICT instructions to enable the chime kit.
But also when poking around in the settings (because I like to ), I noticed that the camera ip settings default to 192.168.0.108 and static. Obviously I changed these to my correct values to match the static ip i have set up through the router.
My theory is the bricking issue is related to the chime kit regulating power (reset button no longer working). You can find my longer theorizing on my amazon review. But the ip resetting to the above default values might be why it can't connect (flashing blue).
I think they are two separate issues that just happen to coincide...the power regulation resets it and disables the reset button somehow, which then sends the network to the preset 192.168.0.108 settings. Note the .0. subnet, not a lot of routers default to that...most are the .1. subnet.
But like I said, just some armchair theorizing.
Edit - I've not had this bricking issue since the replacement device and upgraded firmware, even though I've played around plenty in the settings.
hi @KingKong and welcome to the forum. i can confirm the doorbell does not have a web ui. i think all the smarthome series cameras use the default tcp port of 37777 and there is no need to setup port forwarding for any smarthome camera when you use the recommended smart home app. be careful with the ip config tool when accessing the doorbell because you can easily brick the doorbell with the ip config tool. neither the doorbell's factory reset button nor the hotspot button works when the doorbell is bricked.
I have my Doorbell On my NVR and works just fine. Not something you want to make many changes over. Infact with all the camera bricking that has been going on after making changes through other apps I only make changes to the doorbell camera over the Smart Home app. I get notices from there and can still access the live view from there. Sadly found 1 thing I don't like so far. Been doing well with Motion however it has snowed really good and now all motion that would normally not be detected is now reflecting off the snow and seen in camera as it is within zone however only today... But had 60 alerts going off this am and woke me up so I muted my phone lol... Other then that it has been working well. Are you able to access the doorbell camera still or you can't access after you make connection to your NVR? You remove from NVR and your able to get Live View? Not sure I understand
hi, about the brick problem.
seems that amcrest should help us with this. its very funny that you can access the doorbell perfectly with the ip config tool but as soon you change in my case the brightness i think it was boom doorebell gone.
cant belive that a factory reset does not fix a issue like this.
have anyone tried contacting them about this, maybe sdcard image and then restet could be possible.
I would venture to guess that if you contact them and tell them your camera is dead as long as it wasn't something you did like take it apart or something like that I would bet they will RMA the one you have and get you another one....
Yes it is odd that things would be left open for changes without protections from Killing the thing... I am going to guess maybe trying to get it to the best it could on the first run without having others test out and brick them before Release... I am going to guess if there was a Way to make a repair after someone Bricks it is going to need a Machine that Amcrest would have but the Normal home owner might not.. Or it might be Toast altogether and will be ewasted either way I am sure you will get a replacement as long as you didn't try and plug in 110v or worse yet 240v to the poor thing..
@Revo2Maxx thanks for the info, so any suggestions regading contacting amcrest?
do i dare to say that i change some silly thing with the config tool or just tell the its broken!
), I noticed that the camera ip settings default to 192.168.0.108 and static. Obviously I changed these to my correct values to match the static ip i have set up through the router.
doorebell gone.