My NVR looks totally different, but I have no doubt it’s the same guts. You may or may not have the RTSP option somewhere in the options already, but I know I didn’t with the stock firmware. You’d have to dig around in the menus.
Hello
may I ask what brand your NVR is? I have a YESKAMO NVR with a 2019 firmware as well.
My UI looks identical to the screenshot you posted minus the RTSP server option.
I didn’t send a query to YESKAMO customer support today hoping they will enlighten me but in the meanwhile thought to ask around.
The link that *.rom that you shared is that brand specific?
When you flashed the new firmware did you need to reconfigure the NVR? I.e. re-link the cameras etc?
Yeah. I have looked through them all. No such option for sure.
There is another comment claiming that he got the option after an fw update so I will ask that person the same question.
By the way hen you flashed the new firmware did you need to reconfigure the NVR? I.e. re-link the cameras etc?
Nope, no reconfiguration required after the update.
Honestly, I’d just send Yeskamo’s tech support an email asking if there is an update, it’s going to be way easier and faster.
I did right after your last message. Now hoping they are as responsive and accommodating as in your case. 
Thanks for the guidance!
Ilias
Hi everyone. I’ve also been trying to connect my icatch DVR to home assistant for some time, but I’ve never found a solution. I created a topic about it some time ago (Help Need: Integrate icatch dvr into Home Assistant, Headers in FFMpeg Camera Platform). Now I came across this topic and I hope that I have found a solution. the problem is that I can’t find the url for a high quality video stream. I have analyzed a connection with wireshark when I use the native DVR app (socatch). you can find the results in my topic. I have never used wireshark but seeing the tcp flow I understood that there is a get request to the path “/cgi-bin/net_video.cgi?hq=0&iframe=65535&pframe=65535&audio=0”. below I found a “Magic” parameter which I believe is internal to the app. the dvr has 16 channels but it seems that the connection towards a single path (even changing cameras from the app, the request remains the same). I have tried to setup go2rtc in various ways (many described in the documentation) without having any success. Does anyone know how to help me?
Hello again,
as you suggested I contacted my NVR manufacturer and they sent me the following firmware:
FWHI36D_20211021_W-NVR_K8208-W_3_2_0_2_9013160200_RELEASE.rom
Can you confirm what firmware did you receive?
The reason I am asking is that I don’t see any option for RTSP server:
That screenshot is after the update to version 3.2.0.2
I will seek further support from the manufacturer but since they take a bit of time to reply I am exhausting my options.
In post 108 of this thread I saw this:
As you can see the firmware version is in all, identical to mine minus the fact that it is version 3.1.6.0
and the build date is 7 months earlier.
FWH136D_20210310_W-NVR_K8208-W_3_1_6_0_9013160200.rom
for comparison:
FWHI36D_20211021_W-NVR_K8208-W_3_2_0_2_9013160200_RELEASE.romFWH136D_20210310_W-NVR_K8208-W_3_1_6_0_9013160200.rom
Kind regards,
Ilias
Hi Stefano,
just texting in case you missed my previous posts.
Desperate for help!
Kind regards,
Ilias
Hello @Ilias,
Unfortunately I’m trying to remeber but i cant… I have tried wireshark also with mine DVR and i can’t find the strings… but i remember that i have read somewhere the strings in some wireshark dump…
It’s really strange that you have a different URL for streaming…
I’ll trying the last thing using and old windows version with Internet Explorer to check where i have seen the bubble string.
Best regards
Stefano
I have my nvr camera working with bobble protocol for a long time now suddenly it is not working anymore. I have upgaded to 1.7.1 but the addonn do not start at all and log only say :
13:06:15.438 INF go2rtc version 1.7.1 linux/arm64
13:06:15.440 INF [api] listen addr=0.0.0.0:1984
13:06:15.441 INF [rtsp] listen addr=0.0.0.0:8554
13:06:15.442 INF [webrtc] listen addr=0.0.0.0:8555/tcp
with or without yaml file log always show this addon do not start at all and log only show if i restart hassio and not when i restart the addon
In log viewver i have nothing but addon is red with “the add-on is stopped”
it is possible to use a previous release because 1.5 stopped working but it stars
my yaml
streams:
Salone: bubble://xxxxxx:80/bubble/live?ch=0&stream=0
GiardinoFronte: bubble://xxxxxx:80/bubble/live?ch=1&stream=0
GiardinoRetro: bubble://xxxxxx2:80/bubble/live?ch=2&stream=0
GiardinoLato: bubble://xxxxx:80/bubble/live?ch=3&stream=0
log:
level: info # default level
api: trace
exec: debug
ngrok: info
rtsp: warn
streams: error
webrtc: fatal
Hello,
This is my NVR model N8216-2
Try to write to Alexx here:
Hi again,
just wanted to let you know that although I reached nowhere with bubble source, I got it resolved by firmware update.
Now I have RTSP server enabled on the NVR.
Thank you @Grauwulf!
I have it finally integrated with HA 
of course using the AlexxITs awesome go2rtc. Thank you @AlexxIT for the outstanding work!
Thank you @Wes93 for all your contributions.
Love the HA community!
If only the world was run by open source communities. It would have been paradise.
Perfect, i’m happy that you have solved your problem
1 Like
I’m glad you got it sorted!
1 Like
Hello, thanks to the superb work of @AlexxIT I was able to install go2rtc and with the bubble command I receive the stream from my cameras.
How can I put this video stream on my HA dashboard?
Hi all,
I have a REIGY W-NVR K8210-3WS and I’m trying to find a proper way to set the cameras in frigate but so far without success.
I have frigate install on a NAS Docker and firgate integration on my HA.
Everything works fine but I cannot see the cameras of the above NVR in frgiate
I’m not sure what is the best way to try:
- Bubble command: I have succesfully downloade the version 1.7.2 of go2rtc in the docker config of frigate but not sure it is is enough or what are the next step.
- Try to update the firmware: not able to find it someone have the same NVR
The current frigate config is:
go2rtc:
streams:
mjpeg_cam:
- "bubble://admin:[email protected]:80/bubble/live?ch=6&stream=0"
- "ffmpeg:mjpeg_cam#video=h264#hardware"
cameras:
parcheggio: # <------ Name the camera
ffmpeg:
inputs:
- path: bubble://admin:[email protected]:80/bubble/live?ch=6&stream=0 # <----- Update for your camera
input_args:
- -headers
- "Authorization: Basic YWRtaW46"
mjpeg_cam:
ffmpeg:
input_args: preset-rtsp-restream
inputs:
- path: rtsp://127.0.0.1:8554/mjpeg_cam
roles:
- detect
- record
parcheggio and mjpeg_cam are two config attempts for the same NVR camera but both fails
192.168.1.84:80 is the IP and Port of the NVR
Any help?
thanks
Hello again,
I’ve almost managed to configure my DVR, but I can’t get a video stream. When using go2rtc, it shows a “loading” message, but nothing more.
I would like to provide more information that might be helpful. I have a DVR from the brand iCatch. To operate it, it uses a Chinese app called “iWatchDVR” for PC/Mac or “SoCatch” on the mobile version. I’ve tried contacting the manufacturer, but I haven’t received any response. Unfortunately, it seems that the connection is not through RTSP but through HTTP.
I’ve discovered that it’s managed by a Hi3520 chip, which seems to be connectable through bubble source, but I haven’t been able to configure it.
By sniffing with Wireshark and connecting through the app, I’ve found that the app obtains the stream by connecting to this address:
http://192.168.1.92:9000/cgi-bin/net_video.cgi?hq=1&iframe=65535&pframe=65535&audio=65535
The complete request is:
GET /cgi-bin/net_video.cgi?hq=0&iframe=65535&pframe=65535&audio=0 HTTP/1.1
Host: 192.168.1.92:9000
Authorization: Basic ............
Magic: 406F8261-B1E0-4A7C-9888-6949F5APEC9F
HTTP/1.0 200 OK
Content-type: multipart/x-mixed-replace;boundary=--myboundary
--myboundary
Content-Type: application/octet-stream
I can’t understand what is this “Magic” parameter, does someone know what it is?
The strange thing is that the request doesn’t specify a specific channel, but it seems that the URL is always the same.
Furthermore, I can’t figure out the encoding used by the app.
I’ve connected to the URL through go2rtc, but as I mentioned earlier, I only see the “loading” message.
Does anyone know how I can configure it? I’ve been trying to set it up for years, and go2rtc seems like the right road.
my config and some screenshot:
streams:
casameomartini: "http://admin:[email protected]:9000/cgi-bin/net_video.cgi?hq=1&iframe=65535&pframe=65535&audio=65535"
casameomartini2: "bubble://admin:[email protected]:9000/cgi-bin/net_video.cgi?hq=1&iframe=65535&pframe=65535&audio=65535"
casameomartini3: dvrip://admin:[email protected]:9000/cgi-bin/net_video.cgi?hq=1&iframe=65535&pframe=65535&audio=65535
casameomartini4: http://admin:[email protected]:9000/
In order for every stream:
