Cursor opened in config/ + HomeAssistant MCP is exceptionally good.
I have blundered along with Home Assistant over the years, but it lit up with the above setup for me the other day.
For giggles, I had it set all the lights into a disco.
Next, we vibed a markdown file containing a to-do list of all my upstairs lights that are abstractly named by the different integrations.
I put an x against a name and it turned the light off.
Once I identified it, I wrote a better name next to it. It updated the system.
We vibed dashboards and routines.
The problem with Home Assistant is that once it works, you don't touch it for a year and are back to square one with the layers of concepts.
But I am left satisfied knowing I have backed up the conversation/context that we can pick up next year or whenever again.
right. My goof. That adds two more zeroes across all the math. More crazy, but I think in the realm of "maybe, if we squint hard." But my eyes are hurting from squinting that hard, so I agree that it's just crazy.
If fairness to toon, the alternative json your giving doesn’t include hints on structure.
Not sure LLM are more “tuned” to JSON.
That said, your general point holds that toon maybe unnecessary. Especially in the examples given. But perhaps plan text would suffice. Toon could be useful when automating inputs with many different shapes.
Yea exactly. The LLMs are tuned to natural language. I don't think anything will beat good ol' templating (a.k.a. plain text). In Go I do something like this:
// mytemplate.tmpl
Description="The following data is for the users in our application."
Format="id,name,role"
length=2
Data:
{{range .}}
{{.ID}}, {{.Name}}, {{.Role}}
{{end}}
This way you're able to change the formatting to something the LLM understands for each struct. The LLM might understand some structs better as JSON, others as YAML, and others in an arbitrary format. Templating gives you the most flexibility to choose which one will work best.
