MyCroft 'activating' repeatedly when wake work not said and no conversation is near

Archive - Mycroft Project Archive - Former Random Mycroft Category
1

In the past few weeks, MyCroft has started activating (make the beep sound after the wake word is stated) when there is no sound in the room. It will do this repeatedly every 15 - 30 seconds for a while.

Anyone come across this?

If I say “MyCroft”, it still activates as normal and if I say “Mycroft stop” it will quit for a while.

2

My Mycroft activates sometimes when there is noise/speech in the room (but wakeword “hey mycroft” was not spoken), but I never observed that Mycroft activates when the room is “silent”.

3

Yeah, mine does that as well, but it it generally due to something on the TV or other audio source getting ‘close’ to the device.

I went to bed at Midnight last night and the device worked normally. I turned everything off and later heard it ‘beeping’. Here is a bit of the log entries showing it repeating it over and over…

2022-08-26 09:27:46.793 | INFO     |   852 | mycroft.client.speech.__main__:handle_wakeword:71 | Wakeword Detected: hey mycroft
2022-08-26 09:27:47.237 | INFO     |   852 | mycroft.client.speech.__main__:handle_record_begin:41 | Begin Recording...
2022-08-26 09:27:57.248 | INFO     |   852 | mycroft.client.speech.__main__:handle_record_end:49 | End Recording...
2022-08-26 09:27:59.604 | ERROR    |   852 | mycroft.client.speech.listener:transcribe:239 | list index out of range
2022-08-26 09:27:59.608 | ERROR    |   852 | mycroft.client.speech.listener:transcribe:240 | Speech Recognition could not understand audio
2022-08-26 09:27:59.855 | INFO     |   852 | mycroft.client.speech.__main__:handle_wakeword:71 | Wakeword Detected: hey mycroft
2022-08-26 09:28:00.307 | INFO     |   852 | mycroft.client.speech.__main__:handle_record_begin:41 | Begin Recording...
2022-08-26 09:28:10.307 | INFO     |   852 | mycroft.client.speech.__main__:handle_record_end:49 | End Recording...
2022-08-26 09:28:12.670 | INFO     |   852 | mycroft.client.speech.__main__:handle_wakeword:71 | Wakeword Detected: hey mycroft
2022-08-26 09:28:12.770 | ERROR    |   852 | mycroft.client.speech.listener:transcribe:239 | list index out of range
2022-08-26 09:28:12.777 | ERROR    |   852 | mycroft.client.speech.listener:transcribe:240 | Speech Recognition could not understand audio
2022-08-26 09:28:13.096 | INFO     |   852 | mycroft.client.speech.__main__:handle_record_begin:41 | Begin Recording...
2022-08-26 09:28:23.113 | INFO     |   852 | mycroft.client.speech.__main__:handle_record_end:49 | End Recording...
2022-08-26 09:28:25.475 | ERROR    |   852 | mycroft.client.speech.listener:transcribe:239 | list index out of range
2022-08-26 09:28:25.479 | ERROR    |   852 | mycroft.client.speech.listener:transcribe:240 | Speech Recognition could not understand audio
4

I wonder what the mic level says in the cli. A ding in silence would indicate you’ve cranked up the mic to NSA level. (or the house ghost trying to use mycroft, but ultimately fails)

5

house ghost is my favorite theory so far!

6

Mic level is still set at the default

7

house ghost is my favorite theory so far!

They`re big in privacy :laughing:

Mic level is still set at the default

Talking numbers. If it is idleing at 3000…