-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance warning is always showing on 2023.4.0b5 #267
Comments
Also on 2023.4.1 |
Confirmed, 2023.4.0 |
Also on 2023.4.5 |
Looks like lovelace-card-mod/src/helpers.ts Line 166 in b8c48b9
|
From debugging, I'm seeing roughly the same as you @acshef:
Oddly no |
Still having this issue |
Still seeing this issue |
+1 Home Assistant 2023.9.3 |
+1 |
Is this related to the poor performance as of late? signal-2023-10-16-16-27-50-136.mp4 |
My Home Assistant version:
2023.4.0b5
My lovelace configuration method (GUI or yaml):
gui
What I am doing:
loading tab
What I expected to happen:
Nothing. No bad performance warning in dev console when proper installation procedure is followed
What happened instead:
Performance warning is always shown in dev console
Looks like
function getResources()
fromhelpers.ts
is returning invalid outputMinimal steps to reproduce:
Error messages from the browser console:
![card-mod-performace-warning](https://user-images.githubusercontent.com/570575/229933105-bdc08267-31fb-4b27-884a-3a0dbdc279d8.png)
By putting an X in the boxes ([]) below, I indicate that I:
Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
Have made sure I am using the latest version of the plugin.
Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.
Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.
The text was updated successfully, but these errors were encountered: