Closed igorsantos07 closed 2 months ago
Make sure you have read the issue guidelines and that you filled out the entire template.
If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a :+1: reaction to the issue description. Thanks! :+1:
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4959 Installed Version | 1.34.0 Stage | running Available Repositories | 1393 Downloaded Repositories | 61 HACS Data | okAccuWeather
can_reach_server | ok -- | -- remaining_requests | 40Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.4 -- | -- update_channel | stable supervisor_version | supervisor-2024.06.2 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 28.5 GB disk_used | 24.0 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | rpi3-64 supervisor_api | ok version_api | ok installed_addons | Duck DNS (1.18.0), File editor (5.8.0), AirCast (4.2.1), Home Assistant Google Drive Backup (0.112.1), Advanced SSH & Web Terminal (18.0.0), Grocy (0.21.0), RPC Shutdown (2.5), Scrypted (v0.114.0-jammy-full)Dashboards
dashboards | 5 -- | -- resources | 40 views | 15 mode | storageRecorder
oldest_recorder_run | July 11, 2024 at 15:33 -- | -- current_recorder_run | July 21, 2024 at 21:12 estimated_db_size | 830.60 MiB database_engine | sqlite database_version | 3.45.3Sonoff
version | 3.7.3 (e240aaf) -- | -- cloud_online | 6 / 6 local_online | 6 / 6Checklist
Describe the issue
Experimental features are quite mysterious and totally undocumented. I didn't even know they existed until I stumbled upon a mention while looking for an issue to use the
update
domain for updates.Then I enabled it and yay, it works wonders! After some weeks I was even wondering why the heck it's still an experimental feature. And then I went into HACS to add a new component, and discovered the main interface changed to an odd table, instead of the two columns of cards there was before. I didn't like it, specially because it's harder to skim-read through the new repos.
My suggestion is to split the "enable experimental features" into the actual features one could enable. Thus [1] users get informed on what they're about to enable (given there's not even docs - #3905 - if you decide to look around for such list) and [2] users can enable what they want to try out, instead of being a all-or-nothing approach.
Reproduction steps
Debug logs
Diagnostics dump
No response