I set up Gemini with HA in romanian, and while sometimes on/off works, telling it to set the brightness rarely works. In the debug menu there is no device_id sent, but it gives back a success message
#Google AI not changing device brightness
opal current
i'm guessing the dimmable lights are exposed to Assist. have you tried the default conversation agent? does that work?
tiny jay
i'm guessing the dimmable lights are exposed to Assist. have you tried the defau...
yes, it does
opal current
then i'm guessing the issue is with the prompt for the Gemini integration or how it picks tools to run, but I lack the experience with Gemini to tell you how to fix it. maybe someone else will be able to help
you're using this integration, right? https://www.home-assistant.io/integrations/google_generative_ai_conversation/
tiny jay
yep
opal current
is there any way to check the LLM request logs and verify that the context/system prompt contains tooling for setting brightness?
tiny jay
If I tell it to change the brightness, it says that brightness was changed (it wasnt), and when I ask it to what value did it change the brightness, it says that it didn’t receive new information after dimming it
opal current
can you please add an issue about it on github?
tiny jay
I’ll try, thank you!
vestal sapphire
could try asking it what tool it is using
like I'll ask my LLM "What tool did you use and what arguments did you provide it with?"
near oriole
Here ask it which tool and which args it used
Because definitely it sent something wrong to HA, although using right method HassLightSet (?)
tiny jay
near oriole
Yeah that's wrong
opal current
not necessarily. the brightness needs to be in the 0-100 scale. can you ask for a lower value, like 70?
tiny jay
opal current
i'm assuming you have an area called/aliased "Living" and a light entity named/aliased "Light" "Living" in that area
tiny jay
the light itself is called living light and the area is living
it did get the brightness right though, it’s fully on
should i try with another name for the light?
tiny jay
oh it worked
telling it to set to maximum makes it complain about the error again
i think i found what’s wrong now
it tries to go up to 255, but the light only accepts up to 100
opal current
yes, which is why i said #1324789180710256781 message
tiny jay
yes, which is why i said https://discord.com/channels/330944238910963714/1324789...
i think at that point it was conflicting with the names too
opal current
it should work regardless of whether your light is called "living light"
tiny jay
it seems like hue also created a “living” light group (with just this light), maybe that could be it, i’ll exclude it and check
opal current
but who knows exactly what it's trying to make HA do and how it thinks it should work 🤷♂️ i still think the system prompt and integration need to be checked a bit, hence the request to add an issue
tiny jay
tiny jay
but who knows exactly what it's trying to make HA do and how it thinks it should...
i'll add it in a bit, thank you for the help!
as a workaround for now, I added in the template "The brightest value of a light can be 100, assimilate the value given with the scale given.", which works for setting a light's brightness
One last question, I'm new to issues, sorry, in what repo would this fit?