CCTV Raspberry Pi Based System with Storage using MotionEyeOS

In this project Julian is going to show you how to build a complete Raspberry Pi based home surveillance system in which you can manage all your cameras from one single place using MotionEyeOS. The system built also allows you to save your frames from all your cameras in a 1TB SATA drive.

This project was written by Julian Silver and edited by Rui Santos and Sara Santos.


For an introduction to the MotionEyeOS, you can read this introductory blog post.

Project Overview

The surveillance system built includes: one Raspberry Pi acting as a HUB with 1TB SATA, and 4 cameras (each one connected to a Raspberry Pi Zero W) that can be monitored through the HUB.

All devices are connected to your local network, and you can access all the cameras through the hub using a browser on your computer (or other device on the local network). The following figure shows a high-level overview of the project.

Parts Required

Here are all the parts needed for this project.



You can use the preceding links or go directly to to find all the parts for your projects at the best price!

Hub Setup

The Raspberry Pi Hub setup consists of a Raspberry Pi 2 Model B (if you have a RPi 3, use that board instead) with a Sandisk Ultra 16GB class 10. There is a 1TB SATA drive connected to the Pi with a SATA-USB cable.

The Raspberry Pi is being powered with a 12VDC 1500mA wallwart connected to 2A DC-DC converter set to around 5.2V output.

Note: I have been doing some experimentation with powering RPi 2 and 3 and found that using a 12V 1500mA wallwart adapter and a 3 or 5A DC-DC converter with short leads seems more capable and often cheaper than a big 3A wallwart adapter, and gives you a 12V supply for other associated hardware.

Note: I have found that my SATA drive is capable of being powered by the RPi 2 USB without a powered USB hub. You may not be as lucky. A friend of mine has suggested putting a beefy cap in parallel with the RPi power input

Cameras Setup

The setup for the cameras consists of 4 Raspberry Pi Zero W with a Sandisk Ultra 16GB class 10. Each Raspberry Pi Zero W board is connected to a camera.

The Raspberry Pi boards are being powered with a 12V DC 1500mA wallwart connected to 5A DC-DC converter set to around 5.2V output (this is a temporary setup for testing, after testing that everything is working fine, each Raspberry Pi Zero W should have a separated power supply).

In this setup, the power leads yellow/black are soldered directly to the back of the Raspberry Pi Zero board.

1. Installing MotionEyeOS on the RPi Hub

You need to install MotionEyeOS on your Raspberry Pi, preferably a Raspberry Pi 2 or Raspberry Pi 3. This board will act as the hub.

Burning MotionEye image to the microSD card

Follow the next steps to install MotionEyeOS on the microSD card for your Pi.

  1. Format the microSD card. You can use the SD Card Formatter software.
  2. Choose and download the right image for your device: MotionEyeOS releases page. If you’re using the Raspberry Pi 3, choose motioneyeos-raspberrypi3-xxxxxxxx.img.gz.
  3. Extract the image from the .zip folder.
  4. Use Etcher or Win32 Disk Imager to write the image onto the SD card.

Booting MotionEye for the first time

Your microSD card is now ready. Follow these next steps to boot MotionEyeOS on your RPi 2 or 3:

  1. Insert the microSD in the Raspberry Pi
  2. Connect the SATA drive or any other drive you intend to use to store files
  3. Connect the RJ45 ethernet cable to your network.
  4. Temporarily connect a camera to the Raspberry Pi even if you don’t intend using one in the future. You can remove after all the configuration has been completed.
  5. Connect the power supply to power it up.
  6. Wait a couple of minutes while it configures itself.

Finding the Raspberry Pi IP Addess

To access MotionEyeOS from your browser, you need the find the Raspberry Pi IP address. To find your Raspberry Pi IP address, you can use FingAngryIPScanner or any other similar software. The IP you’re looking for is the one with “meye” on the name, as shown in the following figure.

Alternatively, you can also look at your router DHCP table, or you can connect an HDMI monitor before startup.

2. Installing MotionEyeOS on the RPi Zero W boards

You need to do this procedure for each of your Raspberry Pi Zero W boards.

Burning MotionEye image to the microSD card

