Are you using the Amcrest Hub component? And do you often see errors in the log? If so, I found that there is a bug in the code that makes it not thread-safe. I fixed the problem for myself, and added quite a few other features, but unfortunately given everything else going on I haven’t gotten around to feeding this back to the developer(s) of this component.
If you’re interested in what I’ve done, you can look here. Note this is not very well documented since so far I really haven’t shared this work. But you’re more than welcome to try what I did (if you’re comfortable with hand installing custom components.)
Regarding the thread-safety issue, basically the camera doesn’t like when multiple long commands are pending. (This applies to more than just the camera feeds, e.g., background motion detection monitoring, etc.) When you click on the image in the frontend, and you see the larger box open, what’s happening is now you have two views trying to show the same feed (which, by default, is using the camera’s snapshot API command.) The normal view only grabs a new image every 10 seconds, but the larger one tries to grab snapshots as fast as possible. When these two “collide”, the camera responds with errors.
Since there are many ways to configure HA to work with Amcrest cameras, and there are lots of Amcrest models, and lots of different firmware versions, the above discussion may or may not apply in your scenario.