Log files are not created

aandroide commented 5 years ago

Describe the bug:

I have configured the trigger pin in config.yaml but nothing happens when the button is pressed.
how much I try to close with ctrl + c it starts to listen in loop

Did you go through or search the issues section to check if your issue was already discussed (either currently open issues or closed issues).

Yes

2. Is the issue related to assistant installation ?

No

If answer to question 2 is Yes, then paste the contents of the terminal below.

If answer to question 2 is No, then proceed further.

3. Does the assistant service start normally?

Yes

4. Is the assistant service restarting automatically?

No

If answer to question 4 is Yes, then paste the contents of the terminal below.

If answer to question 4 is No, then proceed further.

Manually start the assistant. For guidelines to start the assistant manually refer this

Paste the command below, that crashed the assistant

Paste the contents of the terminal below

[02d41c38] pulse audio output error: PulseAudio server connection failure: Connection refused
[02d1cd20] pulse audio output error: PulseAudio server connection failure: Connection refused
AIY-HAT
Initializing GPIO 25 for assistant activity indication

Attach the log file. Log file can be found in /tmp directory. Remeber to copy your log file before shutting down or restarting the Pi.

moreover, the log file is not created

shivasiddharth commented 5 years ago

You need to disable custom wakeword for pushbutton to work. Its either or. Either the pushbutton trigger or custom wakeword. You cannot have both.

aandroide commented 5 years ago

Wow, if I had read it in the readme I would not have opened the problem. perhaps it would be necessary to add this clarification

shivasiddharth commented 5 years ago

I thought i had it in the README. Thanks for notifying i have now added it under the custom wakewords section. https://github.com/shivasiddharth/GassistPi/blob/master/README.md#custom-wakeword-activation

aandroide commented 5 years ago

about the gassistpi.log file that is no longer created after the project update, do you have any suggestions?

shivasiddharth commented 5 years ago

I guess we lost the log after the custom wakeword thing. Thats because we are not catching errors from threads. Will fix it in the next update.

fragolinux commented 5 years ago

I guess we lost the log after the custom wakeword thing. Thats because we are not catching errors from threads. Will fix it in the next update.

still no logs in gassistpi folder

shivasiddharth commented 5 years ago

@fragolinux , @aandroide Has fixed this now.

shivasiddharth / GassistPi