home-assistant / frontend

:lollipop: Frontend for Home Assistant
https://demo.home-assistant.io
Other
4.01k stars 2.74k forks source link

Nest Camera Streaming Not Working in 0.81.0 #1990

Closed ghost closed 5 years ago

ghost commented 5 years ago

@mtl010957 commented on Oct 27, 2018, 11:21 PM UTC:

Home Assistant release with the issue: 0.81.0

Last working Home Assistant release (if known): 0.80.3

Operating environment (Hass.io/Docker/Windows/etc.): Raspbian Stretch

Component/platform: Nest Cameras

Description of problem: Nest camera streams are not displaying in the camera cards on the frontend as they should, the cards are just minimal size and gray.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

nest:
  client_id: !secret nest_client_id
  client_secret: !secret nest_client_secret

Traceback (if applicable):

No errors or warnings were written to the log to indicate a problem with the Nest component

Additional information: Was working fine in 0.80.3 before upgrade to 0.81.0. Reverted to 0.80.3 and the cameras are working again.

This issue was moved by cgarwood from home-assistant/home-assistant#17899.

ghost commented 5 years ago

@mtl010957 commented on Oct 28, 2018, 2:52 PM UTC:

This problem appears to be fixed in 0.81.1, closing issue.

ghost commented 5 years ago

@mtl010957 commented on Oct 28, 2018, 5:59 PM UTC:

Unfortunately my earlier test was not completely valid. After reboot of the Pi the problem is still present in 0.81.1, so I am reopening this issue.

ghost commented 5 years ago

@edif30 commented on Oct 28, 2018, 10:39 PM UTC:

what level of logging do you have enabled?

ghost commented 5 years ago

@mtl010957 commented on Oct 29, 2018, 2:16 AM UTC:

Just the default logging at this point, please let me know what to add to the configuration.yaml and I'll send whatever logs will help.

ghost commented 5 years ago

@matthewkrivanek commented on Oct 29, 2018, 11:45 AM UTC:

Having the same issue. No devices are syncing for me with Nest in 0.81.0

ghost commented 5 years ago

@mtl010957 commented on Oct 30, 2018, 1:42 AM UTC:

I've done a bit more testing and I'm finding that the problem is intermittent, apparently caused by some timing condition during the startup process. I waited about five minutes between the shutdown for upgrade from 0.80.3 and starting up after the upgrade to 0.81.1 and it worked fine. I've set the logging for nest to debug by adding this line in configuration.yaml after the logs: line nest: debug I've attached the output from the logging of a successful startup here in case it helps. good_startup_home-assistant.log

ghost commented 5 years ago

@martikainen87 commented on Oct 30, 2018, 10:52 AM UTC:

I have the same issue with 0.81.0 and 0.81.1

Using 7 cameras from zoneminder, and 2 regular MJPEG cameras.

Just downgraded to 0.80.3 and things are working again, here's an example of what it looks like on 0.81.1

unknown

ghost commented 5 years ago

@Mariusthvdb commented on Oct 30, 2018, 10:56 AM UTC:

not only Nest camera's: https://community.home-assistant.io/t/wheather-on-0-81-0-dev0-0-81-1-shows-camera-as-switch/75915 using camera: generic

ghost commented 5 years ago

@bratanon commented on Nov 2, 2018, 11:56 PM UTC:

Same issue for me with other cameras.

ghost commented 5 years ago

@cgarwood commented on Nov 5, 2018, 3:23 PM UTC:

Seems like a frontend issue, moving it to the frontend repo. /move to home-assistant/home-assistant-polymer

iantrich commented 5 years ago

@mtl010957 Can you share your relevant ui-lovelace.yaml

mtl010957 commented 5 years ago

Yes, here's the relevant section, this renders a tab called Desert with just these two Nest cameras, I also show the same cards in a couple of other tabs with the same definitions:

  - id: 9  # Automatically created id
    title: Desert
    cards:
      - id: 2b060805fc4b4a339837ed995d2f6fe2  # Automatically created id
        type: picture-entity
        title: Living Room
        entity: camera.living_room
        camera_image: camera.living_room
        show_info: true
        tap_action: dialog
      - id: 06fe2e0cb4fa4b76b2d5a7b4e5b2c377  # Automatically created id
        type: picture-entity
        title: Front Yard (Front Porch)
        entity: camera.front_yard_front_porch
        camera_image: camera.front_yard_front_porch
        show_info: true
        tap_action: dialog
iantrich commented 5 years ago

So the picture-entity card is displaying a sensor entity row instead or did you add the sensory entity as well, because that would be really confusing.

I'll have to play around with this tonight in dev, unless someone beats me to it.

iantrich commented 5 years ago

@mtl010957 Can you trying putting these in a picture-glance and picture-elements cards as well to see if they are broken there too. They all use the common hui-image element to display the camera source.

- type: picture-glance
  camera_image: camera.living_room
  entities:
    - camera.living_room
- type: picture-elements
  image: https://upload.wikimedia.org/wikipedia/commons/6/68/Solid_black.png
  elements:
    - type: image
      entity: camera.living_room
      camera_image: camera.living_room
      style:
        top: 5%
        left: 10%
bratanon commented 5 years ago

just a notice, this is not only a lovelace issue. I'm using the "old" UI and have the same issue.

ricain59 commented 5 years ago

I used old UI and i have same issue.

iantrich commented 5 years ago

Anyone here using custom_ui? This smells like the same issue as described here: https://github.com/home-assistant/home-assistant-polymer/issues/1991

mtl010957 commented 5 years ago

@iantrich I am not using any custom_ui, just stock Lovelace. I did also see the same behaviour with the "old" ui as the others have mentioned. The intermittent nature of the problem is maddening. I've updated to 0.82.0b2 and the problem seems to have gone away, but I'll try your picture-glance and picture-elements cards and report back if they make any difference.

mtl010957 commented 5 years ago

@iantrich I have tested the picture-glance and picture-elements cards per your suggestion and they are both working fine in 0.82.0b2. I'll need to keep testing to see if there is any way to reproduce the problem but for now it seems to be fixed.