-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Unexpected gap on ha-device-entities-card when no entities are shown #19598
Comments
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
UP |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
PR is pending... |
Checklist
Describe the issue you are experiencing
Large gap between "Sensors" and "+1 entity not shown".
Describe the behavior you expected
Ltitle to no gap.
Steps to reproduce the issue
Browse to device page of device with no sensors available in the panel.
What version of Home Assistant Core has the issue?
core-2024.2.0b0
What was the last working version of Home Assistant Core?
core-2024.1.5
In which browser are you experiencing the issue with?
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 Edg/121.0.0.0
Which operating system are you using to run this browser?
No response
State of relevant entities
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: