I realize this is an old question but thought I’d provide a little more info just in case someone else stumbles upon this or you’re still looking for an answer.

@sdetweil is correct in that the updatenotification is what is generating this error in the log.

For the most part it can be ignored entirely as it doesn’t stop functionality from continuing.

updatenotification module checks each module’s folder you designate in your config file. Within each of those folders it checks to see if it is hooked into git. If it is, then when the updatenotification triggers a check for updates, it will essentially run git fetch for each one of those folders its tracking.

Now, if the remote is a private repository that requires credentials and you have not set those credentials local or global you then receive this error.

I do not recommend setting your credentials for git locally or globally as this information is stored in plain text on your machine. However, if you still want to do this to avoid the error you can do the following:

Navigate to a private repository folder on your Raspberry pi and execute the following:

git config --global credential.helper store && git pull

This will then ask for your credentials. Once you have provided them then all your private repositories will use the credentials you provided and you shouldn’t have to manually provide those credentials again. In turn, you will no longer see this error.

I’ve exhausted everything I can think of. Your working with an ideal situation where everything is updated and fresh and still not able to get the stream. For some reason the videos aren’t getting dropped in that public folder for you when the event gets activated. Based on what you’ve provided it should be working.

Since I can’t recreate the condition on my end there’s not much I can do here. Your specific issue is the first I’ve seen or heard of. That layer of the module is utilizing the ring-api from dgreif which I have no contributions to.

If you’re adventurous enough and have a little bit of coding background you may try downloading his api and play with the browser example he has to see if you can get that working.

Sorry @sithlordhood !

Ok, run in dev mode again but switch over to the Network tab (instead of console) and see if any of the lines have red text prior or after hitting your doorbell again.

I’m assuming you also rang your doorbell to see if the video came up now using localhost?

Is there a reason you’re using 0.0.0.0 over the default localhost?

Test with using localhost by setting it in the config file:

address: "localhost"

They don’t appear until ended? Wow, that’s a new one. You should definitely be getting them as soon as it says “Preparing video stream”.

This might be an authentication issue. Do you use 2 factor authentication with Ring by chance?

Check the debug console window for errors by running MagicMirror with using the following in the main MagicMirror folder:

npm start dev

This should start the MagicMirror with an additional window to the side that you can select the console and look for errors there.

@sithlordhood this one is a bit tough because I can’t recreate the issue you are having.

We can look at if the video is actually showing anything at all to determine if this is a sip session/ffmpeg issue or an issue on hls hooking into the video control and playing the stream. Try this:

1. Run MagicMirror
2. Minimize it
3. Using file explorer navigate to the MagicMirror/modules/MMM-RING/public/
4. Go ring your doorbell
5. Once a .ts file gets dropped into the public location open/play it. Maybe check a couple as well.

Is there video of your doorbell camera when you play those?

BTW, they will all be like 2 second long videos each. The stream (m3u8) is what ties them into a continuous video by playing them serialized.

Ok, so I 've fixed the error you’ve run into. The reason the stream could have stopped is because someone on the account looked at the ring event on the ring app and then stopped/closed it. Unfortunately, it’s basically a “shared” stream in that if applications are looking at the event at the same time one ended could potentially end the other viewing it prematurely. I’ve only had this happen once and that seemed to be what that was.

I made some other small changes which may help here as well. I’d like for you to update all your software first though just to rule that out as well.

Before doing any of the following I would recommend backing up.

1. Update your pi OS to the latest version
   sudo apt-get update
sudo apt-get upgrade
sudo reboot
2. Update MagicMirror to its latest version by using a Terminal to navigate to your MagicMirror folder and running
   git pull && npm install
3. Navigate to the module/MMM-Ring folder and run
   git pull && npm install

This will update everything, hopefully. Now try running MagicMirror again, giving it a couple seconds to a minute, and then ring your doorbell again.

Hope this helps!

Interesting, are any errors printed in the terminal and if none there, are there any errors in the Electron debugger log after running?

You’ll need to install ffmpeg. I’m assuming you’re using a pi with Raspbian. If so, you can run the following in the terminal:

sudo apt-get install ffmpeg

If not, you’ll need to find how to install ffmpeg with whatever OS you’re running.