Apologies, see my correction above.
Ok, no problem! 
Same issue - blank screen - visibile for a second - then blank.
Same on Android.
Tried setting theme to default - still shows blank.
Using -
type: custom:home-feed-card
Custom Components not loading
I only use one weinstein thermosmart. Hacs is working
What is a weinstein thermostat?
what’s on your homepage? sometimes a custom resource not functioning properly blocks the whole view from appearing (had that with air-visual card and dark sky weather card before).
1 Like
Have you checked there are no updates to the custom integration?
Custom integrations now require version in the manifest file otherwise they wont load. check if they have updated to integration or add it yourself manually
Some entities provide quite a few attributes and those show up in the user interface. Most of the time, you don’t need to those and often contain technical data that only confuse or clutter.
How about the “some of the time” when we do need those? I get it that you’re trying to streamline the UI but a lot of these changes that are being made would benefit from being options. Let me enable full attribute view for the entities I want.
2 Likes
Click a button, then you see them.
no not all, several ‘internal’ attributes are hidden from the frontend, you need to go to developer-tools/state to see all attributes, see frontend/hass-attributes-util.ts at 7bc27082595f943d15ca35ae948c766184a93eed · home-assistant/frontend · GitHub
Yes
~{
“domain”: “smartir”,
“name”: “SmartIR”,
“documentation”: “GitHub - smartHomeHub/SmartIR: Integration for Home Assistant to control climate, TV and fan devices via IR/RF controllers (Broadlink, Xiaomi, MQTT, LOOKin, ESPHome)”,
“dependencies”: [],
“codeowners”: ["@smartHomeHub"],
“requirements”: [“aiofiles==0.6.0”],
“homeassistant”: “0.115.0”,
“updater”: {
“version”: “1.16.0”,
“releaseNotes”: “-- Adds support for swing mode”,
“files”: [
“init.py”,
“climate.py”,
“media_player.py”,
“fan.py”,
“controller.py”,
“manifest.json”,
“services.yaml”
]
}
}~
Official windows is only supported over WSL2 and if you follow the official way, you would not have an issue.
2 Likes
There might be misunderstanding here.
HA has internally two variables: Preferred light theme and preferred dark theme. The values of those will be used whenever the user has chosen “Backend-selected” as their theme (which is the default selection if a user logs in).
If the user is on a browser that requests dark mode from HA, then the preferred dark theme will be used.
With the service call from your screenshot you tell HA that theme “default” should be set as the preferred dark theme. If however, the user is on a device that is set to request the light mode (again controlled by the browser), then the preferred light theme will be used (which is also “default” unless you changed that via the service call).
With the service call you cannot override the browser mode selection.
HI Philip,
wondering about sun.sun now, as I’ve just discovered that the frontend shows several attributes after all, (and not in the dropdown box as is expected now), but added to that, doesn’t show a lot of attributes that are available, but aren’t listed in the filter list at all?
1 Like
Well, for the “some of the time” they are still there and only a single click away. We did not remove them.
Sun has a dedicated “more-info” layout (as do many other entity types), that shows some selected attributes that are central to the entity. We did not touch those layouts.
ok thanks, missed that during the beta cycle. sorry.
What’s wrong with having the option to always show them? “It’s only one click” adds up if you’re looking several entities attributes often.
Thanks - no updates on custom integrations so far - will check back in a few hours. Not an issue for now and can roll back. Just providing feedback, in case others are having the same issue.
Unable to determine a root cause yet.
Thank you.
guess you missed my question… to be able to help you, it would be helpful if you show what is used on your home view. A custom integration can have no updates, but that might very well be the reason it now is not showing Also, if you see any issues in the inspector log