HCL Virtual Device

[suds32nz 0]

HI I have been using a virtual device to trigger motion detection on my foscam IP camera and all works great. But now I am trying the same thing with a D-Link DCS 932.

I have the turn motion url from a browser and all works great

Please login or register to see this link.

- sending this from a browser works every time.

 

When I add this to my virtual device (the same process as my Foscam IP Camera)

 

GET

Please login or register to see this link.

HTTP/1.10x0D0x0A0x0D0x0A

 

Pressing the arm button and nothing happens, If I substitute it with the Foscam URL etc the Foscam arms from this virtual device, so I know the device is working.

Not sure why the same setup works well with the Foscam. And I can test the above url in a browser for the DLink and that works fine so the command is correct.

 

Any thoughts help would be appreciated

 

thanks

 

 

 

[suds32nz 0]

anyone struck this or have any thoughts

[wpeeters 30]

I tried to do the same with D-Link DCS 942L.

I tried with several settings and several ways of authentication. I never could manage it to work (while I did with Foscam and Vivotek camera's).

I think the problem is within the authentication method.

[suds32nz 0]

Yeah would have to agree just cant seem to find a solution

 

[Reintjan 29]

I'm not an expert at all but i see dlink cam is port 81. Hcl is using port 80 for http maybe thats why its not working. Can you change dlink port?

[wpeeters 30]

@reintjan All my camera's are using other ports so that might not be the reason.

Edited January 13, 2017 by wpeeters
fast post

[Reintjan 29]

Ok, just a thought

[suds32nz 0]

HI just an update if anyone has struck it but since 4.131 mrs foscams can no longer be armed etc with this virtual . Both were working now neither works. Nothing else was changed