Agree on the craziness.
On the efficacy: It one shot the automation from the example above, and it’s actually correct.
I tried more complicated usecase, and I would say it nailed it too. Even based on that vague description of mine, it figure out what the problem is (abrupt changes etc. - that is actually what bothers me), found the relevant lights, areas, after I nudged it considered only enabled entities, and proposed a better alternative, with an offer to create the automations in independent files. I expect that getting to that stage would take me at least a couple of hours and I am sure I would get many stupid small things like wrong ID or condition on time wrong here and there.
It can also just help me think about all of this very easily. I have like 100 automations, have like 40 bulbs, some led panels, many Shelly RGBW led strips for recessed lighting, … it’s a lot to keep in mind. LLMs can handle that for me.
As a precaution: Before the automation is written to HA can it do a sanity check do it is sure it doesn’t break anything like verifying the yank
I didn’t go that crazy yet, as this validation bit is indeed missing and I am too lazy to copy automations from backups etc. My expected workflow now is to let it create yaml files on my local disk and I copy it manually to the HA yaml automation editor and tweak the details. I would maybe let it use GitHub - wonderwhy-er/DesktopCommanderMCP: This is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities if it couldn’t get patches to the automations.yaml fine if I wanted to go full automated.