Thank you!

Thank you!

Hi, thanks for your message and appreciation for the project. I checked the article and can see the videos (they’re on YouTube). Anyway, if you still can’t see them, I’ve provided the direct links below:

https://youtu.be/A7S0zZ4Hm50

https://youtu.be/8Ir37-reLyQ

Thank you very much for your kind comment and interest in the project!
The project was created by setting the application IP as 192.168.1.190. Therefore, the URL should be http://192.168.1.190:3000/login
This is the default IP, found in two files: main.py in the main project folder videosurveillance/ and config.js in videosurveillance/frontend/src. It was set as a static IP as described in the “Let’s set the static IP” section. Therefore, if you changed the Raspberry Pi’s default IP, you should also update it in the files listed above. You can also check the correct operation (and any error messages from the backend and frontend containers) with the docker logs videosurveillance_frontend -f and docker logs videosurveillance_backend -f commands to verify that everything is working properly. You can also test the login API from the URL http://192.168.1.190:8000/docs also listed in the “Rest APIs available on BE and their list” paragraph to see if it returns an error.

I have tried to reset the password using the reset_admin_db.sh without success, any help?

Thank you.

Thanks! Glad you found it interesting!

Thank you very much for your kind comment and interest in the project!
It’s great to hear that you’re working on a senior project involving an autonomous surveillance robot — this system could definitely help you build a solid foundation.

Here are answers to your questions:

1. Can this surveillance system be used remotely while I’m away at school or work?
Yes, remote access is fully supported, thanks to the integration of WireGuard, a modern and secure VPN solution.

However, please note that certain technical requirements must be met, as explained in the article. For example:

You need to have access to your home router’s configuration panel.

The router must support port forwarding or public IP access.

You should be able to install and configure the WireGuard client on your remote device (laptop, smartphone, etc.).

Once properly configured, you’ll be able to access the system’s web interface as if you were at home, securely and without exposing any ports to the public internet.

2. Is it possible to use the full (non-lite) version of Raspberry Pi OS?
Possibly yes, but it’s not recommended or officially supported.

The project was designed and tested using Raspberry Pi OS Lite, which is headless (no desktop environment), lightweight, and optimized for performance and stability in embedded environments.

Using the full version of Raspberry Pi OS should work in theory, since all required components (like Docker, Docker Compose, etc.) are installable on that version too.
However, since this configuration was not tested, we cannot guarantee full compatibility or stability. Some services or behaviors might differ due to background processes or resource usage by the desktop environment.

In short:
It might work but it’s at your own risk.

If you decide to try it, feel free to share feedback — it might be helpful for others too.

Good luck with your senior project!

Thanks again, and greetings from Techrm!

I have two questions:

1. Can this surveillance system be used remotely, allowing the robot to operate at home while I am away at school or work and still access it?

2. Is it possible to use an updated version of the software for Raspberry Pi instead of the lite version?

Thank you for appreciating the article. Greetings from Italy