home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.9k stars 30.12k forks source link

Assist with ChatGPT and Gemini Error 400 String Too Long #124440

Closed txwindsurfer closed 1 month ago

txwindsurfer commented 1 month ago

The problem

Assist with both ChatGPT and Gemini were working a few weeks ago but are now broken with a 400 Error indicating the string is too long -- expecting max 64 characters but received 66 characters. Sorry, I had a problem talking to OpenAI: Error code: 400 - {'error': {'message': "Invalid 'tools[34].function.name': string too long. Expected a string with maximum length 64, but got a string with length 66 instead.", 'type': 'invalid_request_error', 'param': 'tools[34].function.name', 'code': 'string_above_max_length'}}

If I set Control Home Assistant to No then both ChatGPT and Gemini work but obviously no Home Control. With over 300 entities exposed, I am not sure where to start.

What version of Home Assistant Core has the issue?

core-2024.8.2

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

Assist

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.google_generative_ai_conversation

Source: components/google_generative_ai_conversation/conversation.py:320
integration: Google Generative AI (documentation, issues)
First occurred: 1:46:47 PM (1 occurrences)
Last logged: 1:46:47 PM

Error sending message: <class 'google.api_core.exceptions.InvalidArgument'> 400 * GenerateContentRequest.tools[0].function_declarations[34].name: Invalid function name. Must start with a letter or an underscore. Must be alphameric (a-z, A-Z, 0-9), underscores (_), dots (.) or dashes (-), with a maximum length of 64.

Additional information

No response

txwindsurfer commented 1 month ago

A dead Z-wave node was exposed and was causing the error.