Support for Security Camera System via NVR - ESeeCloud/dvr163

Hello Steven
Unfortunately the only software that I have found with custom header is Shinobi CCTV.
The alternative way is use a proxy that process all request adding the Header but the stream could not work with other software…
The only that work is ffmpeg (Shinobi is based on ffmpeg) with VLC directly won’t work…

Hhmmmm. Question, can I, just like in blue iris, stream Shinobi so that i can access it through other devices in the house through the web?

Yes you can, but when you add the cameras in ShinobiCCTV you don’t need to add also in blue iris or something else, you can stream directly from Shinobi to other devices in your house

Got it. I went my way last night installing shinobi cctv. Sorry for derailing the thread haha. But hm, how would I go my way to adding these cameras streams? would I click on add monitor and add the url to the full url path in shinnobicctv? I dont see an option for ffmpeg.

Hello Steven,
You should use the settings like my screenshot:



Select Advanced:
image
Then on Custom add the header

-headers "Content-Length: 59" -headers "User-Agent: JUAN ProductCheck" -headers "Host: abc" -headers "Authorization: Basic YWRtaW46"

For stream set like here:

Shonibi use natively ffmpeg so no other settings or something else ;-D
Be careful, if your stream is H265/HEVC you should use the link from shinobi in VLC or enable JPEG MODE here


Dropdown menu when click in upper left corner of the page

Best Regards
Stefano

Hey West, sorry for not being able to respond and thank you earlier. I had been bussy to test this out and to reply, so sorry if I made you feel ignored!

I have tried setting up the camera with your setting but in all honesty, I might lack the experience with shinovi to get it to work. Poseidon over http or websocket wouldnt work, and to make sure that was the case, I even tried it on another camera (5MP Amcrest camera). I did get both cameras to work using hevc(h.265), but they also ran poorly/extremely delayed. I guess I will have to keep working on understanding this, wish i could just use blu iris haha, it just works in a sense.

So i have a firstrend nvr but its a juan dvr163 variant, and my cameras are used the “n1” protocol, same crappy nvr system everyone is talking about here.

There are ton of rebranding of the same nvr but has anyone ran a cross a nvr that supports this camera protocol and has rtsp support or is everyone pretty much exactly the same and requires eseecam for remote viewing.

Ive been able to use the low resolution snapshot in HA but thats about it.

Hi,
I find the ones from the cameras themselves (subject to them being the same as mine) are better res than the low res ones from NVR…

http://192.168.1.xxx/snapshot.jpg

So i updated the firmware of my NVR which is a k8208-w model, with the following firmware and under network settings there is now a radio box for a RTSP Server under network settings! I don’t know if my firmware was just way out of date “circa 2019” and other have discovered this but I’ve tried every darn RTSP address I could find and could not discover any way to pull a stream from the NVR.

http://download.dvr163.com/NVR/WIFI--NVR--IPC/K开头/FWHI36D_20210310_W-NVR_K8208-W_3_1_6_0_9013160200.rom

1 Like

Thank you @pgross for your hints :slight_smile:
I’ve just updated my NVR firmware to this version.
I will also try to follow this instruction. I do hope it will work :slight_smile:

@mrkricfalusi try scanning the NVR with NMAP and see if it opened any ports!

I have the K9604-W which isn’t listed on their firmware page :frowning: I was able to auto-update via the NVR but it got me from 2017 to 2019 and no RTSP checkbox.

I have a K8208-W as well, but apparently my hardware version is too old to be able to update the firmware (I have hardware version 1.1.0, but the vendor I bought mine from, OOSSXX, tells me you need h/w version 3.x to be able to use the 3.x firmware). In case it helps for comparing against someone with the updated firmware with the RTSP server enabled, here’s an NMAP scan of the old version (firmware 2.8.8.11):
image

hi, did you find a way to connect the 9604-w NVR?
thanks

1 Like

I’ve got a 9604-W, I unziped the firmware and it’s just a linux system with a bunch of directories full of scripts, can anyone try to understand what’s going on? There is even the network configuration

1 Like

Did you find an way for it?

I´have the Same System and i want to integrate it also in Home Assistant, but i don´t find the RTSP Stream :frowning:

Hello to everyone!! Finally I have some news about this shit and Homeassistant!!

