I have not had that issue in the year I been using it but if precise timing on doorbell button push is mission critical you could always monitor the doorbell through other means rather than relying on the AD110 itself or the amcrest app notification.
So when someone presses the doorbell for you, what kind of delay are you typically experiencing? The default polling on REST is all over the place from my experience. Best case, you may get around 5 seconds. In my use case, that’s a bit too long.
I average around 2 doorbell presses a day and if you are getting way more than that then any delay is going to be more obvious for you. For me the majority of the time the notification I have sent to my phone via HA is near instant and never any longer than a couple a seconds for those times it isn’t. It’s lucky timing I suppose but again the amount of presses you get a day will make any random delay more apparent.
In my original post there is a link where they talk about adding the ability to subscribe to the doorbell’s door presses alert subscription so instead of polling for a change the Amcrest integration would just listen for the alert. It’s been a bit since I checked on the progress for that so you may wanna have a look. other than that as I stated above you will have to go with an additional means of detecting the doorbell press outside of amcrest and the doorbell all together which many do do since that is a universal method.
Polling is intermittently slow for me too. Then again, I can’t keep the damn thing online when temps drop below freezing. Amcrest’s support has been completely erratic. Although eventually arriving at my RMA for my first bricked device, they have a problem with various departments not being in sync. RMA not knowing what support is saying and vice versa. They ran me around in circles for nearly a month, asking for the same data over and over and over.
I chose this doorbell partly because it’s an American company, despite the Chinese guts. I’m beginning to consider other options, as this one has been an unreliable hassle. Unfortunately there’s not a lot of doorbells with RTSP available to chose from. Maybe an opportunity for crafting my own?
Sounds like you have a defective unit. I am on my second which is still running the original firmware. They had a real issue where x amount of these units would ship broken out of the box or quit working within days or weeks after installation and these were units people didn’t mess with trying to change settings and then on top of that you had the super buggy firmware where if you had used anything other than the mobile app to change a setting on it would brick the unit near instantly. It was a real mess.
It’s my second one via RMA. I’d say they have a quality problem.
I got tired of waiting for native Home Assistant support so I’ve created a project to expose the Amcrest events (including AD110 doorbell pushes) via MQTT: https://github.com/dchesterton/amcrest2mqtt. It subscribes to the events, doesn’t use polling and works instantly.
If anyone uses it, please let me know how you get on as I’ve only tested it on my AD110 so far.
Nice. Any chance of making an addon version for those running supervised?
I’d be happy to contribute to your coffee fund if an add-on were published. Pending that it’d be nice to see it published to a docker registry for use in portainer.io as an example.
Nice work, none the less.
Thanks Doug, it’s published here: https://hub.docker.com/r/dchesterton/amcrest2mqtt. I don’t use Portainer but you should be able to add that hopefully?
Ironically I’m currently battling a problem with another add-on I’ve created: https://github.com/dchesterton/texecom2mqtt-hassio/issues/10 and I’m very limited on time but I will take a look at creating an add-on from this soon if there’s demand.
You should create your own thread for this project so people can post with suggestions/comments and link to that thread in this one for further discussion.
Like I have it running atm and I have noticed the motion sensor seems to trigger far more than the original amcrest integration so I am not sure if your motion sensor is the pir or motion and if it’s just motion it seems to trigger a lot when there is none. etc
I’ll move this comment to your new thread if you create one.
Deployed on Portainer perfectly. Thanks
Running on Portainer as well gonna try making an Add-On
Thanks! Feel free to send a PR to the repo if you want to include the add-on in there?
Dude! This is exactly what I was looking for. Thank you! Works great in portainer!
Can this addon now trigger an event on HA when pressed om the ring button?
FYI just installed my AD110 today, your MQTT docker works great. Thank-you so much… I have mixed feelings about this doorbell already but at least we can get those commands!
You say you are tired of waiting for official support? what is stopping you from submitting a pull request to add this to HAs mainline code if you were able to build your own solution?
Really good news on this topic! An add-on would be great.
I am not the most advanced user so I need some basic help here. I already have Portainer running on my HA. I added a Container with all required specifications. The container was deployed and it is now running.
What do I have to do next? What do I have to add to my configuration.yaml file to watch the events?
@dchesterton any tips?
Same here, please help us.
Does anyone know what should I do after deploying the container?