Follow the next steps to install MotionEyeOS on the microSD card for your Pi.

  1. Format the microSD card. You can use the SD Card Formatter software.
  2. Choose and download the right image for your device: MotionEyeOS releases page. If you’re using the Raspberry Pi Zero, choose motioneyeos-raspberrypi-xxxxxxxx.img.gz.
  3. Extract the image from the .zip folder.
  4. Use Etcher or Win32 Disk Imager to write the image onto the SD card.

Setting the Network Credentials

Important note: when burning the ISO to the SD card for the Raspberry Pi Zero W boards, do not eject the card before following the next procedure to set your WiFi credentials. If you do not do this now, the Pi Zero will not log onto your Wi-Fi network and constantly reboot annoyingly requiring you to re-image the SD card.

Follow the next procedure to set your network credentials for each of your Raspberry Pi Zero W boards.

  1. Open Notepad or a similar text editor, and create a new file called Wpa_supplicant.conf
  2. Copy the following lines to your file:
  3. Change the country code to your country, and use your SSID and password. Do include the quote marks.
  4. Save your file. Important: when you save the file ensure it is Wpa_supplicant.conf and not Wpa_supplicant.conf.txt as this will not work!
  5. Copy your Wpa_supplicant.conf file to the root of the SD card.

Setting Multiple Access Points (optional)

Thinking ahead, if you have multiple Access Points (AP) around your house and you want to move your Raspberry Pi Zero Cameras to one of those locations, it would be a good idea to include the SSID and Password for those APs at this point.

The main reason to do this now is I cannot find a way to edit the Wpa_supplicant.conf file after the Raspberry Pi Zero Cameras have configured itself, so it has to be done now. I have tested this and it does work although the change of AP credentials is not reflected in the Network section of the MotionEyeOS GUI. The point is that it does work.

Here is my example Wpa_supplicant.conf file for reference:






Change the country code to your country code, and insert the right SSID and password for your multiple access points.

Booting MotionEye for the first time

After having the microSD card properly prepared follow the next steps to boot MotionEye on the Pi Zero for the first time:

1. Eject the SD card from your PC and insert it into your Raspberry Pi Zero.

2. Attach the camera. When using a Raspberry Pi camera with the Pi Zero, you need to use an adapter cable as shown in the following figure.

3. Apply power to the Raspberry Pi Zero board.

4. Wait a couple of minutes while it configures itself.

Finding the Raspberry Pi Zero W IP Address

Now, look for your Raspberry Pi Zero W IP address, as you did for the Raspberry Pi Hub. The IP you’re looking for is the one with “meye” on the name.

Alternatively, you can also look at your router DHCP table, or you can connect an HDMI monitor before startup using a micro HDMI adopter.

3. Configuring the RPi Boards on MotionEye

To access each of your Raspberry Pi boards, open your browser and type the Raspberry Pi IP address. You’ll be presented with the MotionEye Login Page. The username is admin, and there is no password, so leave the password field blank.

You should see a live image from the camera at this point. If not, check that you’ve properly connected the camera ribbon.

You need to set the following configurations in all your boards (the Raspberry Pi Zero W, and the Raspberry Pi Hub).

Follow the next steps for all your Raspberry Pi boards.

1. Use the menu icon at the top left to expand all menus.

2. For security reasons, in the “General Settings” change the password for the admin user.

3. Turn ON “Advanced Settings”.

4. Fix the IP address of your RPi boards to something outside the range of your DHCP server. Say 200 and above, for example.

5. Set the Time Zone and Hostname.

6. In case of the Raspberry Pi Zero, the wireless network and password were automatically picked up from the Wpa_supplicant.conf file.

7. Apply the settings, which will require a reboot and you will have to point your browser at the new IP you have just chosen.

8. Press “Check for a new software update” and it will download, install, and reboot if there is a software update. This will take approximately 5 minutes.

Note: If at any time you have trouble logging into your RPi, try clearing your cache or use your browser in ‘Incognito mode’.

4. RPi Zero W Specific Configuration

Follow the next steps for configuring each of your Raspberry Pi Zero W boards in MotionEye.

1. Give the camera a name.

2. Change the camera resolution to 800×600.

3. Rotate camera image if required.

