Hi! About openweather api "condition"

[fernan_yeles (Fernando)]

Hello! Hi everyone. I would like to know if you can refer me to a thread that has already been asked about this, and if not, the question is the following:

How can I create an automation or a scene so that when in the openweather API, in the “condition” entity I put for example, rain or snow, I can extract that field to use it as a trigger to lower my blinds, for example? Thank you very much in advance. The idea is to do it without code, in the Lovelace editor, unless there is no other option, I am learning and I do not have much time. Thank you very much, colleagues.

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

Hi Fernando,

Here’s some searching advice.

Tips on Searching for Answers & Duplicate Topics in the Forum

Sometimes searching for what you want to find here in the Community Forum can be frustrating. The Forums base software (Discourse) has a search tool that is somewhat effective, but it relies on only the answers provided by other users in the app to answer your question. It does do a good job of popping up similar topics when you are starting a new topic however. (So please pay close attention to the side panel when you are adding a new topic) If you use a search engine like DuckDuckGo or Googl…

[Didgeridrew]

You should just need to use a State trigger. The state of a weather entity is normally the weather condition you are looking for.

@fernan_yeles

The idea is to do it without code, in the Lovelace editor, unless there is no other option, I am learning and I do not have much time.

Almost all answers you are going to get on this and other forums will be in YAML because there is no more efficient way for us to share the necessary data. If you need a primer on transcribing YAML automation configuration to the UI Editor there is a slightly dated video available here.

[fernan_yeles (Fernando)]

Well, Start from the begining!.

Do you think this is ok?

trigger: state
entity_id:
  - sensor.openweathermap_condition
from: null
to: rainy

Thanks in advance, It won’t rain here now, ha ha ha ha.

[Didgeridrew]

@fernan_yeles

Do you think this is ok?

Yes, that looks fine.

[fernan_yeles (Fernando)]

This is the entire yaml, the “when” and the “then”:

trigger: state
entity_id:
  - sensor.openweathermap_condition
from: null
to: rainy
--------
action: scene.turn_on
metadata: {}
target:
  entity_id: scene.bajar_todas_las_persianas

[fernan_yeles (Fernando)]

I don’t doubt that it works, but I wonder why all the possibilities of the attribute don’t appear in a list, and it has to be written by hand. I don’t know if it will recognize it when it is triggered, because I have noticed the values ​​of the statistics of that attribute (I’m Spanish)

[Didgeridrew]

@fernan_yeles

I wonder why all the possibilities of the attribute don’t appear in a list, and it has to be written by hand.

It’s likely the integration developers did not include that data in the sensor. It should be available in the drop-down if you use the weather entity instead.

@fernan_yeles

I don’t know if it will recognize it when it is triggered, because I have noticed the values ​​of the statistics of that attribute (I’m Spanish)

As far as I am aware, the values from the Weather integration docs are what you should use.

[fernan_yeles (Fernando)]

Thank you, but I don’t understand what you’re saying.

If I put the entire range of values, or some of them, written the same way in stats, and suddenly the state changes from one to the one set in the trigger, would it be executed?

Thanks in advance