Ecare is a very important feature of Immix. Its essentially tells the station if there is a problem at the remote site that might affect monitoring.
Technically speaking, ECare is a reverse heartbeat process where Immix consistently communicates with the remote device to make sure it’s still online and communicating. If the device does not respond then an alarm is triggered in Immix alerting the station of a potential problem onsite so it can be addressed accordingly. If the device comes back online, Immix will send a familiar restoral alarm to clear the event.
Administrators set up the parameters that will trigger an ECare failure alarm when they add a device to Immix. These include the interval to check for Ecare (the reverse heartbeat) and how many failure events need to occur for an alarm to be raised. The reason that these options are provided is to allows you to take into account different network conditions from one site to another. On a very stable LAN environment you might want to set ECare with a very small number of failures (i.e. 1 or 2) over a large period of time (i.e. 5 minutes) whereas at a remote cellular location you might want to have a much higher threshold for failure (i.e. 5 failures) over a shorter period of time (i.e. 1 min).
In addition to the basic Ecare setting, Administrators can setup specific ECare alarms that trigger other automation features to occur, such as SOP’s, alarm tags, notifications etc.
All the details of configuration of ECare are covered in this knowledge base article on our support portal. https://support.sureviewsystems.com/hc/en-us/articles/202717598-Ecare