Cynthia,

API will be an important feature to attract more users and open more applications markets (NOT just security) for Reolink. This request needs to be seriously evaluated since Reolink has reached the point and maybe in a better position than competitors.

I don't agree with the two points you mentioned in your previous message.

1/ Reolink can easily implement some strategies to work with the 3rd party software to manage the battery. Reolink can simply reject API calls when battery level is low and stop API calls from the 3rd party software. Reolink can notify users if the battery is used too fast or is going to be lower than a preset threshold.

2/ The 3rd party application doesn't need to detect IP address of the camera! Most routers can reserve the IP address for the camera.

Reolink will need to treat these API users differently. They will not depend on the standard parts from Reolink for their applications. They will do their own customization on both software and hardware. Then, Reolink opens new applications and markets due to these API users. You may think why Raspberry Pi and is so popular in the US, UK, Germany, etc.

I am thinking to use the battery-powered camera for traffic monitoring. My test is a success. The only missing function is the API for its integration with my application and the existing systems.

Thanks