MMM-voice

[dogfeet]

@strawberry-3.141 i feel so stupid :facepalm:

[dmwilsonkc]

So I must say the MMM-voice module (also with Mykle’s Hello-Lucy enhancements) works perfectly on my mirror… when I don’t have my Mycroft AI running at start as well. It’s an Error: resource busy/unavailable referring to the Microphone. When I stop Mycroft/restart mirror it works perfectly, but then Mycroft gets the same error. Any suggestions?

I am thinking about building a MagicMirror skill for Mycroft, but Mycroft is Python not Java, and not a module. Would it be possible to send the same commands as Hello-Lucy (i.e. ‘HIDE_CLOCK’ for example) only use Websocket-client for Mycroft and send commands to the MagicMirror via socket.io?

If so, what would handle the socketmessage? Would it be communicated to the right module/s. Would I also need to create a fork of the MMM-voice module with code to handle the socketmessages from Mycroft?

Any guidance would be much appreciated!

Sorry, I should have also said my mirror is running on a RPi 3b running Debian Jessie on a 16gb sd.

[dmwilsonkc]

This post is deleted!

[strawberry 3.141]

@dmwilsonkc Error: resource busy/unavailable referring to the Microphone your microphone cannot be used by multiple processes at a time.

In your case I rather suggest to write an own module for mycroft instead of a fork, as you’re using a complete different stt engine.

If you’re interested in doing it via websockets you could have a look into mmm-mobile where i did something similar

[dmwilsonkc]

@strawberry-3.141 So I guess I kind of understood what is happening with the MMM-Mobile module of yours. I am very new to all of this and have only been dabbling in writing simple code up to now. It is much easier to build off of existing code that I know already works. If I could figure out a way to continuing to use your MMM-voice module and Mycroft at the same time, I would probably just do that, but as you pointed out both processes can’t use the microphone at the same time. Since Mycroft skills seem pretty straight forward to create, I thought eh… Why not attempt it.

I can create a Mycoft skill that will send ‘HIDE_CLOCK’ for example to socket.io. What happens when the Websocket-client for Mycroft connects to socket.io and sends ‘HIDE_CLOCK’? How would MagicMirror handle that?
Keep in mind, I have already added Mykle’s modifications from Hello-Lucy.

That’s part of what I can’t wrap my head around.

Thank you for responding and helping me!

[strawberry 3.141]

@dmwilsonkc the module has a socket like https://github.com/MichMich/MagicMirror/blob/master/js/socketclient.js#L11, basically its a channel with the module name, if you then send messages, the module doesn#t differentiate if its from mycroft or node_helper, as it isnt aware of multiple entities.

[dmwilsonkc]

@strawberry-3.141 Oh! Wow! That was awesome! You opened my eyes. I really am starting to understand better thanks to your incite. That makes perfect sense to treat Mycroft more like a remote-control than a voice-control because it handles the STT and can send socket messages to the MagicMirror. The MMM-Mycroft module would need to be very similar in function to your MMM-mobile module.

For example it could have a number of ways to control the MagicMirror:

        socket.on('SHOW_MODULES', () => {
            console.log(`${this.name}: Showing modules!`);
            this.sendSocketNotification('SHOW_MODULES');
        });

        socket.on('HIDE_MODULES', () => {
            console.log(`${this.name}: Hiding modules!`);
            this.sendSocketNotification('HIDE_MODULES');
        });

Just as an example to handle the messages sent to the socket.

If I’m reading your code right, you’re using a qr image to handle security. I hadn’t really thought about the need for security with something like this, but I guess that really should be a consideration. In your opinion, would requiring some kind of user password/key set in the config for both MMM-Mycroft module and the Mycroft MM skill be sufficient?

[strawberry 3.141]

@dmwilsonkc I did MMM-Mobile for my bachelor thesis to connect to the MagicMirror via mobile and be able to control and change config of it, the qr code was meant for pairing the devices, so not everyone is able to hook into my socket channel and send commands. But you have to be aware of the differences between socket notifications and normal notifications. socket notifications describe only the communication between your module and his node_helper (or in my case the mobile app, because I extended the socket server), but this gives you no communication with other modules like the clock. Therefore you need normal notifications which describe the communication between modules and the core MM. Be aware of that those notifications can only be sent via the module not the node_helper.

My workflow was like this. Node_helper extends socket server. Mobile send command to node_helper, then the node_helper sends it to the module and the module broadcasts it to all other modules.

https://github.com/MichMich/MagicMirror/blob/master/modules/README.md#thissendnotificationnotification-payload
https://github.com/MichMich/MagicMirror/blob/master/modules/README.md#thissendsocketnotificationnotification-payload

[dmwilsonkc]

@strawberry-3.141 Thanks for the clarification. The code that I copied came from the node_helper as you are probably aware.
One more question for you concerning extending the socket with node_helper: The code you have for the MMM-mobile module is written like:

appSocket() {
const namespace =
${this.name}/app;

    this.io.of(namespace).use((socket, next) => {
        const hash = crypto.createHash('sha256').update(socket.handshake.query.token).digest('base64');
        if (this.mobile.user && this.mobile.user === hash) {
            console.log(`${this.name}: Access granted!`);
            next();
        } else {
            console.log(`${this.name}: Authentication failed!`);
            next(new Error('Authentication failed!'));
        }
    });

    this.io.of(namespace).on('connection', (socket) => {
        console.log(`${this.name}: App connected!`); 

Mycroft in my case is on the same RPi so I realize the code will be different and you have created this code in a way to “pair” with the mobile device. Again, I am very new to writing code like this, but can you point in the right direction as far as how to extend the socket with the MMM-mycroft module’s node_helper.js? I do not understand how to extend the socket. Why is the code appSocket() {
const namespace =
${this.name}/app;

Would the same code work for MMM-mycroft module?

So my understanding, thanks to your help, to have a flow like this:

Node_helper extends socket server. Mycroft-core send command to node_helper, then the node_helper sends it to the MMM-mycroft module via this.send socketnotification and the MMM-mycroft module broadcasts it to all other modules via this.sendnotification.

I am just not sure how to code the Node_helper.js to extend the socket in my case.

You have been extremely helpful so far and I truly appreciate all of your help.

Also, since this is all done on the RPi, would the ipwhitelist even come into play here? My guess is no.

[strawberry 3.141]

@dmwilsonkc if you run your mycroft core from the node helper as i do with pocketsphinx in voice then there is no need at all to mess with the socket server