What circumstances does an existing automation (native) not open in CAFE?

[thefunkygibbon]

Hi,
Only installed this the other day as i wanted to start using it to to make my existing native HA automations a bit more visual and complex. But I'm finding that a bunch of the automations i have do not do anything at all when clicking on the "open" button within CAFE.
I first thought that it was because the automation in question is based off of a blueprint... so i assume that that would be a reason why... i couldn't see anything in the documentation mentioning that you couldn't open those types of automation, but i'm going to assume it can't. But I tried to open another which wasn't a blueprint based one and it still couldn't open. No errors, nothing. just ignores me trying to open.

A bunch of much more simpler automations seem to open fine.

Is there any kind of documentation which describes what caveats there are with using CAFE in this kind of usecase?

thanks though, this SEEMs to be a game changing project. I hope that it gets built into HA one day!

[FezVrasta]

Some automations may fail to load if the parser can't parse them. I have to improve error reporting to show the exact reason.

[frustrated-dad]

hmm ok yes error logging would be useful. .

just so that you can maybe test and check your code here is the yaml of one that's not importing ...as you can see, it's pretty basic.

also, was I correct in my assumption that blueprint based automations wouldn't import or would cafe just do the whole "take control" thing and use that yaml?

alias: Office - Heating
description: ""
mode: single
triggers:
  - event: start
    trigger: homeassistant
  - event_type: automation_reloaded
    trigger: event
  - minutes: /1
    trigger: time_pattern
conditions: []
actions:
  - choose:
      - conditions:
          - condition: not
            conditions:
              - condition: state
                entity_id: timer.heating_timer
                state: idle
        sequence:
          - data:
              temperature: 21
            target:
              entity_id: climate.office_thermostat
            action: climate.set_temperature
      - conditions:
          - condition: state
            entity_id: binary_sensor.workday_sensor
            state: "on"
          - condition: time
            before: "17:00"
            after: "08:00"
          - condition: state
            entity_id: binary_sensor.office_sensor
            state: "off"
          - condition: not
            conditions:
              - condition: state
                entity_id: group.justme
                for: "00:01:00"
                state: not_home
          - condition: not
            conditions:
              - condition: state
                entity_id: calendar.andrew_thefunkygibbon_net
                state: PTO
                attribute: message
        sequence:
          - data:
              hvac_mode: heat
              temperature: 19
            target:
              entity_id: climate.office_thermostat
            action: climate.set_temperature
      - conditions:
          - condition: state
            entity_id: binary_sensor.office_sensor
            state: "on"
        sequence:
          - data:
              entity_id: climate.office_thermostat
              temperature: 5
            action: climate.set_temperature
    default:
      - data:
          entity_id: climate.office_thermostat
          temperature: 5
        action: climate.set_temperature

[doobes]

I'm having the same issue. I've got several that won't load.

One of which is a blueprint. Should that make a difference?

This one is simple, yet it won't load.

alias: Turn_on_garden_lighting_at_sunset
description: Turn on the garden lights at sunset
mode: single
triggers:
  - event: sunset
    offset: 0
    trigger: sun
conditions: []
actions:
  - type: turn_on
    device_id: 9c0a968e38fcf89b0fa58c01c304ce2c
    entity_id: f33076e74dbf8c02a4e886217e266ffe
    domain: switch

Conversely, many will so that gives me things to work with.

Thanks for this resource.

Is it possible for the tool to "review" automations and perhaps gray out the ones which cause error?

cheers

[FezVrasta]

Thanks, I fixed the bug, the fix will be in the next release

[doobes]

Is this an artifact of the now squashed bug:

yaml:

alias: Kitchen.Freezer_Temp.Automation
description: ""
trigger:
  - platform: device
    entity_id: 05dfa830b43a4f97adfb34a06c2bce50
    for:
      hours: 0
      minutes: 15
      seconds: 0
    above: 20
    device_id: 7239e87f810ebbd9be93fe71f3977211
    domain: sensor
    type: temperature
action:
  - service: notify.e_mail
    data:
      message: The Freezer in the Kitchen is Open!
      title: Alert!
mode: single
variables:
  _cafe_metadata:
    version: 1
    nodes:
      trigger_1768580600661_0:
        x: 12
        "y": 12
      action_1768580600661_1:
        x: 315
        "y": 15
    graph_id: ff6c5b21-5181-4d0f-b56c-1dfc380a8195
    graph_version: 1
    strategy: native

C.A.F.E. interpretation:

Seems like there was a lot that wasn't picked up.

Thanks!

[doobes]

More weirdness.

HA yaml:

alias: Garage.Close_Door.Automation
description: ""
triggers:
  - trigger: time
    at: "22:30:00"
conditions:
  - condition: device
    device_id: eba8eb6324de8d75372d9ad0ac804c55
    domain: cover
    entity_id: fe775701f55300f856d893facc59d8a3
    type: is_open
actions:
  - device_id: 2a78304f9b3ae53d82eaa4f9bfd6a36f
    domain: cover
    entity_id: d5e9f1aa670ccfcfa0d7f08494b4f187
    type: close
mode: single

C.A.F.E.yaml:

alias: Garage.Close_Door.Automation
description: ""
trigger:
  - platform: time
    at: "22:30:00"
action:
  - if:
      - condition: device
        entity_id: fe775701f55300f856d893facc59d8a3
    then:
      - service: cover.close
        target:
          device_id: 2a78304f9b3ae53d82eaa4f9bfd6a36f
        data:
          type: close
          device_id: 2a78304f9b3ae53d82eaa4f9bfd6a36f
          domain: cover
          entity_id: d5e9f1aa670ccfcfa0d7f08494b4f187
    else: []
mode: single
variables:
  _cafe_metadata:
    version: 1
    nodes:
      trigger_1768580917916_0:
        x: 15
        "y": 15
      condition_1768580917918_1:
        x: 312
        "y": 12
      action_1768580917924_2:
        x: 645
        "y": 0
    graph_id: a3663e10-0da6-41d8-

Device node not recognizing the device:

[thefunkygibbon]

So should blueprint based ones be able to be imported or not? all of the ones i've tried to open fail with the message that it can't import something with no trigger (?).
honestly it's fine to not import blueprint ones because, well lets face it, they don't really need to be edited, and if they did, then you should just "take control" and then presumably it would import, right?
would it be possible to flag/ignore the blueprint based automations from the list of importables?

Also, noticing that (normal) automation's which have sunset

conditions:
  - condition: or
    conditions:
      - condition: sun
        before: sunrise
      - condition: sun
        after: sunset

import with blanks where the conditions should be.

[FezVrasta]

Blueprints are not supported yet!

[doobes]

I was able to open an automation with the Sensor Light blueprint. It was a LOT of nodes.

It might be wise to prohibit CAFE from opening blueprint automations, although I have no Idea how that might be done.