@matthew_635366143033465 It supports "Person Detect".

@user_717581899391160_717581899391160
The following worked for me...

Run Windows Powershell as administrator
Copy/paste the following after changing 10.0.1.16 to the address of your Synology NAS...
$params = @{
  Subject = '10.0.1.16'
  TextExtension = @('2.5.29.17={text}IPAddress=10.0.1.16')
  "NotAfter" = (Get-Date).AddMonths(36)
  "KeyAlgorithm" = "RSA"
  "KeyLength" = "2048"
}
Copy/paste the following...
New-SelfSignedCertificate @params

Use the Windows MMC app to export the certificate from your Personal certificate store (for example to the desktop)
Use MMC to import the exported certificate to your Trusted Root certificate store
Install and run openssl
Produce a key file and certificate file from the exported certificate using the following 2 lines...
openssl pkcs12 -in C:\path\filename.pfx -out C:\path\filename.key -nodes -nocerts
openssl pkcs12 -in C:\path\filename.pfx -out C:\path\filename.crt -nokeys
On your Synology NAS, import the certificate using the 2 files produced by openssl

Note: you can probably do it all in either Powershell or openssl - I just happened to have used both tools.
The important bit is the line TextExtension = @('2.5.29.17={text}IPAddress=10.0.1.16'). Not having this correct caused me endless problems.

(also posted on Reolink Facebook)

A heads up for those of you that have a Synology NAS. The latest version of Surveillance Station supports the Reolink Doorbell (without using ONVIF).
It also appears to support 2-way audio, but insists on having a HTTPS connection in order to activate this, not just the unencrypted HTTP. I guess that they mean the connection between your browser and Surveillance Station. I have not yet been able to install a certificate for this so cannot test the 2-way audio.
Anyone out there experienced with self-signed certs?