4. Ensure Text overlay is on.

5. Video Streaming is off.

6. Still Images is on.

7. Set Capture Mode to manual.

8. Under motion settings set motion gap to 2 and minimum motion frames to 5.

The above will reduce the amount of data/frames initially whilst you configure and test the system.

Do not change any of the other settings for the time being. If you need to know the default Frame change threshold it was 3.5%.

Repeat this process for all your Raspberry Pi Zero W boards.

5. RPi Hub Specific Configuration

Access your Raspberry Pi Hub, and follow the next steps for configuration

1. Go to “Services” and turn all on. Apply the settings – this will reboot your Raspberry Pi.

2. Use FileZilla or equivalent from your PC to set up a directory structure on the SATA drive. Once logged in with FileZilla you should see something like the following figure.

3. The MotionEyeOS seems to automatically create 2 shares: sdcard and storage. Double click “storage” and create a directory structure to suit your camera needs. The following figure shows how I configured my structure.

4. Go back to your web browser connected to your Raspberry Pi Hub.

5. Go to “File Storage” and choose the “Mass Storage” device. See the figure below for my configuration. Yours may differ.

This configures the SATA drive for storage of the local camera whether you use it subsequently or not. This section may seem pointless but without a camera connected initially none of the local file storage options appear.

6. Configuring File Storage For the RPi Zero

Follow the next steps to configure file storage for each of your Raspberry Pi Zero W boards.

  1. Log on to each Raspberry Pi Zero.
  2. Configure the file storage as shown in the figure below.

You will notice I have chosen network share in the drop down menu and entered the IP of the Raspberry Pi Hub which has the SATA drive attached.

The share name is vital and in that exact format. The last part of the share name is the specific file storage directory you set up with FileZilla above.

Enter username and password as normal, and root directory should be just /.
Use the test button to confirm the settings. This took me many hours to get right but the above configuration worked fine for me eventually.

Note: I think there is a bug in the system regarding the Disk usage indicator as this is incorrect, unless it just represents local storage.

Testing the Setup

That is all the complicated configuration done!

You can now go to each camera and click on the live image. It will then display an option to take a manual picture, browse saved pictures etc.

Once you are happy with the way the RPi Zero cameras are taking pictures, you can turn motion detection on and see the frames start to flood in. You can configure motion notification, and much more.

7. Add the Cameras to the RPi Hub

Finally you can log into the Raspberry Pi Hub and add the remote Raspberry Pi Zero cameras to allow viewing and administration through one point.

  1. At the top left corner, there is a drop down with the existing local camera, and an option to Add camera.
  2. Click “add camera”. In the new dialogue window that pops ups, drop down to choose “Remote motionEye Camera”.
  3. Enter the address of the Raspberry Pi Zero W camera you would like to add in the following format in the URL
  4. Enter the username and password and it will automatically see the camera attached to the Raspberry Pi Zero W, if the info is correct. Press OK. The following figure shows this configuration setup.

The remote camera can now be selected from the top drop down menu and viewed or administered from the Hub. Do this procedure for all your Raspberry Pi Zero W cameras.

Once you’ve done that, all cameras can be monitored through the Raspberry Pi Hub.

Enclosures and Power Supplies for Raspberry Pi Zero Cameras

After building your Raspberry Pi based CCTV system using MotionEyeOS you need to mount your cameras in an enclosure of some sort and power it with something – it is virtually guaranteed you will not have a plug socket near where you want to install your camera. In this project I powered my cameras from my existing PIR Floodlights.


