Unsolved Assistant taking a long time to post result.
Hello! Hope you are well and that it’s not to much stress for you as the holidays are coming up.
I’ve been having some issues with the assistant.
Suddenly it started to wake up for everything. So I tweaked the sensitivity and the microphone volume a bit and that worked. But now, a couple of weeks after, it takes for ever to come up with a reply.
Jarvis command works and it starts listening.
I takes my voice command and stops listening.
Then it takes a long time to post the result of my command. Before it was only a couple of seconds.
Set the sensitivity back to “null”
Restarted the mirror
Restarted the PC it’s running on.
Tried both 2.4 and 5.0 wifi (the 5.0 signal is weaker were the mirror is)
Checked the system monitor so it’s not a CPU or RAM issue.
NPM run update
I tried searching the forum but didn’t find a issue like this one.
Hi, Sometime Assistant SDK search result can take a lot of time in this case:
- Assistant SDK Server have many latency (from pi <-> to Assistant SDK Server)
- Wireless 5Ghz have (sometime) many latency (confirmed in my pi and only on it) (from pi <-> to internet)
- another module have an infiny loop (bad coding part when an error happen, for example)
Note: EXT-Internet can display ping time from your prefered website and can help to see real ping time
Thank you for the answer.
I should add that also “stop” command takes a long time to execute. So if, for example, I’m playing Spotify and do Jarvis - Stop to stop everything, that command takes a long time as well.
If i send the request from the gateway it goes through and fast as usual.
I saw that I actually do have an error when I check the Terminal Output but I think it has been there all along. But I can’t see what is causing it.
I have until now only been using “Jarvis”. But I tried porcupine and “Ok, Google.” and it was the same. Takes forever between taking the command to executing.
Tried turning off the Pihole.
Speedtest - showed nothing out of the ordinary.
Ping to google DNS no issues.
Hello and Happy New Year!
I can also add that I have updated the mirror and rebuilt some of the modules and removed ones that weren’t being used.
The assistant still takes a good long while to respond. It listens fine. It stops listening fine. Then it takes 30 sec to post the result of my command. Like I said earlier. When I do it by text from the Gateway it posts the result after less than a sec.
I should also mention that I don’t use a Pi. I use a Elitebook with Ubuntu on it. It worked fine at first. I don’t know what changed.
Well. I’ve checked everything I can on my end.
The delay seems to be Google. If I check the Assistant API the average latency it’s 13 seconds which seems to be right. I don’t know if there is anything I can do about that. But I would like to know if someone else is experiencing the same.
Hi, I am experiencing the same. About 11-13 seconds to execute the command. In the previous version, it was almost instant but now it takes more time. Not a big issue but just letting you know. .
Thank you for replying. “Glad” i’m not the only one. Like you said, not a big issue, just a bit irretating. The main use is the information on the screen so… We’ll just have to see if it gets better later on.
Hi everyone, I have the same experience here !
It happens to me too but not always, perhaps in my case it could be an unstable wifi connection?
I’m having another problem with Jarvis, sometimes it activates on its own, but the problem isn’t just this, every now and then it stops responding and the speakers emit a “TAC…TAC” continue and I’m forced to restart MM. Looking in the log I don’t find any problems…What could it be due to?