You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It makes sense that the recommended value would be 1 in case the Control option is selected. But when there is no need in control, there is no reason to limit this value. In addition, It would be great to be able to experiment with the impact of larger Temperature values even when control is permitted.
Another awesome addition would be to be able to override the preset value when explicitly calling "Conversation.Process" in an automation, but this already falls under a feature request rather than a bug.
Hey there @tronikos, @IvanLH, mind taking a look at this issue as it has been labeled with an integration (google_generative_ai_conversation) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of google_generative_ai_conversation can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign google_generative_ai_conversation Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
The problem
It makes sense that the recommended value would be 1 in case the Control option is selected. But when there is no need in control, there is no reason to limit this value. In addition, It would be great to be able to experiment with the impact of larger Temperature values even when control is permitted.
Another awesome addition would be to be able to override the preset value when explicitly calling "Conversation.Process" in an automation, but this already falls under a feature request rather than a bug.
API reference:

Google AI Studio:

What version of Home Assistant Core has the issue?
core-2025.3.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Google Generative AI
Link to integration documentation on our website
https://www.home-assistant.io/integrations/google_generative_ai_conversation
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: