Hello,
I have the NVR K8208-W from Sannce (N48WHE) and have updated to the firmware 3.2.0.2 from 2021 and activated RTSP, but when I want to access it via the RTSP URL, the image of the NVR operating system freezes on the monitor and the NVR restarts after a short time. I tried to use the bubble URL via go2rtc, but that doesn’t work either. I get the error message from go2rtc: 404 Not found. I think I don’t have the right URL to access it. I’ve also tried to monitor the connection with Wireshark to read out a URL, but I haven’t found anything. I’m not very familiar with the program either.
Maybe someone has another idea.
Hi,
I was able to configure the stream for a K8208-3WS with the following:
rtsp://user:pass@ip:80/ch0_0.264
But I’m not able to get a snapshot, I have tried every URL but all are returning 404, Does anyone have an idea of this?
Also, I want to share this page that has a lot of URL for different camera models, you can input your NVR IP and credentials and this generates the URL that needs to be used, is really helpful if you don’t know what URLs can be valid for your NVR.
I hope this help someone:
Thanks!
1 Like
Has anyone done this? I have the ip of the camera, but going to it in a web browser just by http://ip gives me a page not found on this server error. So I know I’m hitting it, but does anyone know any direct webpage name on these cameras (HM241 for me)?
Hello everyone, I have a WIFI NVR with 4 cameras, all from the Reigy brand. Yesterday the NVR stopped working. There was a beep and then there is no more image on the monitor with the EseeCloud app. I can no longer log in via the IP address of the NVR. I have left the power off for a few hours, but that does not solve the problem. The NVR only beeps once a minute and otherwise the NVR does nothing. Does anyone know what else I can do?
In the meantime I am also looking for a new NVR. But every NVR on Amazon and AliExpress states that they are only suitable for cameras from the same brand. Is that a sales trick or is that really the case? Many of the NVRs look the same.
Hopefully someone from you has answers. Thanks in advance!
Rob.
This is developer talk and it goes over my head a lot of it 
Can someone add in the repository addon an interface for the Esse cams? Thank you,
Ernesto
Hi, I have a NVR I want to integrate with HASS on RPI4
I set hass with your plugin
I set the NVR as described
When I click Test nothing happens
Logs shows nothing useful.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting dovecot
Starting postfix
Starting python server
[2025-04-14 10:29:01 +0200] [270] [INFO] Starting gunicorn 20.0.4
[2025-04-14 10:29:01 +0200] [270] [INFO] Listening at: http://0.0.0.0:8080 (270)
[2025-04-14 10:29:01 +0200] [270] [INFO] Using worker: sync
[2025-04-14 10:29:01 +0200] [272] [INFO] Booting worker with pid: 272
What have I missed?
Where should I find informations regarding camera alarms?
Thanks
I don’t know 
I no longer use or maintain this. I moved everything from an r pi to a laptop about a year ago and haven’t used it since.
but I guess troubleshooting step 1 is verify port 25 is open?
Sziasztok! K8208-W NVRen miként tudom beállitani, hogy csak emberi mozgást vegyen fel és mindenfle levélmozgást, pokhálo mozgást ne rögzitsenek a kamerák?
I spent almost three sleepless days trying to figure out how to connect this camera to Firgate, and I finally managed it. The problem is that the camera doesn’t need internet access. If the camera gives you a cloud ID, you won’t be able to connect it. The stream you need to use for eseecloud, which was my case, is eseecloud://admin:[email protected]:80/livestream/12
What you need to do is the following: remove the camera from your eseecloud app. Then, link it again, but only so it connects to Wi-Fi, NOT the cloud. When it beeps to indicate it’s connected to the Wi-Fi network, it doesn’t matter if the timer on your phone app hasn’t finished. As soon as it beeps, unplug the camera from the power outlet. Then, go to your firewall or simply disconnect the fiber optic cable from your router and turn on the camera. The camera will turn on, but it won’t… You’ll have the camera configured in your app. Go to “Add Camera” and look for the “Manual IP” option. Find the camera using the IP address assigned by your router, connect it as is, without a password, and set it to 1 channel, etc. Once you’ve configured the camera, go to the Eseecloud options and set a password (I used 12345678). That’s it! The camera connects locally, not with its cloud ID. You save yourself the expense of buying a DVR.
The Chinese are making hardware hacking increasingly difficult; they’re forcing you to buy their cloud service!
I tried everything, I extracted the firmware with CH341, I tried flashing a bunch of firmwares, but the problem is that anyka_ipc doesn’t come with RTSP anymore, it’s a real nightmare, but in the end I managed it!!