Hi Alberto,
Thanks for contacting Milesight-IoT Support Team,
The device's local configuration takes priority over the settings on the IoT Cloud, as configurations on the IoT Cloud are essentially modified through downlink. If the device's local settings are manually changed, those changes will not be synchronized to the IoT Cloud.
Any problems, feel free to let me know,
Have a great day.
Best Regards,
Van Fan.
Hi Fan,
(I think Fan is your first name, please correct me if I am wrong)
Firstly, let me thank you for your prompt answer.
I have several questions related to this topic.
1) When I configure the device, by NTP. As far as I understand, I must configure the radius for the geofence.
The only possibility here is circular Geofence.
Then, suppose I want to configure in IoT Cloud a polygonal Geofence. Will this configuration send through downlink take priority over the previous one done by NTP. Is this correct?
2) If someone modifies by NTP the configuration , then , in this case the local configuration will take priority as you said. Is this correct?
3) What about if I send the command Restart the device. In this case, would the configuration given from IoT Cloud not take effect?
4) I have noted that alarms due to tamper bottom are received in lest of one minute by the application. But it is not the case for alarms due to going out of the geofence, Is it normal , or probably I am doing something wrong?
5) Do they have the same performance as the circular and the polygonal geofences?
Do they have the same time to send the alarm?
Sorry for sending too many questions.
BR
Thanks again,
Alberto
Hi Alberto,
Regarding the five questions you raised, here are my answers in order:
Yes, after modifying via IoT Cloud, the previous device configuration will be overwritten. The priority mainly depends on the sequence of changes. After making changes, you can use Toolbox to read the device again, and the configuration information should reflect the changes accordingly.
I believe you are referring to the NTP in the mobile Toolbox. As mentioned in point 1, after making modifications in IoT Cloud, if you then make changes through Toolbox, the configuration will be based on the last modification.
Restarting the device will not change the device's configuration, unless you modify it again afterward.
Since the time to obtain the geographic location may vary, if there is a delay in acquiring location data, it might not report within the minute, which is a normal occurrence.
Yes, their alarm mechanisms are the same. As long as the threshold is exceeded, an alarm packet will be sent immediately. However, there may be slight delays in GPS location.
Any problems, feel free to let me know,
Have a great day.
Best Regards,
Van Fan.
Crystal clear.
you can close the ticket.
Thank you very much
Alberto Dimerman
It is just to confirm
It is possible to configure a circular radius for setting the geofencing in the device. If we use Milesight Cloud IoT we have the possibility to configure a circular or Polygonal geofence. Does the geofence configured in IoT cloud have priority over the one configured in the device itself?