Rpi Camera streaming to Domoticz

[embee999]

Hi.

Has anyone had problems getting the stream from a Rpi Camera Noir? I am aware of the settings (from ispyconnect).

My AgentDVR installation on the same Rockpi4/Dietpi box with Domoticz has no issues picking it up - nor does TinyCamPro on the mobile.
Browser access is also ok.

The stream uses the Motion package on the Pi with it's user/password authentication.
I found VERY occasional connections on the Test page but never anything solid when I first set it up without the authentication, but now it's just never there.

Two other Foscam wifi streams are both connected to the Domoticz ok.

Is there any debugging for this?

[waltervl]

See wiki https://www.domoticz.com/wiki/Camera_Setup

The image url is the url to take a snapshot, not an url for a stream! Domoticz will take snapshots fast to emulate a stream.

[embee999]

My apologies, I should not have used the word stream. Both the Foscams are providing a SNAPSHOT.
The Pi camera gives nothing in Domoticz using either / or /raspberry.cgi or any of the entries in ispyconnect's list for the Noir.

It would be useful to know how to see the command that Domoticz is sending. Browsers, AgentDVR and mobile apps all work.

[waltervl]

See the source https://github.com/domoticz/domoticz/bl ... a.cpp#L174

But perhaps that has changed in newer raspberry OS or camera solution.
Can you get a snapshot out of your camera when you follow raspberry instructions for a snapshot directly?

[waltervl]

Did you install it correctly?
Is

Code: Select all

raspistill -o output_filename.jpg

working?
See also the raspberry camera section in the camera wiki.

[embee999]

Hmm. Originally, I did a 'normal' install and got the camera operable with the raspi-*** utilities working. BUT, I then installed the motion package. This is where it went wrong. The test commands now produce mmal errors. The documentation in motion is not terribly explicit and attempts to cover many scenarios in a short paragraph. Anyway, thanks for the pointer to the sources. I now have many tabs open and will start again.

This is a very revealing thread https://github.com/Motion-Project/motion/issues/1434

(Shows what can happen if you have a spare Pi, spare time and can't find decent replacements for network cameras that don't require subscription and only use mobile apps for configuration. I'm truly sick of reading reviews of the crap out there.)

Cheers

[ferrosk]

just a hint, maybe it would be easier for you to install motionEye:
https://github.com/motioneye-project/motioneye

or motionEye OS provide you with OS image that you just put on SD card and use RPI as video surveillance system:
https://github.com/motioneye-project/motioneyeos/wiki

[embee999]

Thanks. I was hesitant to use either projects based on the loss of the prime developer and the age of the documents.
If you have direct experience with the latest Pi4 board and noir camera then I am happy to give it a go.

[ferrosk]

If you have direct experience with the latest Pi4 board and noir camera then I am happy to give it a go.

Sorry, I do not have experience with motionEyeOS on rpi4. It is true motionEyeOS is not maintained anymore by its original developer, he had to step out from the project for personal reasons. Latest available motionEyeOS images support only rpi4 with older bootloader - see the issue on gitub

But motionEye project continues and has been taken over by new developers - curently migration to python3 is ongoing - see dev branch of the project and installation instructions are there. You can install Raspbery Pi OS on rpi4 then install motionEye from dev branch. But currently, for rpi camera you need to enable 'legacy camera' stack in raspi-config and it will work then.

[embee999]

Thanks - I knew about the new project. Following the github issue, I have the older bootloader (29/4/21) so I'll go ahead and try the latest motioneyeos and see where that gets me.

UPDATE #1: well, turns out the board is too new, regardless of the bootloader age for motioneyeos image. I'll look at the alternative.

UPDATE #2: I had to load Buster (Legacy) and then followed the latest dev instructions for motioneye. I then found a domoticz thread #15538 which gives a single picture view :

"In Motioneye added a user with no password. (only view rights)
Then i made the configuration as mentioned with: picture/1/current/
The standard port = 8765"

This worked for me. I suspect I had originally added just the motion package and not motioneye since that seems the only difference. One thing remains true - you cannot run the raspistill test since it generates the MMAL errors once motioneye is installed - that was a blind alley.

Thanks to everyone for their thoughts.