Read the statement by Michael Teeuw here.
MMM-AssistantMk2
-
@sgopala Thank you!! I’ve fixed. I think I had assumed that was the last field of ESSENTIALS parts, so I might have missed the last comma.
-
@sean Thanks a ton for your modules sir, you are a rockstar. But somehow I liked the previous version because of the following reasons:
(i) there is a delay after the hotword detection in the new version
(ii) the hotword detection hangs after 1st interaction with the assistant
(iii) the output window (iframe) was better sized and placed, too small on this versionRequest to please see if these are feasible.
Once again, thanks a lot for this lovely module.
-
@sgopala
You can always checkout the older version from github (use1.x.x-final-snap
)
And for the issues;- some delay is added intentionally to avoid possible collision. I’ll modify it could be customizable in next patch.
- output size could be controllable with
screenZoom
field.
Thanks.
-
@sgopala Thanks for pointing this out. ;)
@sean I keep getting either a black MM screen or the ‘config.js’ message.
At this point I prefer to work with a config with MMM-AssistantMk2 only and no other modules until everything is working 100%.
If you could help me by giving please a look at the below config? :)
Please note that I am trying to use0:0
as device Id.
-
@cr4z33
Try this.{ module: "MMM-AssistantMk2", position: "top_right", config: { record: { recordProgram: "arecord", device: null // or device: "hw:0,0" }, play: { playProgram: "mpg321", }, } },
-
@sean sweet i added a bunch of outher modules and now get a memory error how do i update to the newer version so hopefully these errors sort themselvs out
-
!!! { audioFormat: 1,
endianness: ‘LE’,
channels: 1,
sampleRate: 16000,
byteRate: 32000,
blockAlign: 2,
bitDepth: 16,
signed: true }
mmap() failed: Cannot allocate memory
Failed to create permanent mapping for memfd region with ID = 3246537711
Ignoring received block reference with non-registered memfd ID = 3246537711
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Protocol error[…/deps/mpg123/src/output/alsa.c:165] error: cannot open device default
Error: open() failed: -1
at Speaker._open (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/speaker/index.js:106:13)
at Speaker._write (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/speaker/index.js:183:23)
at doWrite (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/readable-stream/lib/_stream_writable.js:428:64)
at writeOrBuffer (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/readable-stream/lib/_stream_writable.js:417:5)
at Speaker.Writable.write (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/readable-stream/lib/_stream_writable.js:334:11)
at Reader. (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_helper.js:287:17)
at emitNone (events.js:111:20)
at Reader.emit (events.js:208:7)
at /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/wav/node_modules/readable-stream/lib/_stream_readable.js:934:16
at _combinedTickCallback (internal/process/next_tick.js:131:7)
Some error happens. Try again.
Whoops! There was an uncaught exception…
TypeError: this.sendSocketNotification is not a function
at Reader. (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_helper.js:296:20)
at emitNone (events.js:111:20)
at Reader.emit (events.js:208:7)
at /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/wav/node_modules/readable-stream/lib/_stream_readable.js:934:16
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)ya looks like speaker error
-
@Sean
If I usenull
I get a black MMM screen.If I use
hw:0,0
I get the config.js message.Finally if I use
"hw:0,0"
(with quotes) I get a black MM screen again.:smiling_face_with_open_mouth_cold_sweat:
-
@cr4z33
Ok… Are you using Telegram?
I can give more direct help on Telegram. My id is@eouia
.
Here is not so good place to talk these things. -
@Sean
Yep adding you right now. :)