"No visual editor support for this action" after latest update

Configuration Frontend
,
1

So after the latest update 2024.8.1 some of my automation and scripts come up with “No visual editor support for this action”

Screenshot 2024-08-16 at 3.11.10 PM
Screenshot 2024-08-16 at 3.11.10 PM2226×1342 156 KB

(The photo is a script example)

Where others look normal

Screenshot 2024-08-16 at 3.12.17 PM
Screenshot 2024-08-16 at 3.12.17 PM2174×1946 259 KB

(Another script example)

And if I remove the blocks and add new they look normal when saved, but when I go back to the overview and open it again, it’s UNKNOWN again.

Odd thing is, i can have two identical automation or scripts where one is normal and the other have “UNKNOWS”

I only experience this for blocks with “Call a service”

Anyone else seen this?

2

I’m getting this too after updating to 2024.8.x.

Rolling back to 2024.6.x hasn’t resolved the issue. Several of my automation show this with calls ranging from light.turn_on to scene.turn_on. Even invoking scripts.

It’s broken about 5 of my automatons at random.

Recreating the action fixes it but, like you, as soon as I exit the automation and open it again for editing it’s back to being “Unknown” and unsupported by the visual editor.

Did you ever find a fix?

EDIT:
Okay, it turns out that rolling back to 2024.6 DID fix this issue of service calls becoming “Unknown” and not supporting the visual editor. It appeared not to at first because the roll-back presented a different (but related) issue.

Some time between 2024.6 and 2024.8, the term service has been replaced with action. Where the YAML for a service call in an Automation used to be as follows:

metadata: {}
data:
  targets:
    - Janes Phone
    - Johns Phone
  content: Abnormal water activity detected at home
  header: Water Alert
service: script.send_alert

it is now:

metadata: {}
data:
  targets:
    - Janes Phone
    - Johns Phone
  content: Abnormal water activity detected at home
  header: Water Alert
action: script.send_alert

Similarly, the tab to call a service in the Developer tools page has been renamed to “Action”.

When updating to 2024.8, it seems the service calls within various automatons get automatically adjusted to move from service to action verbiage. When rolling back to 2024.6, that isn’t reverted (probably to be expected) and so many automatons will appear broken until you go back and replace the verbiage to service.

It’s possible that it was part of this shift from service to automation that is what’s causing the primary issue here of the Visual Editor not recognizing the action blocks in 2024.8. Maybe during the rename, a bit of code got missed and now there are certain instances in which it is looking for the old naming and not finding it, causing the visual editor to break?

Either way, for now I’m going to stay on 2024.6 and hole up there until a few more releases, or until there is some activity here. Hopefully this added detail gets us that much closer to a fix.

3

Can someone share a complete script that when saved and reopened, exhibits these unknown actions?

4

This is the YAML for an automation that was build, looked as it was suppose to, then saved and now display unknown.

alias: GOOD MORNING (FOCUS OFF)
description: ""
trigger:
  - alias: NOAH = FOCUS OFF
    type: turned_off
    platform: device
    device_id: d815b1067815aae942904819480ce366
    entity_id: 9eb298ddffbe4be20dd206c462fe62a1
    domain: binary_sensor
    enabled: true
  - alias: VICTORIA = FOCUS OFF
    type: turned_off
    platform: device
    device_id: 009af8bf9ce1a82773f2d1884a4f29de
    entity_id: 5dc1dd2bad3ea32bf2b4cbd576da2f6a
    domain: binary_sensor
    enabled: true
condition: []
action:
  - target:
      entity_id: alarm_control_panel.house_alarm
    data: {}
    action: alarm_control_panel.alarm_arm_home
  - data: {}
    action: script.thermostats_home
  - type: turn_on
    device_id: 07896c25bc63aa7dfb7096ddb7347da7
    entity_id: 8b80a3b1afd5902d8ba7321560ad9289
    domain: switch
    alias: TURN ON LIGHTS HALLWAY
  - type: turn_on
    device_id: bed964e4ed37f26765b50e65d3766c0d
    entity_id: 2547ca1156d70771e5be928579dee489
    domain: switch
    alias: TURN ON LIGHTS KITCHEN
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
    alias: DELAY 5 SECONDS
  - alias: TURN RADIO ON
    if:
      - condition: state
        entity_id: binary_sensor.victoria_iphone_15_pro_max_focus
        state: "off"
      - condition: state
        state: "off"
        entity_id: binary_sensor.iphone_lars_focus
    then:
      - data: {}
        action: script.start_radio_in_the_morning
  - metadata: {}
    data: {}
    target:
      entity_id: switch.master_bedroom_bed_socket_1
    action: switch.turn_off
  - metadata: {}
    data: {}
    target:
      entity_id: switch.game_tv_socket_1
    action: switch.turn_on
mode: single

Screenshot 2024-08-19 at 9.10.00 AM
Screenshot 2024-08-19 at 9.10.00 AM2226×2104 243 KB

And this is a script

alias: THERMOSTATS - AWAY - DAYTIME AND NIGHTTIME
sequence:
  - data:
      hvac_mode: heat_cool
      target_temp_low: 65
      target_temp_high: 88
    target:
      entity_id: climate.family_room
    action: climate.set_temperature
  - data:
      hvac_mode: heat_cool
      target_temp_low: 65
      target_temp_high: 85
    target:
      entity_id: climate.garage
    action: climate.set_temperature
  - data:
      hvac_mode: heat_cool
      target_temp_high: 85
      target_temp_low: 65
    target:
      entity_id: climate.master_bedroom
    action: climate.set_temperature
  - data:
      hvac_mode: heat_cool
      target_temp_high: 88
      target_temp_low: 65
    target:
      entity_id: climate.guest_bedroom
    enabled: true
    action: climate.set_temperature
mode: single
icon: mdi:home-thermometer

Screenshot 2024-08-19 at 9.11.04 AM
Screenshot 2024-08-19 at 9.11.04 AM2840×882 104 KB

5

Hmm, I’m not able to reproduce it. I copy-pasted your script exactly and saved it and the visual editor looks as it should.

If you copy/paste that into a brand new script and save it, does it work correctly or show unknown?

6

I tried copying the YAML code, created a new script and pasted the YAML, saved it and the same happens . I get UNKNOWN i all fields.

7

An update is in place.

I kept getting these UNKNOWN in but automation and scripts, some would work and some would not and no matter what I did i’d still see UNKNOWN.

Then I though, let’s try from a phone, and from the phone I had no UNKNOWN.

So that led me to suspect the browser cache/cookies and after clearing that all my UNKNOWN was gone.

I am sorry guys, this is on me :frowning: