How to remove a YAML entity customization

Configuration Frontend
1

Hi, this question is probably very basic, but I can’t find the answer.

So, I was experimenting with changing an entity icon by adding a customize section in the configuration.yaml like:

homeassistant:
  customize:
    sensor.studioalba_ipad_battery_level:
      entity_picture: /local/battery-0.png

The customization didn’t show immediately. It took many restarts and eventually the entity default icon was replaced by the custom picture.

So, I removed the customize section from configuration.yaml and restarted HA.
But now, the entity icon has not returned to the default icon. It is still the custom picture.

What have I done wrong?
It looks like the customization has been made permanently.
Thanks for your help

2

Did you clear your browser cache?

3

Yes, many times.
I tried a new browser that I never used to open an HA session and I have the same result.

If I check the Developer Tools/States, I see that an attribute:
entity_picture: /local/battery-0.png
has been added, but not by me.
I have other battery level sensors and they don’t have an entity_picture attribute.

Where is it coming from?

4

could be in core-entity-registry
do you find it in /settings/devices&services#entities ? (remove filters)

6

It should be either replaced after HA reboot or (if not rebooted) after first change of the entity’s state.

By you , but it is still there.
You do not need to remove it if you added it intentionally and still want the image to be shown.

But there is another point.
What was the reason you added the image?
This is a battery level sensor with a “device_class: battery” attribute which adds a dynamically changed icon.
When you add an entity picture, it will be shown instead of that icon. Not good imho.

7

@boheme61
In settings/devices&services/entities the icon shown for the sensor is the default one.
If I click on the sensor to get the history window, the icon shown for the sensor is the custom one (/local/battery-0.png)

1 Like
8

@Ildar_Gabdullin
I think there is a misunderstanding.
My intention was to test the customization functionality.
I chose this sensor because I already had it defined in a card tile and was easy to monitor.
All I did was to add a customization in configuration.yaml :

homeassistant:
  customize:
    sensor.studioalba_ipad_battery_level:
      entity_picture: /local/battery-0.png

As I said, the custom icon showed up only after many restarts and platform reboots. Since this was just a test, I removed the customization from configuration.yaml, but the custom icon wasn’t replaced by the default icon.

So I started investigating.
In Developer Tools/States, you can see the entities attributes. That’s where I noticed that a new attribute had been added to the sensor.

My understanding is that this attribute:
entity_picture: /local/battery-0.png
is added to the sensor when added to the customize section in configuration.yaml and HA restarted.
Since I removed it from the customize section in configuration.yaml and HA restarted, shouldn’t this attribute be also removed from the entity?

9

@Ildar_Gabdullin
Hello again,
When I started writing my previous comment, the icon shown for the sensor was the custom icon. Now, the sensor icon is back to the default icon. I check in Developer Tools/States and I confirm that the entity_picture attribute has been removed.

I didn’t make any changes, HA didn’t restart or reboot. But I woke up my ipad.

Obviously, HA reboot doesn’t set or reset the customization.
But the first change of the entity’s state explains the behavior.
The sensor I modified is an ipad battery level.
This particular sensor doesn’t change it’s value when the ipad battery level changes. To get an updated value, the ipad must be in wake mode and the HA ios app must be active. Also, values are rounded to 5%, so 1% change doesn’t show up.
When I woke up my iPad, the sensor value went from 40% to 30% and thus the icon changed from custom to default.

The customization refresh behavior is a bit counter intuitive. I would assume that a simple yaml refresh would do the trick, but it seems that a state change is also required.

I guess we can close this issue.
Thanks for your help.

1 Like
10

OK, i didn’t read this first :wink: , good that it’s solved

Please mark above Post as Solution, so other people can find this in such cases
Under your above POST click the 3 dots, Mark Solution

11

I do not think this is correct. HA reboot does reload integrations which causes a change of added “entity_picture”.

Same, reloading a particular integration will refresh entity_picture.
Imho you were too quick with marking the post as a “solution” (((. Why the attribute was not added after proper operations - needs to be found.

12

I actually agree with you, after reading Francois posts again, as i asked him about the entities status-page

So it was actually changed back, but maybe the Card first reacted, upon a sensor-state-change
Mystery remains :slight_smile:

13

@Ildar_Gabdullin
Please let me disagree.
An HA reboot most probably reloads integrations, but I’m positive it doesn’t cause a change of added “entity_picture”. I had multiple HA reboots and the custom “entity_picture” remained in the list of sensor attributes until the iPad woke up.

If you’re not convinced, then I suggest you give it a try to see by yourself. You need the mobile integration to get the battery_level sensor and an iPad with the ios app. It’s probably the same for an iPhone, but I didn’t try it. I don’t know if it’s the same with Android because I don’t have android phone or tablet.

From my observations, the customized “identity_picture” is either added or removed upon state change. An HA reboot doesn’t seem to force a state change. In the case of this particular sensor, state change occurs when the iPad is awake, the ios HA app is active and the battery_level varies more than 5%.

So, from my point of view, this case is solved because it provides a good explanation of the customization refresh behavior.

Now, if this behavior is not appropriate, then feel free to open a bug report.

14

May be because a whole config entry for this device could not be updated since the device was unreachable.

This is not about me. In the post which you marked as a “solution” you claimed that “entity picture” is only updated after a state change. May be (let some core expert to say), but this usually happens on an integration reload. That means that a statement “HA reboot doesn’t set or reset the customization” is not correct.

… with partially wrong assumptions.
Since I found them incorrect - I suggested you to correct them.

This is something for you to decide, no one gonna register issues for another person.

15

After a while, I think this a probable explanation. On HA reboot (or even after a manual reload of a config entry), if the device is unreachable, it’s entities cannot be updated.

16

What do you mean, you can change the icon, name etc. on entities on a unplugged device, or battery dead or gone

17

We can because we are editing data on a local entity_registry file. But getting data from an entity (with added attribute) seems to be different thing.

18

Ain’t the “added” attributes etc made in HA, and not on the Device ? :thinking:

It Seems to me like it was updated, however the Card/View(or whatever) seemed first to be updated when his device came on, and changed the Status ( Then i guess the Entity was “Called/Pulled” to frontend/view with it’s “removed/changed” attributes )

19

Erm, all entities are made on HA)))

20

right, we don’t change anything on the device, but we can tamper with it’s entities

21

No, frontend has an access to “states” object containing entities. If the objects is not updated (here - does not have the added property) then the frontend will not show it.