Min Jekal

@mateuszdrab Sorry for late reply. It happened me when using `3.5`. Have you tried `gpt-4o-mini`?

Thanks for reporting an issue! In order to use same message history, [conversation_id](https://github.com/jekalmin/extended_openai_conversation/blob/1.0.1/custom_components/extended_openai_conversation/__init__.py#L159) should be passed to ConversationAgent. It seems Wyoming satellite devices don't pass `conversation_id` after first conversation. In...

@AJediIAm I'm sorry that I omitted to mention adding a custom repository in HACS. However, it will be registered to default repositories in HACS soon! I will let you know...

Thanks for your help! I indeed need to make documentation more readable and accurate. Please keep pointing out what needs to be done.

Please try [1.0.0](https://github.com/jekalmin/extended_openai_conversation/releases/tag/1.0.0) version. I just released it!

Fixed README https://github.com/jekalmin/extended_openai_conversation/pull/136/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L19

It's now available on hacs by default. Thanks for reporting an issue.

Currently, the exposed entity has only these [four fields](https://github.com/jekalmin/extended_openai_conversation/blob/1.0.0/custom_components/extended_openai_conversation/__init__.py#L245). - `entity_id` - `name` - `state` - `aliases` It is a good idea to add area to exposed entity. Another approach...

I will probably make `execute_service` to be called with one of `entity_id`, `area_id`, or `device_id` like commented [here](https://github.com/jekalmin/extended_openai_conversation/issues/86#issuecomment-1884971752). Hopefully gpt will execute service based on area_id if asked.

It looks good to me. As you did, I want the integration to be flexible so that users can customize as their needs. > What do you think of this...