@shbatm said in Clean installation... fails left and right:

I’m seeing issues with the newest “Raspbian Stretch with desktop image” (Nov 2018–non-bloatware) as well – I did a fresh, manual installation, no errors, but electron will not start with the OpenGL driver (full KMS or fake KMS) enabled.

Confirming what I confirmed in the issue on GitHub just so others aren’t misled… Upgrading to Electron v3.0.13 is working fine (this is now the version installed if you use the develop branch of MM). V2.x is not working on the new Raspbian because of the OpenGL driver and we can’t use V4.x yet because of bad dependency references.

@devinhedge said in Clean installation... fails left and right:

for the last couple months Node.js and npm are currently BROKEN on RaspberryPi.

What version of node are you using and how are you trying to install it? Node.Js works fine with Raspberry Pi, just don’t install it from the default repos. Use these instructions:

https://github.com/nodesource/distributions/blob/master/README.md

I’ve installed both v8 and v10 successfully multiple times on new Pis in the last few months.

@axel said in HELP to use a cam with MM PLEASE:

see my usb cam in live on the mirror!

If you can get an RTSP stream URL from your IP camera you can use my module: MMM-RTSPStream. Use the develop branch right now–and search this forum if you’re having issues getting it to work.

If you want to stream your USB camera by hooking it up to the Pi, you can look at something like mjpg-streamer (Google ‘OctoPrint mjpg-streamer setup’ for some good guides) and then use MMM-iframe to show the image.

So I was looking at the Fauxmojs project–what this module uses to handle the “devices”–and it looks like there are some issues with Gen 2 Echos not discovering the devices–but for most, the alexa.amazon.com website was working. I’ll keep an eye on that project–but at the moment, I don’t have anything else I can do from my end.

If you want to see some more detailed logs–start the MM manually with the following:

cd ~/MagicMirror
export DEBUG=sstp-server,deviceEndpoints,discoveryService
npm start

@richland007 - I just tested my installation with 3 devices and, while it wasn’t showing all of the ports on the log line due to a bug, it was opening the ports (visible with netstat -tulpn | grep electron – see below). Just in case anyone is wondering–port 1900 is the discovery port.

tcp        0      0 0.0.0.0:21900           0.0.0.0:*               LISTEN      15738/electron.js
tcp        0      0 0.0.0.0:21901           0.0.0.0:*               LISTEN      15738/electron.js
tcp        0      0 0.0.0.0:21902           0.0.0.0:*               LISTEN      15738/electron.js
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      15738/electron.js
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           15738/electron.js

@evroom said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

Will revert back to the master branch and try again.

Yes, the omx_stream1 is created the first time you play a stream with the module.

Please use the develop branch with omxplayer. It was working on my machine the last time I started.

@Cr4z33 try inserting this.playing = true; at Line 574 as the first line in the if statement and see if that works. I’ll test later today.

EDIT: Just pushed an update. Please try the latest release in develop

@cr4z33 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

With omxplayer (and autoStart: false) I see stream labels changing when giving a voice command, but then no stream is starting.

OK. I’ll check this later today, the notification RTSP-PLAY should switch and start the stream so that’s an issue.

@evroom said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

after every mm restart

There was a problem with the steams not stopping on a restart, so the module sends a stop command first whenever it starts, do you have autoStart: true in your config?

@richland007 said in [MMM-AlexaOnOff] Simple Mirror Control from External Home Assistant (Alexa/Google Home/HASS.io):

It only show that 1 one port 0.0.0.0:21900

It would be in pm2 logs mm or ~/.pm2/logs folder. I’ll check when I get a chance why it’s not opening more than 1 port.

@djsunrise19 said in [MMM-AlexaOnOff] Simple Mirror Control from External Home Assistant (Alexa/Google Home/HASS.io):

wemo skill

You shouldn’t need a separate skill with it. It looks like everything is working from the mirror side so I’m not sure what else to try…