Latest version has the fix btw 
Just saw v 2.1.0 - AI assisstant app is not aivailabe I guess?
It is, as a test version:
Thank you, will test immediately 
It works great. What I would like to improve is the screen duration time when displaying the AI answer. I would prefer to dismiss the screen manually.
Please let me know if you used one of the (untested) models. I am testing with Gemeni currently, and i’m very happy with the results. Also the AI Assistent app is a “Generic“ App that other app devs can interact with if they like.
I am testing with Gemini as well because I already had an account.
Ok, I see, that works
Would it also be possible to integrate Perplexity voice chat?
probably, is that something you would use? i can’t subscribe to all the AI’s to test. If you are willing to test i’ll make it happen.
Yes, this is the standard AI i use. Would definitely test it.
One thing you maybe want to improve (not AI related): some sensor information is not localized; always English, eg „on“ instead of German „ein“, „off“ instead of German „aus“.
Perplexity has no STT API (Speech to text) , that is what the UC remote uses.
Or did you meant you would like support in the AI app for Perplexity?
I have to investigate if its possible and if it’s feasable. ill let you know
Please test version 2.2.0, Just implemented localization 
I meant support in the AI app for Perplexity
Just installed 2.2.0 
this is everything I ever wanted for UC Remote I always wanted - great job!!!
@Niels would it be possible please to add system instructions option to settings and then when you call api to use that?
example:
model = genai.GenerativeModel(
model_name=“gemini-2.5-flash”,
system_instruction=”You are an expert at transcribing audio into text. The speech in the recording is Dutch. Transcribe verbatim and preserve punctuation.”
@Niels: Your app provides the following AND-cards for the remote:
I am al little bit confused on their meaning.
Can you elaborate on what the difference is between them? When are they true/false?
Does ‘turned on’ e.g. indicate whether the device is physically turned on or perhaps if the screen is turned on?
There is also an ‘on/off’ tag provided. Is seems that this reflects the standby state of the remote, which might be confusing as there is also the ‘turned on’ flowcard (for which no separate status tag is available), which is different than the ‘is in standby’ card.
I noted that, when selecting the ‘Invert’-option to invert the said flowcards, the title of the ‘is in standby’ and ‘is connected’ flowcards does not change to ‘is not in standby’ and ‘is not connected’. Though it seems their behavior is inverted.
Yes, this is on my ToDo list. so stay tuned. It will be named system prompt or something along these lines.
You can pretty much interchange them in usage, the difference is mainly the connected/disconnected reason. Where the device is marked in standby when we told it to go into standby or when the remote tels homey it goes to standby.
I’m trying to find the right one to check if the remote has been powered down (switched off) completely (so not in stand by, while powered on). I find that the ‘is connected’ card works best for this purpose, as there is no connection possible to the remote when powered down.
