[about Customizing entities tab in configuration]
Release notes mention a revamp. I was not aware that revamp remove functionnality.
It’s a strange situation now because change made previously can’t be edited.
I don’t find a way to re-customize entities that I touched earlier.
Why this has been removed ?
To have had this option in the UI previously, you must have included a customize: section in your main config.yaml at some point. It’s common practice to put an !include here to keep all customisations in a separate file e.g. !include customize.yaml
I think any customisations you made should be saved there (not 100% sure on this to be honest), but you should be able to edit this file for future customisations. Full documentation here. [This would only apply to entities without a unique id that you can’t already change through the UI.]
Well duh, but the docs didn’t say anything about unsupported. I was trying to clarify if the device had an error mid way through the process and resulted in the word unsupported in the UI. Turns out I was right on that bit.
Because customizations are implemented on the entity now and everything is moving that direction. The customize UI was a temporary solution a number of years back, the temporary solutions time ran out. You can still customize entities by going to the entity in the entities page. If you need to customize a yaml entity (Entity without a unique_id) then you need to customize it in Yaml.
Check the supervisor logs. Is your system healthy?
Thank you petro for the information. If I can continue to use and doing change into customize.yaml, it’s fine. What I don’t see is a way in entity to change the device class in your new implementation which is sometime not as desire by default.
Thank you reste_narquois,
Indeed, It’s in the file customize.yaml. Thank you to have remember this.
It’s not my implementation. I’m just a moderator.
device_class should be set by your integration. If it’s not, add a feature request for it, otherwise customize it in custimize.yaml.
[solved]
I tried it without a backup bevor the update and this time it worked!
So everything fine atm
Hello mcarty,
this is my supervisor log. I can´t see any problems.
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-12-14 10:50:38 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-12-14 10:51:54 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-12-14 10:52:22 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-12-14 10:53:24 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository-edge repository
21-12-14 10:53:24 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
21-12-14 10:53:24 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/thomasmauerer/hassio-addons repository
21-12-14 10:53:24 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/sabeechen/hassio-google-drive-backup repository
21-12-14 10:53:24 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
21-12-14 10:53:24 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/maxlyth/hassio-addons repository
21-12-14 10:53:29 INFO (MainThread) [supervisor.store] Loading add-ons from store: 108 all - 0 new - 0 remove
21-12-14 10:53:29 INFO (MainThread) [supervisor.store] Loading add-ons from store: 108 all - 0 new - 0 remove
21-12-14 11:18:39 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
21-12-14 11:18:39 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
21-12-14 11:22:23 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-12-14 11:45:25 INFO (MainThread) [supervisor.host.info] Updating local host information
21-12-14 11:45:25 INFO (MainThread) [supervisor.host.services] Updating service information
21-12-14 11:45:25 INFO (MainThread) [supervisor.host.network] Updating local network information
21-12-14 11:45:25 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-12-14 11:45:25 INFO (MainThread) [supervisor.host.manager] Host information reload completed
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-12-14 11:50:38 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-12-14 11:52:23 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-12-14 12:18:41 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
21-12-14 12:18:41 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
21-12-14 12:22:24 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-12-14 12:50:38 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-12-14 12:51:54 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-12-14 12:52:24 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-12-14 13:18:44 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
21-12-14 13:18:44 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
21-12-14 13:22:25 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
Thank you for you help,
I removed all components prior to your post, and then it upgraded even though it said
ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /core/update request Server disconnected
ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /core/update -
To my surprise it was upgraded, and then I re-added all my components.
Good to know that it was a matter of alexa_media this should help many others as that components is quite commonly used.
You realize you can click anywhere on the set state title bar right? This is normal UX behavior with collapse/expand tabs. It’s just not apparent because of the theme you’re using. Just click on the phrase set state and it will expand.
not sure why you are saying this has anything to do with my theme:
this is default theme.
If this is normal behavior, we should adapt it. Maybe on mobile this is ok-ish (then again, we don’t see attributes on mobile at all, so this page is useless on mobile anyways, hardly the device to develop the page design for imho.)
If clicking the ‘Set state’ would need the user focus, the text could be more intuitive. Currently, and coming from the previous design, this only leaves the user wondering and without a clue what the ‘Set state’ does. there’s simply no visual feedback or suggestion for it
I created an issue on home-assistant/frontend GitHub page:
Are you sure the property wasn’t changed? Theme variables get changed frequently. Comparing results to mini-graph-card won’t get you anywhere because the card is custom.
Why didnt You added button as helpers in gui?
If/When buttons get implemented as a helper, it will be an input_button. You can make a feature request to make that happen if it’s not already in the works.
It might be worth noting that in your issue then. “Hey change the theme to make that look like an expandable box with the built-in themes”
EDIT: Like the attributes box on entities more info page.
cool, edited the post per your suggestions FR: move dropdown arrow next to "set state" · Discussion #10915 · home-assistant/frontend · GitHub
button is a platform like number and select. It’s meant to be implemented by other integrations. For example, the MQTT integration implements button, number, select and others.
Having said that, I agree that a button-like Helper (input_button) would probably make it more accessible for most users. Creating a button via MQTT requires a bit more effort than creating a Helper via the UI.
Pressing an input_button would generate a custom event that could be detected by an Event Trigger.
