Hello @reolink-fiona,

I appreciate your feedback, but the command used to work a few weeks ago. Actually, I have been using such command in my automation system for months. I had not to enable push in the app for this to work. Pity that it doesn’t work now for some reason. Are you sure there is no way to make push notifications work with any sort of command or option that I am missing? Has this behaviour changed in the latest version? The strange thing is that I tried to downgrade to the previous version and it doesn’t work either.

If this is not officially supported, I will keep trying myself to try to figure out a workaround. Anyway, it would be great if Reolink developers enable this option in a future firmware upgrade so notifications can be fully automated.

Thanks!

Best regards,
Sésar

@reolink-fiona Thank you! Managed the command to work using the single quote between the brackets section. Home Assistant gave a validation error with such single quotes, but I found a way to fix this and make Home Assistant compliant. I don't understand why this was working before, but I don't really care as it is working fine now.

Problem now is that, when I issue the following SetPushV20 command, the { "Push" : { "enable" : state changes from 0 to 1 as expected. I Check response with https://[NVR_IP]/api.cgi?cmd=GetPushV20&user=admin&password=[PASSWORD]

COMMAND

curl -H "Content-Type: application/json" -X POST -d '[{"cmd":"SetPushV20","param":{"Push":{"enable":0}}}]' "https://[NVR_IP]/api.cgi?cmd=SetPushV20&user=admin&password=[PASSWORD]" --insecure

RESPONSE

[ { "cmd" : "GetPushV20", "code" : 0, "value" : { "Push" : { "enable" : 1, "schedule" : { "channel" : 0, "table" : { "AI_DOG_CAT" : "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000", "AI_PEOPLE" : "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000", "AI_VEHICLE" : "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000", "MD" : "111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111" } }, "scheduleEnable" : 1 } } } ]

However, neither the Reolink Mobile App PUSH switch nor the NVR interface change. I don't receive notifications when I issue the command above like I used to do.

It is strange that, if I enable the PUSH command from the App or the NVR interface, the response to the GetPushV20 is the same than the curl command ("enable" changes to 1). However, notifications work in this case.

EDIT: Actually, it happens the same from the Web Interface. If I login in the Web interface and enable PUSH, I don't receive notifications, and push switch is not updated in the mobile App. If I enable the switch in the mobile App, switch is not updated in the Web Interface either. However, in this case (enable/disable from the App) notifications work.

How can I make the curl command to actually work and enable the "real" notifications, in addition to the GetPushV20 response? How can I make all PUSH switches to be sync'ed?

Kind regards,
Sésar

Dear All,

I have been using some Reolink API commands for quite a long time with no issues. I have integrated such commands in Home Assistant through cURL commands. However, I upgraded my NVR to the latest version a few days ago. Since then, some commands are still working but some are not. Specifically, I am missing the command to enable/disable PUSH notifications, which is a very useful option to be automated upon leaving and returning home.

These are the commands I issued until it stopped working:

TO ENABLE:

curl -H "Content-Type: application/json" -X POST -d ''[{"cmd":"SetPushV20","param":{"Push":{"enable":1}}}]'' "http://[NVR_IP]/api.cgi?cmd=SetPushV20&user=admin&password=[PASSWORD]"

TO DISABLE:

curl -H "Content-Type: application/json" -X POST -d ''[{"cmd":"SetPushV20","param":{"Push":{"enable":0}}}]'' "http://[NVR_IP]/api.cgi?cmd=SetPushV20&user=admin&password=[PASSWORD]"

According to latest API version v7, these commands haven't changed. However, the response to such cURL commands is now the following:

curl: (3) bad range in URL position 2:
[param:{Push:{enable:1}}]
 ^

Taking into the account such error, I have been trying different command parameters order. If I issue the following command, response is different (I am adding the --insecure option because it seems that Reolink new firmware accepts https requests only, and the certificate is a self-signed one):

curl -X POST -H "Content-Type : application/json" -d "[{"cmd": "SetPushV20","param": {"Push": {"enable": 1}}}]" "https://[NVR_IP]/cgi-bin/api.cgi?cmd=SetPushV20&user=admin&password=[PASSWORD]" --insecure

RESPONSE:

[
  {
     "cmd" : "SetPushV20",
     "code" : 1,
     "error" : {
        "detail" : "please login first",
        "rspCode" : -6
     }
  }
]

It seems this command works. But, response is asking to login first, although the credentials are passed in the command in the same way it used to work before latest firmware upgrade. I know there is a TOKEN option, but I'd rather to use the "short-session" access option, because it is more convenient for the purpose. Nevertheless, I have tried the token option and behaviour is the same.

In order to compare with another command, the response of the following command is fine:

curl "https://192.168.0.55/api.cgi?cmd=GetPushV20&user=admin&password=Cabanillas2015" --insecure

RESPONSE:

[
  {
     "cmd" : "GetPushV20",
     "code" : 0,
     "value" : {
        "Push" : {
           "enable" : 0,
           "schedule" : {
              "channel" : 0,
              "table" : {
                 "AI_DOG_CAT" : "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
                 "AI_PEOPLE" : "111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111",
                 "AI_VEHICLE" : "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
                 "MD" : "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
              }
           },
           "scheduleEnable" : 1
        }
     }
  }
]

As you can see, the command response is the expected, and no "please loging first" message is issued, so I think there is a specific issue with certain commands, or the SetPushV20 one at least.

Typing some NVR information below for reference:

NVR Model: RLN8-410
NVR Hardware Version: N2MB02
Config Version: v3.0.0.0
Firmware Version: v.3.1.0.211_22102413

For the moment, I think I will downgrade the NVR, because this feature is quite important for me.

In the meantime, is anyone experiencing the same problem? Any way to fix this, please?

Thanks in advanced.

Sésar

@cwleth_495534361215110 I also support the request to include a relay or somethinng it is able to control an electrical door/gate opener with.

Please, make the WiFi connectivity reliable enough so it can really used. I have tried a few WiFi doorbells, and WiFi option is useless, even though you install an access point just a few meters away from the doorbell. For the rest of features, the community is asking for very good options, so as long as you take them in account, I believe you will have an awesome doorbell in your products catalogue. Thanks!