<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[MMM-Hotword Listening, but not doing]]></title><description><![CDATA[<p dir="auto">Re: <a href="/topic/8412/mmm-hotword">MMM-Hotword</a><br />
Hello, and hopefully hello to Sean, if you see this.</p>
<p dir="auto">I have Hotword installed with MMM-AssistantMk2 on the latest build of MM2 (2.90), running on an RPi3.  Everything except Hotword is running great!  At one point, before upgrading everything, I had all this working fine, but now my pm2 logs show</p>
<pre><code>0|mm  | [HOTWORD] Detector starts listening.
0|mm  | [HOTWORD] Final Result: { detected: false }
0|mm  | [HOTWORD] begins.
</code></pre>
<p dir="auto">over and over in a loop… No attempt on my part gets it to recognize anything.  I even removed all modules except Hotword (and the clock so I’d know it was running) and I get the same results.</p>
<p dir="auto">I have deinstalled and reinstalled Hotword via the automatic script And the manual method. Installation appears to be fine, and components are there.  Using this config:</p>
<pre><code>{
			module: "MMM-Hotword",
			config: {
				chimeOnFinish:"resources/dong.wav",
				mic: {
				  recordProgram : "arecord",  
				  device        : "plughw:0",
				},
				models: [
				  {
					hotwords    : "smart_mirror",
					file        : "smart_mirror.umdl",
					sensitivity : "0.5",
				  },
				],
				defaultCommand: {
				  notificationExec: {
					notification: "ASSISTANT_ACTIVATE",
					payload: (detected, afterRecord) =&gt; {
					  return {profile:"default"}
					}
				  },
				  afterRecordLimit:0,
				  restart:false,
				},
			  },
		},
</code></pre>
<p dir="auto">The line for “device        : “plughw:0”,” is because I’m using the Google HAT and mic/speakers/etc.  That’s not the issue, I don’t think, because the HAT has worked fine in the past with Hotword.</p>
<p dir="auto">Please tell me I’m an idiot and that this is an easy fix I’m just not seeing right now.</p>
<p dir="auto">Thanks, and thanks to Sean for all the good work on this module!</p>
]]></description><link>https://forum.magicmirror.builders/topic/11512/mmm-hotword-listening-but-not-doing</link><generator>RSS for Node</generator><lastBuildDate>Wed, 13 May 2026 09:54:34 GMT</lastBuildDate><atom:link href="https://forum.magicmirror.builders/topic/11512.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 03 Nov 2019 04:43:16 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to MMM-Hotword Listening, but not doing on Tue, 26 Nov 2019 09:58:45 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nakedrabbit" aria-label="Profile: nakedrabbit">@<bdi>nakedrabbit</bdi></a><br />
I’ll launch AMK2 ver 3. in a few weeks. (I hope. I have not enough time nowadays). In that version, this annoying dependency for sound output will be deprecated, so you may use your HAT without issue. Wait a while and sorry again for your inconvenience.</p>
]]></description><link>https://forum.magicmirror.builders/post/65140</link><guid isPermaLink="true">https://forum.magicmirror.builders/post/65140</guid><dc:creator><![CDATA[[[global:former-user]]]]></dc:creator><pubDate>Tue, 26 Nov 2019 09:58:45 GMT</pubDate></item><item><title><![CDATA[Reply to MMM-Hotword Listening, but not doing on Mon, 25 Nov 2019 20:22:04 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nakedrabbit" aria-label="Profile: nakedrabbit">@<bdi>nakedrabbit</bdi></a> I have the same issue I think but I’m using an all-in one PC and its internal sound card. Every once in a while, it stops processing and gets into a loop like you’ve shown above</p>
]]></description><link>https://forum.magicmirror.builders/post/65102</link><guid isPermaLink="true">https://forum.magicmirror.builders/post/65102</guid><dc:creator><![CDATA[Keith]]></dc:creator><pubDate>Mon, 25 Nov 2019 20:22:04 GMT</pubDate></item><item><title><![CDATA[Reply to MMM-Hotword Listening, but not doing on Sun, 03 Nov 2019 18:39:36 GMT]]></title><description><![CDATA[<p dir="auto">@Sean<br />
VERY interesting!</p>
<p dir="auto">FWIW, there was NO issue with HAT previously!  That’s why I thought it would be OK going forward with it.  Dammit, I should have left well enough alone and not upgraded!  Too late now, everything’s changed!</p>
<p dir="auto">I don’t know enough about ALSA to fight my way out of a wet paper bag. But it is worth figuring out, because I’m not the only one who picked up a cheap HAT for $5 and figured it would work - the form factor is nice.</p>
<p dir="auto">So I guess I’ll take this on and report back when I work it out.  OR blow it off, connect some externals and get my Mirror done.  Either way, thanks so much for the suggestion!</p>
]]></description><link>https://forum.magicmirror.builders/post/63747</link><guid isPermaLink="true">https://forum.magicmirror.builders/post/63747</guid><dc:creator><![CDATA[nakedrabbit]]></dc:creator><pubDate>Sun, 03 Nov 2019 18:39:36 GMT</pubDate></item><item><title><![CDATA[Reply to MMM-Hotword Listening, but not doing on Sun, 03 Nov 2019 13:00:25 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nakedrabbit" aria-label="Profile: nakedrabbit">@<bdi>nakedrabbit</bdi></a><br />
There is an issue about HAT.<br />
Usually, VOICE HAT is a 2-in-1 kit, so commonly the same device name is assigned to mic and speaker. It would be not the issue at all in usual usage. People can <strong>record-then-play</strong> by turns.</p>
<p dir="auto">My modules are working like this;</p>
<ol>
<li>Opening Mic and Recording</li>
<li>After time or silence, closing the mic</li>
<li>Some processing</li>
<li>Opening the Speaker</li>
<li>Streaming output to the speaker</li>
<li>After time or EOS, closing the speaker</li>
<li>repeat the whole process</li>
</ol>
<p dir="auto">Ideally, the HAT should have no issue with my module, but…<br />
Physically Step 2. (closing Mic) could take some time to finish closing. (not predictable)<br />
So, sometimes Step 2. will be started before but ended after step 4. With separated Mic and Speaker, It will not be the problem at all.<br />
But with the HAT, This could be an issue. <strong>Closing Device:0(mic)</strong> is ended after <strong>Opening Device:0(speaker)</strong> and it will make <strong>Re-closing Device:0(speaker)</strong>. Vice versa would be same.</p>
<p dir="auto"><strong>Suggestion</strong></p>
<ul>
<li>give different device names to the mic and speaker.</li>
</ul>
<p dir="auto">As far as I know, it could be done by ALSA configuration. However, I’m not that kind of expert so cannot give you exact instruction or example. sorry.</p>
]]></description><link>https://forum.magicmirror.builders/post/63732</link><guid isPermaLink="true">https://forum.magicmirror.builders/post/63732</guid><dc:creator><![CDATA[[[global:former-user]]]]></dc:creator><pubDate>Sun, 03 Nov 2019 13:00:25 GMT</pubDate></item></channel></rss>