Raspbery Pi2 Camera Monitor w/Rpisurv

SvenVD said:
Hi please do read the first lines of the config file

#THE FOLLOWING ARE EXAMPLES WITH ALL OPTIONS EXPLAINED, REMOVE OR ADAPT THEM WITH YOUR REAL CONFIG

In your config file all the examples are still there, please remove them first
Click to expand...

@SvenVD
I use rpisurv since version 1.0 and have installed it 4-6 times.
And version 2 is even a lot better because of more function than version 1.
Really like it!!!

But the configuration in the surveillance.yml is somewhat disgusting.
It is not at all self explaning, even after a view installations.
Especially the usage of spaces and not using CF is for me totally abstruss.

I hope we can get in a future version a simple website to configure
or if not,
I would appriciade a major change of the surveillance.yml file:

  • Dropping all spaces,
  • Beginning each config line at the beginning of a line

So the look and feel would be like all other Linux config files.

Anyhow I don't what to miss rpisurv and thank @SvenVD for is great software!
 
  • Like
Reactions: smole and msantic
Hi I agree on the website. I don't agree on the config file. yaml is quite a beautiful solution to configure all the complex options and hierachy rpisurv needs. It s the middle ground for human readers and machine interpreters. Nowadays most new tools are using yaml. I agree it needs some level of expertise to edit it, therefore the website would be a solution. The yaml file is perfectly suited to easily base a website on.

The other option would be xml XML Introduction or json JSON Example. IMO both are harder to edit then yaml.

A minimal config with one screen
 
  • Like
Reactions: cball and msantic
Thanks, this looks easier.

Still I believe, there can be done more:

Code: 
#THE FOLLOWING ARE EXAMPLES WITH ALL OPTIONS EXPLAINED, REMOVE OR ADAPT THEM WITH YOUR REAL CONFIG
#THIS IS A , INDENTATION IS IMPORTANT. ALSO DO NOT USE TABS FOR INDENTATION, BUT USE SPACES

#Here the basic configs need to be done
essentials:

#For the first screen
screen:
-camera_streams:
#Example for XY
- url: "rtsp://<user>:<password>@<ip or dnsname>:<port>/videoMain"
#Example for whatever
- url: "http://<ip or dnsname>:<port>/suffix"
#Example for Hikvision
- url: "rtsp://<user>:<password>@<ip or dnsname>:<port>/play1.sdp"
#Example for Dahua
- url: "rtsp://<user>:<password>@<ip or dnsname>:<port>/cam/realmonitor?channel=1&subtype=1"


#!!!Normal users do not need to edit this section!!!
advanced:
#@SvenVD: Here is litte explanation for update_stats necessary
update_stats: True

#In case the automatic doesn't recognize
fallbacks:
#The resolution can be fixed here
resolution:
width: "1920"
height: "1080"

In this example I tried to avoid spaces.
Would this work?

This way it looks like a regular Linux config file.
 
I changed my surveillance.yml to the following but still the Pi boots with no video other than text. Is it necessary to delete the cameras that don't exist? I only have one. This replaced the file in Home/Pi/rpisurv/surveillance/conf

#THIS IS A YAML FILE, INDENTATION IS IMPORTANT. ALSO DO NOT USE TABS FOR INDENTATION, BUT USE SPACES
#THE FOLLOWING ARE EXAMPLES WITH ALL OPTIONS EXPLAINED, REMOVE OR ADAPT THEM WITH YOUR REAL CONFIG

essentials:
screens:
- camera_streams:
- url: "rtsp://admin:admin@192.168.16.179:554/cam/realmonitor?channel=1&subtype=1/cam/realmonitor?channel=1&subtype=1"
- url: "rtsp://<user>:<password>@<ip or dnsname>:<port>/videoMain"
- url: "http://<ip or dnsname>:<port>/suffix"
- url: "rtsp://<user>:<password>@<ip or dnsname>:<port>/play1.sdp"

#!!!Normal users do not need to edit this section!!!
advanced:
update_stats: True

fallbacks:
resolution:
width: "1920"
height: "1080"
 
Ok. I am getting closer. I now have the RPISURV screen visable via the HDMI out from the PI. It says cannot open stream. I can however open the stream on VLC player without issue. Below is my config text.

#THIS IS A YAML FILE, INDENTATION IS IMPORTANT. ALSO DO NOT USE TABS FOR INDENTATION, BUT USE SPACES
#THE FOLLOWING ARE EXAMPLES WITH ALL OPTIONS EXPLAINED, REMOVE OR ADAPT THEM WITH YOUR REAL CONFIG

essentials:
screens:
- camera_streams:
- url: "rtsp://admin:admin@192.168.16.179:554/cam/realmonitor?channel=1&subtype=1"

#!!!Normal users do not need to edit this section!!!
advanced:
update_stats: True

fallbacks:
resolution:
width: "1920"
height: "1080"
 
Ok Figured it out. It did not like subtype=1 it had to be subtype=0 What is the difference?
 
subtype=0 or subtype=1 are different channels on your ip camera, what they mean depends on your configuration of them on the camera.

For all other things rpisurv, support questions, feature request, showcases are moved to Rpisurv
 
User feedback sought - I am using Hikvision cams and using H265 for recording the main stream to SD card. I am going to use the secondary stream h264 (640 x 480) for the Rpisurv display. On a 32-47" TV do you think a 4 x 4 grid will look good enough? Do most people use the main or sub stream?

Thanks for any feedback.
 
obqo said:
User feedback sought - I am using Hikvision cams and using H265 for recording the main stream to SD card. I am going to use the secondary stream h264 (640 x 480) for the Rpisurv display. On a 32-47" TV do you think a 4 x 4 grid will look good enough? Do most people use the main or sub stream?

Thanks for any feedback.
Click to expand...

Answered at Basic Questions for Hikvision
 
I have no experience with HLS streams,maybe someone else? but if omxplayer supports it you can use it with rpisurv
 
Fun read.

For anyone running Kodi there's an app now called Surveillance Cam.

Pro. Easy config & navigation (Using TV remote)
Con. Displays single cam Only. Only 3 cams can be added.
 
You must log in or register to reply here.
Top Bottom