William Easton

> Since my last update of HA, I have quite a similar error, the logs are a little bit different. >  > My current version : >  >...

Hi, we have published a new pre-release of the v1.0.0 branch that should resolve this issue. Can you switch to that version? For others watching this issue, please note the...

Staying on the 2.0.0 branch is fine too :) Swapping back while pointed to the same destination ES cluster may complicate things

Can you enable debug logging and grab the error log that occurs (viewable in HomeAssistant logs) and provide it here? We've made some changes to how the auth is verified...

I had this issue previously with the old version of the integration too. I'll try to find some time in the next couple days to look closer. Also looks like...

Will require 2024.11: https://github.com/home-assistant/developers.home-assistant/pull/2435/files The config entry is apparently already available under `self.handler` and the entry id is available under `self._config_entry_id`

Could we have this support multiple nameservers right away, or is the intention to add that in a later revision? Any thoughts on TCP transport?

looking at this again i think it takes an LLM param which itself does take request params, though i guess it would be nice for it to take a routing...

In one of my other projects I've just given agents a list of tools they are allowed to run and I only hook up the servers required to provide that...

Yeah that sounds like a great place for it. On a side note, one of the things I'm trying to put together is a "best practices analyzer" that orchestrates (parallel?!)...