How to hide forecast attributes?

Configuration
1

How do I hide a forecast sensor?
I’ve tried sensor.forecast_humidity and sensor.weather_humidity , both does not work.
Does anyone have some suggestions?

Greets
Jacko

2

Just remove the unneeded conditions from monitored_conditions: or the whole entry for the forecast sensor…

3

Yeah but I need some informations for some triggers and I don’t want those informations on the main page.
Is this possible or not?

Greets
Jacko

4

Check https://home-assistant.io/getting-started/devices/#customizing-devices-and-services

5

@fabaff I’ve read that and sensor.weather_humidity is the right attribute, but hidden: true does nothing.

Greets
Jacko

snippet from my configuration.yaml

customize:
sensor.weather_humidity:
hidden:true

6

*Disclaimer, I am super new at this stuff.

I am experiencing a similar issue with the following config which I am messing around with to better understand how the yaml translates to UI

Questions

  1. How do you reference monitored conditions syntactically? The only way I was able to get the customize block to work without erroring out was with the following syntax, since both forecast and open weather map have a ‘temperature’ monitored condition I am not sure how this works. Clearly I am missing some reference to forecast/open weather map right?

  2. Assuming I wanted to use forecast temperature monitored condition as part of an automation, but did not want to display it on screen I am assuming that I would have to list it under monitored conditions under sensor, and then reference it under the customize block using ‘hidden: true’ right? This is not working for me, and I have tried it using other monitored conditions examples as well.

        customize:
     sensor.temperature:
       hidden: true 

    sensor:
       # Open Weather Map
       - platform: openweathermap
         api_key: 497f0fccf540ede2acc2d6a59732a363
         forecast: 0 or 1
         monitored_conditions:
           - temperature
       # Forecast IO
       - platform: forecast
         api_key: a64d34fa7155ef4e7fd55134da465914
         monitored_conditions:
           - temperature
7

Ok I was able to figure out how to determine the entity id’s of monitored conditions using the developer tools and get the hidden: true functionality to finally work. Wasn’t super intuitive, but now I know!

8

Sharing is caring. Someone else may want to know how you did it…

1 Like
9

If you are asking me, my issue was that I didn’t fundamentally understand how entity id’s work and was not referencing the correct entity id’s in my configuration.yaml. I assumed that the entity id’s would match the monitored conditions list in the yaml when in reality somewhere behind the scenes the true entity id is generated which can be different particularly when there is contention between similar items and can be found under the ‘Set State’ Developer Tool listed under ‘Current entities’ which I was unaware of. This tool is briefly mentioned in the documentation, but for newbies like myself it wasn’t intuitive. Once I had the true entity id’s referenced in my config all was well.

10

Thanks, I was asking for myself and other newbies who might come along. You’ll also find this happens when using sensor templates as well. It’s usually a good practice when creating sensor templates to check the dev state tool to see how the template name is now being registered.