It’s truly a gem of the internet and I’m glad that I could share it with the world.

Looking back on my config convention, it’s really confusing. autoPlay does not mean that the video plays right when the mirror boots up, it means that when the view is switched to video by use of the notification it plays without any more need for interaction. The play feature is mostly meant to be used with voice modules and I specifically developed it to work with my own in which all you would need to do to get it to work would be to add the module and put the following into your config.js { module: MMM-Voice-Commands, config: { commands: { "play video": "ROSS_PLAY_VIDEO", "stop video": "ROSS_SHOW_IMAGE" } } } Now when you say play video, it will switch to the video view and when you say stop video, it will switch back to the painting. However, using MMM-Voice-Commands is not necessary, any module that can be configured to emit a notification to ROSS_PLAY_VIDEO and start the video. There isn’t much I can do about the low definition pictures. That is just the quality the website I am using has them in. That’s why I put the module in the lower left hand corner and made it small; it still looks like a nice nature scene, but the low resolution is unobtrusive.

@Riaanh this looks like being started under docker

After trying out the method of importing the config, it works well and seems to be stable. If anyone has any reason why not to require the config.js in a node_helper file, I would appreciate an explanation.

I did it manually using references the modules and containers. It worked a lot better than I assumed it would as well since references to the modules seem to stay intact so hiding them still works. I will post the full module when I’m done if in case anybody wants to see how I hacked it together. P.S. If there is a more official way, I would still like to know what it is.