home-assistant / frontend

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

Weather card does not render if initially visible #2139

Closed nkaminski closed 5 years ago

nkaminski commented 5 years ago

Home Assistant release with the issue: 0.82.1

Last working Home Assistant release (if known): Not known

Browser and Operating System: Chrome 71.0.3578.62 on Mac OS X 10.14

Description of problem: If the frontend / UI is opened such that the weather card is visible without needing to scroll or change views the weather card fails to render and instead shows as a small blank space (Between the front hall group and vacuum card in my screenshot). Once you navigate to another view and back, the Weather card loads as expected.

Javascript errors shown in the web inspector (if applicable): none shown

Additional information:

screen shot 2018-11-28 at 9 42 34 am
zsarnett commented 5 years ago

Are you sure there are no errors in your Home Assistant Log nor the Console of the Dev tools in your browser?

nkaminski commented 5 years ago

I didn't see anything, but I will reproduce this again and verify.

On November 30, 2018 12:19:22 PM CST, Zack Arnett notifications@github.com wrote:

Are you sure there are no errors in your Home Assistant Log nor the Console of the Dev tools in your browser?

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/home-assistant/home-assistant-polymer/issues/2139#issuecomment-443292643

-- Sent from my Android device with K-9 Mail.

nkaminski commented 5 years ago

No errors or warnings in JS console, HA log is also free of errors.

nkaminski commented 5 years ago

After updating to 0.84.1, this now results in the following error in the log when this occurs:

Log Details (ERROR) Wed Dec 12 2018 20:54:10 GMT-0600 (Central Standard Time)

https://localhost/frontend_latest/bf7146608f595468a214.chunk.js:3157:1377 Uncaught TypeError: Cannot read property 'name' of undefined

iantrich commented 5 years ago

@nkaminski can you share your relevant configuration?

nkaminski commented 5 years ago

Sure, my config is quite involved so I will setup a dev instance within the next day or two and see if I can isolate what specifically triggers this and share.

In the mean time, the config for the impacted weather card (darksky) is:

weather:
  - platform: darksky
    api_key: !secret darksky_api_key

and impacted camera card:

- platform: mjpeg
    name: Frontyard Camera
    mjpeg_url: http://videoserverpi:8080/?action=stream

The weather card is in the default view:

default_view:
   view: yes
   name: Main
   entities:
      - sun.sun
      - weather.dark_sky
      - device_tracker.devicea
      - device_tracker.deviceb
      - device_tracker.devicec
      - group.climate
      - group.recroom
      - group.livingroom
      - group.fronthall
      - binary_sensor.garage_door
      - binary_sensor.leak_sensor_1
      - binary_sensor.leak_sensor_2
      - binary_sensor.rec_room_motion
      - binary_sensor.front_hall_motion
      - vacuum.roomba
      - alert.garage_door

and the camera card is in another separate view:

holiday_decor:
   name: Holiday Decor
   view: yes
   entities:
      - camera.frontyard_camera
      - group.outdoor_holiday_decor
      - group.light_show_equipment

The video source of this camera is mjpg-streamer running on an RPi3. Connectivity between this Pi and and HA server is all wired as well.

Also 2 other observations regarding this:

bastshoes commented 5 years ago

Have same issue. Weather card is not shows in UI. Opened issue #2297

Queuecumber commented 5 years ago

I'm also having this issue, but it seems to be the camera and weather card. If I resize the window to make it really small and then scroll down and back up, the card shows. Only error I have in console is

Uncaught (in promise) TypeError: Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script.
iantrich commented 5 years ago

Anyone still having this issue?

iantrich commented 5 years ago

Closing as no response in 3 weeks