- Messages
- 647
- Points
- 43
litedev.us.hik-connect.com
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
How did you get this on a K series I have an 8p K series running the last version V4.22.000 build 190821 but cant take it to anyother as i was aware hik pulled the k series from gui 4
Thanks, I tried "litedev.sgp.hik-connect.com"
But my NVR changed it to "litedev.eu.hik-connect.com"...
Anyway it works and my IP address updates within the hik connect cloud now.
Unfortunately the alarm input notifications are still not playable from the hik connect app.
Upgraded to V4.40.015 build200616 firmware last week and all went without any hitches and has been working fine.
Yesterday I decided to do a manual restart via the NVR GUI and now I’m getting “Not Enough Network Bandwidth“ error message and lost one of my IP cameras
if I restart again the fault moves to another IP camera and I lose connection to the IP camera via local and remote viewing..
very odd considering my setup has been working fine for the past year...
can I roll back to a previous version ?
I had the same - i just plugged in 1 at a time, and reduced the quality. Once you have them all online, push up the quality again until you find the breaking point, I did this. My issue is badly terminated cabling.
Having the same issues here after the first time of ever updating the FW.Upgraded to V4.40.015 build200616 firmware last week and all went without any hitches and has been working fine.
Yesterday I decided to do a manual restart via the NVR GUI and now I’m getting “Not Enough Network Bandwidth“ error message and lost one of my IP cameras
if I restart again the fault moves to another IP camera and I lose connection to the IP camera via local and remote viewing..
very odd considering my setup has been working fine for the past year...
can I roll back to a previous version ?
Backup current settings - do the upgrade with a lower version firmware.Having the same issues here after the first time of ever updating the FW.
How do you roll back the FW?
ThanksBackup current settings - do the upgrade with a lower version firmware.
You may want to look for my other post, how I dealt with it, it may or may not work for you
It's also largely nonsense from what I can see, since I get the issue both connecting via Hik-Connect AND via a local LAN connection (directly to NVR_IP_ADDRESS:8000) and also on the local LAN via the web interface.Hi @rickwookie
We tested this ourself with a 2385 turret connected to our 7716NI-I4 NVR and we saw a very similar problem and we hadn't had problems streaming 8MP cameras from this NVR before so we assumed it was probably related to an update in one of the recent v4 firmwares. We took this issue to Hikvision support, they asked to remote access our NVR to take a look at the issue and after some fiddling with many settings the stream did improve but to make this improvement as you will see from the Hik Support response below they had to drop the resolution:
From the test, we can see the stream freezing issue can be solved by lowering the camera resolution, which means the issue comes from the network environment. I would suggest the customer lower the mainstream resolution and change the encoding format to H.264. If he insists to live view 8 MP video on Hik-Connect, he can configure DDNS which can improve the video. Please find the relevant how-to document in the attachment.
Obviously, lowering the resolution is not a great solution (especially when they had to drop it to 720p to stream smoothly) and so for the time being if you absolutely need the 8MP resolution on the mobile app you will have to port forward your NVR and add it to the app with DDNS, you can do this using the documents attached.
We were not happy with this answer and we asked that they pass this on to their R&D team because I assured them we have not had problems streaming 2385 and other 8MP cameras through this NVR on earlier firmware and that the problem has only appeared when a recent firmware was installed. (we are not 100% sure which version introduced the problem as we are a version behind v4.40.015) Hopefully, they will investigate further and solution will be introduced in a later firmware update.
Who's brave enough to try the latest firmware first. I'm hoping it fixes a few more problems than they mention.
Maybe the release notes should show what it breaks.