search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.8k stars 30.89k forks source link

Automation Lights showing YAML when editing Advanced Options #125186

Closed labanex closed 2 months ago

labanex commented 2 months ago

The problem

I recorded this issue and uploaded it to YouTube https://youtu.be/eQVT_mBjhNQ

Since HA 2024.6, when editing a light action in automation, the Advance function turns to YAML edit mode only. I asked people in the community, and they are not having this issue. It only happens when going to Advanced. Before, the advanced expansion thing was not there before. I like how you can expand it but when I use anything in Advanced, it goes straight to YAML mode. Is there anything I can do to fix this? What else do you need from me that you need to look at?

This is happening on Zigbee2MQTT, Govee2MQTT, and SmartLife lights. I am not seeing this issue anywhere else, like switches and such.

It is doing the same in Developer Tools, Actions.

First image, I tried to use Brightness 1-255. Second, I removed Brightness and UI comes back.

image image

Thank you.

What version of Home Assistant Core has the issue?

core-2024.8.3

What was the last working version of Home Assistant Core?

core-2024.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Automation, not sure if an integration is affecting this. All lights.

Link to integration documentation on our website

https://developers.home-assistant.io/docs/core/entity/light/

Diagnostics information

Since it is not an integration causing this, as far as I know, not sure how to get diagnostics.

Example YAML snippet

action: light.turn_on
target:
  entity_id: light.office_ne_tall_top_lamp
data:
  rgb_color:
    - 255
    - 100
    - 100
  brightness: 192

====

This shows up fine in UI:

action: light.turn_on
target:
  entity_id: light.office_ne_tall_top_lamp
data:
  rgb_color:
    - 255
    - 100
    - 100
  brightness_pct: 76

Anything in the logs that might be useful for us?

I recorded logs in F12 of Microsoft Edge. The same thing happens in Chrome as well.
How can I get logs from using light entities in Automations or Developer Tools / Actions?

Additional information

This has been happening since 2024.6. I really hope it is something simple because I have backups going, but it only back up every 10 hours and up to 10, so 2024.5.4 is long gone. Second, I am utilizing a lot of features of upgrades since then. I asked people in the Community, no one has reported this happening.

I restarted in Safe Mode to see if running HAOS RAW would do it. Same thing is happening. So, it may not be an integration.

labanex commented 2 months ago

System Information

version core-2024.8.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.4
os_name Linux
os_version 6.6.46-haos
arch x86_64
timezone America/New_York
config_dir /config
Home Assistant Cloud logged_in | true -- | -- subscription_expiration | July 4, 2025 at 20:00 relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true remote_server | us-east-1-7.ui.nabu.casa certificate_status | ready instance_id | I was not sure if this is needed or needs to be redacted. If needed, let me know. can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 13.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.08.0 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 234.0 GB disk_used | 100.5 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | Samba share (12.3.2), OneDrive Backup (2.3.1), Terminal & SSH (9.14.0), Node-RED (18.0.5), Mosquitto broker (6.4.1), Zigbee2MQTT (1.40.0-1), File editor (5.8.0), Studio Code Server (5.15.0), Log Viewer (0.17.0), InfluxDB (5.0.0), Govee to MQTT Bridge (2024.07.13-82ddc6e9), Matter Server (6.4.2), Assist Microphone (1.2.0), openWakeWord (1.10.0), Music Assistant Server (2.2.2)
Dashboards dashboards | 10 -- | -- resources | 23 views | 38 mode | storage
labanex commented 2 months ago

Right now, I am at: Core 2024.9.0 Supervisor 2024.08.0 Operating System 13.1 Frontend 20240904.0

labanex commented 2 months ago

Any idea of what I can do to fix this? Thanks. Added note: This issue does not affect performance of the automations or scripts. It is simply the GUI that is affected.

karwosts commented 2 months ago

I guess this will probably end up being a frontend issue, see also https://github.com/home-assistant/frontend/issues/21629