This model name sounds more like OEM ezviz than OEM hikvision.
Ezviz tend to distance between hikvision and work with mobile app only. Every new firmware removes more and more desktop support plus integration with hik
If you use perimetar protection channels for NVR VCA, you cannot use Motion detection on any channel with Human/Vehicle checkmark. You Can disable that and use a standard motion.
Check if there is on any channel Motion 2.0 enabled. Perhaps overlooked?
When setting up motion, make sure the Record Channel is ticked under linkages. In order to be shown on bar, the recording log has to exists besides the footage.
So bar is being filled by log timestamps
Cheers
Ditch query params and only use /ISAPI/Security/users
You dont need to add encrypted data it can be plain text.
Authorization to device Digest
This security iv= is just token for device interacting with itself
There is documentation how to set alarm host via PUT request. You create a TCP or HTTP server listener to fetch data.
Second option is to use API to retrieve passes by polling POST requests with time interval.
to get api register and sign NDA at tpp.hikvision.com
Cheers.
There is no known hikconnect exploit at the moment. So going via their cloud should be safe from internet side, but as ive stated it is exploitable within your lan.
So whoever gets to your lan, or your PC gets virus, it could use camera for accessing everyhting.