For some reason after enabling SSL to my domain using Let’s Encrypt, the Amcrest previews showing up in my dashboard start going on and off. My setup is a Mikrotik router and all is in the same subnet. I can access the cameras by IP and the previews appear and work every once in a while, but other times they appear as if you had no permission to access the camera. (Offline)
Anyone has any ideas?
Logger: homeassistant.components.amcrest
Source: components/amcrest/init.py:261
Integration: Amcrest (documentation, issues)
First occurred: 11:44:08 PM (10 occurrences)
Last logged: 11:44:10 PM
Error while processing events from Garage camera: CommError(HTTPStatusError(“Client error ‘400 Bad Request’ for url ‘192.168.88.121/cgi-bin/eventManager.cgi?action=attach&codes=[All]’\nFor more information check: httpstatuses.com/400”))
Error while processing events from Patio camera: CommError(HTTPStatusError(“Client error ‘400 Bad Request’ for url ‘192.168.88.122/cgi-bin/eventManager.cgi?action=attach&codes=[All]’\nFor more information check: httpstatuses.com/400”))
I think your SSL/Let’s Encrypt concern is just a coincidence.
The issue started with the latest updates to the Amcrest integration. Very frustrating.
Two of my five cameras are going on/offline every few minutes as well.
The issue is documented here: https://github.com/home-assistant/core/issues/68272
Specifically, this entry: https://github.com/home-assistant/core/issues/68272#issuecomment-1073114514
As of Home Assistant 2022.3.7, the issue is still there.
Feel free to add your comments and let’s hope for a prompt resolution.
Thank you for sharing that @Zoriontsu , I downgraded back to 2022.3.4 and that resolved the issue for the time being. Hopefully they fix it soon.
Hi there, being on the same boat with 5 dahua cameras and having discovered this Change Amcrest event monitor to non-async by flacjacket · Pull Request #69640 · home-assistant/core · GitHub I was wondering if anyone of you has an idea about when this will be fixed? Thank you
I think I have to add another issue: after having downgraded to 2022.3.4, as mentioned by microalpha, I discovered that sometimes the motion detection of all amcrest (dahua) cameras stop working (btw with no issues reported in the logs) and to have them working again I have to restart Home Asssistant. Will this be related to the same “bug”?
My bad, there are in fact errors (HA 2022.3.4) in the logs preceeding the motion detection interruption, they are a bit confusing and relate to a generic attribute CommError or ERRORTYPE_111, Connection refused. After that the video stream carries on with no issues (I feed Frigate with it) but the motion detection stops until I restart HA. I will try now with the latest HA release …
Well, it looks like this fix is going nowhere.
I need a WiFi camera for my front driveway due to distance. POE won’t work for me.
Last week I purchased and returned an ASH43-W. It was awful and did not work with HA.
QUESTION:
Is anyone using a WiFi Amcrest camera reliably with the latest HA version (2022.4.X +) ???
Yes.
- Create a generic camera following these steps using the RTSP URL
Generic Camera - Home Assistant - (Optional) Add RTSP to WebRTC to improve lag
RTSPtoWebRTC - Home Assistant
Thanks for the reply!.
I tried using the generic camera approach in the past without much success.
My challenge is that I am less concerned with streaming video, and more interested in object recognition. In this particular case, I have a camera in from of my gate, and upon motion detected by the camera, I use Deepstack to identify the object. I am able to identify a delivery vehicle (UPS, FedEx, etc) and open the gate automatically. It also alerts me if a human is lurking by my front gate and announces via Google cast.
If I remember correctly, the generic camera lacks a motion sensor.
That is why I went the Amcrest integration route. Has anything change with the generic camera?
Thanks.
Ahhh understood.
For object detection I’ve been using Frigate nearly since inception. It’s fantastic and there is a huge thread on it, link to documentation below.