#Bad experience with M5Stack Echo

1 messages · Page 1 of 1 (latest)

near eagle
#

Was able to setup M5Stack Echo and enabled Home Assistant Cloud trial period for 1 month.
So far it's useless.
I decreased from 180 entities to only 30
I searched how to ask the commands https://github.com/OHF-Voice/intents/tree/main/sentences/nl
When I say the wake word, the echo starts to blink blue but then it remains blinking blue or after a long time it responds that it doesn't understand or something.
Checked Voice Assistant debug and the command I said was almost never understood correctly.
What to do?
The audio response I get is almost interrupted, so maybe that's why my command is also not understood.

GitHub
intents/sentences/nl at main · OHF-Voice/intents

Intents to be used with Home Assistant. Contribute to OHF-Voice/intents development by creating an account on GitHub.

void tree
#

can you post a screenshot of your voice pipeline setup?

#

settings -> VA -> click on your pipeline

#

this should be the pipeline that is assigned as the assistant for the device which you can see in its device page

near eagle
void tree
#

ok, you a mixing languages it seems. that's probably not going to help it understanding

near eagle
near eagle
void tree
#

ok so the conversation agent is the "brain" which is set to dutch. so it is running against dutch "intents" the STT being in flemmish means that its sending flemmish against the dutch intents which i guess is an issue

near eagle
#

Changed all to Dutch and tried 5 commands in Dutch but nothing works

void tree
#

ok, on the VA settings page if you click the menu of your pipeline and go to debug

near eagle
#

I say something and the LED becomes RED on the M5Stack

void tree
#

can you show me a screenshot of the AE's device page?

near eagle
#

I just say in Dutch: Close and then the name of a cover. And this entity is set as cover and I say the name of the Alias I made

near eagle
void tree
#

something like this

near eagle
#

It worked 1 time out of maybe 40 trials

void tree
#

okay, I was mostly checking firmware version. if you try other times, and look at the debug traces of them does it show anything different?

#

also, are you able to test it in english? english tends to work better (there is more data for it)

near eagle
#

Seems useless. Changed all to English. Add an alias to my cover 'backdoor'. Say 'Close Backdoor', 'Close cover backdoor'... Doesn't work

void tree
#

it could be getting confused between "backdoor" and "back door"

#

the default agent can be a little "dumb"

near eagle
#

I say backdoor in 1 smooth word...

void tree
#

but the STT is detecting it as 2

near eagle
#

Yes, I see, any better translation agent?

void tree
#

try adding both "back door" and "backdoor" as aliases and see if it helps?

#

this is the kind of thing that a llm based agent can help with as it handles "knowing what you mean"

near eagle
#

I said 'Close the backdoor'....

void tree
#

between the limited microphone capabilities of the AE, STT not being perfect, and the rigid intents its going to be a bit shakey

near eagle
#

Can an llm based agent be installed as HA integration?

void tree
#

yes, do you have any llm setups currently?

near eagle
#

Sorry, llm stands for?

void tree
#

large language model

#

or "AI"

near eagle
#

no, I just started by buying this tiny thing and started to play with it

#

I also have a Google Nest at home but I belive then I have to use the Google sentences

void tree
#

HA supports various setups. using openai/gemini apis or local setups from ollama

#

if you expose your devices to the google nest you should be able to control them from that which may help get to your goal.