You have a sensor that is not providing a reading to the card I reckon. Try a simplified setup without adding custom sensors
There seems to be a bug in weather chart card. If I select to display time, the CPU usage starts to grow slowly, but constantly. Does not matter if I use FireFox or Vivaldi. If time is not displayed, everything is OK.
I am not an expert in JavaScript, but it seems to me, that the error is at the end of the function renderMain():
updateClock();
if (showTime) {
setInterval(updateClock, 1000);
}
If I understand correctly, setInterval() creates a timer, which periodically calls updateClock(), so with each call to renderMain() a new timer is created, which starts to call updateClock().
If I am right, may be some expert can fix this?
Great work!
I just installed this component and really like it.
If I may here are some observations/wishes
- having a horisontal grid with banding, see example from dmi.dk below, could provide a more instant overview without having to read digits
- then showing the digits could be made optional
- showing the date or time header could be made optional, or at least to omit “:00” in each hour
- there could then be an alternative to have the weather icon there instead
- an alternative configuration to show a wind speed diagram having the direction icon where the temperature number is now
- the windspeed data is ovewflowing when
type: hourlyis used andnumber_of_forecastsis >10
A wind speed mock up for the next 12 hours.
The current way I set it up showing how the wind speed overflow to the right when having more than 10 hours selected.
@parolx
Even when not having the time or date explicitly displayed there are calls to updateClock().
The timeline is on hour and date basis so it should be enough to redraw the card at the start of each hour, or at the start of the day if that’s the finest granularity in use.
I was not allowed to add this remark in a new reply due to some “max 3 replies for new users” limitation.
How dmi.dk utilise banding to and a vertical axis to avoid having to show digits.
… and their wind speed chart.
The memory leak with the Time display is significant. I recently added this card (with time display of hours+minutes+seconds) to my wall-mounted iPad kiosk running the Home Assistant app and within a few hours the app was frozen and non-responsive. After restarting it over and over for a couple days I found this thread and an existing bug report on github, so I removed the time display and now it’s working fine. I’m currently testing out a proposed fix someone provided in the Github issue to see if that resolves it.
I have always had the time display (hours+minutes) I have never noticed a problem with the memory leak, my dashboards to auto refresh every 20mins though. I will check this out on Git


