Skip to content

fix: Allow enabling disabled entities from UI#939

Open
Sopsy wants to merge 1 commit intodavidrapan:mainfrom
Sopsy:disabled_entity
Open

fix: Allow enabling disabled entities from UI#939
Sopsy wants to merge 1 commit intodavidrapan:mainfrom
Sopsy:disabled_entity

Conversation

@Sopsy
Copy link
Contributor

@Sopsy Sopsy commented Jan 14, 2026

Disabled entities (disabled: in entity definition) are skipped completely and cannot be enabled without editing the yaml files.

This tiny fix removes the is_enabled check from get_entity_descriptions so they are added into the registry and become enablable from the UI.

Disabled entities are really not used right now, but HA recommends they should be used, and I totally agree.
https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/entity-disabled-by-default/

There are 4 disabled entities in the existing definitions, all in solis_1p-5g.yaml:

  • Inverter ID
  • Product Model
  • DSP Software Version
  • LCD Software Version

I did not change these to "force" which would have been equivalent to old functionality.

@Sopsy Sopsy marked this pull request as draft January 14, 2026 18:33
@Sopsy Sopsy marked this pull request as ready for review January 14, 2026 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant