William Easton

Rolling over your datastreams should fix the issue with routing and there is now a PR up for the area issue

That's okay, I reproduced the area issue and have an open PR to resolve it. Will comment here once there's a new version to try

Fixing this will require bumping the minimum HA version to 2024.10 which I think we should wait to do

I believe this is an mcp inspector issue, if you look at the schema the schema is correct and the LLM is able to interact with it

That schema looks correct to me, what part looks incorrect?

From my testing we'll need to include: ``` hass.entity.attributes -> hass.attributes hass.domain -> hass.entity.domain hass.entity_id -> hass.entity.id hass.entity_id_lower -> hass.entity.id hass.object_id -> hass.entity.object_id hass.object_id_lower -> hass.entity.object_id hass.value -> hass.entity.value hass.entity.attributes.friendly_name...

It looks like maybe you cannot actually create an alias to a multifield so this may not be possible in the way I thought it might be

The 2.0 integration switches to using data streams by default and changes the schema and mapping to take full advantage of data types in Elasticsearch (among other things). You will...

> I jumped up to 2.0 after .7 went haywire and no matter what I do I cannot disable Verify TLS certificate (recommended) and Verify hostname matches server certificate. It...

Looks like fixing this on the 0.7.x branch would require bumping the ES7 dependency to 7.17.12 https://github.com/elastic/elasticsearch-py/releases/tag/v7.17.12 That may break compatibility with 7.11 to 7.16. As an alternative we could...