Andrei4 wrote:Hello, on what devices it does not take effect sometimes?
about "auto-restart", for some users this could be unwanted behaviour, so it is better to restart it manually.
Could you tell more about chain of actions?
Tested devices: Samsung Galaxy S6 Active and S8 Active. I have not yet tested on any IOS devices.
The auto-restart would be the same as the configuration taking effect immediately wouldn't it? As the configuration has to be read and made active.
Chaining events would be like this:
- Notification sent
-> push new configuration
-> cmd stop
-> cmd start
Alternative with restart command
- Notification sent
-> push new configuration
-> cmd restart wiatag
A lot of this depends on a success/fail report from the push if success then issue the stop/start or restart. If the push failed then do something else, like retry or send a message notification.
My use of Wialon is completely different that anyone else's so I have a lot of "odd" things we integrate with our customers. This particular one is for GeoFence notifications to control Home Automation events (open/close Garage door, turn on/off alarm system etc etc).
The use is for pushing WiaTag "active" configuration when leaving a geofence (home/work/etc) and then pushing a new "idle" configuration when "entering" a geofence. One problem I am aware of is the "leaving" part of the time period it takes for the idle configuration to actually report that it is no longer in the geofence which leads to the exit message being missed or thrown away due to the age of the message.
I'm also looking to see if the "chaining" of commands can be tied from one device "unit" to another.
Example: I have OBD units in my vehicles. When the ignition is turned on for "Wife Jeep" being able to use that Event to trigger a notfication/action to push the new Wiatag configuration of "Active". That would help with the update lag time of the Idle configuration when leaving the "Home" geofence.