No idea. If you can get the URL, string, or whatever the payload of the QR code is, then you could use a third party QR encoder library on that.
Its just the serial number.
I guess I also need to be able to enable and disable p2p via API as well... I dont see that in there either...
But I have no idea if I am using the newest version of the API... or how to even get it.
I guess I also need to be able to enable and disable p2p via API as well... I dont see that in there either...
But I have no idea if I am using the newest version of the API... or how to even get it.
hey thank you so much!
i appreicate it!
For some reason that did not work to display the QR code... I can run other API commands with no problem... maybe it has to do with the version of firmware that my nvr is running...
Yep, that works to get the serial number! Thanks.
What document are you getting these commands from?
Mike A.
Known around here
- Joined
- May 6, 2017
- Messages
- 3,831
- Reaction score
- 6,389
You probably should wonder. I've seen different behavior for that with different Dahua cams/firmware. For at least one of mine, disabling the 'enable' box at the top does not stop the cam from attempting P2P connections. You have to untick P2P (and/or each of the other services below as desired) to stop the attempts to connect. On another cam unticking the enable box disables the services below. On another cam/firmware, it doesn't matter what you have ticked, it still tries to make a P2P connection or does other similar things (attempting to find Google's DNS) disregarding how you have things set.
I've not tested your case specifically leaving the enable box ticked with the service below unticked on whatever cam/firmware but if this is important, then I'd test it by watching the traffic using WireShark or other sniffer to see what it actually does.
I've not tested your case specifically leaving the enable box ticked with the service below unticked on whatever cam/firmware but if this is important, then I'd test it by watching the traffic using WireShark or other sniffer to see what it actually does.
Update:
So the api command in the above post doesn't seem to disable P2P, it does stop you connecting remotely but the cameras are still hammering port 8800 on the firewall.
Unfortunately this is still the case if you untick P2P in the browser!
On both NVRs and some cameras P2P is disabled but still trying to route out via port 8800 around 50 times per second!!
I've had a customer complain that their firewall has been hit close to 5 million times over a 24 hour period!!
I know that's what the firewall is there for but it is worrying that this cant be disabled!
So the api command in the above post doesn't seem to disable P2P, it does stop you connecting remotely but the cameras are still hammering port 8800 on the firewall.
Unfortunately this is still the case if you untick P2P in the browser!
On both NVRs and some cameras P2P is disabled but still trying to route out via port 8800 around 50 times per second!!
I've had a customer complain that their firewall has been hit close to 5 million times over a 24 hour period!!
I know that's what the firewall is there for but it is worrying that this cant be disabled!