Open neo3 opened 5 years ago
The mute was turned off automatically and now the commands are back.
I have a DHT22 sensor connected to GPIO 23, could it unintentionally activate the mute?
Edit:
I updated the GPIOs pins in the config.yaml file and the problem did not occur again.
Is it possible to execute a custom command such as "sudo ./codesend 123456" of 433Utils (https://github.com/ninjablocks/433Utils) through GassistPi?
IMPORTANT NOTICE
If you do not complete the template below it is likely that your issue will not be addressed. When providing information about your issue please be as extensive as possible so that it can be solved by as little as possible responses.
FAILURE TO COMPLETE THE REQUESTED INFORMATION WILL RESULT IN YOUR ISSUE BEING CLOSED
Board and OS details:
Open a terminal and run
pi@afccasa:~ $ cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
processor : 1 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
processor : 2 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
processor : 3 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4
Hardware : BCM2835 Revision : a22082 Serial : 0000000088436fd4
pi@afccasa:~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)" NAME="Raspbian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" VERSION_CODENAME=stretch ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Describe the bug:
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
Attach the log file named Gassistpi.log
Log file can be found in /tmp/ directory
2019-10-28 18:21:14,492 : DEBUG : Making request: POST https://accounts.google.com/o/oauth2/token 2019-10-28 18:21:14,505 : DEBUG : Starting new HTTPS connection (1): accounts.google.com:443 2019-10-28 18:21:15,032 : DEBUG : https://accounts.google.com:443 "POST /o/oauth2/token HTTP/1.1" 200 None 2019-10-28 19:17:04,869 : DEBUG : Making request: POST https://accounts.google.com/o/oauth2/token 2019-10-28 19:17:04,887 : DEBUG : Starting new HTTPS connection (1): accounts.google.com:443 2019-10-28 19:17:05,388 : DEBUG : https://accounts.google.com:443 "POST /o/oauth2/token HTTP/1.1" 200 None