@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 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… 😉