Hik-Connect - Local connect/view and app on Android closes

[Dave Howard]

We use multiple devices (Android phone + iOS IPAD + Android tablet) to view cameras on M2-series NVR.
These have worked successfully for number of years, both locally and when away from home accessing via web.

In last few months and primarily on newest device (Lenovo Android Tablet) Hik-Connect has timed out after 5-mins of viewing LIVE cameras either one or all seven; no difference.


I have variously cleared data, cleared cache, uninstalled and reinstalled Hik-Connect multiple-times. No difference.
All the time, the other Android phones and IPAD's have continued to work fine (mostly) both home and away. NOTE: In home these are not configured to look for local-IP.

Today after Xmas break I have tried again....
Uninstalled and reinstalled Hik-Connect on the Android tablet (Lenovo). This is showing V 6.7.150.

When connecting to NVR via LAN but using Hik-Connect service this is timing out after 5mins of Live Viewing (I guess I now accept on this device it's a feature!!) not happy tho.

When connecting to NVR using local device and local IP on LAN it appears to connect. Shows me cameras BUT when I go to live view any camera the app closes and nothing/zero/nada.

Is this a known issue on Hik-Connect now that the time out of 5minutes is persistent and local IP must be used if wanting to view 24/7 live camera(s)?
If the above is true then why do Android phones and iPADS still work fine using shared device not local IP address and stream 24/7?
Why on this Android tablet is the app appearing to crash and not show live feed from camera when connecting using the local IP address or shared device connection and what is fix?

NOTE: The main reason I purchased the Lenovo Android tablet was to have a larger than ipad screen that was mobile around home (not using TV's).

Thanks in advance crew for any insights and advice on how to get the Android Tablet working how it was pre-Oct24 when I could view live camera(s) 24/7 using Hik-Connect.

 

[JB1970]

Is this a known issue on Hik-Connect now that the time out of 5minutes is persistent and local IP must be used if wanting to view 24/7 live camera(s)?

This was always the case when viewing cameras via Hik-Connect P2P and doesn't time out when viewing 'local' device whether truly local (app device is on the same LAN as the DVR/NVR) or added using IP/Domain with port forwarding.

I think using DDNS (device three dot menu > Configure DDNS and entering port numbers along with login details switched connection the device from P2P to DDNS and gets around the 5 minute timeout.

As for the app crashing when selecting a camera, try toggling the setting for 'Hardware Decoding Preferred' to the opposite of what is currently set.

 

[trempa92]

there is workaround using HikPartnerPro SDK

 

[Dave Howard]

This was always the case when viewing cameras via Hik-Connect P2P and doesn't time out when viewing 'local' device whether truly local (app device is on the same LAN as the DVR/NVR) or added using IP/Domain with port forwarding.

I think using DDNS (device three dot menu > Configure DDNS and entering port numbers along with login details switched connection the device from P2P to DDNS and gets around the 5 minute timeout.

As for the app crashing when selecting a camera, try toggling the setting for 'Hardware Decoding Preferred' to the opposite of what is currently set.

Thanks as always @JB1970.

Did the toggling of Hardware Decoding on and then off, and this resolved. Weird as it really just set if back to what it was originally.

I found there was no need to change DDNS (never had that over last years on any device for HIK in house) which I'm thankful for

Thanks for the clarification on your first point "whether truly local .... " as this helped my understanding. I have to admit I'm puzzled though as literally nothing had been changed on Hik or by me on that device and it simply started the 5-min 'rule' thing after working for over 3 months AND other devices (ipad + Android phones) continue to work in the home without me using/specifying a local IP address. Anyway all working again now so I'll keep quiet