Try to start it manually:

cd /home/pi/spotify-connect-web
./spotify-connect-web -n MAGICMIRROR -o plughw:CARD=ALSA,DEV=1

NB! plughw might not work for you…

What happen if you open http://127.0.0.1:4000 in a browser on the RPi – or change the IP to the IP of the RPi and open in a browser on your own machine?

You say you get permission errors even when using sudo?

No sudo is required. Hmmm, did I forget that in my documentation… :-)

What did you do? Did you read my documentation?

Have you installed Spotify Connect Web on that address?

Really cool using LED strips. First time I’ve seen that!

Hi

A couple of moth’s ago I started to get this message. No doubt the popularity of MM and it’s forum must have increased substantially!

The question is: what would it take to make room for the increased traffic? Ad’s to paying for more capasity or a way to donate?

Keep up the good work!

Nice! Now I just need to get an touch mirror… 😊

@emos The URL you are using in your config seems to be the “web hook”-URL that you have to configure inside MotionEye if you want to automatically show video stream when motion is detected.

The URL should be configured like this (from documentation): Video Streaming URL. You find it in Motion Eye in the Video Streaming Section under Usefull URLs by by clicking the Streaming URL link. It should look something like this: http://motioneye:8081 (probably an IP instead of hostname).

@lolobyte As long as the software can provide a “motion jpeg”-stream, it can be supported.

Basically, you can test it your selv by making a local .html-file with <img src="xxxxx" />

@lolobyte You will have to install motionEyeOS or motionEye to use this module. Please read pre-requisites.

@lolobyte First question: What motion software do you use?

@Snille Had some comments. Fix those and I’ll merge it :)

@LincolnClay Well, I still don’t think it’s the module’s fault. I tried to replicate your exact configuration and it works.

What output do you get from npm start?

@LincolnClay The error indicates the port 8080 is in use. Did you install pm2? If so then Magic Mirror is already started when you run npm start. Just restart it with pm2 restart mm

@Snille Ok found the bug - update to 1.1.0 as instructed in README.md in GitHub.

@Snille I don’t remember if “motion jpeg” is enabled by default in Motion Eye. Can you check your settings in Motion Eye? I’m at work now and have no change to check myself…

(Maybe it has another name)

@Snille Can you try another position (and maybe size): bottom_right / 400px

Nice!

You say that the motion sensor is very sensitive. Do you get any false positives or is it sometimes it doesn’t trigger when it should?

I like the idea of an USB extension! Why didn’t I think of that… 😉