I would like to do the same thing :-)

I am still trying to fix the drop outs on the radio stream. I now suspect that it has nothing to do with the wifi connection but somehow with the resources of the PI. I have Alexa & WakeWord running in the background as well as Magic Mirror and Node Red. I switch alexa and wakword off by closing the terminal screens but the server probably still runs so i cant realy rule it out. Anyway to provide radio with more resources or to finalse the cause ?
I also noticed, that after a few seconds of running radio, the VCN connection and even terminal connection disconnects.

My present situation is a follows: I get the radio station to play but I got many many drop-outs.
I tried iFrame as an alternative platform to play radio and I have the same problem. Changing the radio station or link doesnt help either.
I dont think its an issue with the module but probably more with the Pi resourcs. My internet connection clocks at >10 Mbyte download and>4upload speed hence I dont think thats the issue.
Now how to find out the actually cause ?
Could I try to use a lower quality (bitrate) radio stream instead or allocate more hardware resources ???
Please help !

@strawberry-3.141 I got the following error when I run pm2 log mm:

error: cannot open .git/FETCH_HEAD: Permission denied

@Sputnik I suspected, that maybe my Wifi connection is not good enough but the speedtest shows 11-14Mbt download speed and about 4 Mbt upload speed which I believe should be sufficient.

I would like to do the same thing :-)

Yes, I am also trying to find a simple way to play a single mp4 file which is stored on my PI. Anyone has a solution inside a module ??

@cruunnerr said in SSH & VNC & Alexa disconnected after a brief moment of MagicMirror startup:

sudo iwlist wlan0 scan | egrep “Cell|ESSID|Signal|Rates”

My signal strength was indeed weak with -71dB. I changed the wifi channel from ch9 to ch6 and it improved. I will monitor now for a couple of days and see if the situation stabilizes.

I would also like to mention how I start Alexa and MagicMirror.
I wrote an sh file which is saved under Desktop. This file starts Alexa with Sudo lxtermin… in three individual terminals. after 40sec of waiting it starts pm2 start mm.sh (without sudo) then MM changes from the GUI (which shows the three Alexa terminals) to the MM screen. After a few sec .the problem starts.

Even when the SSH and VNC connection is cut my router shows the PI as connected via wifi. The only additional setting I did one is on the router under “Port forwarding/triggering”: which I set to Service name: HTTP, Service Type: TCP/UDP, External port range: 3000-3000, Internal portrange: 3000-3000.
In the MM config.js file I maintained IP address “localhost” and I put 0.0.0.0 under the whitelist IP.
With a keyboard attached to the PI I can use Ctrl-M to switch the display to GUI and I get back SSH and VNC connectivity but the connection is super slow and basically useless.
I am using the latest Raspbian Scretch 4.9 and all the programs are updated.
I also noticed, that after leaving the MM on for a couple of hours that the time and date/calender is correct as well as the messages but the holidays and news are showing waiting as well.

Re: MagicMirror fails to be started via SSH console

I installed MagicMirror as well as Alexa (including Wake Up Word) on my Pi3. Individually MM as well as Alexa are working perfectly. I even got SSH and VNC up and running to work remotely.
However when I start Alexa followed by starting MM the MM screen loads and refreshes but the SSH, and VNC connection gets cut and Alexa seems to listen to the wake up word (acknowledges buy bip) but doesnt answer anymore. Has this todo with the settings in regards to IP addresses for Alexa and MM and SSH and VNC or is this an overload of resources ? Where do I start looking ??