Still can’t understand
What is the difference of this
and the command I am sending which is this
curl -i --digest -u admin:1234qwer -X PUT -d '<RemoteControlDoor><cmd>open</cmd></RemoteControlDoor>' http://192.168.70.220/ISAPI/AccessControl/RemoteControl/door/1
I see no difference, unless I am blind 
Do you ?
In 2 posts above you were only sending the word ‘open’ … You need the complete XML…
-X PUT -d ‘open’
Ok, but I have corrected this since you pointed out!
Am sending exactly the command bellow but still the door open doesn’t work 
curl -i --digest -u admin:1234qwer -X PUT -d '<RemoteControlDoor><cmd>open</cmd></RemoteControlDoor>' http://192.168.70.220/ISAPI/AccessControl/RemoteControl/door/1
But I get the following
HTTP/1.1 401 Unauthorized
Date: Thu, 27 Jan 2022 18:48:40 GMT
Server: webs
Content-Length: 235
Connection: close
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store
Pragma: no-cache
WWW-Authenticate: Digest qop="auth", realm="DS-D35B66A6", nonce="NDI0ZmM1MDIxMmJkMzk4NGMwNTU3OTQ2NjVjOTg1YmI=", stale="false", opaque="", domain="::"
Content-Type: application/xml
HTTP/1.1 400 Bad Request
Date: Thu, 27 Jan 2022 18:48:40 GMT
Server: webs
Content-Length: 40
Connection: close
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store
Pragma: no-cache
Content-Type: application/xml
<?xml version="1.0" encoding="UTF-8"?>
Please help, I am almost done!
By the way the door status with the rest sensor seems to work
curl -i --digest -u admin:1234qwer http://192.168.70.220/ISAPI/VideoIntercom/callStatus?format=json
HTTP/1.1 401 Unauthorized
Date: Thu, 27 Jan 2022 18:49:36 GMT
Server: webs
Content-Length: 0
Connection: close
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store
Pragma: no-cache
WWW-Authenticate: Digest qop="auth", realm="DS-D35B66A6", nonce="NjFmMTIzODcwYmM4MzI1ZmI2MzZlZDUxMGRiMmYyM2M=", stale="false", opaque="", domain="::"
Content-Type: application/json
HTTP/1.1 200 OK
Date: Thu, 27 Jan 2022 18:49:36 GMT
Server: webs
Content-Length: 42
Connection: close
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store
Pragma: no-cache
Content-Type: application/json
{
"CallStatus": {
"status": "idle"
}
No found compatble devices.
Can you explaine me more ?
What are you trying to achieve?
strange, the command looks ok, have you resetted the device after upgrade? can you actually open the door? maybe its not setup yet
that callsensor, that will give you indeed “idle”, but its always idle, also when someone pressed the doorbell, thats an issue in firmware, upgrade now to the firmware in first post, also that 2.2.45 build, that will give a good callstatus 
also when you do an upgrade, make sure to factory reset the device
he wants to grab a snapshot from the camera entity, but the still image in his config is an rtsp url, that doesnt work, you need a real still image url
use motionEye, i use my synology surveillance for cameras
I haven’t reset after the upgrade as there are 3 houses on this door bell.
If I reset nobody will be able to open the door right ???
I confirm that the call sensor gives always “idle”…
I will update as soon as I fix the door open problem…
Still can’t figure out why the command is not working for me.
One more question.
Main Unit has the camera module with 3 buttons (one for each house)
How can I trigger and make automation only when my house’s button is pressed ???
(ofcourse I will update to your custom firmware but I just want to know that it is possible when do it)
thank you in advance
I don’t know, I can’t check with mine, I only have 1 button
Maybe the info is present in the ISAPi output…
I think the SDK script maybe gives you the output, it gives more then ISAPi anyway
What do you suggest?
It’s strange, the command should work, have you tried on Windows command prompt?
Otherwise best upgrade to custom and do a factory reset, it’s like 5 min setup anyway
You can also use the hikconnect cloud integration, it does also have the feature now to open door and callstatus… The RTSP you already have
Then you don’t need to change any firmware or setting
I am using reqbin.com for testing! It is very nice!
here is again what I try
and here is the answer I get
its strange, all looks ok, maybe a reset to facory is needed, it was also needed for mine
but try hikconnect cloud, it works too, then you dont need to reset it
If I go for custom firmware and then rest it, what are the steps to setup again?
I haven’t done it before and I am not very sure…
the steps? well configure the door relay, make user passwords, register again swipe cards? remember, after a factory reset, the IP is back on some weird static IP , so you need ivms
make sure ivms is also updated
thank you. I think i can do this .
when you are saying “do a factory reset” do you mean through the ivms ??
Restore Default Settings or Restore All ?
i did a “restore all”
final question before I proceed with the upgrade of the custom firmware,
If something goes wrong, can I restore previous firmware right ??
