Hi everyone,
I'm encountering a very frustrating issue with the new Google Home Script Editor and wanted to see if anyone else is experiencing this or has found a workaround.
The Problem: I'm currently unable to save any script I create. Every time I click "Save," I consistently receive an error message like "X errors found." What's particularly concerning is that even when I open a new script with the default template provided by Google and try to save it without making any changes, I get "3 errors found."
This happens for any script I attempt, including a simple automation to turn on my Midea 12,000 BTU DUO Portable Air Conditioner, model MAP14AS1TWT-C, when I arrive home. The errors consistently appear on the top-level lines of the YAML structure (e.g., metadata:, automations:, starters:, actions:).
What I've Already Tried (Extensive Troubleshooting): I've gone through a lot of troubleshooting steps, which lead me to believe this isn't a simple mistake on my end:
YAML Validation: I've had my custom YAML code validated by external YAML validators (like yamllint.com), and they confirm it's syntactically perfect.
Location/Presence Setup: I've meticulously checked all my Google Account location settings, my Pixel 6a's location permissions, and the "Presence sensing" settings in the Google Home app. I can confirm that "Presence: Home" (the "When I arrive home" trigger) is now an available option and works correctly when creating standard routines directly in the Google Home app (i.e., outside the Script Editor). I've also cleaned up old, unused devices from my account's location reporting.
Copy-Paste & Browsers: I've tried meticulously clean copy-pasting (using Notepad to strip any hidden formatting) and have tested across different web browsers (Google Chrome and Microsoft Edge) with the exact same negative results.
Script Helper Test: Even the YAML code generated by the "Help me script" feature within the editor (after a minor structural correction) still showed at least one error, indicating the editor itself is the problem.
"Scene" Workaround Attempt: I specifically tried the workaround suggested by other community members for Midea AC units, by creating a scene in the Smart Life app to control my AC and then attempting to call that scene using device.command.ActivateScene in the Google Home script. This also resulted in the same "5 errors found" parsing errors in the Script Editor.
Seeking Community Help: Has anyone else encountered this problem where the Script Editor itself seems unable to parse even its own default template, leading to persistent errors on the main structural lines? Is there a known workaround or a specific setting I might be overlooking that affects the editor's core functionality?
Any insights, similar experiences, or potential solutions would be greatly appreciated.
Thanks in advance for your help!
