New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amcrest reports 1000s of errors in log after update to 2022.3.5 #68272
Comments
amcrest documentation |
Hey there @flacjacket, mind taking a look at this issue as it has been labeled with an integration ( |
I started digging into this. I found that my old Amcrest had firmware upgrade since I checked two years ago. Also also removed the - sdcard from the config for the Living Room camera. I still have problems but it is new errors. I am now trying the different ways to stream to see what works best. But the error has changed. The camera works but not stable. |
I have tried snapshot, mjpeg, and rtsp. All the same result. I also lowered the frame rate from 25 to 5 and changed the bit stream to 2 Mbit. I have a software on my iPad streaming the rtsp stream from same camera without a problem. I get the log flooded with
|
Last update (for today). The low frame rate made it worse. I put it back to 25 fps but with 2Mbit frame rate and I changed to VBR. I now get the error in the log every minute when I look at the stream. PTZ works which is the most important for me. I also change the picture entity card that shows the camera from camera_view auto to live. That seems to also lower the number of errors but rise the load on the link when viewing that tab of Lovelace. I forgot to say that the camera is IP2M-841W and it is wired, not wifi. |
Well the fixes in 2022.3.5 fixed the amcrest issues I had where the binary sensors would get stuck in a state and never update until a HA restart. I do see the errors here but nowhere near the same amount of errors. Maybe 20-30 per day per camera. I have several IP2M-841W and a couple IP4M-1051 all on wifi. |
What exact firmware version? And can you share your yaml config? |
IP4M-1051 - V2.620.00AC000.3.R, Build Date: 2019-08-03 example of one camera:
|
Same here, I think my issues started on the 2022.3.1 release. I haven't changed anything on my camera and the firmware has been at V2.420.AC01.3.R, 6/2/18, for quite some time. The camera initially works on home assistant start, then the stream goes to unavailable and the camera is unusable (in home assistant). Works fine thru motion eye. Camera model number: ip2m-853ew yaml:
I have tried swapping to snapshot as my stream source as well. No luck. |
The same for me. Before 2022.3.1 amcrest integration was working fine. Occasional connection errors were, well, occasional and did not result in dropped streams or other camera functionalities not being available through HA. I have three IP3M-941B cameras at 2.520.AC00.18.R firmware.
My error log is showing:
Hope this will get resolved soon. Thanks! |
I have 4 Amcrest Cameras, 3 of which I am running through the HA Integration. They are: Amcrest IP8M-2493EW-V2 The 4th camera is an AD410 doorbell which I'm running the Dahua integration as it has support for the doorbell functions. I am not experiencing the issues you outlined with the Amcrest integration - the logs are clear. I'm not sure how helpful this comment is other then to provide a configuration that is working. My config is: amcrest:
|
@drewancil Just out of curiosity what firmware versions are you running on your cameras? |
2493 - V2.800.00AC001.0.R, Build Date: 2021-07-12 |
My problem camera has firmware V2.420.AC00.18.R, Build Date: 2020-03-30 |
Similar issue here. Two out of my five Amcrest cameras are reporting thousands or errors, and are offline now (in HA). |
Just updated my HA to 2022.3.5 (from 2021.12.x) and I too am seeing the same errors as everyone else for my 2 Amcrest cameras. Everything was great before the update. |
So when we moved the integration to use async methods, we needed to change the underlying library from requests to httpx. This change affected streaming from the cameras (which is how the non-polling sensors listen for events) as when the camera would disconnect and reconnect, there would not be an error that would force us to reconnect (see #66661 for example). We added a read timeout which would be handled and cause a re-connection, but it seems like that isn't a robust solution for all amcrest cameras. It may be best to change back the synchronous requests at least for waiting for events until we can figure out a better streaming solution. I'm not sure how aiohttp handles this, but we need them to support digest authentication, which has an open issue there. We may also want to reach out to httpx for a fix on the library side to let us raise an error that we can handle when the camera is disconnected. |
Having same issue with Amcrest camera IP4M-1026B, downgraded to 2022.3.4 for the time being until a new patch is issued. |
Same issue here with multiple IP2M-841B cameras. |
Other than staying on 2022.3.4, are there any plans to address this? I haven't noticed any related entries in the [2022.4.] pre-releases. |
I have a draft fix up at #69640, but I haven't had a chance to actually test anything out with that, I should be able to get to that this weekend. |
The problem
After upgrade to 2022.3.5 which contained several updates to the Amcrest code my error log is flooded with errors related to Amcrest
The cameras are not very new and there has always been an occational glitch that fixed itself with 10-15 lines of warnings.
The CommError(HTTPStatusError("Client error '400 Bad Request' for url 'http://192.168.1.61/cgi-bin/eventManager.cgi?action=attach&codes=[All]'\nFor more information check: https://httpstatuses.com/400")) is new.
What version of Home Assistant Core has the issue?
core-2022.3.5
What was the last working version of Home Assistant Core?
core-2022.3.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Amcrest
Link to integration documentation on our website
https://www.home-assistant.io/integrations/amcrest/
Diagnostics information
A sniplet from the log
It just continues like that with 1000s of lines - just for half a day
Occationally this variation is seen
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
UPDATE: Please read my comments below. The errors changed after a firmware upgrade of the camera but things are still not really good
The text was updated successfully, but these errors were encountered: