Good fences make for good neighbors…
OK team - looping back to this one for a moment and it’s important…
Remember up top where we described system limits and what happens when you hit tool 129? I have the first instance of this causing a problem.
It begat a discussion on whether there is a limit at all on Discord. Here’s the brass tacks for anyone I end up tagging on this issue.
NO HA ITSELF does not have a limit in the assist pipeline - that is 100% correct. (I traced the code this is fact) The ISSUE is
The OAI API call - the OpenAI API specifies 128 tools with descriptions of 1024 chars or less and tools slot descriptions of 128 chars or less (Sound familliar?)
SOOOO That means ANY OpenAPI style conversation agent is affected. (Pretty much all of them)
Which by transitive properties makes it HA’s problem. You have 129 tools your LLM QUITS. Period. That’s why this is a problem - it’s NOT a problem for Speech to Phrase. But we’re not doing Speech to Phrase here - we’re doing LLM.
So for the record Im re-iterating th elimits and WHY - NOW
Why is this an issue. SpotifyPlus just released an update that has a lot of built-ins to help voice… TO do so they added OVER 40 individual intents… (of 128) 30% of the total tool space. I hard noped out of SpotifyPlus immediately. It crashes Friday just by installing it.
Bugged here: Must consolidate intents. · Issue #185 · thlucas1/homeassistantcomponent_spotifyplus · GitHub
The dev isn’t happy about it but, I think he sees my point. If you’re trying to support voice you can’t kill it by installing the tool. And if you’re doing LLM be aware this is out there and they’re looking at how to work around it. (I just use Fes’ MusicAssistnat Scripts)