With a little research I found that the Raspberry Pi Zero with a ZeroCam or a ZeroCam Noir or a ZeroCam Fisheye draws a maximum of 280mA and an average of 215mA. So, I opted to use some 99p AC-DC power supplies from eBay. Rated at 3.5W.


  • Input voltage: AC 85 ~ 265 v 50/60 hz or DC 100~ 370 v
  • Imput current: 0.0273A(AC110V) 0.014A(AC220V)
  • Input Inrush Current: 20A
  • Output voltage: DC 5V (+ / – 0.2 V)
  • Output current 700 mA
  • Power 3.5 W
  • Operating temperature -20~60℃
  • Relative humidity 40-90%RH
  • Output 5V, min current 0a, max current 700mA, peak current: 800mA, output range: 4.8~5.2v, ripple wave: 60mV
  • Output power:0-4W(DC current)
  • Output efficiency: 80%
  • Switch machine overshoot: MAX 10%
  • Output voltage rise time: MAX 100MS
  • Output over voltage: 4.8-5.2V, recovery:Lock, restart after recovery
  • Output over power protection:YES ,recovery:Lock, restart after recovery
  • Short-circuit protection: YES, automatic recovery after problem solved
  • Temperature protection: YES,recovery:Lock, restart after recovery
  • Overcurrent protection: YES,recovery:Lock, restart after recovery

So connecting this up with short DC leads and plugging it into a mains power monitor I got the following results:

  • 239V
  • 0.015A
  • 1.5W
  • 7VA
  • 49.9pF

So, to run the camera for a year will cost:

13.14kWh x 0.15 = 1.97€. (My electricity is 0.15€ per kWh) –> Won’t break the bank!

Enclosure Ideas

I had some dummy security enclosures and opening one up and with minimal modifications I managed to fit the Raspberry Pi Zero W with the camera and power supply inside with ease. It doesn’t seem to affect the picture that much. The dummy camera enclosure was £4 from eBay. And it looks very professional!

Another approach is placing 2 cameras in one enclosure. So, I used a standard project box (75x100x40mm), one of the AC-DC power supplies shown above, and some hot glue and insect netting to cover the air holes, as shown in the figure below.

Taking It Further

There are many choices of cameras for the Raspberry Pi and Pi Zero, so Julian run some tests to compare of the Raspberry Pi cameras in his selection. You can learn more about that in the following post: What’s the Best Raspberry Pi Camera for your project?

Wrapping Up

In this post you’ve show you how you can build your own surveillance system using MotionEyeOS. The surveillance system built allows you to monitor 4 different cameras, each one connected to a RPi Zero, that can be monitored through one Raspberry Pi Hub. This system allows you to monitor all your cameras, as well as save frames on a storage device.

We hope you’ve found this project useful and that you can modify it to fulfill your needs.

If you liked this project you may also like:

About Julian Silver

This project was built by Julian Silver. Here you can learn more about Julian.

My name is Julian Silver (Jules) and I am a reasonably competent student in the art of electronics. I have been playing with Raspberry Pi for many years and Arduino and ESP8266 more recently. My first Pi camera project for rudimentary face recognition was nearly 5 years ago now and I made my first AM radio 45 years ago. I am semi-retired living in Southern France and have a keen interest in all things electronics.

This Pi Zero Cam project has been in the offing for nearly 2 years but it wasn’t until this Christmas I ordered the parts to create it. I decided on MotionEyeOS to run the project and that has been relatively painless although there were a few confusing moments. It took about 2 days in all to create which is why I decided to document the process to save you a lot of time if you wish to replicate the process – I estimate no more than 1 day.

I do not profess to be an expert by any means. This document is just what I did to create a simple but functional cctv system. Your system will almost certainly be different in many ways so this is just a document for thought process. With that in mind Do Not contact me for technical support. All the answers ARE out there on the WWW. You just have to search. I found most of the answers on the excellent and would recommend anyone thinking of using MotionEyeOS to start their journey there.
Good luck. Regards… Jules.

Learn how to build a home automation system and we’ll cover the following main subjects: Node-RED, Node-RED Dashboard, Raspberry Pi, ESP32, ESP8266, MQTT, and InfluxDB database DOWNLOAD »
Learn how to build a home automation system and we’ll cover the following main subjects: Node-RED, Node-RED Dashboard, Raspberry Pi, ESP32, ESP8266, MQTT, and InfluxDB database DOWNLOAD »

Enjoyed this project? Stay updated by subscribing our newsletter!

