Automation: Numeric Trigger shall be state not "become"

Hello,

Based on tests of my simple automations with a Numeric Trigger like: close shutter if temperature is above 23 degrees and sun is shining (brightness), it looks like they get only activated if the Numeric Trigger crosses the defined threshold.
So, when all requirements are met, but the actual temperature is already above 23 degrees, nothing happens.

Does anybody know the concrete solution how to get it always activated when it is above a threshold? (I see only rough ideas on other postings).

Many thanks!
Roland

Automation Example:

id: ‘1622314242009’
alias: Cooling South
description: ‘’
trigger:

  • platform: numeric_state
    entity_id: climate.living_temperature_3
    attribute: current_temperature
    above: ‘24’
    condition:
  • condition: numeric_state
    entity_id: sensor.weather_station_brightness_south
    above: ‘30000’
    action:
  • service: cover.close_cover
    target:
    entity_id:
    - cover.living_top_shutter_2
    mode: single
id: '1622314242009'
alias: Cooling South
description: ''
trigger:
  - platform: state
    entity_id: climate.living_temperature_3
    attribute: current_temperature
condition:
  - condition: numeric_state
    entity_id: climate.living_temperature_3
    attribute: current_temperature
    above: '24'
  - condition: numeric_state
    entity_id: sensor.weather_station_brightness_south
    above: '30000'
  - condition: state
    entity_id: cover.living_top_shutter_2
    state: 'open'
action:
  - service: cover.close_cover
    target:
      entity_id: cover.living_top_shutter_2
mode: single

The automation triggers whenever the living room’s current_temperature changes then proceeds to evaluate three conditions:

  1. The current_temperature is above 24.
  2. Brightness level is above 30000.
  3. The shutter is open.

If all three conditions are true, it proceeds to close the shutter.

Also, please get used to posing your code properly for the forum by using three backticks (```) on the line before and after the code block.

It makes it easier to read and see errors.

Wow, it works - many thanks Taras!

This is the second time you helped me - can I hire / pay you for additional issues?

I.e. it would be interested to get this automation / shutters back to the previous state if one of the thresholds or state are not met.

It is a family house with a KNX system.

Best,
Roland

What kind of actuator / weather station are you using? Some provide sophisticated support for these things outbox the bus :wink:

If you just invert this automation you probably won’t get a satisfying result.
Some thoughts of practical cases:

  • a cloud causes the brightness to drop below the limit for 3 minutes → you need some hysteresis
  • you just opened it manually and some minutes later the temperature changes → you need some timeout to fall back to “automatic mode”
  • it’s very bright outside, but the sun dont shine directly on the window → add a condition for a sun angle range
  • in Winter you may want to have different conditions: open at daytime as long as the room doesn’t overheat (limit eg target room temperature + 3K or just 24°C)

Hi Matthias,

Many thanks for your very valuable comments.

It is A SIEMENS AP257/31 which offers a facade control, but with brightness only and a Logic module with up to 4 and/or parameters. Room temperature had probably to be an External Alarm, but this is beyond my KNX skills as I have never seen before how you can define temperature thresholds or ranges there.

My weather station looks exactly the same but is from Elsner. It can calculate sun angle and use it for the facade control.

The temperature stuff and automation-fallback-time is done by my ABB JRA actuator. It always depends on the applications of your devices and how they fit together.

Interesting.
I also use ABB shutter actors, but it as far as I see, there are no temp parameters. Did you develop a similar automation just with these two devices ? I would be highly interested.
Maybe my Infoterminal Touch from Gira with its logicmodul could solve it, but again, way above my skills.

Yes these two and a heating actuator. It’s a ABB JRA/S x.230.2.1
The heating actuator sends binary objects for Heating/Cooling and the current temperature.
The max. temp for winter is hard configured in the blind actuators application (no communication object).
The weather station just sends a “Sun” binary object for the different facades. Hysteresis of brightness and sun angle is calculated there.

I also use the ABB heating actor. Is there a way that you could send me a screenshot of your shutter actor comm objects and the (relevant) group addresses? I Could give you my email address

Works with PayPal only which I do not want to use anymore. Sorry

Not sure if it would really help more than reading the manual. But if you think so and you can read German I can try to make some screenshots later this week.

Danke Matthias,

Ich bin Deutschschweizer und nehme alles, was Du mir geben kannst.

Beste Grüsse
Roland

6/6/202 Is the sun object “Fassade 5: Status - Ausgang” coming from the weather station.

Many thanks Matthias,

Unfortunately, I have the older version of the ABB Shutter Act. without this sun protection …

Best, Roland

@roland23

Did adding “three backticks” actually solve the original problem? Because that’s what has been marked as the Solution.

If it did then I’ll remove my first post so as not to mislead other users reading this thread.

My guess is that @roland23 saw that @finity’s post started with “Also”, and ass-u-med that was a follow-on post by the same author.

@roland23 — please give your Solution to Taras’ first post.

I did that quit e a while ago

1 Like

You can only mark one post in the entire thread with the Solution tag. If you mark a second one, the first one loses the Solution tag. Perhaps you originally marked my post and then marked finity’s post.

I checked it several times. I only marked your solution you sent me 9 days ago, 100% sure.