Not completly sure about this but the http server : 5055 might just be the port AlexaPi using to comunicate with the MagicMirror module MMM-AlexaPi . I do have the same message and it doesn’t prevent AlexaPi to work

You might have to activate the ssh through the sudo raspi-config panel. It should be under interfacing option. also you need to have ssh keys ssh-keygen It will ask you some stuff but you can let it empty

I’m quite new in Rpi and I had a loooooooooooooot of troubble with the sounds.

I believe there is a way to desactivate HDMI audio somewhere in the sudo raspi-config and forcing the 3.5 m jack in the Advanced Options and Audio

if that doesn’t work, I noticed that if you open alsamixer through a terminal, you can just change the value of the different channel but not “select” it as the default device to use.
You can, however, open the “Audio Device Settings” in “Preferences” within the main menu of the pi on the desktop and choose the “default card” to use and reboot.

Alternatively, you can creat a .asoundrc in your pi folder to describe what is the default card.(It will only concern the pi user though. You can make it globale if you use a /etc/asound.conf file instead). Those files probably doesn’t exist at first, you might have to create them.

But at the end of the day, I never trully succeded to use my usb sound card fully. Not sure why but in a lot of circumstances the driver crash or something if I play a sound with it and all my usb devices directly plug in the pi freez. so I end up configure the asound.file to say that my output is the normal output of the pi and my microphone is the external sound card.

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

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

@disakos I didn’t use it to run script, I wanted it specificaly for mmm-alexa. However I did check that the other module received the notification It send.
I did that by writing my own useless module that only print the notification it received.
You need in your main file a

notificationReceived: function(notification, payload, sender){
   //Whatever you want to do
},

This is different to “socketNotificationReceived” , socket notification receive only deal with your node helper file. But “notificationReceived” catch notification send from a module to another.

With that in mind, you can add the notificationReceived thing to the module you want to control with the voicecontrol module or add whatever you need to it if it already exist

Hello everybody, I try to use this voicecontrol module AND mmm-alexa in the same time (mmm-alexa need to be trigger by a notification. That where voicecontrol is interesting at the moment) but because both the module use the mic, it doesn’t work.
If I put only one module at the time no problem. Both of them in the same time, voice control doesn’t work.
How can I use the same mic for two different module ?

@theusu5k MMM-AlexaPi is module that show what https://github.com/alexa-pi/AlexaPi is sending to it so you need to install this as well.

As for MMM-alexa, it need to be activated either by receiving the right notification or by using a button. I’m not sure on which pins the button should go though

Hello, I wanted to use the MMM-alexa module but it need to be trigger and I do not have a button. The alternative is to send a notification to trigger it. Which is working (I tryed by sending a notification every 30 second and ask a question then).
The next natural step was to use a voice detection module to send the notification right ? So I cloned alexyak voicecontrole module. The idea of that module is that it would send a notification to others module when a specific keywork is detected .
Even though a bunch of error show up on the screen, I am able to make that module works. I can say “Alexa” and it does send the notification I chosed to other module.
So, both module work separatly.
But if I run both module in the same time, It doesn’t work anymore.
I noticed that If a module is using my mic, I can’t do an “arecord” on the terminal. So I’m guession that the MMM-alexa module prevent other programme to use it in the same time.

Is it a way to use the same mic with two different module ?

@undergroundauth This is weird, you said you did not add module and yet, your log talk about “modules/aiclient” wich isn’t a default module . In a fresh cloned repository, your modules folder should only have a “default” folder, a “node_modules” folder and a “Readme.md” file in it.
your error talk about a “modules/aiclient” so it’s clear that you have another folder named “aiclient” in it. And If there is an error on it, it’s also mean the magic mirror try to call it which mean you add a section on the “config/config.js” file in the magic mirror repository.
So this module must have an error in it that messed up the display.
do something like renaming the current config file and reset the default value on a new one.
the following command should do the trick

mv ~/MagicMirror/config/config.js ~/MagicMirror/config/old_config.js.save
cp ~/MagicMirror/config.js.sample ~/MagicMirror/config.js

If you didn’t mess with the config.js.sample it should reset your config.js to the default configuration.
Try to run the magic mirror next and tell us if something appear on the mirror.