The solution that I have found, better then the old Shinobi, it’s Frigate!!

You just install the addon from HA addon store then make the config file and everything works like a charm!

Now I’m on mobile so when I come back to home I will add my config file!! I have all cameras working well and very stable, but substream because the main stream slow down my system.

Best regards
Stefano

2 Likes

Hi @Wes93
Can you please share your config file?

Hello,
sorry for my delay, this is my config file:

mqtt:
  host: <IP>
  user: <User>
  password: <Pass>

#logger:
  # Optional: default log level (default: shown below)
#  default: debug
ffmpeg:
  # Optional: global hwaccel args (default: shown below)
  # NOTE: See hardware acceleration docs for your specific device
  #hwaccel_args: []
  hwaccel_args:
    - -hwaccel
    - vaapi
    - -hwaccel_device
    - /dev/dri/renderD128
    - -hwaccel_output_format
    - yuv420p

#  input_args:
#    - -headers
#    - "Authorization: Basic YWRtaW46"

# Optional: RTMP configuration
# NOTE: Can be overridden at the camera level
#rtmp:
  # Optional: Enable the RTMP stream (default: True)
#  enabled: True

detect:
  enabled: false

cameras:
################# Telecamere DVR163 #######################
  parcheggio: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: http://192.168.0.50/livestream/12 # <----- Update for your camera
      input_args:
        - -headers
        - "Authorization: Basic YWRtaW46"

  bagnostudio: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: http://192.168.0.51/livestream/12 # <----- Update for your camera
      input_args:
        - -headers
        - "Authorization: Basic YWRtaW46"

  cameraospiti: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: http://192.168.0.52/livestream/12 # <----- Update for your camera
      input_args:
        - -headers
        - "Authorization: Basic YWRtaW46"

  giardinopost: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: http://192.168.0.53/livestream/12 # <----- Update for your camera
      input_args:
        - -headers
        - "Authorization: Basic YWRtaW46"

  ripostigio: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: http://192.168.0.54/livestream/12 # <----- Update for your camera
      input_args:
        - -headers
        - "Authorization: Basic YWRtaW46"

  parchmoto: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: http://192.168.0.55/livestream/12 # <----- Update for your camera
      input_args:
        - -headers
        - "Authorization: Basic YWRtaW46"

  laghetto: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: http://192.168.0.56/livestream/12 # <----- Update for your camera
      input_args:
        - -headers
        - "Authorization: Basic YWRtaW46"

################# FINR Telecamere DVR163 #######################
################# Telecamere RTSP #######################
  capanno: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: rtsp://192.168.0.57:554/realmonitor?channel=0&stream=1.sdp # <----- Update for your camera
      input_args: -an

  veranda: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: rtsp://192.168.0.59:554/realmonitor?channel=0&stream=1.sdp # <----- Update for your camera
      input_args: -an

  studio: # <------ Name the camera
    ffmpeg:
      inputs:
        - path: rtsp://192.168.0.60:554/realmonitor?channel=0&stream=1.sdp # <----- Update for your camera
      input_args: -an
################ FINE Telecamere RTSP #######################

#  i3mega:
#      ffmpeg:
#        input_args: -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -use_wallclock_as_timestamps 1
#        inputs:
#          - path: http://192.168.0.184:81/
#      rtmp:
#        enabled: False

#  test: # <------ Name the camera
#    ffmpeg:
#      inputs:
#        - path: http://192.168.0.184:81/ # <----- Update for your camera
#      input_args: -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -use_wallclock_as_timestamps 1
################ DUMP Telecamere #######################
#  parcheggio: # <------ Name the camera
#    ffmpeg:
#      inputs:
#        - path: rtsp://192.168.0.60:554/realmonitor?channel=0&stream=0.sdp # <----- Update for your camera
#          roles:
##            - detect
#            - rtmp
#      input_args: -an
###        - -headers
###        - "Authorization: Basic YWRtaW46"
##    rtmp:
##      enabled: True # <-- RTMP should be disabled if your stream is not H264
##    detect:
##      width: 2304 # <---- update for your camera's resolution
##      height: 1296 # <---- update for your camera's resolution

You can use the mainstream you just want it to have the record role only, use the substream with the detect role

Unortunately my PC is not performant and if i use the mainstream the CPU go at 100%