The icon does not change either in the sensor declaration or in customize.yaml or both. Of course I have deleted browser browsing data several times (Chrome).

How would you propose changing the icon for this class? There are many different types of radio receiver and all have different sensitivity ranges in dBm. It’s not like a battery where we have 0 to 100%.

There are already **Material Design Icons** that can be used: mdi:wifi-strength-4 to 1, mdi:wifi-strength-outline, mdi:wifi-strength-off-outline

That’s not the issue. The issue is that there is no universal scale in dBm to match to the icons. All radios are different.

This is the sensor template I have to use: sensor: - platform: template sensors: icono_nivel_senal_wifi_despacho: friendly_name: Nivel Señal Wifi Despacho unit_of_measurement: 'dBm' value_template: '{{ states("sensor.nivel_senal_wifi_despacho") }}' icon_…

This use is for WiFi connections

And would that wifi range apply to Bluetooth? Zigbee? 433MHz ISM? Zwave? Answer: no, no it would not. The device class covers more than just wifi.

So it seems that it is best to have different Classes depending on the type of Radio since it is very important to know directly in the Application the feasibility of the connection when installing new device.

Far easier to allow the user to implement things like this: [Screenshot_2020-05-19 Overview - Home Assistant]

I suppose that it is a summary of connections to have, for example, on a main screen, not on the individual screen of each device. Visually it is more attractive and I suppose it requires manual editing of the yaml using templates. I think that facilitating the use of Home Assistant is using the m…

[image] oalvarez: I suppose it requires manual editing of the yaml using templates. Nope. The bar card supports Lovelace UI editing.

Device_class: "signal_strength" does not work

Feature Requests

anon11644107 May 19, 2020, 10:11am 13

Correct. Easy to install once you have HACS set up.