Hi!
I finally managed to use the CGI API of my E1 outdoor with PTZ commands by making calls to https instead of http.

But I think there is a bug in calls to setAiCfg: I wanted to set the aiTracking on and to people. So I call API with setAiCfg/aiTrack=1/trackType-people=1/AiDetectType-people=1

I got a 200 response code (means ok), but if I check with GetAiCfg the aiTrack parameter is set to 1 (correct) and the type-people is ALWAYS set to 0.

I can check this in the web UI, where the check box for people tracking is unchecked after that.

With this combination (aiTracking set to 1 but no track type chosen) the ios app of Reolink crashes if I try to switch on motion detection!

Will there be a bug fix so users can switch on person tracking with CGI API?

@d-beckers_494387272687778

I solved my problem with PTZ control of Reolink E1 outdoor: the curl calls to PtzCtrl MUST be send to HTTPS and not to HTTP! Thanks to a user in Reddit who posted the correct curl call.

@Reolink: you should clearly document this because this is not obvious from your description of CGI API!

@crimp-on_62210811129
This is a document created by Reolink. So their cameras should support all the commands. But obviously they deactivated the usage of most of the commands for E1 outdoor and RLC 823a. And I want to know why and at which time they (re-)activate e.g. the PTZ commands via CGI.

@crimp-on_62210811129

https://support.reolink.com/hc/en-us/articles/900000629206-Where-Can-I-Get-Reolink-Camera-s-CGI-File

A little bit more progess, but frustrating:

curl -X POST 'http://admin:xxxxxxxx@192.168.178.39/api.cgi?cmd=Login&cmd=PtzCtrl' -H 'Content-Type: application/json' -d '[{"cmd":"Login","action":0,"param":{"User":{"userName":"admin","password":"xxxxxxx"}}},{"cmd":"PtzCtrl","action":1,"param":{ "channel":0, "op":"ToPos", "id":2, "speed":32 } } ]'
[
  {
   "cmd" : "Login",
   "code" : 0,
   "value" : {
     "Token" : {
      "leaseTime" : 3600,
      "name" : "b46ce7b11a0ba37"
     }
   }
  },
  {
   "cmd" : "PtzCtrl",
   "code" : 1,
   "error" : {
     "detail" : "ability error",
     "rspCode" : -26
   }
  }
]

If I get the ability list same way, there are again only a few commands allowed to the admin user! Why is this? As admin and owner of the camera I should have full access to all commands! This is again as unusable as the Reolink E1 Outdoor! I want to trigger PTZ commands by myself and NOT via the Reolink app or the web interface. This should be possible as with other cameras.

Even if I try to get a simpe rtsp snap with curl "http://192.168.178.39/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=wuuPhkmUCeI9WG7C&user=Dirk&xxxxxxxx=ideFix99" >snap.jpg I get an invalid user error -27.

The user IS NOT INVALID, same to the password! I tried with user admin - same shit.

What is wrong with that expensive piece of .... camera?!? These are all complete normal CGI API calls, working with almost every camera in the world!

What the hell are the Reolink developers doing? Do they have something like testing and quality control? I bought a Reolink E1 Outdoor - the CGI API only offers 3-4 features in ability list, almost all features are disabled. Then I took more money, bought a RLC 823a - the CGI API is complete nonsense and/or not implemented according to spec!

May I have a look to other companies building IP cameras? Dahua or something like that?

Hello!

I'm facing a lot of problems with my new RLC 823a and using CGI API.

I try to get the user abilities with CGI API call: curl -X POST 'http://192.168.178.39/api.cgi?userName=admin&password=xxxxxxcmd=GetAbility' -H 'Content-Type: application/json' -d '{"cmd":"GetAbility","param":{ "User":{ "userName":"Dirk" } } }'
[
  {
   "cmd" : "GetAbility",
   "code" : 1,
   "error" : {
     "detail" : "please login first",
     "rspCode" : -6
   }
  }
]

Next I tried to get a token according to spec: curl -X POST 'http://192.168.178.39/cgi-bin/api.cgi?cmd=Login'                        

But I simply receive:
[
  {
   "cmd" : "Login",
   "code" : 1,
   "error" : {
     "detail" : "login failed",
     "rspCode" : -7
   }
  }
]


Ok, next I tried: curl -X POST 'http://192.168.178.39/api.cgi?cmd=Login&userName=admin&password=xxxxxx' I get

[
  {
   "cmd" : "Login",
   "code" : 1,
   "error" : {
     "detail" : "invalid user",
     "rspCode" : -27
   }
  }
]

The user is a valid user with a valid password, I can login through webinterface of camera. But CGI does not really work. With my former E1 outdoor CGI calls were working, but I cannot use the PTZ features with CGI API because I always get an abiity error.

Using the CGI API according to your spec "Camera HTTP API, User Guide, Version 5 2021-12" does not work in any case! I hoped the RLC 823a is working full with CGI API and give it a try. But without full access to the CGI API commands I'll send it back, because the camera is useless for me.

Please explain the differences between the spec and the real implemented API to the RLC 823a! Thanks!