Restart Detector #1
Replies: 6 comments 12 replies
-
|
I’ll consider |
Beta Was this translation helpful? Give feedback.
-
|
Can you provide the exact error log when it happened? |
Beta Was this translation helpful? Give feedback.
-
|
Does this help? |
Beta Was this translation helpful? Give feedback.
-
|
I suspect one thing: MMM-Sounds or other mic/speaker-related modules may interfere with the system. |
Beta Was this translation helpful? Give feedback.
-
|
Getting the same thing with MMM-Sounds commented out ''' |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for confirming |
Beta Was this translation helpful? Give feedback.
-
|
First, if I don't know exactly what caused the error, restarting it won't solve the problem. The problem will occur again; this time, it will go into an infinite loop because of the restart. I have a few more questions to clarify the symptoms.
[Test More]
{
module: "MMM-Hotword2",
position: "bottom_right",
config: {
verbose: true,
hotwords: [
{
hotword: "COMPUTER",
}
]
}
} |
Beta Was this translation helpful? Give feedback.
-
|
I have no problems until I add the following: MMM-NewsAPI I suspect it is something that happens when data is pulled for these. Will terminating it after a certain amount of delay work without the word being detected? |
Beta Was this translation helpful? Give feedback.
-
|
First, this kind of problem is very hard to reproduce, so the exact cause isn't easy to pinpoint. Based on your symptoms, a new detection cycle(right after onDetect: async ({ helper, error }) => {
const asleep = (ms) => new Promise(resolve => setTimeout(resolve, ms))
... // Your jobs
await asleep(3000) // <- wait 3 seconds before the end of `onDetect`
}I think 3 seconds would be enough to close the mic.
Maybe I can implement that feature, but in that case, after sleep, how can you reactivate this module? I'm considering introducing an |
Beta Was this translation helpful? Give feedback.
-
|
One more thing; If possible, can you show the front-end log also? (You showed me the backend log, but there is also browser-level log. You can check it with |
Beta Was this translation helpful? Give feedback.
-
|
I found this in the front end log |
Beta Was this translation helpful? Give feedback.
-
|
Thank you |
Beta Was this translation helpful? Give feedback.
-
|
The error occurs when the detector is in standby mode for a while. |
Beta Was this translation helpful? Give feedback.
-
I would also like to see this. I am running this on a PI4 compute and I also see the same thing and restarting the mirror is what fixes the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for your guys' inconvenience. I'm testing the new version, but as you know, this kind of issue is not so easy to reproduce intentionally, so I do not have enough certainty to release it. |
Beta Was this translation helpful? Give feedback.
-
It doesn't happen right away, but I will get an error "pvrecorder failed to read audio data frame"
My question is about restarting the detector when it errors. I can restart my mirror and then it works fine for a while but eventually the error returns.
I tried adjusting the soundThreshold thinking it was something the microphone was picking up causing the error but I couldn't get the error to stop,
My thoughts are just restart the detector but if the error could be resolved another way that would work as well
Beta Was this translation helpful? Give feedback.
All reactions