For a first quick demo:
https://streamable.com/5s6bn

Just to let you know, i managed to integrate the assistant application as a python child process running in is own virtualenv which is created using npm, limiting the amount of installation steps required by users.

Now the fun part starts, handling commands from the assistant and implementing fancy animations :)

Thanks for the info.
I do indeed already use MMM-RemoteControl for manual control and plan on using it for the actual control of the mirror.
Concerning communication between the processes i’m looking at letting the js module spawn the python google assistant as a child process and communicate using process piping.
This would make it way easier to run the module as the user would not need to manage multiple applications.

Hi all,

I am aware that there are already a number of google assistant modules.
However these modules lack the ability to actually interact with magic mirror.
I would like to be able to perform actions like:

• Turning display on/off
• Setting brightness
• Show/hide modules

I have some experience with the google assistant sdk and the recent adition of custom device traits should allow us to do this. As an experiment i already have a proof of concept which correctly detects the command show/hide [module_alias].

However this is a python script as it has to interact with the google assistant library. Therefore i have the question what you would think is the best way to communicate with a magic mirror module. I have experimented with websockets, which works. But i am not sure wether this is the right method.

Does anyone have any relevant experience/advice with buidling modules which communicate with third party applications?

With kind regards,
Tim

You could create a fork and have a branch within this repo referencing the original master branch.
Using git different branches can have different remotes. (https://stackoverflow.com/questions/15775183/git-different-remote-for-each-branch).

In this case if the master branch of the original project is updated you can pull these changes and merge them into your own fork’s branch. There could of course be merge conflicts which you would have to resolve.

If you feel you have made changes which more people could benefit of, it would be easier to contact the original developer.

@gizmo90 Could you please specify in which logs you see these errors, and tell me a little bit more about which mpd server you are using? (Personaly i use mopidy.)

I did push a maybe fix which was definitely a bug to github, so you can try to pull and run npm install. But i have not been able to reproduce your error with this limited amount of info.

I will have a look this afternoon ;)

@goprojojo

I had the same issue adding a host value to the device constructor in mirormirror.js after line 16 did the trick for me.
You can find it in the AWS IOT settings panel.

app.device = awsIot.device({
    keyPath: __dirname + "/certs/MagicMirror.private.key",
    certPath: __dirname + "/certs/MagicMirror.cert.pem",
    caPath: __dirname + "/certs/root-CA.crt",
    clientId: "MirrorMirror" + (new Date().getTime()),
    region: "us-east-1",
    host: "************.iot.us-east-1.amazonaws.com",
  });

If you are still interested, i just published a simple mpd client for magic mirror.
https://forum.magicmirror.builders/topic/5272/mmm-mpd

Description

I just created my first module and thought it would be nice to share it with you.
Its an MPD (music player deamon) integration.
It show the current state of your music player and songs coming up.

It’s an early version, i still need to do some refactoring but if anyone would like to try it feel free to do so.

Next up is propably an integration with the Home Assistant API.

Screenshot

Download

[card:timjong93/MMM-MPD]