In my sensors.yaml, an AirVisual sensor creates three entities.
In groups.yaml, I added all three in my Weather group,
- us_air_pollution_level
- us_air_pollution_index
- us_main_pollutant
With customization.yaml configured
- us_main_pollutant:
hidden: true
When the “hidden: true” didn’t work, I moved “us_main_pollutant” to a new group that I named “Hidden”, and I created an automation to set group’s “visible” attribute to false. Before I run the automation, the Hidden group is visible, and us_main_pollutant" is displayed. When I run the automation, the group disappears as expected. However, “us_main_pollutant” becomes a badge at the top of the window.
I should also mention that HA also ignored friendly names when I attempted to assign them to AirVisual entities.
I do have “config:” in my configuration.yaml file. Based on what I’ve read, this may be what is causing the problem. I don’t want to remove “config:”, so I am looking for other options:
These are the questions going through my head.
-
Is there any way to configure the AirVisual sensor so it will not produce the unwanted entity?
-
Is there a way to prevent “config:” from overriding my customizations related to the AirVisual entities?
-
Is there another source for Air quality data that works with config:?