Greetings everybody,
Started working on native kotlin android sadp tools with posibilities for live view and configuration. I will post updates as it goes.
registration and login(statistical data)
SO far:
-Discovery via multicast
-Device info
TO DO:
Activation
Change net params
Change...
Maybe this would ve more suitable, or atleast something like this. As i dont believe hikvision devices support ethernet over usb port
https://www.epever.com/product/epever-wifi-adapter-2-4g-rj45-d/
I have made local test using the same firmware as yours, as well tried different poe NVR on different platform. Result is same.
Conclusion:
It has nothing to do with virtual host neither its a backdoor, it is plug and play script. Steps to reproduce:
-PoE NVR
-Do not activate via SADP Tools...
Ive seen firmware versions where nvr autologins without asking for credentials. I guess there are multiple versions then. But yes it did ask me for logins on others as well.
Ill fire debug on v5 and see whats up behind
This is virtualhost in action. The only problem is ngtest shouldnt be there. Usually virtual host uses default channel password/ admin password to open up settings on camera.
New firmware v5+ can start virtual host on configuration click, its not located in network -> others anymore. So perhaps...
It should work, check your parsing.
The response you get is multipart data, so dont parse json only but also binary after boundery
The other way around is doing manual ISAPI pull and then doing GET request to pictureURL
is it HTTPListener, ISUPListener , ISAPI CRUD or SDK ?
Please be more specific.
Did you enable option to capture image on authentication inside device configuration?
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