Device registration is reported unregistered, while it is registered OR it core dumps #313
Comments
Yes same issue for me maybe there is an issue with Google Cloud. I hope someone will find the solution or at least try to help :) |
Same issue here |
Which version of the library are you using? 1.0.0 or 1.0.1? |
I believe version 1.0.0, as it's in the pip list;
However, no update is available it seems;
At least not from the default pip command. Edit: quick search found that 1.0.1 is available, trying to install that now. |
Trying to install 1.0.1 results in these;
While this is the install
|
Manually replacing the files in the install with those from Seems to have bypassed the issue. At least no core dumps. |
Ok so I noticed something weird... Pushtotalk is working fine actually but hotword isn't, I still have this core dumped issue. I only want to use hotword not pushtotalk :( |
Yes I have same issue when using Here is my detail issue : https://stackoverflow.com/a/54209321/1802624 Besides that using our own version of |
(env) omprakash@omprakash:~$ googlesamples-assistant-hotword --project-id assistant-60d3a --device-model-id assistant-60d3a-assistant-6c4k5s |
@redopm try to clone the project from https://github.com/googlesamples/assistant-sdk-python and work directly with the hotword.py solving my issue. Here you can download and modified the hotword.py file : https://github.com/googlesamples/assistant-sdk-python/tree/master/google-assistant-sdk/googlesamples/assistant/library |
I am clone this directory but it cann't be resolve. i am cloning in my virtual environment created in python. |
if i run this (env) omprakash@omprakash:~/env$ |
Did you already updated all the required packages?
And did you try to execute with this way after clone the project and execute the hotword.py?
|
When i run this i found error again Current thread 0x00007f1bc8ff8740 (most recent call first): |
I had the same SEGV issue. It seems that string/buffer operaiton code needs to be fixed in libassistant_embedder.so which is not open source. (env) ubuntu@bionic:~/work/google/assistant-sdk/project$ gdb env/bin/python3 Program received signal SIGSEGV, Segmentation fault. (env) ubuntu@bionic:~/work/google/assistant-sdk/project$ pip list cachetools 3.1.0 |
I have segmentation fault on orange pi zero too with ubuntu! |
guys any update on this? I am running orange pi zero armbian but get segmentation fault |
Hi, I have some news about this issue. First step is to update the hotword.py file, which adds the following:
After that I was able to follow the issue up to assistant.py. Something wen wrong here, but by now I don't know what:
The error is about this: Any ideas? |
For what I can see, the commands use different technologies:
Could it be possible that googlesamples-assistant-hotword hasn't been ported to gRPC, yet...? |
Well, sometimes is better to hack what is working. So I modified googlesamples-assistant-pushtotalk to avoid to stop for an 'enter' to record. In the file env/lib/python3.7/site-packages/googlesamples/assistant/grpc/pushtotalk.py you can comment the following lines:
Now you have the assistant listening all the time. It's not the same, but it could work in some cases! |
For those asking about this issue, seems this is a dead way. As discussed on #356, #357 and #358, the use with the old library is deprecated and this affect to hotword. The new Goggle Assistant Service works over gRPC and right now there a discussion on how to adapt the pushtotalk working feature to make something like hotword. IMHO, this issue can be closed. |
but is the solution in gRPC available yet? |
The initial issue reported is solved. The hotword recognition is not yet solved, but this is other issue. :) |
check this post for workaround and clarification from google |
So, as I said before, the hotword recognition is not yet solved and seems that have to be achieved with a 3rd party tool. Is better to close this issue. |
Long time ago I use https://github.com/Kitt-AI/snowboy to trigger push-to-talk (c++ ver) on Rasp pi zero. Look like it's the only working option right now. |
When trying the googlesamples-assistant-hotword bit, the assistant does not work at all. This is the result of the hotword command;
And this, if the project_id provided, when it segfaults;
Howevere, the devices, according to the tool, is registered:
Also, when it only complains, not segfaults, the assistant is not working, no input is gathered on the mic.
When running the push-to-talk version, it does work, but it then uses an other device id;
I've rebuild the entire system from scratch twice now. So I believe it's reproducible.
The text was updated successfully, but these errors were encountered: