@shbatm thanks for the reply.

I can confirm that I’ve got rid of the white frame by following @evroom 's suggestion (thanks mate).

Back in topic I’ve uploaded here the log 'cause I am not sure whether it is actually reporting a problem with MMM-RTSPStream or not. :thinking_face:

Looking at it it says MMM-RTSPStream.js:161 MMM-RTSPStream has resumed... after two questions I made to Google Assistant, but I found no mention about RTSP pausing or stopping.

However I can confirm that omx_stream has indeed stopped from running! :frowning_face_with_open_mouth:

 pm2 status
┌─────────────┬────┬──────┬────────┬─────────┬─────┬────────┬──────────┐
│ Name        │ id │ mode │ status │ ↺       │ cpu │ memory │
├─────────────┼────┼──────┼────────┼─────────┼─────┼────────┼──────────┤
│ mm          │ 0  │ N/A  │ fork   │ online  │ 0   │ 0%     │ 2.5 MB   │
│ omx_stream1 │ 1  │ N/A  │ fork   │ stopped │ 0   │ 0%     │ 0 B      │
└─────────────┴────┴──────┴────────┴─────────┴─────┴────────┴──────────┘

@evroom no problem mate although it looks like the developer is no more active in this thread my bad. :confused_face:

Do you know by chance what to edit to see the stream in the same position as the white frame (I actually would like to get rid of it)?

@bkeyport oh great doing it now thanks.

@evroom oops it came out I have to wait at least 30-40 seconds before I can see (succesfully) a 1080i @ 60Fps HD stream. :smiling_face_with_smiling_eyes:

However yesterday I found one more issue…
I connected the RPI for the first time to the TV to see how MagicMirror was looking on it, but I found out that the stream stops as soon as I ask something to Google Assistant (MMM-AssistantMk2 + MMM-Hotword by @Sean ) and it replies.
After that the stream doesn’t resume at all.

I don’t know where to start and cannot see why this is going on as the RPI can easily play 2+ media files at a time. :confounded_face:

@bkeyport so that’s not only me?

I thought I messed up something in the CSS.

@evroom lol indeed! :grinning_face_with_smiling_eyes:

@evroom found out the mistake thanks to your suggestion:

I missed to add an additional close curly bracket after line 213!

@evroom thanks for the help I give it immediately a look. :)

Also didn’t know that terminal command.

First of all why are all online JavaScript linters completely useless for our config.js file? :thinking_face:

They all report completely no sense mistakes while the REAL error might be located in somewhere else line.

Now back in topic I might have edited/canceled something that has screwed up the file by ending with the CONFIG.JS screen when launching MM. :face_with_cold_sweat:

Can someone please help me finding the mistake?

https://pastebin.com/BAQTi012

@justjim1220 that’s what I already did, but I see you now fixed that. :)

Thanks.