Amcrest Smart Home "Server" down?

[amcrest168]

hmm... just be careful because it's not fun bricking the doorbell. it's not something one can easily jtag or use an usb ttl cable to resurrect the doorbell from the dead.

[tgfarrell]

@GaryOkie Nice, thanks.

[Dan87]

Below is the response I received from support. No mention of any ETA still. This firmware update really messed these up it seems like. :/

"There is an issue occurring with the server from what I understand and it is affecting a majority of our customers who have updated to the latest firmware. The issue is currently under investigation and our R&D team is working on resolving the issue. I apologize for the inconvenience. "

[srags]

@amcrest168 any update on this issue? The tech support engineer yesterday stated that the server issue was going to be resolved last night.

[amcrest168]

sorry @srags, i'm in the dark just like everybody else--no eta. my suggestion to all is to stay put because using any other app other than the smart home app could potentially brick the doorbell.

[jdefuria]

When I called, they said you have to speak with the Smart Home Team, which can only be reached via the form on this page: https://amcrest.com/smarthomesupport. I filed a ticket and am hoping for a callback.

[Dan87]

When I called, they said you have to speak with the Smart Home Team, which can only be reached via the form on this page: https://amcrest.com/smarthomesupport. I filed a ticket and am hoping for a callback.

That's who I opened a ticket with with my reply above. No ETA. Just stated it's a wide-spread issue.

[moedot]

Finally got mine to connect. Had to do a hard reset. Make sure you get it enough time to fully complete. It was able to connect with no issues after that. I'm on Android and am still on firmware .200509. Good luck.

[djsteve]

Finally got mine to connect. Had to do a hard reset. Make sure you get it enough time to fully complete. It was able to connect with no issues after that. I'm on Android and am still on firmware .200509. Good luck.

Thank you. I can confirm that this has worked for me also - my AD110 is now communicating with Amcrest Cloud again after a 5+ day downtime, sadly via a fix discovered and conveyed by other users rather than from Amcrest themselves. A hard reset is not ideal and requires reconfiguration of all settings, but at least it works. iOS, firmware 200509.

I saw a previous post that said they heard directly from an Amcrest technician that they weren’t sure it would be fixed over the weekend because they “had the weekend off.” This is UNACCEPTABLE for a security product from an security provider. Worse still, it is currently Tuesday night and not a single official notification/apology or ETA has been provided.

THANK YOU to the forum users - we are lucky to have each other as we attempt to make this product work despite the best efforts of Amcrest

[amcrest168]

hmm...sounds like it was a botched firmware update but i find it interesting the doorbell stayed connected to the cloud for about a week post firmware update before the doorbell decided not to play nice with the smart home server on thursday night. did amcrest make any change or update its smart home server on thursday night? a change must have been introduced on thursday night. without any proactive communication or an official announcement, any hypothesis is simply a guess.