OldGuyMeltsPlastic
OldGuyMeltsPlastic
When I tried running the app on port 5000, I got:  I expect this because I already configured the service to run in the background, so I don't have...
As the feedback seems to indicate that the cameras are in use by whatever process is running on port 5000, I try to point the browser to http://192.168.68:5000, and the...
I am wondering if I am missing some package(s) that this code has as dependencies?
So, stopping the background service and starting the flask app from the command line on port 5000 allowed me to see both camera feeds in the web app in the...
Here's raspiCamSrv.service:  Here's kTAMV_server.service:  I have uninstalled kTAMV just to confirm there is no conflict, and rebooted. Now when I run `sudo journalctl -e`, I see that raspiCamSrv...
I also just ran a sudo rpi-update, to get myself onto the latest kernel: Linux gemeaux 6.6.22-v8-16k+ #1747 SMP PREEMPT Wed Mar 27 17:06:56 GMT 2024 aarch64 Still see only...
Yes, changing the After line to: After=network-online.target moonraker.service has resolved this for me.

No, thank you for your work and assistance! I know just enough about Linux to be dangerous. ;-) Now to see if I can resolve the errors I am seeing...
Alright, I fixed kTAMV by updating Flask to 3.0.2 and Werkzeug to 3.0.1 in its own venv, and it is now running as designed. But I am still getting inconsistent...