It looks there is search error in yaml editor of automations. When searching for a word that is out of view, the editor do not move to the position that is found. If you do so in yaml of raw dashboard it works fine ?
Hi, try by refreshing your browser or use another one to see if there is any difference.
Hi, yes, it’s the same in firefox and edge.
HA core version 2025.4.2
1 Like
Works for me. I just tested it in firefox.
You’re not using any add-ons in your browser?
Edge without add-ons, firefox with 3.
It’s strange because the yaml editor of HA is the same for dashboards and automations, isn’t it ?
Maybe try FF without add-ons?
I’m running FF with 20 or so extensions. Nothing that modifies the behavior of FF though.
1 Like
I have the same problem.
While searching in automation yaml editor the Window does not move.
In the dashboard code editor it works ok as before.
My system:
Home Assistant:
Core 2025.4.4
Supervisor 2025.04.0
Operating System 15.2
Frontend 20250411.0
Windows 11 24H2
Browsers:
Firefox 137.0.2
Chrome 135.0.7049.115
Microsoft Edge 135.0.3179.98
Also tested in Windows 10 and Linux Mint (VirtualBox VM)
I think, there could be a problem with the number of lines in the editor window.
In my window there are 35 visible lines.
I am testing with a 45-lines-automation.
Cursor-Position line 1:
Pressing and holding the arrow-down-key: Cursor moves down and disappears, no screen updating.
Ctrl+End: Cursor disappears, no screen updating
After pressing Pgdn-key 3 times the screen ist finally updated.
Cursor position last line:
Pressing arrow-up-key 11 times until the cursor appears in line 35
Pgup-key works ok.
Ctrl-Home works ok
Just tested with an older Version of my System on a VM.
Searching and moving in the yaml automation editor works fine.
Core 2025.3.4
Supervisor 2025.04.1
Operating System 15.0
Frontend 20250306.0
=====================
Further test:
Test system:
Core 2025.3.3
Supervisor 2025.04.1
Operating System 15.2
Frontend 20250306.0
Searching and moving in yaml-automation editor ok
Doing just the core-update, no other manipulation in the test system.
Test System:
Core 2025.4.4
Supervisor 2025.04.1
Operating System 15.2
Frontend 20250411.0
Searching and moving in yaml-automation editor not ok.
@tempuser
Yes, I tested it after your comment, it’s really strange, the first 3 PgDn keypresses are ignored, then you can use PgDn to go through the complete source code.
The problem was definitely not in previous versions, I would have noticed that immediately.
Just updated to the last core version:
Core 2025.5.0
Supervisor 2025.04.1
Operating System 15.2
Frontend 20250507.0
Problem is still there.
Deleted all automations in my test system.
Created a new automation.
Problem is still there
Updating to
- Core 2025.5.1
- Supervisor 2025.04.1
- Operating System 15.2
- Frontend 20250509.0
BUG is still there !
Guys, someone needs to replicate the issue in order for anyone to fix it. Updating and hoping it gets fixed without creating an issue first does nothing. I doubt anyone outside this thread even knows about this issue because it doesn’t affect many people.
What to do:
- Find out how to replicate the issue.
- Create an issue in homeassistant/frontend repo with your findings.
What not to do:
- Update and expect it to be fixed.
- Come here and complain that it hasn’t been fixed when the dev’s don’t even know about it.
1 Like
Not a complaint, just acknowledgement: I just tested it now myself and I get the same behavior.
The search function works, as in highlighting the keyword outside of actual view, but not navigating to it.
So @HAUser2023 as @petro suggests: if you want it fixed (or at least let the right persons know), open an issue on GH.
I do so yesterday, hope they find the problem
1 Like
Thank you for opening the case in Github!
Here some Information for the case:
“BUG: automation yaml editor search error #25437”
Last known good for me (not backuping every day):
Core 2025.3.4
Tested in safe mode:
Problem is still there.
@HAUser2023
Maybe you could refer in Github to this community post.
No offense guys, but this post doesn’t have any relevant that helps anyone find the issue. It’s just a full thread of people saying they have the issue. Linking likely won’t provide any new info.