Amcrest Camera component streaming only works with aiohttp==1.2

[tchellomello]

Home Assistant release (hass --version):
0.41

Python release (python3 --version):
3.5

Component/platform:
camera/amcrest

Description of problem:
With Home Assistant 0.40/41 the Amcrest camera component streams the data for only 4 or 5 seconds and then freezes. To get it streaming again, a full page refresh is needed and then it works for more 4 or 5 seconds.

Downgrading the aiohttp==1.2 version the Amcrest camera component works as expected and continue streams without any problems.

I'm not sure where to look because the component code remained the same and only the aiohttp version is different.

Note that screenshot images are not affected.

Expected:
Should stream continuously without issues.

Problem-relevant configuration.yaml entries and steps to reproduce:

camera:
  - platform: amcrest
    name: "Amcrest Driveway"
    host: !secret amcrest_driveway_host
    username: !secret amcrest_driveway_user
    password: !secret amcrest_driveway_password
    port: 80
    resolution: low
    stream_source: mjpeg

Traceback (if applicable):
No traceback generated.

Additional info:

17-04-02 01:04:39 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy/camera.amcrest_driveway to 127.0.0.1 (auth: True)
17-04-02 01:04:49 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy/camera.amcrest_driveway to 127.0.0.1 (auth: True)
17-04-02 01:04:59 INFO (MainThread) [homeassistant.components.http] Serving /api/camera_proxy/camera.amcrest_driveway to 127.0.0.1 (auth: True)

Then clicked on image to start streaming and it freezes the image after 4 seconds,
however no traceback is displayed.

Downgrading to aiohttp==1.2 works as expected with any issues.

[tchellomello]

@pvizeli @balloob do you have any idea on how I can troubleshoot this? Since I'm not seeing any traceback I don't know if this is on the frontend side or on the backend/core side.

[cmsimike]

I'm sorry if this doesn't help, but I believe there was a new version if hass released recently that allowed components to install versions of core hass libraries that are different: https://home-assistant.io/blog/2017/03/22/broken-dependencies/

[tchellomello]

@cmsimike Thanks for pointing this out. I've already double checked that. The problem is with the library version. I'm still digging to see what could be the cause of that.

[pvizeli]

Try dev. We upgrade to aiohttp2 that change a lot

[tchellomello]

@pvizeli I'll give a try and let you know

[tchellomello]

@pvizeli Unfortunately it is still happening on dev and 0.42.