Entity sensor.adoradry_v2000_gesamtverbrauch cannot be added as the entity category is set to config

[redneckdba]

Hi
I'm getting below errors during startup of HA for my AdoraDry V2000 and AdoraWash V4000 devices for the follwoing sensors:
Error adding entity sensor.adoradry_v2000_gesamtverbrauch for domain sensor with platform vzug
Error adding entity sensor.adoradry_v2000_durchschnitt_pro_charge for domain sensor with platform vzug
Error adding entity sensor.adorawash_v4000_gesamtverbrauch for domain sensor with platform vzug
Error adding entity sensor.adorawash_v4000_durchschnitt_pro_charge for domain sensor with platform vzug

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 657, in _async_add_entities await self._async_add_entity( entity, False, entity_registry, config_subentry_id ) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 979, in _async_add_entity await entity.add_to_platform_finish() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1367, in add_to_platform_finish await self.async_internal_added_to_hass() File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 284, in async_internal_added_to_hass raise HomeAssistantError( f"Entity {self.entity_id} cannot be added as the entity category is set to config" ) homeassistant.exceptions.HomeAssistantError: Entity sensor.adoradry_v2000_gesamtverbrauch cannot be added as the entity category is set to config
This seems to be related to this issue which had already been fixed some time ago for a different sensor -> siku2/hass-dingz#40

Thanks

[david-aggeler]

Just saw this myslef. @siku2 I've created a branch called entity_category. Since I changed the default, I have no clue on the side effects. With this, I don't see the above errors anymore, and the 2x3 sensors still seem to work. But I've not tested any actions.

[siku2]

Just saw this myslef. @siku2 I've created a branch called entity_category. Since I changed the default, I have no clue on the side effects. With this, I don't see the above errors anymore, and the 2x3 sensors still seem to work. But I've not tested any actions.

That's completely fine. The category is mostly irrelevant. It only changes how the entity is displayed in the device view and whether it is added to the dashboard by default.
Can you open a PR for that, @david-aggeler ?

[TheFab21]

hi manage to sort it out :
in sensor.py
from homeassistant.const import EntityCategory

... (déjà présent en haut du fichier)

class UserConfigSensor(SensorEntity, UserConfigEntity):
# on annule toute catégorie "config" héritée du mixin pour un Sensor
_attr_entity_category = None

@property
def entity_category(self) -> EntityCategory | None:
    # un sensor ne peut pas être CONFIG ; on force None (ou DIAGNOSTIC si tu préfères)
    return None
    # alternative si tu veux les classer en diagnostic :
    # base = super().entity_category
    # return EntityCategory.DIAGNOSTIC if base == EntityCategory.CONFIG else base

@property
def native_value(self) -> StateType | date | datetime | Decimal:
    return self.vzug_command.get("value")

Stop HA
clear pycache
in /config/.storage/core.entity_registry search for the entities en replace for entity_category "CONFIG" by null
restart HA

[david-aggeler]

@siku2 , I don't think the merged code to main from Sep (5931c73) ever got published as new version. Is there somthing that is missing?

[david-aggeler]

@siku2 , Anything missing before the fix from September can be made public?

[siku2]

@david-aggeler thanks for the shout. I honestly don't remember what was stopping me from releasing it. FYI you should also have the permissions to create releases by triggering the release workflow.

EDIT: The release has been created!