90 thoughts on “CCTV Raspberry Pi Based System with Storage using MotionEyeOS”

    • Hi Craig.
      You should definitely try this. You’ll be surprised to see how simple it is, and how well it works!

  1. Great project and great writeup. Your email appeared Feb 1, I ordered 3 different cameras to go with my R-Pi3 and R-Pi-ZW and SD cards, all arrived Feb 3, and I got the system set up. The only thing I did different is that I had to set “Capture Mode” to “Motion” instead of “Manual”–you say this, but I was at first puzzled by the absence of shots on the drive.

    With my DC-DC step-down module set at 5.2V for the pi3, I’m only reading about .5A, occasionally jumping up to .6A. Is the beefy power supply really needed?

    • Hi Lance.
      We’re glad you’ve successfully followed this project!
      This project was built by our reader Julian.
      He decided to use that method to power the Raspberry Pi.
      But using a regular power supply for the Pi should work too.

    • To add another element to the mix, I installed the motioneye os distribution on an original raspberry pi and plugged in a usb wifi dongle and a Logitech Quickcam 9000 Pro usb camera, and that also ran and connected to my pi3 hub–at 960×720 pixels..

      Now I have the hub, 2 pi-0Ws, an original pi saving motion detection snaps to the hub, plus a view on the hub site of a pogoplug running openWrt and streaming from a Deluxe 9000 with mjpgstreamer.

      What a great and flexible project. Now I just have to figure out where I’m going to place all my cameras.

      • Nice!
        Yes, this is a very flexible project, very simple to follow, and with a lot of functionalities you can customize.
        Thanks a lot for your feedback 🙂

      • I don’t know how it could. Pi3 is a 64 bit machine and the zero is a 32 bit. I tried it and couldn’t get it to go past the color screen. I am also having trouble getting it to define the wifi. I have tried a bunch of iterations of wpa_* and cant get past the boot loop. I tried loading raspian streach on the zero, took what it had for wpa_supplicant.conf and it wasn’t picked up as a valid wifi starter either. Got any suggestions?
        I also tried adding other networks to the stretch build in the manner suggested by editing the wpa_* file, and that broke the wifi totally, to the point I couldn’t correct it from the GUI. bummed.

        • Hi Bryan.
          I’m sorry for the misunderstanding. You should use the release that says “Raspberry Pi” for the Pi Zero, not the “Raspberry Pi 3”. You can found the links here for the specific board you’re using.
          If you’ve followed the instructions, I have no idea why you can’t define the wifi.
          Some common mistakes include:
          – creating a wpa_supplicant.config.txt file – it can’t have the extension .txt
          – removing the double-quotes “” when writing your SSID and password on the file
          I hope this helps. And I’m sorry for the misunderstanding about the motioneyeOs releases.

      • I mean use the version that says Raspberry Pi. You can download it here –

        I’m sorry for the misunderstanding.

  2. Still playing with this with multiple cameras. Is there a way to limit the area within which motion is detected? I have a view which includes plants which sway in a breeze. I’d like to restrict motion detection to the bottom 3/4s of the frame, while keeping the entire view.

    • Found the answer. Under Motion Detection, click “Mask” on, select Mask Type of “Editable”, click Edit Mask, then click on boxes in your view to mask, or click and hold to sweep through boxes to be masked.

  3. I was wondering if there’s a way to record without having a network connection. I am trying to have the board started and automatically start recording to an external HDD. Please let me know if that’s possible Thank you

    • Hi Rami.
      Yes, it is possible. We don’t have any tutorial about that.
      However, I found a tutorial on instructables that might help you.
      Sara 🙂

  4. Excellent write-up! It would have saved me a lot of time when I set up my 4 camera system last year. One question..can I add the hard drive after the fact, or will I have to re-configure the hub? Thanks

    • Hi Steve.
      I haven’t tested that.
      You can add the hard drive later, but you need to configure the hub to save the footage or photos to the hard drive.
      Sara 🙂

  5. Great Project :)…

    I have a question..
    How can i save the videofiles on the SATA Drive AND and the SD card of each Raspi Zero?

    Thanks, Niko

  6. Hi, I’m connecting a USB 150GB drive to the RPI Hub, but hub is not picking up the drive. What do I need to do so that RPI Hub is realizing the USB drive. Is a special format required. write now USB drive is formated in NTFS.
    Thanks in advanced for your feedback
    Regards, Gerald

    • Hi Gerald.
      The best way to find out the solution for your issue is searching on the motioneyeos issues here:
      Motioneyeos also has an active forum where you can search if someone had the same problem or ask a question:!forum/motioneye

  7. Hi, Sara
    Great Job!
    Could I add motion detectors in order to save images only after movement’s presence.
    Thanks & Regards

    • Hi José.
      Yes, you can do that. There’s a feature on MotionEyeOS that does precisely that.
      When configuring the cameras in your MotionEye dashboard, there is a section for Motion Detection that you can configure.

  8. Stupid question. will this work with more than 4 cameras. I could see me easily installed 6-8 cameras for this price point of this setup.

    • Hi Daniel.
      MotionEye supports multiple cameras and you can add as many cameras as you want.
      See here:

  9. I’m a NOOB and I’ve tried every which way to attach a hard drive to this. The drive is formatted FAT32. I attached, but can’t see it listed in the drop down on motioneyeos. Do i add it as a custom option and if so what is UNC of it?
    Please help

  10. The author couldn’t create/edit a wpa_supplicant.conf file because the root filesystem is read-only. There is another one in /data/etc/ which can be editted – I haven’t tried it but suspect that without the one added to the root before booting as described, this is the definitive one.

  11. Success! Works great, will be deploying around the house, inside and out.

    Is it possible to pass Audio as well? I ask as this would work perfectly for another application at work.

  12. Hi
    I’m going to implement this system, but I don’t have a camera for the Raspberry Hub, is there a problem? Why, when you first start the Raspberry, it says that it is to have a camera connected to it. Do I need this camera the first time?
    Thank you so much.

  13. Hi There,

    Thank you for a wonderful guide! Really looking forward to attempting this soon – I will be using ‘OctoCams’ to start with :).

    I was looking at setting up a NAS as part of a separate project which got me wondering – is it possible to run, say OMV, on the Central HUB running MotionEyeOS? In effect, ‘killing 2 birds with one stone’?

    I take it that running MotionEyeOS on the central hub is what allows the user to view all the separate streams/captures in one convenient webpage?

    If this is not possible, I suppose I’d have to set up the NAS and Central Hub separately, but this seems inefficient!

    Thank you very much in advance.

  14. I tried running motionEye on a Pi ZeroW and had it create 30 second videos (800×600 10fps) on motion trigger. The videos all paused after about 5-10 seconds. I noticed you only configured still pics on the Pi Zeros… did you try video? If so, what was your experience? Thanks!

  15. So I know this is a little old, but hopefully someone can help. How can i do this set up without the external drive? As in save all the movies to the sd card in the hub? Also, I’m running a ps4 8gb (with a 128gb sd card) as the hub, and 3 pi0w’s with pi cameras. Thank you for anyone that has any helpful advice.

  16. MotionEyeOs would not work on my Raspberry Pi 4B 2 GB. I found find the solution on Follow the instructions by Kevin Shumaker. It works also on the 4 and 8 GB versions.

  17. Ok like this but I would like to outdoors with motion sensor and lights I have Deer and other wild life But i can’t find any thing on turning on with the camera

  18. Hi guys,
    I’m having an issue where I cannot directly access the sd drive immediately after imagining the RPI zero. If i unplug and reinsert it I can access the drive and all files are there, but then the conf file cannot be added. Not sure what the deal is, using Windows 10 and the etcher program to image. Tried goggling, but not getting anywhere. Using a usb 3 Inland card reader. I already have my PI 3B imaged, working and just need to add my Zero’s. Anyone have in idea what’s going on or suggestions for a workaround?

  19. Hi Sara,
    I have a Raspberry Pi Zero 2 W. After loading the Image motioneyeos-raspberrypi-20200606.img.xz and modified the Wpa_supplicant.conf as described. WLAN is never startet, never taken an IP address from my DHCP Server.
    Is ist possible that I have a wrong image for the newest Raspberry Pi Zero 2 W?
    Thanks for help in advance!!

    • Hi Hans, I had the same problem, and the problem is the Wpa_supplicant.conf file. I had a heck of time trying to figure it out. If you don’t modify the file in the right sequence, the changes are not made. I believe if I remember correctly, the conf file (in the root directory) is accessed on first boot and copies the files to I believe 2 local folders and uses those conf files on subsequent booting. I was successful at locating all the .conf files I could and using vi to modify my network settings in the files and save. In my case I couldn’t get a windows editor to successfully modify my conf file initially. Still don’t know why either, as I can create other.Linux type files without a problem. I did this a few months ago so hope my memory is correct and this helps you. I did a lot of googling on the conf file to figure it out..

  20. Hi Hans, Back with a couple more thoughts. I’m not positive if that was your problem, but here are a few more suggestions you might use to find out if it is. use the desktop with a monitor, keyboard and mouse you can use the graphical interface to setup the WiFi.
    2.The command wpa_supplicant -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf is the only useful way I could use to find what the problem was
    That very useful command reported back problems with the syntax of the text in my wpa_supplicant.conf file
    3. Location of Wpa_supplicant.conf file
    4. Good article on how to fix
    Hope this helps

    • Oh one more way is to attach an ethernet to usb (probably need a hub) to your Pi, boot it, and it will then get a DHCP address and access the interface, then you can configure the wireless in the motioneye network interface. let me know if any of this helps.

  21. Hi Terry,
    many thanks for your help. I will try and let you know.
    btw… if a Monitor is attached via hdmi I can see a colored screen but without any gui or something like that.
    Also i have ordered new mat.

    • Hi Hans, since you don’t have access to the GUI yet, if you attach an HDMI cable from the Pi to your monitor, a USB hub to your pi using a usb 2 to micro cable ( and plug in a USB to network adapter ( into the hub, and plug in an Ethernet cable to it from you router. Boot the Pi and you should see that the pi is getting an ip adddress during boot. Then you can access the GUI and change the wireless within the app. Please note that the links above are merely to show the proper type of devices. All this I did because I could not create the proper wpa_supplicant.conf that the system would accept. I suspect my problem was that my operating system wasn’t able to create the file (structure) properly during the building phase described in the tutorial. Not a problem with the tutorial, but my OS. So with that said, you also might retry following the instructions in this tutorial again to see if there is a problem with you being able to create the .conf file. If not this is an alternative I found that worked for me. Let me know if this helps.

  22. I want to try this project but I don’t really see the need to view video cameras of an area that you are present at. I would want to view my cameras away from home. Is that possible without signing up for some sort of subscription that’s going to drain my wallet every month?

    • I would want to view my cameras away from home. Is that possible

      Yes, I’m doing that. Each motioneye device has its own local IP address. If you open a port on your router with port forwarding to that address, you can stream the camera from a remote location. Or you can port forward to the motioneye hub.

      The exact sequence differs between routers, but you set up an “external” port (something obscure like 29753) and point it to the internal port number (80) of your motioneye hub. Then from your phone, with wifi turned off, data turned on, and a terminal program, you should be able to access the hub at IP ###.###.###.###:29753.

      (Don’t use an external port number of 80–it opens you too readily to probes. There are additional ways to make access more secure, but I haven’t tried them.)

  23. Nice project! I have completed part of it. I’m using a Pi2 for my hub without a camera. I have one Zero attached so far. It seems to be working ok so far. As of now I’m not using any type of storage device. My next step is to try to view my camera on an ipad off site. Thank you Lance Benson for that recent tip. Just in time!
    I have three older Dlink cameras that don’t work anymore with the Dlink app. I want to try getting those working with MotioneyeOS. One step at a time.

  24. Oá Sara, great project.
    One question, can you clarify if with this project will be also prossible to record audio together with the video?


  25. Very nice project. I plan to setup several networked cameras and have them use a server in my computer closet. T he first problem I have is setting up the server as it doesn’t need a camera. Do you know if a motioneye server can be configured without a camera? Could a camera be installed to configure the server and then removed?


  26. Great project. Wish I had read this before I went down a similar path. Seems like they have let the MotionEyeOS and MotionEye app dev languish. None of the most recent versions support the newer 16MP and 64MP cameras which is what I got.

  27. Am I correct that the Raspberry Pis used with the cameras cannot be Pico boards or is there a way to get those boards to work?


Leave a Comment

Download Our Free eBooks and Resources

Get instant access to our FREE eBooks, Resources, and Exclusive Electronics Projects by entering your email address below.