Right, I think this is the only way too. It’s kind of annoying though because the value can change so I would need to send it to send node helper every single time it change to keep it up to date.
Oh well.

Scratch that, the first example is working. It’s just that, because of the body black background, the text inside the iframe wasn’t visible. Justed needed to to change the css for the iframe to overide the background of the body

I sometime receive the same notification multiple time, like if the mirror run my module twice or something. It’s not happening every time.
As an example, I have a module that send a socket notification in the start function to the node helper to initialise something. let’s call it Notif_A.
l catch it the notification, make sure it’s Notif_A with an if statement, and When the node helper did it’s job it send back the data he got. still with a send socket notification Let’s call it Notif_B.
The odd thing is that I sometime got into the if that check if it received Notif_B twice in a row. Like if I got the notif twice.
The thing is, I only send Notif_A in the start function And I only send Notif_B if I received Notif_A.

I also noticed that the getDom function on some modules are callde 2 or 3 time in the raw at the begining (I checked with console.log)

So… what’s happening here ? Why is the notification is catched twice ? Is the start function runned twice for some reason ?

Romain can you please tell me how you were able to do that?

I did it, It wasn’t easy but it’s work, I can use voicecontrol and others voicecontrol driven module at the same time.
I had to change my /etc/asound.conf file again (yes, again. Because changing it already solve some of my issue on the past)

before my file looked like this:

pcm.!default { type asym playback.pcm { type plug slave.pcm "hw:0,0" } capture.pcm { type plug slave.pcm "hw:1,0" } }

Easy enough when you know what your doing (that wasn’t my case). this file is there to say what is the default device to playback and capture (A lot of application or software just use the default device so if the default configuration isn’t working for you, you need to change it for you.) In my cas ethe microphone is the “hw:1,0” and my speaker is the “hw:0,0”

That worked well when my microphone is used by one application at the time. However, not so much when it need to be used by multiple ones.
So my new /etc/asound.conf file is looking like this now

pcm.myTest { type dsnoop ipc_key 2241234 slave { pcm "hw:1,0" channels 1 } } pcm.!default { type asym playback.pcm { type plug slave.pcm "hw:0,0" } capture.pcm { type plug slave.pcm "myTest" } }

instead of directly say that my input device is the “hw:1,0” I say it’s “myTest”, which is describe above. myTest’s type is “dsnoop” , that’s whats allow the michrophone to be use by multiple application at the same time. The ipc_key is there with a random value because when I tested with arecord, it asked me to put one. The channels is there because it was on the documentation ( http://alsa.opensrc.org/Dsnoop ) >.> not sure what it does though.
And there you go, after that I could use two voice control things at the time

Hello, I try to make MMM-Alexa work (I don’t have a button, so I use another module to send the start recording notification for now).
But I got an exeption

Uncaught (in promise) Error: No Media Stream connected. :8080/modules/MMM-alexa//alexaRunner.babel.js:527 at Promise (:8080/modules/MMM-alexa//alexaRunner.babel.js:527) at AVS.startRecording (:8080/modules/MMM-alexa//alexaRunner.babel.js:525) at alexaRunner.notificationReceived (:8080/modules/MMM-alexa//alexaRunner.babel.js:4326) at Class.notificationReceived (:8080/modules/MMM-alexa//MMM-alexa.js:59) at sendNotification (main.js:87) at Object.sendNotification (main.js:454) at Class.sendNotification (module.js:301) at Class.notificationReceived (:8080/modules/shemur//shemur.js:43) at sendNotification (main.js:87) at Object.sendNotification (main.js:454) TypeError: Cannot read property 'byteLength' of undefined alexaRunner.babel.js:4468 at Promise (alexaRunner.babel.js:670) at AVS.sendAudio (alexaRunner.babel.js:601) at alexaRunner.avs.stopRecording.then.dataView (alexaRunner.babel.js:4435)

The color of the square is red.
I receive the following notification in that Order :
ALL_MODULES_STARTED
DOM_OBJECTS_CREATED
ALEXA_CREATED
ALEXA_TOKEN_SET (When I receive this one I send the ALEXA_START_RECORDING notification)
ALEXA_VAD_VOICE_DETECTION_START
ALEXA_VAD_VOICE_DETECTION_STOP (I receive this one immediatly after the start one)
ALEXA_RECORD_STOP
ALEXA_STOP_RECORDING

If I don’t send the alexa start recording notification, I have no exception so It must be related to the recording right ? I do have a mic and I can record a sound with arecord and play that sound with aplay or play in my terminal.
So why is the vad voice detection stoping immediatly ? why do I receive the “No media stream connected” exception ? Is the module dosn’t detect my mic ?
How can I solve this?

Little update: If I send the notification again (with about 30 second spacing) I am able to have an answer from Alexa.if I speak quickly enough at the moment the notification is send. So… I’m guessing the first time is for initialization and after that it’s ok to talk. Still not sure why I got exception but I guess it’s fine…
I need to find a way to trigger it with a wake up world now.
Also, Is there a way to see when it’s ok to talk ? (kinda like the MMM-AlexaPi module that show you the mic status and a little symbole that show Alexa is processing your request)

Ok, turned out It was a silly mistake, I forget to change the region in the MirrorMirror.js.
I don’t have that exception anymore.
However, even though the module launch without crash, nothing is happening. I say to my mic “Alexa on the wall” but nothing is happening. (The log doesn’t say anything). Any idea why ?

Oh ! Thanks !! It work