I also used a monitor (with a mini HDMI adapter) for troubleshooting purposes. For storage, I used a 16 GB SD card, with power provided via a 2.5 amp Micro USB power supply. For this build, I chose the Raspberry Pi Zero W because of its low price and compact size, along with a Pi Camera V2.1. To use MotionEyeOS, you'll need a Raspberry Pi board with Wi-Fi capabilities (or a Wi-Fi dongle) and a camera. The official Raspberry Pi Zero case includes space for a camera. I could be wrong and the client might query something else and not receiving an answer could make it stop from taking any further actions, but I am not sure about this.While the HDMI and OTG USB adapter aren't strictly necessary, they can be quite helpful. My guess is that it could actually work with these three in the following order: GetSystemDateAndTime -> GetProfiles -> GetStreamUri. What I would do is create a simple C/C++ web server with predefined xml answers for these 3 requests, take a general ONVIF client like ODM (Onvif Device Manager) and try to connect to the camera from it and see what happens, if any other requests are issued that block the flow or not. One important request is GetSystemDateAndTime - ONVIF clients query this since the timestamp is used in the authorization token. The ONVIF client may as well send a lot of other requests like capabilities etc., but you could ignore those for now. The ONVIF client may as well send some authorization headers, but you might for start just as well ignore them and implement authorization when the actual streaming is running. The GetProfiles request itself does not depend on any input parameters so you should be safe here.

I assume since you are writing a solution for an exact use case, just predefine the xml response to this request and with a single profile and a hardcoded token. This is why you need to implement the GetProfiles request. I assume there are some out-of-the-box RTSP streaming solutions for Raspberry Pi so I won't talk about how to setup live555.Ģ) For the GetStreamUri to work, the client needs to know a profile token for this specific stream.

Here is a similar question on how to implement ONVIF compliant interface that I've already tried to answer, but since in this case I guess you just want the video stream and using gSoap or anything would violate the third party software limitation, here is what I would do:ġ) For an ONVIF client to be able to retrieve your stream URL, you need to implement a response to the GetStreamUri ONVIF request - through that you can return the actual RTSP link and if you have some sort of RTSP server running (I guess live555 is the most common choice these days) then the client will continue connecting to the RTSP server and will get the stream.

Raspberry pi onvif