core: Amcrest Camera Component Retrying ConnectionTimeoutError Repeatedly in Logs
Home Assistant release with the issue:
0.84.6
Last working Home Assistant release (if known):
?
Operating environment (Hass.io/Docker/Windows/etc.):
Docker on Synology NAS, Amcrest IP3M-HX2
Component/platform:
https://www.home-assistant.io/components/camera.amcrest/
Description of problem:
My 4 Amcrest Cameras are generating Retrying ConnectionTimeoutError enteries in my logs every minute. The camera feed appears to work, however it disappears after a few seconds if I click into the image. Noticed this as an issue when I moved to MySQL for recorder. Here’s the log details:
Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f727c0e3c18>, ‘Connection to 10.0.0.184 timed out. (connect timeout=3.0)’)’: /cgi-bin/storageDevice.cgi?action=getDeviceAllInfo
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
camera:
- platform: amcrest
Traceback (if applicable):
Additional information: I’m testing ffmpeg, Synology Surveillance Station, Zoneminder, and Shinobi as alternatives to provide camera feeds into my frontend.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 15 (8 by maintainers)
There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
I’ll be very interested in seeing this too. Months ago I tried to take a shot at fixing it, but found the learning curve a bit too steep, and abandoned the effort. Thank you, Phil for doing this.