Care Home CMS PDF

™
Care@Home
CMS
User Guide
ESUG05074
Version 1.6
July 2015
Legal Notice
Usage of this document, and all information (including product information) provided within, are subject to the following terms and conditions, and all
applicable laws. If you do not agree with these terms, please do not access or use the remainder of this document.
This document contains highly confidential information, which is proprietary to Essence SmartCare Ltd. and/or its affiliates (hereafter, "Essence"). No part of
this document's contents may be used, copied, disclosed or conveyed to any third party in any manner whatsoever without prior written permission from
Essence.
The information included in this document is intended for your knowledge and for negotiation purposes only. Essence makes no implicit representations or
warranties with respect to such information.
The information included in this document is subject to change without notice. Any decision to rely on the information contained herein shall be at your sole
responsibility, and Essence will not accept any liability for your decision to use any information or for any damages resulting therefrom.
Certain laws do not allow limitations on implied warranties or the exclusion or limitation of certain damages. If these laws apply to you, some or all of the above
disclaimers, exclusions, or limitations may not apply to you.
By using the information contained herein, you agree that the laws of the State of Israel, without regard to principles of conflict of laws, will govern any dispute
of any sort that might arise between you and Essence regarding the information contained herein, and any such dispute shall be settled exclusively in the
competent courts of Tel Aviv-Jaffa, Israel.
All registered or unregistered trademarks, product names, logos and other service marks mentioned within this document are the property of Essence, or their
respective owners. Nothing contained herein shall be construed as conferring by implication, estoppels, or otherwise any license or right, either express or
implied, under any patent or trademark of Essence or any third party. No use of any trademark may be made without the prior written authorization of Essence.
This document and all of its contents are protected intellectual property of Essence. Any copying, reprinting, reuse, reproduction, adaptation, distribution or
translation without the prior written permission of Essence is prohibited.
Please check your End User License Agreement (EULA) for terms and conditions.
© 2015 All rights reserved to Essence SmartCare Ltd.
For more information, please contact: Essence SmartCare Ltd.

12 Abba Eban Avenue,
Ackerstein Towers Bldg. D
Herzliya Pituach,
4612001 Israel
www.essence-grp.com
Tel: +972-73-2447777
Fax: +972-9-7729962
Table of Contents
Table of Contents
1. Overview ................................................................................................................................................. 7
1.1. The Control Panel Parameter File ............................................................................................... 8
1.2. Minimum System Requirements ................................................................................................ 9
2. CMS Implementation Process ............................................................................................................... 10
2.1. CMS Installation ........................................................................................................................ 10
2.1.1 Running the Installation Wizard .................................................................................. 10
2.2. Administrator Privileges ............................................................................................................. 11
2.3. Identify the Communications Port ............................................................................................ 13
2.4. CMS Connect to the CP ............................................................................................................. 14
2.5. The Connect Window................................................................................................................ 14
2.6. Local Connection ...................................................................................................................... 16
2.6.1 Local Connection to the CP ......................................................................................... 17
2.6.2 Configuration File........................................................................................................ 18
2.7. Remote Connection................................................................................................................. 20
2.8. Initial Control Panel Connectivity............................................................................................. 24
2.8.1 Upload Control Panel Settings Procedure ................................................................... 25
2.8.2 The Panel Info Window ................................................................................................ 25
2.8.3 Control Panel Re-Connect ..........................................................................................28
3. Getting Started ...................................................................................................................................... 31
3.1. Care@Home™ CMS Home Page ............................................................................................... 31
3.2. Main Action Icons ..................................................................................................................... 32
3.3. File Menu Functions .................................................................................................................. 33
3.3.1 Open Function ............................................................................................................34
3.3.2 Quit Function ..............................................................................................................34
3.3.3 Print… Function ...........................................................................................................36
3.3.4 Print Log… Function ....................................................................................................36
3.3.5 Print Setup Function ....................................................................................................36
3.4. The Main Navigator Menu......................................................................................................... 37
4. The Control Panel Module .................................................................................................................... 39
4.1. Control Panel Module Specifications ....................................................................................... 40
4.1.1 Enabling Care@Home™ Analytics Functionality ......................................................... 40
4.1.2 Parameters from Account Number to Remote Call-In ................................................ 41
4.1.3 Parameters from Password to Mains Failure ................................................................43
Care@Home™ CMS User Guide 3

Table of Contents
4.1.4 The Control Panel Communications Module ............................................................. 44

4.1.5 Parameters from DTMF Password to Temperature .................................................... 47
4.1.6 Parameters from Emergency Pendant to Sound ........................................................ 48
4.1.7 More Options ............................................................................................................. 49
4.1.8 The Control Panel Module Buttons ............................................................................. 55
5. The Dialer Module ................................................................................................................................ 56
5.1. Destination Definition ............................................................................................................... 57
5.1.1 Defining Communications Attributes ......................................................................... 57
5.1.2 Defining Communications Channel Attributes ...........................................................59
5.2. Managing the Destination List ................................................................................................. 60
5.3. The Dialing Sequence ...............................................................................................................62
6. The Activity Sensors Module................................................................................................................. 67
6.1. Defining Sensor Device Attributes ........................................................................................... 68
6.2. Managing the Activity Sensors List .......................................................................................... 70
6.2.1 Add an Activity Sensor ............................................................................................... 70
6.2.2 Update an Activity Sensor ........................................................................................... 72
6.2.3 Delete an Activity Sensor ............................................................................................ 73
6.3. Zone Status .............................................................................................................................. 74
7. The Safety & SOS Module ...................................................................................................................... 75
7.1. Defining Attributes for Safety & SOS Devices ............................................................................76
7.2. Specific Safety and Emergency Attributes ................................................................................ 77
7.3. Managing the Safety & SOS Devices......................................................................................... 80
7.3.1 Add a Safety or SOS Device ......................................................................................... 81
7.3.2 Update a Safety or SOS Device ....................................................................................82
7.3.3 Delete a Safety or SOS Device ..................................................................................... 83
7.4. Radio Frequency Input Status .................................................................................................. 84
8. Control Panel Internal Clock ................................................................................................................. 85
8.1. Importance of the Internal Clock ..............................................................................................85
8.2. Automatic Internal Clock Update .............................................................................................85
8.2.1 GSM Automatic Update...............................................................................................85
8.3. Manual Update Using the Panel Date Time Module ................................................................. 86
9. Voice Announcements Module ............................................................................................................88
9.1. General Configuration Parameters ........................................................................................... 91
9.2. Reminder Schedule Types .........................................................................................................92
9.2.1 One-Time Schedule Type............................................................................................93
9.2.2 Weekly Schedule Type ............................................................................................... 94
4 Care@Home™ CMS User Guide
Table of Contents
9.2.3 Day of the Month Schedule Type ................................................................................95

9.2.4 Day of Week Schedule Type ....................................................................................... 96
9.3. Medication Reminders ..............................................................................................................97
9.4. Appointment Reminders.......................................................................................................... 99
9.5. Ride Reminders ...................................................................................................................... 100
9.6. Alarm Reminders..................................................................................................................... 102
9.7. EP Test Reminder .................................................................................................................... 103
10. Mobile Operators ............................................................................................................................... 105
10.1. APN Information ..................................................................................................................... 106
10.2. Managing the Mobile Operator List ........................................................................................ 107
10.2.1 Add a Mobile Operator ............................................................................................. 107
10.2.2 Update a Mobile Operator ........................................................................................ 108
10.2.3 Delete a Mobile Operator ......................................................................................... 109
10.3. Load APN Information............................................................................................................. 110
11. The Custom Labels Module ................................................................................................................. 112
11.1. Defining Custom Labels ........................................................................................................... 113
12. The Log Events Module ....................................................................................................................... 114
12.1. Log Events Module Actions ..................................................................................................... 115
12.2. Number of Events .................................................................................................................... 115
12.3. Read Log .................................................................................................................................. 115
12.4. Reset Log ................................................................................................................................. 116
12.5. Save Log ................................................................................................................................... 116
12.6. Open Log ................................................................................................................................. 117
12.7. Print Log… ................................................................................................................................ 118
13. Care@Home™ CMS Implementation .................................................................................................... 119
13.1. Load the Factory Settings ....................................................................................................... 120
13.1.1 Upload the Factory Settings ...................................................................................... 120
13.2. Verify the Factory Settings ...................................................................................................... 120
13.2.1 Account Number........................................................................................................ 121
13.2.2 APN Settings.............................................................................................................. 122
13.2.3 Customize CP Configuration ......................................................................................123
13.3. Additional Configuration ........................................................................................................ 124
13.3.1 Dialer Module ............................................................................................................ 124
13.3.2 Activity Sensors Module ............................................................................................ 128
13.3.3 Safety and SOS Module ..............................................................................................132
13.3.4 Log Events Module..................................................................................................... 133
Table of Contents
14. Software Updates.................................................................................................................................134

14.1. The Remote Boot Feature ....................................................................................................... 134
14.1.1 Launching the Remote Boot Feature ........................................................................ 134
14.1.2 Remote Boot Setup ................................................................................................... 134
14.1.3 The Software/Firmware Update Procedure............................................................... 136
Appendix A Terms, Abbreviations and Acronyms ............................................................................... 142
Appendix B End User License Agreement and Terms & Conditions .....................................................145
Appendix C Care@Home™ System Terms of Use ................................................................................. 148
Appendix D USB to RS232 Adapters ...................................................................................................... 151
Appendix E Voice Announcements ..................................................................................................... 153

Overview
1. Overview
The Care@Home™ CMS software application provides a user-interface that enables access to the
parameter values of the Care@Home™ Control Panel (CP) and its peripheral devices.
With the Care@Home™ CMS software application, the user can configure the Care@Home™ CP
parameters, prior to the Care@Home™ System installation at the customer premises.
The user can modify the parameter values of a CP installed at the customer premises, as well as update the
CP software and the firmware for its peripheral devices. These modifications can be performed locally at
the customer premises or remotely by the Monitoring Station.
The Care@Home™ CMS software application allows the End-User to configure the parameters that define
the operating environment, consisting of the Control Panel and its peripheral devices, including the
Care@Home™ Analytics functionality.
The purpose of this User Guide is to provide a description of the Care@Home™ CMS software application,
including the Care@Home™ Analytics functionality, and how to manage it.
NOTE: This User Guide refers to version 5.7.52.5 of the Care@Home™ CMS software
application. Version 5.7.52.5 works with Control Panel firmware version 1.2.
The User Guide is written with the assumption that the Care@Home™ Analytics functionality is enabled.
For more information about enabling Care@Home™ Analytics functionality, see section 4.1.1 on page 40.
NOTE: The images in this chapter, used to guide the installation and implementation
processes, reflect the processes performed on a Windows 7 machine. The images of
the same processes performed in other operating environments may differ.

Overview
1.1. The Control Panel Parameter File
Each Control Panel (CP) contains a set of parameters defining the configuration of the CP and other
information for the firmware of the CP’s peripheral devices. This data defines and controls the operation
of the CP and its peripheral devices.
The CMS software application provides you with the tools to save this set of configured parameters in an
external file called “the CMS parameter file”. The CMS parameter file is an external file with the extension
.cpf. The user is responsible for naming the .cpf file.
The purpose of the .cpf file is two-fold:

 The .cpf file may be used as an offline backup to store a given set of configuration parameters
and peripheral firmware information. The .cpf file can be kept indefinitely.
 The .cpf file allows the user to distribute a given set of configuration parameters and peripheral
firmware information to be used by multiple CPs.
The tools to manage the CMS parameter file are:

 The Upload action in the Care@Home™ CMS software application transfers the data from the CP
to the Care@Home™ CMS application.
 The Download action in the Care@Home™ CMS software application transfers the data from the
Care@Home™ CMS application to the CP.
 The Save action in the Care@Home™ CMS software application downloads the data from the
CMS application to a CMS parameter file.
 The Open action in the Care@Home™ CMS software application opens the .cpf file and
automatically uploads the configuration parameter settings to the CP, at the end of the session.
The data downloaded from the CMS application includes:

 The CP parameter values
 The peripheral device parameter values
 The operation-related configuration values

Overview
1.2. Minimum System Requirements

The following are the minimum requirements of a personal computer (PC) for a successful Care@Home™
CMS software application installation, to insure optimal application performance:
 A minimum of 1 GHz 32-bit processor
 A minimum of 256 Mb of RAM memory
NOTE: 512 Mb RAM is recommended for a better response time.
 At least 1 Gb free hard disk space

 Any one of the following operating systems in either 32-bit (x86) or 64-bit (x64) versions:
 Windows XP
 Windows Vista
 Windows 7
 Windows 8 and 8.1

CMS Implementation Process
2. CMS Implementation Process

The first stage of the implementation of the Care@Home™ CMS software application begins with running
the installation. The process ends with identifying the communications ports, used to connect to the
Control Panel (CP).
2.1. CMS Installation

The CMS installation program, setup<release number>.exe file, installs the Care@Home™ CMS software
application. The program, received from Essence Technical Support, runs an installation wizard utility.
NOTE: Contact Essence Professional Services personnel to receive the latest version
of the CMS installation execution file.
2.1.1 Running the Installation Wizard

The installation is performed by the InstallShield Wizard for Care@Home™ CMS.
Figure 1: Installation Wizard Window
To install the Care@Home™ CMS software application:

1. Upload the CMS installation execution file, setup<release number>.exe, and store it on the local PC.

2. Run the CMS installation execution file. The installation wizard window appears as in Figure 1 above.
3. Follow the wizard instructions, clicking the relevant buttons until the installation process finishes, as in
Figure 2 below.
Figure 2: Installation Wizard Finish Window
The Care@Home™ CMS software application is installed. The icon for the CMS program appears on the
desktop of the local PC.
Figure 3: The Care@Home™ CMS Icon
2.2. Administrator Privileges

Following the successful completion of the installation procedure, the administrator property for the
Care@Home™ CMS software application should be set as follows:
1. Click the right button of the mouse on the Care@Home™ CMS icon, as shown in Figure 3 above. A
menu opens, as in Figure 4 below.

Figure 4: Right-click Icon Menu
2. Click the Properties option, as indicated in Figure 4 above. The Care@Home™ CMS Properties window
appears, as in Figure 5 below.
Figure 5: Properties Window Compatibility Tab
3. Click the Compatibility tab in the Properties window.

4. Mark the checkbox for “Run this program as an administrator” option, under Privilege Level, as
indicated in Figure 5 above.

2.3. Identify the Communications Port

You must synchronize the communications (COM) port used to connect to the Control Panel (CP) with
the COM port selected in the Connect window of the Care@Home™ CMS software application.
Figure 6: Care@Home™ CMS Connect Window
To identify the COM port number used to connect to the Control Panel (CP), perform the following
procedure:
1. Click the Windows Start icon.
2. Click Control Panel option on the Windows menu.
3. Click the Device Manager option on the Control Panel menu. The Device Manager
window appears, as in Figure 7 below.
4. Under Ports (Com & LPT), as indicated on Figure 7 below, locate the communications port to which
the CP cable is to be connected.

Figure 7: Ports listed in the Device Manager
2.4. CMS Connect to the CP

A configuration file is required for the CMS to connect to the Control Panel (CP). Both a remote
connection and a local connection, using a local communications port, use a configuration file.
The Care@Home™ CMS configuration file (config.ini), which contains the CMS parameters, is located at
either of the following default paths:
c:\Program Files (x86)\Essence\Care@Home CMS\

c:\Program Files\Essence\Care@Home CMS\ (Windows XP only)
The configuration file assigns COM ports to the serial definitions. The Care@Home™ CMS Connect window
Connect box options are defined via the config.ini file.
2.5. The Connect Window

The Connect window enables the following functionality:
 To allow the technical support personnel to perform maintenance and error recovery.
 To upload configuration parameter values and monitoring information from the Control Panel
(CP) to the Care@Home™ CMS software application.

 To activate the Remote Boot feature.

For more information about the Remote Boot feature, see section 14.1 on page 134.
Figure 8: The Care@Home™ CMS Connect Window
The Connect window appears automatically when you open the Care@Home™ CMS software application.
Table 1 below describes the Connect window parameters with instructions how to apply them.
Name Definition and Instructions Data Required or Default

Values Optional Value
User For Essence technical support use only Optional Blank
Password For Essence technical support use only Optional Blank
Protocol Upload Radio Optional
Select this protocol to establish a connection to the CP to Group
maintain the CP settings.
Remote Boot Radio Optional
Select this protocol to activate the Remote Boot feature to Group
update the software and firmware of the CP and the peripheral
devices.
Note: The Remote Boot window appears when this option is
selected. See Figure 138 on page 135.
Remote Software Update using FTP Radio
Note: This option is only valid for Care@Home™ PERS. Group
Connect Select the connection method. Dropdown Required
If you are using a cable connection, select a COM port. List
Phone Note: The phone number is not used for a cable connection. Disabled

(View system This field displays system messages and error messages issued N/A Display Only
messages) during the connect process.
Table 1: Connect Window Parameters
Figure 9 below shows the four (4) action buttons at the bottom of the Connect window.
Figure 9: CMS Connect Window Buttons
Table 2 below describes the functionality of these action buttons.
Name Definition and Instructions

Click this button to establish a connection with the CP. The Panel Info window appears. For
information about the Panel Info window, see section 2.8.2 on page 25.
Click this button to abort the connection process. The button is disabled until the connection
process begins.
Click this button to clear the message field of all displayed information, such as system messages
and error messages.
Click this button to exit the Connect window. The Care@Home™ CMS software application enters
“offline” mode which is reserved for use by the Essence technical support personnel.
Table 2: The Connect Window Action Buttons
2.6. Local Connection

The Care@Home™ CMS can connect to the Control Panel (CP) using a local communications (COM) port.

2.6.1 Local Connection to the CP

To connect the CP to the local PC, use an Essence ES7000BACMS cable with a serial communications
(COM) port (RS232). Contact Essence Professional Services personnel for information about this cable.
Figure 10: Essence ES7000BACMS Cable
When there is no RS232 COM port available on the PC, use an USB-RS232 adapter, such as:
 ESCL05019 mini-USB adapter
 USB Gear Serial adapter
For more information about these adapters, see Appendix D on page 151.
Note: The Control Panel must be turned on before connecting the cable to the
RS232 COM port on the local computer.
For the RS232 Com port connection, there is a set of beeps that are sounded for different connect or
disconnect actions as follows:
 A beep emitting a long rising pitch indicates a successful plug-in connection.
 A beep emitting a double low octave pitch indicates an unsuccessful plug in.
 A beep emitting a long falling pitch indicates a successful disconnect.
When the CP beeps indicate a “disconnect” or an unsuccessful plug in, you must re-connect to the CP.
For information about re-connecting to the CP, see section 2.52.8.3 on page 28.

2.6.2 Configuration File

The parameter values for the local communications (COM) port connection between the computer (PC)
on which the Care@Home™ CMS is installed and the Control Panel (CP) are defined in the config.ini file, as
shown in Figure 11 below.
Figure 11: The Configuration File
If the COM port, used to connect the PC to the CP, is defined incorrectly, the configuration file must be
edited, using the Notepad utility, to correct the assignment statements accordingly.
For example, the user chooses to use serial port COM5 to connect the CP to the local PC.
Figure 12: COM Ports on Local PC
In the configuration file, config.ini, the SERIAL1 port is defined as COM1, as indicated in Figure 13 below.

Figure 13: SERIAL1 Defined as COM1
The user must edit the configuration file, using the Notepad utility, to redefine the SERIAL1 port as COM5.
To edit the config.ini file, perform the following procedure, as illustrated in Figure 14 below:
1. Open the config.ini file in the Notepad utility.
2. For [Config], modify: SERIAL1=COM5->Cable
3. For [SERIAL1], modify: ComNumber=5
4. Save the file changes.
Figure 14: SERIAL1 Defined as COM5
When the user opens the Connect window, COM5 appears as the default COM port, as indicated in Figure
15 below.

Figure 15: Connect Default Port COM5
2.7. Remote Connection

Connecting to the Control Panel (CP) remotely requires no modems or cables. For a remote a connection,
the CP can use cellular (4G/3G/2G) communications. The user should use the Windows Remote Desktop
utility to connect remotely to the CMS.
Figure 16: Remote Desktop Connection Window
The Windows Remote Desktop connection requires the user to connect to a server, as in Figure 16 above,
and to enter user credentials (user name and password) for accessing the server, as shown in Figure 17
below. The server connects to a cellular CP, using GPRS protocol.

Figure 17: Enter User Credentials Window
NOTE: Consult Essence Professional Services personnel to receive the server IP

address and the user credentials for accessing the server.
Following the successful remote connection to the Server, the Remote Desktop screen displays the
Care@Home™ CMS shortcut. Enter the CMS application via the shortcut.
Figure 18: Care@Home™ CMS shortcut
When the user clicks over the Care@Home™ CMS icon, the Care@Home™ CMS software application opens
the home page. The Connect window automatically appears, as in Figure 19 below.

Figure 19: Connect Window via Remote Connection
Table 3 below provides the instructions for configuring the parameters on the Connect window for a
remote connection.
Name Definition and Instructions Data Values Required or Default

Optional Value
User For Essence technical support use only Optional Blank
Password For Essence technical support use only Optional Blank
Protocol: Upload Select this option to establish a connection Radio Group Optional Selected
with the CP to maintain the panel settings.
Protocol: Remote Select this option to activate the Remote Radio Group Optional Not Selected
Boot Boot feature to update the CP and
peripheral firmware.
Note: The Remote Boot window appears
when this option is selected. See Figure 138
on page 135.
Connect Select the remote connection method via Dropdown List Required COM16->
Amigo communications application. Amigo
Panel ID Enter the Account number assigned to the Up to 8 digits Required None
Control Panel.
(View system Amigo connection messages are displayed. N/A Display Only N/A
messages)
Table 3: Remote Connection Parameters

Perform the following procedure to establish a remote connection from the CP to the CMS, after
connecting and logging on the remote server via Remote Desktop:
1. Select the COM16 port (Default) for the Amigo Remote connection.
2. Enter the Control Panel Account Number.
3. Click at the bottom of the Connect window.
System messages are displayed in the message window, as illustrated in Figure 20 below, describing the
status of the connection process.
In Figure 20 below, the messages explain that the system opens the Amigo virtual port and calls the CP
using the Connect API Web Service. When the CP responds, the system displays messages that the “COM
is OK” and that the system is verifying the communications connection.
Figure 20: Remote Connection Successful

Following the completion of the connection procedure, the Panel Info window appears displaying the
customer (resident) current status. Figure 21 below shows examples of the customer status in the window
title of the Panel Info window.
Figure 21: Panel Info for Remote Connection
Click , in the Panel Info window, to upload the CP data to the CMS software application.
For more information about the Connect window functionality, see section 2.5 on page 14.
Note: All functionality is available using the remote connection. However, the
response time for this type of connection is slower than direct connection types.
For more information about the Panel Info window, see section 2.8.2 on page 25.
2.8. Initial Control Panel Connectivity
You must first connect the Care@Home™ CMS to the Control Panel (CP), to use the CMS software
application to manage your Care@Home™ CP and peripheral devices functionality.

2.8.1 Upload Control Panel Settings Procedure

To establish a connection to the CP, perform the following procedure:
1. Click the Care@Home™ CMS icon. The Care@Home™ CMS software application opens the home
page. The Connect window automatically appears, as shown in section 2.5 on page 14.
2. Select the Upload Protocol option.
3. Select the COM port according to the connection method required:
 Local connection: See section 2.6 on page 16.
 Remote Cellular connection: See section 2.7 on page 20.
4. Enter a phone number, if required by the connection method chosen.
5. Click the button at the bottom of the Connect window.

Following the successful completion of the connection procedure, the Panel Info window appears.
6. Click to upload the CP data to the CMS software application.
2.8.2 The Panel Info Window

Following the successful completion of the connection procedure, the Panel Info window appears. Click
the push buttons on the Panel Info window as needed.
Figure 22: The Panel Info Window

Table 4 below describes the information and functionality of the Panel Info window.
Name Data/Buttons Definition and Instructions

Firmware: Serial Serial number of the Control Panel
Main CPU Firmware version of the Control Panel
Panel Time: Date Date of the Control Panel
Time Time of the Control Panel
GSM Current strength of the GSM reception signal, for a 4G/3G/2G Model CP only
Coverage
Commands: Click this button to restart the CP. The restart occurs at the end of the current session.
Push Button Click this button to load new status information of the CP to the Panel Info window.
Functionality
Click this button to upload the CP configuration parameter values to the CMS
application modules.
The Remote Panel window appears, as in Figure 23 below, displaying a progress bar of
the data transfer process.
Table 4: The Panel Info Data
Figure 23: CP Data Upload
Following the completion of the connection procedure, the connection information is displayed on the
left-most part of the Care@Home™ CMS software application home page, as shown in Figure 24 below.

Figure 24: CMS Home Page Connection Data
The connection data is similar to the data displayed on the Panel Info window. For information about the
Panel Info data, see Table 4 on page 26. The Account Number displayed is the account number currently
assigned to the CP.
The End-User can update the configuration parameter values of the CP by:
 Clicking the button on the Panel Info window
 Clicking the button on the left side of the CMS Home page
Figure 25: The Reset Panel Message Window

 Selecting the Open function in the File menu on the CMS Home page
Figure 26: The Open function Message Window
At the end of the CMS session, the CP integrates the updated configuration parameter values into the CP
functionality.
2.8.3 Control Panel Re-Connect
When the local connection to the CP fails, it is necessary to re-establish the connection to the CP.
There are four (4) instances when it is necessary to re-connect to the CP:
1. The CP is not connected to a working USB cable.

The messages in the System Messages window show the communication checking process. This
process terminates with an Authentication Time-Out message.
The Care@Home™ CMS software application issues the Authentication Time-Out message window,
as shown in Figure 27 below.

Figure 27: Authentication Time Out
2. The user does not wait the acceptable time period before attempting to re-connect to the CP.
See the re-connect procedure on page 30.
As in the previous instance, the connection process terminates with an Authentication Time-Out.
The Care@Home™ CMS application issues the error message as shown in Figure 27 above.
3. The COM port specified is being used by another device.

The COM port chosen, from the dropdown list in the Connect field, in the Connect window is
unavailable, as illustrated in Figure 28 below.
The messages in the System Messages window show that the attempt to access the COM port failed.
4. The COM port chosen in the Connect window is invalid.

The COM port chosen, from the dropdown list in the Connect field, in the Connect window, is
incorrectly defined in the configuration file.
As in the previous instance, the messages in the System Messages window, as in Figure 28 below,
show that the attempt to access the COM port failed.

Figure 28: Port Unavailable or Undefined
When re-connecting the CP to the local PC, there is a beep that is sounded when the re-connect is
successful.
For information about the beeps sounded during the connection process, see page 17.
2.8.3.1 Re-connect to CP Procedure

To re-connect the Control Panel (CP) to the local personal computer (PC), perform the following
procedure:
1. Click the Disconnect icon in the toolbar of the Care@Home™ CMS software application screens.
2. Remove the USB cable from the USB connection on the CP.
3. Wait a minimum of 40 seconds. This allows the CP to reset itself.
4. Attach the USB cable to the USB connection on the CP. A successful plug-in beep is sounded. If the
beep is not sounded, try again.
5. Click the Connect icon in the toolbar of the Care@Home™ CMS software application screens.
NOTE: The time period required for the CP to reset itself is vital to the successful re-
connect of the CP to the local PC.

Getting Started
3. Getting Started
Open the Care@Home™ CMS software application by double clicking over the Essence icon (see Figure 4
on page 12). The Care@Home™ CMS software application home page appears.
3.1. Care@Home™ CMS Home Page
The Care@Home™ CMS software application home page provides a File menu, action icons, and the Main
navigator menu to operate within the software application.
Figure 29: The Care@Home™ CMS Home Page

Getting Started
3.2. Main Action Icons
The following is a list of the action icons on the toolbar of the Care@Home™ CMS software application
screens including the functionality description of each action icon.
Action Icon Action Definition and Instructions
Exit the Care@Home™ CMS software application.
CMS properties: Revising COM port properties is reserved for Essence technical
support personnel use only.
Disconnect from the Control Panel (CP).
Connect to the CP: Opens the Connect window. For information about the
Connect window, see section 2.5 on page 14.
Download the configuration parameter settings from the Control Panel module to
the Control Panel (CP).
Upload the configuration parameter settings from the local configuration file (.cpf
file) to the Control Panel module.
Refresh: Load new status information to the CMS software application.
Monitor activity sensors, safety devices, and emergency devices connected to the
CP.
See Figure 30 and Figure 31 to view the monitoring windows.
Figure 30: The Activity Sensors Monitoring Window

Getting Started
Figure 31: The Safety and SOS Monitoring Window
Click the Monitor action icon in the toolbar or the Monitor sub-menu on the menu bar to access the
monitoring windows. The monitoring windows display the status information for the devices connected
to the CP, as follows:
 The Activity Sensors - Monitor window is a consolidated view of the information about the
sensor devices as displayed in the Activity Sensors module.
 The Safety & SOS - Monitor window is a consolidated view of the information about the safety
and emergency devices as displayed in the Safety and SOS module.
3.3. File Menu Functions
Figure 32: File Menu on Care@Home™ CMS Home Page

Getting Started
Table 5 below explains the functions in the File menu which allow management of the CMS parameters file
(.cpf file) for the Care@Home™ CMS software application:

Open Locate and “open” the local .cpf file on the personal computer (PC) to be uploaded to the CMS software
application, using the Windows CMS File Dialog box.
Save Save the current configuration parameter settings to a local .cpf file using the same file name. If the .cpf file
is a new file, use the Save As… function.
Save as… Save the current configuration parameter settings to a new local .cpf file with a new file name.
Print… Produce an external file or hardcopy of the configuration parameter settings. See Figure 35 on page 36.
Print Log… For the description of this functionality, see section 12.7 on page 118.
Print Setup Set the printer settings to produce a hardcopy of the configuration parameter settings. See Figure 36 on
page 36.
Quit Select this function to exit the Care@Home™ CMS software application. A window appears to confirm the
exit request. See Figure 33 on page 35.
Table 5: File Menu Parameters
3.3.1 Open Function
The Open function not only locates and opens the .cpf file but also automatically uploads the
configuration parameter settings to the CP, at the end of the session.
3.3.2 Quit Function
The Quit function monitors the user when exiting the software application. A window appears to confirm
the exit request as demonstrated in Figure 33 below.

Getting Started
Figure 33: The CMS Exit Window
If the CMS is connected to a Control Panel, the message in the window that appears reminds the user of
this connection, as in Figure 34 below.
Figure 34: Exit CMS with CP Connected
This window prompts the user to confirm the request to exit the Care@Home™ CMS software. The window
appears when the user selects the Quit option from the File menu or when the user clicks the Window
Close button ( ) to close the Care@Home™ CMS software application home page.
When the Exit CMS window appears:
 Click to confirm the exit request.
 Click to cancel the exit request.

Getting Started
3.3.3 Print… Function
Figure 35: The Print Panel Configuration Window
The Print… function opens the Print Panel Configuration window. This function provides the tools to
choose the media format to print the CP data. The End-User can choose whether to produce an Excel file,
a .csv (comma separated values) file, or a hardcopy of the configuration parameter settings.
3.3.4 Print Log… Function

The Print Log… function has same functionality as in the Log Events module. For information about the
Print Log function, see section 12.7 on page 118.
3.3.5 Print Setup Function
Figure 36: The Print Setup Window

Getting Started
The Print Setup function opens the Print setup screen, shown in Figure 36 above. Select the printer and
the other print-related settings to produce a hardcopy of the configuration parameter settings and other
information.
3.4. The Main Navigator Menu

The Main navigator menu provides a user-friendly guide to access all of the modules in the Care@Home™
CMS software application.
The following is a list of the modules in the Care@Home™ CMS software application along with a
description of the functionality of each module.
Figure 37: The Main Navigator Menu
 The Control Panel module – This module provides the tools to configure the Care@Home™
Control Panel (CP) parameters.
For more information about this module, see chapter 4 on page 39.
 The Dialer module – This module provides the tools to define the communication methods,
such as phone numbers, IP addresses, and ports, and to manage the flow required to
communicate with a Monitoring Station.
 The Activity Sensors module – This module provides the tools to manage and control the
activity sensors installed on the customer premises.
 The Safety and SOS module – This module provides the tools to manage and control the safety
and emergency devices installed on the customer premises.

Getting Started
 The Panel Date Time module - This module allows the Operator to set the local time of the
Control Panel Internal Clock.
 The Vocal Announcements module – This module provides the Operator with a tool to define
which type(s) of announcements and reminders are to be used and to manage the vocal
announcements and reminders for the resident.
The reminders announce:
 When the Residents should take their medication
 The schedule time of an appointment
 The time transportation should arrive to take a Resident to an appointment or meeting
 Wake-up calls similar to an alarm clock
 Random requests from the Operator for the Residents to test their Emergency buttons
 The Mobile Operator module – This module provides the tools to provide APN information for
the SIM card in the Care@Home™ CP.
 The Custom Labels module - This module provides the tools to define and manage the
personalized labels, defined by the user, to label areas on the customer premises not included in
the list of possible areas provided by the software application.
 The Log Events module – This module provides the tools to view the log of events and activities
recorded by the CP for a given time period.

The Control Panel Module
4. The Control Panel Module
Figure 38: Access to the Control Panel Module
Click the Control Panel option on the Main navigator menu. The Control Panel Module is the tool that
allows the configuration of the settings for the Care@Home™ CP installed at the customer premises.
Figure 39: The Control Panel Module

4.1. Control Panel Module Specifications

The purpose of this section is to define all the Control Panel (CP) configuration parameter values.
4.1.1 Enabling Care@Home™ Analytics Functionality
To enable the Care@Home™ Analytics functionality, mark the Enable Care@Home Analytics checkbox. In
so doing, the CMS software application activates functionality specific for a cellular (3G) centric
configuration.
When uploading CP parameter values from a local .cpf file or from a CP connected to the CMS and the
parameter values are defined for Care@Home™ Analytics functionality, the Enable Care@Home Analytics
checkbox is automatically marked and the Care@Home™ Analytics functionality is activated.
Figure 40: Care@Home™ Analytics Functionality Enabled
When Care@Home™ Analytics is enabled, changes occur to the CMS GUI in the CMS software application
modules, to accommodate Care@Home™ Analytics functionality.
WARNING! Do not change the “marked” Enable Care@Home Analytics checkbox to

unmarked.
The More Options button appears to the right of the Enable Care@Home Analytics checkbox on the
Control Panel module window. When clicked, the More Options button displays an extension for the
Control Panel configuration specific to Care@Home™ Analytics functionality.
For more information about the CP configuration extension, see section 4.1.7 on page 49.

4.1.2 Parameters from Account Number to Remote Call-In
Figure 41: Parameters from Account Number to Remote Call-In
Table 6 below describes the CP configuration parameters on the left side of the screen from the Account
Number parameter to the Remote Call-In parameters.
Name Definition and Instructions Data Values Required Factory

or Settings
Optional
Account Enter the CP account number assigned by the Integer(8) Required None
Number Monitoring Station.
Speakerphone Enable Enable = Checked Optional Enable =

Mark the checkbox to activate the option to answer Disable = Checked
incoming calls using the CP Emergency Call button Unchecked
(Medical Alarm).
This parameter activates the speaker in the CP.


or Settings
Optional
Medical Alarm Delay Number(3) Required 10 seconds
Set the time duration before the Medical Alarm is Values: 0-180
triggered. This allows time to cancel the medical Unit of measure:
alarm, if triggered by mistake. Seconds
Cancel the Medical Alarm by pressing the CP Reset
button.
Voice window Number(2) Required 10 minutes
Set the timeframe for the CP to automatically Values: 0-60
answer an incoming call. Unit of measure :
The window allows the Operator to call the Resident minutes
after a call was terminated accidentally, (not by 0 = disabled
DTMF) after the Medical Alarm was triggered.
Periodic Test: The following three (3) parameters combined define the reporting frequency for forwarding a periodic
system test report to the Monitoring Station.
Days Number(2) Required 7 days
The part of the reporting frequency that defines Values: 1-31
number of days Unit of measure: days
Hours Number(2) Required 0 hours

number of hours Unit of measure:
hours
Minutes Number(2) Required 0 minutes
number of minutes Unit of measure:
minutes
Activity Timer Not applicable to Care@Home Analytics
Remote Call In Enable Enable = Checked Optional Disable =
Mark the checkbox to allow the CP to Disable = Unchecked Unchecked
automatically answer incoming calls.
Rings Number (2) Required 4
Set the number of rings for the CP to wait before Values: 4-12
automatically answering a remote call. The user
must enter the DTMF code to start a half-duplex
conversation.
Mute Rings Enable = Checked Optional Enable =
Mark the checkbox to silence the telephone rings Disable = Unchecked Checked
for the CP ringer for remote calls.
Table 6: Account Number to Remote Call-In Parameters

4.1.3 Parameters from Password to Mains Failure
Figure 42: Parameters from Password to Mains Failure
Table 7 below describes the CP configuration parameters in the middle of the screen from the Emergency
parameter to the Mains Failure parameters.
Name Definition and Instructions Data Values Required or Factory

Optional Settings
Password DTMF Code Integer (4) Required 1234
Enter the Dual-tone multi-frequency (DTMF) Code used to
allow the CP to receive remote calls.
Inactivity Not applicable to Care@Home Analytics

Mains Message Enable Enable = Checked Optional Enable =
Failure Mark the checkbox to activate the ability to broadcast of Disable = Checked
power-outage events to the Monitoring Station. Unchecked
Message Delay N/A Display Only 4 minutes

A fixed time-delay before broadcasting a power-outage
event.
Random Range Limit N/A Display Only 2 minutes

A 2-minute time interval during which the power-outage
event is broadcast randomly. This is used to avoid
overloading the Monitoring Station.
Table 7: Password to Mains Failure Parameters

4.1.4 The Control Panel Communications Module
Since the Care@Home™ Analytics functionality supports a cellular (3G) centric configuration, the
communications module for the CP is the Global System for Mobile Communications (GSM) – A cellular
telephone.
The .cpf file received from Essence for each CP is pre-configured with the matching communications
channel parameters.
WARNING! The Control Panel ceases operation if you change the Control Panel
Communications Channel parameters to the wrong communications channel.
Select only the GSM option to display the GSM configuration parameters.
Figure 43: GSM communications module
Table 8 below describes the CP configuration parameters for the GSM communications module.


or Settings
Optional
Transmitter(GSM) Telit 4G/3G/2G Radio group N/A Display
The GSM Module Only
Ring Tones Dropdown list Required “Default”
Select the ring tones for when the CP Values, “Default”, 1-18
receives a call.
Min GSM Level Number (2) Required 10
Set the minimum GSM reception level. Values: 1-31
ACK Timeout Number (3) Required 30 seconds
Enter the wait time, in seconds, to receive Values: 15-300
an acknowledgement message. Unit of measure: Seconds
Number of Retries Number (3) Required 2
Enter the number of times the dialer Values: 0-255
redials a phone number.
Retry Timeout Number(3) Required 1 second
Enter the time interval, in seconds, Values: 0-255
between redials. Unit of measure: seconds
DNIS Number(5) Required 00000
(Dialed Number Identification Service)
Enter the DNIS number which is included
in every message sent from the CP to the
Monitoring Station.
The number is used by the Monitoring
Station to differentiate between multiple
Service Providers.
Table 8: GSM Configuration Parameters
Click to open the GSM More window, as shown in Figure 44 below.
Figure 44: The GSM More window

Table 9 below describes the additional GSM configuration parameters in the GSM More window.

Optional Settings
SIM PIN Enable Enable = Checked Optional Disable =
Mark the checkbox to allow this option if Disable= Unchecked Unchecked
there is a PIN code for the CP SIM card.
SIM PIN Code Number (4) Optional Blank
Enter the PIN code for the CP SIM card.
Provider Lock Enable Enable = Checked Optional Disable =
Mark the checkbox to allow the selection of Disable= Unchecked Unchecked
a specific Cellular Provider. This option
disables the SIM card roaming option.
Provider Dropdown list per Required N/A
Choose the Cellular Provider for the CP SIM customer region or
card. N/A
APN in Use APN The CP loads the actual Disabled
The Access Point Name (APN) for your SIM APN information from
card Service Provider. the Mobile Operators
User Name: module, according to Disabled
The APN user name. the APN name from the
SIM-card inserted in
the CP.
Password Disabled
The APN password.
Table 9: Additional GSM Configuration Parameters
Click to exit the GSM More window.

4.1.5 Parameters from DTMF Password to Temperature
Figure 45: Emergency to Temperature Parameters
Table 10 below describes the CP configuration parameters on the right side of the screen from the
Emergency parameter to the Temperature parameters.

Optional Settings
Emergency Default Conversation Half Duplex Half Duplex = Checked Optional Half Duplex
Mark the checkbox to define the Full Duplex = Unchecked = Checked
conversation mode between the user
and the Monitoring Station during an
emergency call.
Speaker Volume Dropdown list Required 4
Set the volume level of the Control Values: 1-7 when the
Panel speaker, for a Half-Duplex checkbox is
emergency call. marked
Note: Appears only when previous
checkbox is marked.
Temperature Extreme Temperature Enable Enable = Checked Optional Disable =
Mark the checkbox to activate the Disable = Unchecked Unchecked
capability to trigger an alarm when one
(or more) of the devices, in the system,
reports a temperature that passes the
given thresholds.
Freeze Threshold Dropdown list Required 40oF
Set the low threshold for cold Values: 30-75 at 5o increments.
temperatures. Unit of measure: Fahrenheit
Heat Threshold Dropdown list Required 100oF
Set the high threshold for hot Values: 75-120 at 5o increments
temperatures. Unit of measure: Fahrenheit.
Table 10: Emergency to Temperature Parameters

4.1.6 Parameters from Emergency Pendant to Sound
Figure 46: Emergency Pendant to Sound Parameters
Table 11 below describes the CP configuration parameters on the right side of the screen from the
Emergency Pendant parameters to the Sound parameters.

Optional Settings
Emergency Min Press Duration Dropdown List Required 0.5 seconds

Pendant (EP) Set the minimum press time to trigger Values: 0.5-12 with
an emergency event using the increments of 0.5
Emergency Pendant (EP). Unit of measure:
Seconds
Pairing Min Press Dropdown List Required 4 seconds
Set the minimum time to press the EP Values: 4-15
to pair the EP with the CP. Unit of measure:
Seconds
Pairing Max Press Dropdown List Required 23 seconds
Set the maximum time to press the EP Values: 4-23 with
to pair the EP with the CP. increments of 0.5
Unit of measure:
Seconds
Supervision Report N/A Display Only 110 hours
The maximum number of hours within
which the CP must receive at least one
Supervisory Report from the EP.
Note: If no report is received, the CP
sends an event message to the
Monitoring Station that the EP is lost.


Optional Settings
Sound Beep Level Dropdown List Required 7

Set the volume of the beeps. Values: 1-7
Where 1 is Low.
Internal Siren Duration Number(3) Required 5 seconds
Set the time duration for sounding the Unit of measure:
CP alarm. seconds
Table 11: Emergency Pendant to Sound Parameters
4.1.7 More Options
Figure 47: More Options Button
Access to the Control Panel Configuration Extension window is available by clicking the More Options…
button in the Control Panel module, as in Figure 47 above.
The Control Panel Configuration Extension includes four (4) tabs as follows:
 Photo Config – Definitions for the Camera detectors configuration

 Analytics – Other additional configuration parameters
 PERS – Additional communications protocol and Debug option for Technical Support
 DTMF Config – Definitions for DTMF keys configuration

4.1.7.1 Configure the Camera Devices
Figure 48: CP Photo Configuration
When triggered, each of the Infrared Camera (IPD) peripheral devices photographs five (5) consecutive
photos of the event. If both cameras are enabled, the photos are taken in the order defined by the
configuration parameters. The purpose of the Photo Configuration tab is to configure this camera-
related functionality.
NOTE: Inclusion of the IPD peripheral devices in the Care@Home™ System

installation is optional.
If IPD peripheral devices are installed, mark the relevant checkboxes to enable the following capabilities:
 Alarm – If enabled, the CMS instructs the IPDs to take photos when an alarm is triggered. The
default is disabled (unmarked).
 Photo Request - If enabled, the CMS instructs the IPDs to take photos when an event is detected
by any of the configured sensors. The default is disabled (unmarked).
 SOS - If enabled, the CMS instructs the IPDs to take photos when an emergency event is
triggered. The default is disabled (unmarked).

Define the order in which the IPDs photograph events when the camera option is triggered.
 Camera 1
 Camera 2
If the camera parameter is set to “None”, the camera option is disabled. The default configuration is
“None”.
If a numeric value is selected for a camera parameter, this is the device identification number for the IPD
that is configured to photograph the events.
Camera 1 is the first priority camera. Camera 2 is the second priority camera.
Click to add the Photo configuration parameter values to the CP configuration.
4.1.7.2 Analytics
Figure 49: Analytics Tab
The purpose of the Analytics tab is to configure other Care@Home™-related functionality:

 Care@Home™ Report interval – The reporting frequency is in minutes; values included are
“Default”, and from 10 to 180 with increments of 10. The default value is “Default”.
 STUN Interval – Enable the STUN communications type and define the interval in seconds;
values range from 1 to 43200 seconds. No default value provided.

 Panel’s Trouble LED – When the LED on the Control Panel is lit, a technical event has
occurred, such as:
 Communications with the CP is lost
 Supervision with a peripheral is lost
 Battery power is low
Mark this checkbox to disable the LED and ignore technical event warnings.
Unmark this checkbox to enable the LED and allow technical event warnings.
Click to add the Analytics parameter values to the CP configuration.
4.1.7.3 PERS Configuration Extension
Figure 50: PERS Tab
Table 12 below describes the communication parameters on the PERS tab, as shown in Figure 50 above.

Optional Settings
IP Protocol Dropdown List: Required SIA IP
Communications Choose the communication protocol method  SIA IP
Protocol between the CP and the Monitoring Station.  SIA DC-09


Optional Settings
Debug Enable Enable = Checked Optional Disable =
Disable = Unchecked Unchecked
For Essence Communication log overlapping Enable = Checked Optional Disable =
Professional Disable = Unchecked Unchecked
Services personnel Push Button N/A N/A
only
Table 12: PERS Parameters
Click to add the PERS parameter values to the CP configuration.
Click to exit Control Panel Configuration Extension window and return to CP module.
4.1.7.4 DTMF Configuration
Figure 51: DTMF Config Tab
The purpose of the DTMF Configurations tab is to configure DTMF-related functionality:

 To define the telephone keys to use for the Conversation Flow, through the Control Panel (CP),
between the Service Provider Operators and the Resident.

 To set the period when the DTMF is blocked for Emergency Alarm Calls through the Control
Panel.
The DTMF configuration file (DTMFConfig.ini) file is located at the following default path:
c:\Program Files (x86)\Essence\Care@Home CMS\
c:\Program Files\Essence\Care@Home CMS\ (Windows XP only)
Figure 52: DTMF Configuration File
Table 13 below describes the configuration parameters on the DTMF Configurations tab.

Optional Settings
DTMF Keys Half duplex: Speaker Number(1), Possible Display Only 1
Half duplex: Microphone values : 1-10, Note: Data values 3
Full duplex: increase speaker volume Note: 10 equals are set via the 2
Full duplex: Speaker DTMF key code 0 DTMFConfig.ini 0 (10)
Disconnect the Call file 9
Reset the Control Panel after 5 presses 8
DTMF blocking This feature is used during an Emergency Dropdown List Required Default
period Call, for a given time period, to intercept the Values: 1-60 seconds
DTMF codes sent to the CP. The purpose is and “Default”
to prevent the CP from acting according to Note: Default – The
these DTMF codes. blocking period is
Note: The DTMF codes are sent when the disabled. All DTMF
Monitoring Station is transferring the call to codes are received
the Operator assigned to answer the by the CP.
Emergency Call.
Table 13: DTMF Configuration Parameters

Click the button to add the DTMF Configuration Parameter values to the CP configuration.
Click the button to exit the Control Panel Configuration Extension window and return to CP
module.
4.1.8 The Control Panel Module Buttons
Figure 53: Control Panel Module Buttons
The Control Panel module buttons are located at the bottom of the screen. The functionality of the
module buttons is:
 Clear – Restores the values of the Control Panel module configuration parameters to the values
of the last update. If no update was done since the CP upload, the original values from the CP
upload are restored
 Update - Updates all the new and revised configuration parameter values to the Control Panel
module.
Note: The user must click to insure that the modifications are
integrated into the CP configuration.

The Dialer Module
5. The Dialer Module
Figure 54: Access to the Dialer Module
Click the Dialer option on the Main navigator menu. The Dialer module is the tool that enables the
definition of communication methods and the management of the flow required to communicate with a
Monitoring Station. The module allows you to manage the Destination list, comprised of Domain names
and IP addresses, along with the connect sequences for communication between the Care@Home™
Control Panel (CP) and the Monitoring Station.
Figure 55: The Dialer Module

The Dialer Module
Note: If the Care@Home™ system is configured to work without the PERS receiver,
do not use the PERS Dialer functionality as follows:
 The Comm Type: Message
 The Sequence Protocols: PERS Supervisory and PERS Alert
5.1. Destination Definition

A destination in the Dialer Destination list is limited to one of the following combinations:
 An IP address and a Port number
 A Domain name (URL) and a Port number
The communications type and communications channel attributes must be defined for each destination.
Additional attributes are defined for a destination according to the communications type and
communications channel attributes selected.
5.1.1 Defining Communications Attributes
Figure 56: Comm Type Options
Figure 57: Comm Channel Options

The Dialer Module
Figure 56 and Figure 57 above display the dropdown lists of the pre-defined values for the Destination
attributes.
Table 14 below describes the basic attributes required to add a destination to the Destination list.

Optional Value
Phone ID Choose a number to identify each Dropdown list Required None
destination in the Destination list. Values: 1-16
To view the Destination list, see
Figure 55 on page 56.
Comm Select the communications type for Dropdown list: Required None
Type the Destination.  Analytics Message
Note: Use the “Message” Comm  Data Stream
Type only if the Care@Home™  Message
system is configured to work with a
PERS receiver.  Video
 STUN
 Debug Printing
Comm Select the broadcast method to use Dropdown list. Required GPRS
Channel with the communications type  GPRS
entered in the previous field.  GPRS 2G
Table 14: Destination Basic Attributes
The communications types available are:

 Analytics Message – Panic emergency-related messages for the Care@Home™ Server
 Message – Panic emergency-related messages for the PERS receiver
Note: Use this Comm type only if the Care@Home™ system is configured to work with a PERS
receiver.
 Data Stream – Raw data files for the Care@Home™ server or for transfer to 3rd party software via
an API
 Video – Photos taken by the Infrared Camera (IPD) peripheral devices
 STUN – The Session Traversal Utilities for Nat (STUN) protocol retrieves the public IP address of
the Control Panel (CP).
 Debug Printing – For use by Essence Technical Support only. If enabled, this feature allows for
the printing of commands for the GSM modules.

The Dialer Module
5.1.2 Defining Communications Channel Attributes

The available communications channels are both based on general packet radio service (GPRS):
 GPRS
 GPRS 2G
Figure 58: GPRS communications channel
For GPRS or GPRS 2G, the Dialer module prompts the user to enter the following information:

Optional Value
Domain Enable if a URL is required rather than an IP Enable = Checked Disable Optional Disable =
Name address. = Unchecked Unchecked
URL If Domain name is enabled, enter a URL name. Character Required None
IP address Enter an internet protocol (IP) address of the A set of 4 3-digit strings Required None
receiver. Values from 0- 255
Port Enter the port number used with the IP Integer (5) Required None
address entered in the previous field. Values: 1-65536
Protocol Note: Not applicable for Debug Printing Dropdown list Required None
Select the communications protocol  TCP
associated with the GPRS communications  UDP
channel type chosen.
Emergency Enter a phone number to call in case of an 7-18 digit string Optional None
Number emergency.
Note: The emergency number is only
prompted for communications types ADL
Message and Message.
Table 15: Attributes for GPRS Comm Channel

The Dialer Module
Click to add the IP addresses and more to the destination list of the Dialer module along
with the attributes entered for each destination.
5.2. Managing the Destination List

The Dialer Module allows the End-User to manage the Destination list. The user has the capability to
perform the following functions:
 Add - The End-User can add a new destination in a blank row in the list of destinations.
 Update – The End-User can update a row with an existing destination.
 Delete - The End-User can delete a row from the Destination list with an existing destination.
5.2.1.1 Add a Dialer Destination

The Update function allows the End-User to Add a new destination to the Destination list by updating an
empty row.
1. Select an empty row in the Destination list window.
2. Enter the destination information in the fields to the right of the Destination list window:
 Comm Type
 Comm Channel
 Receiver Address Information
3. Place the cursor on the row, in the Destination list window, selected in Step 1.
4. Right click on the mouse. A window appears displaying the functions available to manage the
Destination list, as in Figure 59 below.
Figure 59: Manually Add Destination

The Dialer Module
5. Click to add the new destination to the Destination list. The selected row is populated
with the information entered in Step 2.
5.2.1.2 Update a Dialer Destination

The Update function allows the End-User to revise an existing destination in the Destination list.
1. Select a row in the Destination list window with an existing destination.
2. Revise the destination information in the fields to the right of the Destination list window:
 Comm Type
 Comm Channel
 Receiver Address Information
3. Place the cursor on the row, in the Destination list window, selected in Step 1.
Destination list, as in Figure 59 above.
5. Click to revise the existing destination in the list. The selected row is populated with
the information revised in Step 2.
5.2.1.3 Delete a Dialer Destination

The Delete function allows the user to remove an existing destination from the destination list.
1. Place the cursor on the row, in the Destination list window, that is to be removed from the
destination list
Destination list, as in Figure 59 above.
3. Click Delete to remove the existing destination from the list. A window appears prompting the End-
User to confirm the delete request, as in Figure 60 below.

The Dialer Module
Figure 60: Confirm Delete Destination
4. Click to confirm the Delete request.
5. Click to cancel the Delete request.
5.3. The Dialing Sequence

The End-User can enter dialing sequences for the following communication types:
 Message – For the communications types Analytics Message and Message
 Video - For the Video communications type
 STUN - For the STUN communications type
 Data - For the Data Stream communications type
Each communications type has its own protocols.
Figure 61: Dialing Sequence Types
The CMS software application verifies that the destinations chosen for the dialing sequence are of the
same communications type as the dialing sequence protocol.

The Dialer Module
Figure 62: Destination List Example
For example, in Figure 62 above, the destination list includes destinations of different communications
types. Destinations 1, 2 and 3 are of communications types valid for the Analytics Message dialing
sequence. When choosing a destination with a communications type invalid for the selected dialing
sequence, an error message appears, as in Figure 63 below.
Figure 63: Error Message for Incorrect Comm Types
The following are the protocols assigned to the dialing sequence types:
 The Message dialing sequence uses the Analytics Alert protocol.
Note: Use the PERS Supervisory and the PERS Alert protocols only if the Care@Home™ system is
configured to work with a PERS receiver. For information about the PERS Alert protocols, see the
Dialing Sequence section in the ESUG05071 Care@Home™ PERS CMS User Guide.
 The Video dialing sequence uses the Comfort protocol.
 The STUN dialing sequence uses the STUN protocol, allowing for only one destination per
dialing sequence.
 The Data dialing sequence uses the Debug Printing protocol. This is for use by Essence
Professional Services only.

The Dialer Module
View the dialing sequences and their protocols in Figure 64, Figure 65, Figure 66, and Figure 67 below.
Figure 64: Analytics Message Dialing Sequence Protocol
Figure 65: Video Dialing Sequence Protocol
Figure 66: STUN Dialing Sequence Protocol
Figure 67: Data Dialing Sequence

The Dialer Module
Select a protocol and choose the destinations listed in the Destination list window for the relevant dialing
sequence, as defined in the Table 16 below.

Optional Value
Sequence Enter the IDs for the relevant destinations, in the Number(2) Required None
order they must be contacted. Values: 1-16
See the list of ID numbers in the Destinations window
at the top of the screen. To view the Destination
window, see Figure 55 on page 56.
Note: Only choose an ID number for which an IP
address is listed.
No. of Retries Enter the number of times to re-connect with each IP Dropdown List Required 1
address, if the connection does not succeed. Values: 1-8
Table 16: Dialing Sequence Information
Click to add the dialing sequence to the selected protocol.
Figure 68: Dialing Sequence Example for the Analytics Message Protocol
For example, in Figure 68 above, the Control Panel (CP) sends events to the Monitoring Station receiver,
as follows:
1. CP sends Analytics Alert events to the Monitoring Station receiver according to the IP Address:Port
details of Destination ID #10
2. The CP attempts to communicate with the receiver twice, as defined for the number of retries in the
example.

The Dialer Module
3. If no acknowledgement is received in both communication attempts, the CP moves on to the next

Destination ID in the sequence, such as Destination ID # 8 as in the example above.
4. The process of sending this event to the Monitoring Station receiver continues until one of the
following situations occur:
a. An acknowledgement is received for the event. The process ends successfully.
b. No acknowledgement was received for any of the Destination IDs defined in the sequence. The
process ends unsuccessfully. The CP issues the following vocal announcement:
“Attention, communication with the Monitoring Station is lost.”

The Activity Sensors Module
6. The Activity Sensors Module
Figure 69: Access to the Activity Sensors Module
Click the Activity Sensors option on the Main navigator menu. The Activity Sensors module is the tool
that allows management of the sensor devices for the Care@Home™ Control Panel (CP) installed on the
customer premises.
Figure 70: Activity Sensors Module

All the sensor devices connected to the CP are listed by identification number in this module. For each
sensor device, the following information is displayed:
 Identification number- The internal identification number assigned to the sensor device
synchronized with the Care@Home™ Web Application
 Serial Number – The sensor device serial number
 Device Type – The sensor device type
 Mode – The characteristics of the device type functions, such as “Chime”, “Bypass”, and
“Inactivity”
 Status – The status of the sensor device, such as “Tamper”, “Open” and “Low Bat”
 Label – The location monitored by the peripheral device
6.1. Defining Sensor Device Attributes

Figure 71 below shows the attributes required to define the activity sensors.
Figure 71: Sensor Device Attributes
Table 17 below describes the attributes for the sensor devices. Some of the attributes are display only.


Optional Value
Device ID The identification number (1- 55) assigned by the Integer from 1-55 N/A Display
CP for each sensor device. Only
RF The radio frequency (RF) level of the selected Percent N/A Display
sensor device. It is the received signal strength Only
indicator (RSSI) level of the selected device.
Device The device type of the selected sensor device. Character N/A Display
Type The sensor devices are: Only
 MGLS – MaGnet with dual LEDs and Shock
sensors
 PIR – Passive Infra-Red sensors
 IPD – PIR with a Camera (optional)
Version The version of the Firmware of the device Number (5,2) N/A Display
Only
Zone Label Choose the label that describes the location Dropdown list Optional None
where the sensor was installed.
Note: The dropdown list includes both system-
defined location labels and user-defined custom
labels.
First Choose the first camera to photograph the Dropdown list Optional None
priority events. Choose “NONE” to disable the camera
option.
IPD Note: For more information about the camera,
see section 4.1.7.1 on page 50.
Second Choose the second camera to photograph the Dropdown list Required None
priority events. Choose “NONE” to disable the camera
option.
IPD Note: For more information about the camera,
see section 4.1.7.1 on page 50.
Enable Mark the checkbox to enable the device LEDs to Enable = Checked Optional Disable =
LEDs light up is movement is detected. Disable = Unchecked Unchecked
Activity Choose the type of activity the sensor is Dropdown List Required None
Type configured to detect.
Send Mark the checkbox to enable the sensor device to Enable = Checked Optional Disable =
Detections send all its event detections to the CP. Disable = Unchecked Unchecked
External Note: MGLS device only Enable = Checked Optional Disable =

Magnet Mark the checkbox to confirm that the MGLS Disable = Unchecked Unchecked
device is installed outdoors.
(Enable Activate or deactivate modes that alter the Enable = Checked Optional None
modes) functionality of the activity sensor devices. Disable = Unchecked
Chime- Mark the checkbox to sound the chime, if For the following set of
the sensor device detects activity. checkboxes:
 Chime


Optional Value
Bypass – Mark the checkbox to deactivate the  Bypass
sensor device, including the ability to sense  Bypass Extreme
extreme temperatures. The sensor device remains Temperature
connected to the CP.  Inactivity
Inactivity – Mark the checkbox to enable the
sensor to send an Inactivity event to the
monitoring station, when no activity occurs
during a given time-frame.
Table 17: Attributes for Sensor Devices
Click to add the sensor device attributes to the CP.
6.2. Managing the Activity Sensors List
The Activity Sensors module allows the End-User to manage the Activity Sensor list manually. The End-
User can add an activity sensor to the Activity Sensor list or update the attributes of an activity sensor in
the Activity Sensors list.
To delete an activity sensor from the Activity Sensors list, the End-User requires privilege access usually
reserved for a system administrator or Essence technical support personnel.
6.2.1 Add an Activity Sensor
Figure 72: Functions to Manage the Activity Sensors

Figure 73: Add Activity Sensor
Figure 72 and Figure 73 above illustrate adding a new activity sensor to the Activity Sensors list.
To add an activity sensor to the Activity Sensors list, perform the following procedure:
1. Select an empty row in the Activity Sensors list.

Activity Sensors list.
3. Select the Add function. The Device Details window appears.
4. Enter the activity sensor device serial number.
5. Select the activity sensor device type.
6. Click the button.
Figure 74 below shows the message window that appears when the activity sensor is successfully added to
the Activity Sensors list.

Figure 74: Activity Sensor Added Successfully
6.2.2 Update an Activity Sensor
Figure 75: Select Activity Sensor for Update
To update a row in the Activity Sensor list with an existing activity sensor:
1. Select the row in the Activity Sensor list with the activity sensor requiring update.
2. Modify the values of the activity sensor attributes requiring revision. See the attributes on the right
of the Activity Sensor list in Figure 75 above.
3. Right click the mouse on the selected row. The function window appears as in Figure 76 below.
4. Click the Update function in the Function window or click at the bottom of the screen.

Figure 76: Update Activity Sensor
6.2.3 Delete an Activity Sensor

To delete an existing activity sensor from the Activity Sensor list compromises all the data that has been
accumulated for the End-User. It essentially “erases” all the event history not only for the activity sensor
requiring deletion but also for all the activity sensors installed on the End-User premises.
To delete an activity sensor from the Activity Sensor list:
1. Select the row in the Activity Sensor list with the activity sensor requiring deletion.
2. Right click on the mouse on the selected row. A window appears prompting the End-User to
confirm the delete request.
Figure 77: Confirm Delete Activity Sensor

3. Confirm the delete request:
 Click to confirm the Delete request.
 Click to cancel the Delete request.
6.3. Zone Status
Figure 78: Zone status for the selected device
The Zone Status box displays the status (normal = Green; problem = Red) of the selected sensor device.
The following is the list of the available statuses:
 Tamper – The selected sensor device was touched, moved, or installed incorrectly.
 Low Battery – The battery of the selected sensor device requires replacement.
 Bypass – The selected sensor device appears to be deactivated.
 Open – The connection for the selected sensor device is “broken” or “open”.
 Supervisory – A problem with the selected sensor device has occurred. The device is offline.

The Safety & SOS Module
7. The Safety & SOS Module
Figure 79: Access to the Safety & SOS Module
Click the Safety & SOS option on the Main navigator menu. The Safety & SOS module is the tool that
allows management of the safety and emergency devices for the Care@Home™ Control Panel (CP)
installed on the customer premises.
Figure 80: The Safety & SOS Module

All the safety and emergency devices connected to the CP are listed by identification number in this
module. For each safety or emergency device, the following information is displayed:
 Identification number - The internal identification number assigned to the safety or emergency
device
 Serial Number – The serial number of the safety or emergency device
 Device Type – The safety or emergency hardware device type
 Mode – The status of the safety or emergency device: Enable or Disable
 Label – The RF Input Label of the safety or emergency device describing where the device is
installed
7.1. Defining Attributes for Safety & SOS Devices

Figure 81 below shows the attributes required to define the safety and emergency devices.
Figure 81: The Safety & SOS Module Attributes
Table 18 below describes the attributes of the safety and emergency devices connected to the CP. All of
these attributes are display only.


Device ID The identification number (1- 8) assigned by the CP for Integer from N/A Display
each safety or emergency device. 1-8 Only
RF The radio frequency (RF) level of the selected safety or Percent N/A Display
emergency device. It is the received signal strength Only
indicator (RSSI) level of the selected device.
Hardware The code for the hardware type of the selected safety Character N/A Display
Type or emergency device. Only
Device Type The name of the hardware type of the selected safety Character N/A Display
or emergency device. Only
Table 18: General Attributes for Safety & SOS Devices
7.2. Specific Safety and Emergency Attributes
The safety and emergency devices require specific configuration values to monitor the events that occur
at the End-User premises that might threaten the safety of the End-User.
The hardware types of the safety and emergency devices are as follows:
 SK2 – Smoke detector devices
 EP – Emergency pendant (panic) devices
 SPB – Standard panic button devices
 Water Detector – MGLS devices with a Flood Detector attached to the devices’ dry contacts
Each hardware type for the safety and emergency devices has its own specific set of attributes. View these
attributes in Figure 82, Figure 83, Figure 84, and Figure 85 below.

Figure 82: SPB Emergency Device Attributes
Figure 83: PB Emergency Device Attributes
Figure 84: SK2 Safety Device Attributes

Figure 85: Water Detector Attributes
Table 19 below describes the attributes specific to the hardware types of the safety and emergency
devices connected to the Control Panel (CP).

RF Input Label Note: Not for EP Dropdown Required None
Choose the label that describes the location where the list
safety or emergency device was installed.
Note: The dropdown list is the same as dropdown list for
the Zone Label attribute, in the Activity Sensors
module. The list includes both system-defined location
labels and user-defined custom labels.
Bypass Mark the checkbox to temporarily deactivate the option Enable = Optional Disable =
to answer calls via buttons. If the checkbox remains Checked Unchecked
unchecked, mark the checkbox to enable the CP to Disable=
answer a call via buttons, such as a panic button. Unchecked
Enable Note: Not for SK2 or for the Water Detector Enable = Optional Enable =
Answer call Activate the option to answer incoming calls using the Checked Checked
via Buttons panic button. Disable=
Unchecked
Bypass Mark the checkbox to temporarily deactivate the Enable = Optional Disable =
Extreme capability to trigger an alarm when one (or more) of the Checked Unchecked
Temperature devices in the system registers a temperature that Disable=
passes the given thresholds. Unchecked
First Priority Note: Not for EP Dropdown Optional None

IPD Choose the first camera to photograph the events. list
Choose “NONE” to disable the camera option.
Note: For more information about the camera, see
section 4.1.7.1 on page 50.


Second Note: Not for EP Dropdown Optional None
Priority IPD Choose the second camera to photograph the events. list
Choose “NONE” to disable the camera option.
Note: For more information about the camera, see
section 4.1.7.1 on page 50.
Enable SPB Note: SPB Only: Enable = Optional Enable =
LED Activate the LED display for the SPB device. When the Checked Checked
SPB device is clicked, the LED lights up. If disabled, the Disable=
SPB device continues to function. However, the LED Unchecked
does not light up.
Safety Note: SK2 Only: Dropdown Required Default
Standard Select the safety standard to apply to the smoke list:
detector device. The standards relate to the event  Default
reporting frequency. The safety standards are:  EN
Default –out-of-the box factory settings designed to  UL
preserve battery life.
EN – European standards  ULC
UL – USA standards
ULC – Canadian standards
Enable LEDs Note: Water Detector Only: Enable = Optional Enable =
Activate the LED display for the water detector device. Checked Checked
When the water detector device is clicked, the LED lights Disable=
up. If disabled, the water detector device continues to Unchecked
function. However, the LED display does not light up.
Table 19: Specific Attributes for Safety & SOS Devices
Click to add the safety and emergency device attributes to the CP.
7.3. Managing the Safety & SOS Devices
The Safety & SOS module allows the End-User to manage the Safety & SOS device list manually. The End-
User can add a safety or emergency device to the Safety & SOS device list or update the attributes of a
safety or emergency device in the Safety & SOS device list.

7.3.1 Add a Safety or SOS Device
Figure 86: Functions to Manage the Safety or SOS Devices
Figure 86 above and Figure 87 below show how to add a new safety or emergency device to the Safety &
SOS device list.
Figure 87: Add Safety or SOS Device
To add a Safety or SOS device, perform the following procedure:

1. Select an empty row in the Safety & SOS device list.
2. Right click on the mouse. A window appears displaying the functions available to manage the Safety
& SOS device list.
3. Select the Add function. The Device Details window appears.
4. Enter the safety or emergency device serial number.
5. Select a safety or an emergency device type.

Figure 88 below shows the message window that appears when a safety or emergency device is
successfully added to the Safety & SOS device list.
Figure 88: Safety or SOS Device Added Successfully
7.3.2 Update a Safety or SOS Device
Figure 89: Select Safety or SOS Device for Update
To update a row in the Safety & SOS device list with an existing safety or emergency device:
1. Select the row in the Safety & SOS device list with the safety or emergency device requiring update.
2. Modify the values of the safety or emergency device attributes requiring revision. See the attributes
on the right of the Safety & SOS device list in Figure 89 above.
3. Right click on the mouse on the selected row. The function window appears as in Figure 90 below.

Figure 90: Update Safety or SOS Device
4. Click the Update function in the function window or click at the bottom of the screen.
The selected row is revised accordingly.
7.3.3 Delete a Safety or SOS Device

Deletion of an existing safety or emergency device, from the Safety & SOS device list, can compromise the
integrity of all the data that has been accumulated for the End-User.
It essentially “erases” all the event history not only for the safety or emergency device requiring deletion
but also for all the safety or emergency devices installed on the End-User premises.
To delete a safety or emergency device from the Safety & SOS device list:
1. Select the row in the Safety & SOS device list with the safety or emergency device requiring deletion.
2. Right click on the mouse on the selected row. A window appears prompting the End-User to
confirm the delete request.
Figure 91: Confirm Delete Safety or SOS Device

7.4. Radio Frequency Input Status
Figure 92: RF Input Status for a Selected Device
The radio frequency input status reports the status of a selected safety or emergency device (normal
=Green; problem =Red).
The following is the list of the available statuses:

 Tamper – The selected device was touched, moved, or installed incorrectly.
 Low battery – The battery of the selected device requires replacement.
 Bypass – The selected device appears to be deactivated.
 Supervisory – A problem with the selected device has occurred. The device is offline.

Control Panel Internal Clock
8. Control Panel Internal Clock

The Control Panel (CP) has an internal clock used by the Care@Home™ system to:
 “Timestamp” notifications
 Trigger time-sensitive activities
 Track events
Configuring the internal clock to the local time zone of the CP’s location is vital to the operation of the
Care@Home™ system.
8.1. Importance of the Internal Clock

The CP internal clock is used to trigger Care@Home™ time-sensitive functionality, such as the Vocal
Announcements feature.
For information about the Vocal Announcements feature, see chapter 9 on page 88.
It is important to synchronize the CP internal clock to the local date and time wherever the CP is located.
For example, consider the situation where the CP for an End User is located in Los Angeles, California and
the Service Provider is located in New Jersey. The CP is located in a different time zone than the Service
Provider. The Service Provider administrators must synchronize the CP internal clock to the local date and
time of Los Angeles, California. This ensures that all Vocal Reminders for this CP are announced according
to the Los Angeles, California time zone.
8.2. Automatic Internal Clock Update

Care@Home™ Analytics functionality supports GSM (4G/3G/2G) communications. The CP is connected
through its own SIM-card, using cellular communications.
The CP internal clock is automatically updated by the cellular communications processed through the CP.
8.2.1 GSM Automatic Update

The date and time of the internal clock of a GSM (4G/3G/2G) Control Panel is updated by the Cellular
Service operator.

The Control Panel updates its internal clock:

 Upon Panel Reset
 During Panel Power Up
 Every time the Control Panel sends a Periodic Test message, according to the Periodic Test
parameters
The Control Panel updates the following Date/Time components:

 Month
 Day
 Year
 Hour
 Minute
8.3. Manual Update Using the Panel Date Time Module
Figure 93: Access to the Panel Date Time Module
For the management of the Care@Home™ Control Panel (CP) internal clock, the Panel Date Time module
functionality enables manual update of the local date and time of the Care@Home™ CP

Figure 94: Manage CP Local Date Time
NOTE: Consult with Essence Professional Services personnel for more information
about the Panel Date Time module and its functionality.

Voice Announcements Module
9. Voice Announcements Module
Figure 95: Access to the Voice Announcements Module
Click the Vocal Announcements option on the Main navigator menu. The Vocal Announcements module
has a two-fold purpose:
 To allow you to configure the receipt of vocal announcements for technical, medical, and safety
issues
 To allow you to configure the Control Panel (CP) to “vocally” remind the Resident about
scheduled activities.
The vocal reminder is characterized by the following attributes:

 The purpose of the reminder announcement
 Additional information related to the purpose of the reminder
 The scheduled frequency of the reminder announcement (schedule type)
 The period of the reminder announcement
 The time of the reminder announcement
The mechanism for issuing vocal reminders includes four (4) schedule types:
 One Time: For instructions about defining a “One Time” Vocal Reminder, see section 9.2.1 on
page 93.
 Weekly: For instructions about defining a “Weekly” Vocal Reminder, see section 0 on page 94.

 Monthly (Day of the month): For instructions about defining the “Day of the Month” Vocal
Reminder, see section 9.2.3 on page 95.
 Monthly (Day of the week): For instructions about defining the “Day of the Week” Vocal
Reminder, see section 9.2.4 on page 96.
For each schedule type, you can choose the “date” and time for the reminder to be announced. The time
configuration for a reminder announcement is restricted to the hour plus one of the following 15-minute
increments:
 00 minutes – For example: 10:00

 45 minutes – For example: 10 :45
The structure of the mechanism to define a reminder includes all the parameters that define the attributes
of a Vocal Reminder. For example, Figure 96 below illustrates the structure of the mechanism to define a
Weekly Vocal Reminder.
Figure 96: Vocal Reminder Structure
Table 20 below describes the parameters that define the attributes of a Vocal Reminder.
Parameter Definition/Instructions Attributes Required Factory

/Optional Settings
(Reminder) Mark the checkbox to activate the Vocal Enable = Checked Optional Disable =
Enabled Reminder. Disable = Unchecked unchecked
Schedule Select the type of schedule you require for the Dropdown list: Required
Type Vocal Reminder.  One-Time
 Weekly
For information about each schedule type, see

Parameter Definition/Instructions Attributes Required Factory

/Optional Settings
section 9.2 on page 92.  Monthly (Day of Month)
 Monthly (Day of Week)
Report Mark the checkbox to allow the Panel to send Enable = Checked Optional Disable =
Enabled the Monitoring Station reports if a reminder was Disable = Unchecked unchecked
not acknowledged.
For more information about the reports, see
page 92.
Period: Day: The format of the date is Optional
Day and Time Enter either the day of the week, the day of the dependent on the
month, or the date when you require the schedule type.
reminder announcement. For more information, see
the description of each
schedule type in
section 9.2 on page 92.
Time: Time in hh24:mi format Required
Enter the time when you require the reminder
announcement
Days/Weeks Mark the one or more days/weeks when you Per day/week: Optional Disable =
require the reminder announcement. Enable = Checked unchecked
Disable = Unchecked
Set Default Click this button to reset to default settings. The Push Button N/A
Button Reminder structure is reset to Factory Settings,
disabled, and displayed in Grey, as illustrated in
Figure 97 below.
Time to Enter the time to add to the Vocal Reminder Time in hh24:mi format Required
Announce Announcement, to inform the Resident when
the event is scheduled.
For more information, see the sections about
Appointment Reminders and Ride Reminders.
Table 20: Vocal Reminder Parameters
Figure 97: Vocal Reminder Default Settings

There are five (5) kinds of Vocal Reminders:

 Medication: For instructions about defining a Medication Reminder, see section 9.3 on page 97.
 Appointment: For instructions about defining an Appointment Reminder, see section 9.4 on
page 99.
 Rides: For instructions about defining a Ride Reminder, see section 9.5 on page 100.
 Alarms: For instructions about defining an Alarm Reminder, see section 9.6 on page 102.
 EP Test: For instructions about defining an EP Test Reminder, see section 9.7 on page 103.
9.1. General Configuration Parameters

The Vocal Announcements module includes parameters to manage the functionality of the module.
These global parameters configure the scope of the Vocal Reminders definitions.
Figure 98: Vocal Announcements General Configuration
Table 21 below describes the instructions to configure the General parameters of the Vocal
Announcements module, as shown in Figure 98 above.

Field Definition/Instructions Attributes Required/ Factory

Optional Default
Language The language of the vocal announcements N/A Display Only English
Silence Voice Mark the checkbox to silence the voice Enable = Checked Optional Disable =
Announcements announcements. Disable = Unchecked Unchecked
Note: Enabling this option silences all vocal
announcement groups and vocal reminders.
The announcement groups and vocal
reminder parameters are removed from the
page.
Enable Groups Mark the checkboxes of the group of announcements you want to enable.
Technical – Mark the checkbox to enable Enable = Checked Optional Disable =
vocal messages about technical problems Disable = Unchecked Unchecked
such as tamper and low battery power.
Vocal Reminders– Mark the checkbox to Enable = Checked Optional Disable =
enable vocal messages for Vocal Reminders. Disable = Unchecked Unchecked
Safety Alarm– Mark the checkbox to enable Enable = Checked Optional Enable =
vocal and audio messages for safety alarms. Disable = Unchecked checked
Medical Alarm– Mark the checkbox to Enable = Checked Optional Enable =
enable vocal and audio messages about Disable = Unchecked checked
panic and emergency alarms.
Vocal Reminders: Mark the checkbox to allow the use of the Enable = Checked Optional Disable =
Enable Vocal Reminders feature. Disable = Unchecked Unchecked
Global Report Mark the checkbox to allow the broadcast of Enable = Checked Optional Enable =
Missed Reminders: events to the Monitoring Station if a Disable = Unchecked checked
Enable reminder is not acknowledged by a Resident.
A Resident is supposed to press the blinking
button on the Control Panel to
acknowledge the reminder and stop the
repetitious announcements of the reminder.
Timeout Select the timeframe for the continued Radio group: Required 15 minutes
repetition of the reminder announcements. 15 minutes or
Note: At the end of the timeframe, if the 30 minutes
Resident has not pressed , a Missed
Reminder report is sent to the Monitoring
Station, if Global Report Missed Reminders:
Enable is enabled.
Snooze Time Select the time between announcements in Dropdown list: Required 8
minutes. Values: No Repetition,
1 - 30 minutes
Table 21: Reminder Configuration Parameters
9.2. Reminder Schedule Types

The following sections describe the different schedule types of the Vocal Announcements and how to
apply the schedule types in setting up the Vocal Announcements.

 One Time: See section 9.2.1 on page 93.

 Weekly: See section 9.2.2 on page 94.
 Monthly (Day of Month): See section 9.2.3 on page 95.
 Monthly (Day of Week): See section 9.2.4 on page 96.
9.2.1 One-Time Schedule Type

For the One-Time Schedule Type:
1. Choose a specific date for the reminder to be announced.
2. Choose a specific time for the reminder to be announced.
Figure 99: One-Time Schedule Type
On the chosen date, at the time specified, the reminder is announced.
In Figure 99 above, shows the mechanisms provided:

 Enter a date manually or choose a date from the calendar mechanism.
 Enter the time manually, in <hh24:mi> format.
For example, to set a Reminder to a specific date, January 14, 2015 at 10:30,
1. Use the calendar mechanism to select the date you require. The calendar mechanism closes and the
date changes to “14-01-2015”.
For information about using the calendar mechanism, see section 9.2.1.1 below.

2. Position the cursor on the “hour” part of the time field and enter “10”.
3. Position the cursor on the “minute” part of the time field and enter “30”.
9.2.1.1 The Calendar Mechanism

Figure 99 above illustrates the various tools provided by the calendar mechanism to aid you in choosing
the date you require.
 To select the year you require,
 Click the space immediately to the right of the Year. “Up and Down Arrows” are displayed.
 Scroll back and forth, using the “Up and Down Arrows”, to locate the year required.
 To locate an earlier month, scroll backwards through the months in the year, using the “Arrow”,
to the left of the Month.
 To locate a later month, scroll forwards through the months in the year, using the “Arrow”, to
the right of the Month.
 To select the day of the month you require, click the number within the dropdown calendar,
such as the circled day in the example.
To select the current date, click the red circle at the bottom of the dropdown calendar next to Today, as
shown in Figure 99 above.
9.2.2 Weekly Schedule Type

For the Weekly Schedule Type:
2. Choose one or more days of the week when the reminder is to be announced.
Figure 100: Weekly Schedule Type

Every week, on the chosen day or days of the week, at the time specified, the reminder is announced.
Figure 100 above shows the mechanisms provided:

 Enter the time for the announcement, in <hh24:mi> format, using the “Up and Down Arrows”.
 Mark the checkboxes to the left of the day or days, of the week, for the reminder to be
announced.
For example, as shown in Figure 100 above, to set a Reminder to make an announcement at 14:00, on
Sunday, Monday, Wednesday, and Friday:
1. Position the cursor on the “hour” part of the time field and select “14”, using the “Up and Down
Arrows”.
2. Position the cursor on the “minute” part of the time field and select “00”, using the “Up and Down
Arrows”.
3. Mark the checkboxes to the left of the following days:
 Sunday
 Monday
 Wednesday
 Friday
9.2.3 Day of the Month Schedule Type

For the Monthly (Day of Month) Schedule Type:
1. Choose a specific day of a month for the reminder to be announced.
Figure 101: Day of Month Schedule Type

Every month, on the chosen day, at the time specified, the reminder is announced.
Figure 101 above shows the mechanism provided:

 Select the “day” in a month, only be between 1 and 28, using the “Up and Down Arrows”.
 Enter the time, in <hh24:mi> format, using the “Up and Down Arrows”.
For example, as shown in Figure 101 above, to set a Reminder to make an announcement at 09:30, on the
23rd day of each month:
1. Position the cursor on the “day” part of the date and time field and select “23”, using the “Up and Down
Arrows”.
Arrows”.
Arrows”.
9.2.4 Day of Week Schedule Type
For the Monthly (Day of Week) Schedule Type:

1. Choose a day of the week for the reminder to be announced.
3. Choose the week or weeks of the month for the reminder to be announced
Figure 102: Day of Week Schedule Type

Every month, during the chosen week or weeks, on the chosen day of the week, at the time specified, the
reminder is announced.
Figure 102 above shows the mechanisms provided:
 Select the “day” in the week and scroll to the day required, using the “Up and Down Arrows”.
 Enter the time, in <hh24:mi> format, using the “Up and Down Arrows”.
 Mark the checkbox to the left of the week or weeks in the month, for the reminder to be
announced.
The Last checkbox refers to the last week of a month, specifically for months with more than four
(4) weeks.
For example, as shown in Figure 102 above, to set a Reminder to make an announcement at 11:15, on
Tuesday of the first four (4) weeks of each month:
1. Position the cursor on the “day of the week” part of the date and time field and select “Tues”, using the
“Up and Down Arrows”.
Arrows”.
Arrows”.
4. Mark the checkboxes to the left of the following weeks:
 1
 2
 3
 4
9.3. Medication Reminders
The Vocal Announcements module allows you to define up to four (4) scheduled Medication Reminders.
The reminders are identified by the labels: MI1 – MI4
The purpose of the Medication Reminders is to broadcast vocal announcements through the Control
Panel to remind the Residents to take their medication.

The text of the message is:
"Attention! It is time to take your medication. Please take them and press the Reset button"
To acknowledge the reminder, the Resident must press the blinking button on the Control Panel
within the configured Timeout timeframe. If the resident does not press the button before the
Timeout timeframe ends, a Missed Reminder Report is sent to the Monitoring Station, if the Report
feature is enabled.
For information about configuring the Timeout parameter, see page 92.
Figure 103 below shows the Medication Reminders Tab.
Figure 103: Medications Reminders Tab
For information and instructions about using the Reminder Schedule Types, see section 9.2 on page 92.

9.4. Appointment Reminders
The Vocal Announcements module allows you to define up to four (4) scheduled Appointment
Reminders.
The purpose of the Appointment Reminders is to broadcast vocal announcements through the Control
Panel to remind the Residents to prepare for their appointments.
Each reminder is defined with an additional parameter: Time to Announce.
This time parameter is added to the text of the vocal announcement to remind the Resident of the
scheduled time of the appointment.
The text of the message is:
"Attention! Your appointment is at <time to announce>. Please press the Reset button."
feature is enabled.
Figure 104 below shows the Appointments Announcements Tab.

Figure 104: Appointments Reminders Tab
9.5. Ride Reminders
The Vocal Announcements module allows you to define up to four (4) scheduled Ride Reminders.
The purpose of the Ride Reminders is to broadcast vocal announcements through the Control Panel to
remind the Residents to prepare for their rides.
Each reminder is defined with an additional parameter: Time to Announce.

This time parameter is added to the text of the vocal announcement to remind the Resident of the
scheduled time of the ride.

The text of the announcement is:
"Attention! Your ride will arrive at <time to announce>. Please press the Reset button."
feature is enabled.
Figure 105 below shows the Rides Reminders Tab.
Figure 105: Rides Reminders Tab

9.6. Alarm Reminders
The Vocal Announcements module allows you to define up to four (4) scheduled Alarm Reminders.
The purpose of the Alarm Reminders is to use the Control Panel as an Alarm Clock to remind the
Residents of scheduled times, such as when to wake up in the morning or when to wake up from their
other rest periods.
"Attention! Alarm reminder. Please press the Reset button."
feature is enabled.
Figure 106 below shows the Alarms Reminders Tab.

Figure 106: Alarms Reminders Tab
9.7. EP Test Reminder
The Vocal Announcements module allows the Operator to define one (1) scheduled EP Test Reminder.
The reminder is identified by the label: MI17
The purpose of the EP Test Reminder is to broadcast vocal announcements through the Control Panel to
remind the Resident to perform a test of their personal panic button.
"Attention! It is time to test your pendant. Please press your pendant button."

To acknowledge the reminder, the Resident must press the Pendant button within the configured
Timeout timeframe. If the resident does not press the Pendant button before the Timeout timeframe
ends, a Missed Reminder Report is sent to the Monitoring Station, if the Report feature is enabled.
Figure 107 below shows the EP Test Reminder Tab.
Figure 107: EP Test Reminder Tab

Mobile Operators
10. Mobile Operators
Figure 108: Access to the Mobile Operators Module
Click the Mobile Operators option on the Main navigator menu. The Mobile Operators module is the tool
that allows management of the Mobile Operators APN information for the Care@Home™ CMS software
application installed on the customer premises.
Figure 109: The Mobile Operators Module

Mobile Operators
10.1. APN Information
Access Point Name (APN) information provides access to the cellular external communications channel.
This information is provided by your SIM-card’s Cellular Operator or your Service Provider.
You should call your cellular Service Provider and obtain all the following relevant APN data:
 APN Name
 User name
 Password
Table 22 below provides instructions for entering the APN information for each Mobile Operator.
Field Definition and Instructions Attributes Required/ Default

Optional Value
ID Automatic allocation of an internal identification N/A Required Display
code for each Mobile Operator. Only
Mobile Operator Code Enter the code issued by the MCC or the MNC for the Integer (6) Required
Mobile Operator.
APN Enter the Access Point Name (APN) name from your Internet URL Required
SIM-card Cellular Operator. or address
User Enter the APN user name. Characters Required
Password Enter the APN password. Characters Required
Table 22: Mobile Operators APN Information

Mobile Operators
10.2.Managing the Mobile Operator List

The Mobile Operators module allows the End-User to manage the APN information for a list of Mobile
Operators. The Mobile Operators module supports APN information for up to 10 Mobile Operators.
The module provides you with the capability to perform the following functions:
 Add – To add a new Mobile Operator in a blank row in the list of Mobile Operators.
 Update – To update a row with an existing Mobile Operator.
 Delete – To delete a row from the Mobile Operator list with an existing Mobile Operator.
10.2.1 Add a Mobile Operator

The Update function allows you to Add a new mobile operator by updating an empty row.
1. Select an empty row from 1-10 in the Mobile Operator list window.
2. Enter the destination information in the fields to the right of the Mobile Operator list window:
 Mobile Operator Code
 APN
 User
 Password
3. Right click your mouse positioned on the row in the Mobile Operator list selected in Step 1. A
function window appears displaying the functions available to manage the Mobile Operator list, as in
Figure 110 below.
Figure 110: Manually Add Mobile Operator

Mobile Operators
4. Click the Update function in the function window or click at the bottom of the screen, as
illustrated in Figure 110 above, to add the new Mobile Operator to the Mobile Operator list. The
selected row is populated with the information entered in Step 2.
10.2.2 Update a Mobile Operator

The Update function allows the End-User to revise an existing destination in the Mobile Operator list.
1. Select a row in the Mobile Operator list window with an existing destination.
2. Revise the APN information in the fields to the right of the Mobile Operator list window:
 Mobile Operator Code
 APN
 User
 Password
3. Place the cursor on the row, in the Mobile Operator list window, selected in Step 1.
4. Right click on the mouse. A function window appears displaying the functions available to manage
the Mobile Operator list, as illustrated in Figure 110 on page 107.
5. Click the Update function in the function window or click at the bottom of the screen, as
illustrated in Figure 110 on page 107 above, to revise the APN information for an existing Mobile
Operator to the Mobile Operator list. The selected row is populated with the information entered in
Step 2.
Figure 111: Manually Delete Mobile Operator

Mobile Operators
10.2.3 Delete a Mobile Operator

The Delete function allows the user to remove an existing Mobile Operator from the Mobile Operator list.
1. Place the cursor on the row, in the Mobile Operator list window, that is to be removed from the
Mobile Operator list
2. Right click on the mouse. A function window appears displaying the functions available to manage
the Destination list, as in Figure 111 above.
3. Click the Delete function in the function window or click at the bottom of the screen, as
illustrated in Figure 112 below, to remove an existing Mobile Operator from the Mobile Operator list.
A window appears prompting the End-User to confirm the delete request.
Figure 112: Confirm Delete Destination

Mobile Operators
10.3. Load APN Information

APN information is located externally in a .cpf file.
You can upload the APN information automatically from another .cpf file by using the
button. The APN information is loaded directly into the Mobile Operators module, as illustrated in Figure
113 below.
Figure 113: Upload APN Information
To load APN information from an external file, perform the following procedure:
1. Enter the Mobile Operators module in the Care@Home™ CMS application.
2. Click the button, as shown in Figure 109 on page 105. An Open CMS File browser
window appears, as shown in Figure 114 below.
Figure 114: CMS File Browser

Mobile Operators
3. Click the .cpf file that includes the APN information.
4. Click to load the APN information from the .cpf file into the Mobile Operators module.
The Mobile Operators list displays the updated APN information, as illustrated in Figure 113 on page 110
above.
NOTE: Only APN information is uploaded from the selected external .cpf file into the
CMS application.
5. To save the APN information:

 Download the CMS information to the Control Panel (CP).
 Save the CMS information to a CMS parameter file (.cpf).
Use the Main Action icons as described in section 3.2 on page 32.

The Custom Labels Module
11. The Custom Labels Module
Figure 115: Access to the Custom Labels Module
Click the Custom Labels option on the Main navigator menu. The Custom Labels module is the tool that
allows management of the personalized labels for the Care@Home™ CMS software application installed on
the customer premises.
Figure 116: The Custom Labels Module

The Custom Labels Module
11.1. Defining Custom Labels
Figure 117: Custom Label Definition
Table 23 below describes the parameters needed to define the personalized labels to the CMS application.

Optional Value
Label Id Choose a number to identify each label in the Dropdown List Required None
Custom Label list. Values: 1-50
To view the Custom Label list, see Figure 116
on page 112.
Encoding Choose the encoding character set with Dropdown list Required Latin-1
which to enter the personalized text for the
custom label.
Label Text Enter free form text, using the character set Up to 31 A/N Required None
chosen in the previous field. characters
Table 23: Custom Label Definition Parameters
Click to add the personalized label information to the Custom Label list. The update process
adds the custom labels to the dropdown list for the following parameters in other modules:
 The Zone Label parameter in the Activity Sensors module
 The RF Input Label parameter in the Safety and SOS module

The Log Events Module
12. The Log Events Module
Figure 118: Access to the Log Events Module
Click the Log Events option on the Main navigator menu. The Log Events module is the tool that allows
management of the event log files for the Care@Home™ Control Panel (CP) installed on the customer
premises.
Figure 119: Log Events Module

The Care@Home™ system provides the ability to capture and read a CP event log file (.lgf file). Essence
Professional Support personnel use the log file to analyzing system behaviors and malfunctions.
12.1. Log Events Module Actions

The log files are stored in the CP. The Log Events module action buttons allow the user to view, store,
print, or reinitialize the events log file in the CP.
Figure 120: Log Events Module Action Buttons
12.2. Number of Events

The Number of Events parameter allows the user to enter the number of records to retrieve from the CP
cyclical event log file. The records retrieved are the last events recorded by the log file.
For example, if the user enters “5” and clicks the button, the last five (5) recorded events are
displayed.
The log file can store up to 945 event records. Since the log file is cyclical, these records are of the last 945
events recorded by the CP and its peripheral devices.
12.3. Read Log

Click the button to retrieve the number of records entered in the Number of Events
parameter. The records are retrieved from the CP event log file in “Last In First Out” (LIFO) order. The
records are displayed in the Log Events main page in “descending order” by the date and time the event
was reported.
For example, Figure 119, on page 114, shows the records displayed on the Log Events main page in
“descending order”.

12.4.Reset Log
Click the button to empty the current CP event log file. You are prompted to confirm the
reset log request, as in Figure 121 below.
The contents in the CP event log file are deleted. The event log file is ready to log new CP events, issued by
the CP, the sensors, and other peripheral devices connected to the CP.
Figure 121: Reset Log Confirm Prompt
12.5. Save Log

Click the button to create an external copy of the retrieved records from the event log file in
the CP. The records displayed on the Log Events screen are saved to an external file.
A Windows Save Log dialog box appears, as shown in Figure 122 below, to allow the user to specify the log
file name with the extension .lgf and the location to store the log file on the local personal computer (PC).
Figure 122: Save Log window

NOTE: Use the Save Log feature to create the external .lgf file, when requested by
the Essence Professional Service personnel to send them the CP events log file.
12.6. Open Log

Click the button to open the Windows Open Log dialog box, as shown in Figure 123 below, to
locate an event log file on the local PC, “open” it, and display its contents on the Log Events page.
For example, Figure 124 below shows the records in the event log file, retrieved in Figure 123 below,
displayed on the Log Events page.
Figure 123: Open Log window
Figure 124: Log File opened on the Log Events Screen

12.7. Print Log…

Click the button to open the Print Log window, as shown in Figure 125 below, to allow the
user to choose whether to produce an Excel file, a .csv file, or a hardcopy of the event log file.
Figure 125: Print window for Print Log function
The log file is formatted in Windows EXCEL to properly view and understand the event log records.
For example, Figure 126 below shows an event log file formatted and printed as an Excel file.
Figure 126: Print Log Function Results

Care@Home™ CMS Implementation
13. Care@Home™ CMS Implementation
The Care@Home™ system is assembled by the manufacturer according to a pre-defined default

configuration:
 One Control Panel (CP)
 Five (5) Motion Detectors (PIRs)
 Two (2) Magnetic Motion Detector (MGLS)
The Care@Home™ CP is initialized with the default factory settings for the control panel configuration
parameter values. For example, the account number should be set for the account number assigned to
the customer for whom the Care@Home™ system is allocated.
The default peripheral devices are defined in the Care@Home™ CP as Activity Sensors. Each of these
peripheral devices is assigned a Dialer Destination ID, an IP address and other Dialer information for
communication with the Care@Home™ server.
Optional peripheral devices can be added to the configuration to provide additional capabilities to the
Care@Home™ system, such as
 The Camera option (IPD) for a Motion Detector (PIR)
 Safety devices (the Smoke Detector (SK2) or the Water Detector (MGLS))
 Emergency devices (the Panic Button (EP) or the Stationery Emergency button (SPB))
The default configuration of the Care@Home™ system is flexible and allows for expansion. The
Care@Home™ system can accept additional peripheral devices as needed.
The Care@Home™ CMS software application provides the user interface to verify that the Care@Home™
system has been pre-defined according to the customer’s needs. The CMS software application has the
tools to modify and re-define the configuration parameter values of the CP and its peripherals, as needed.
These tools allow the user to define additional peripheral devices to the Care@Home™ system, as needed.

To maintain the Care@Home™ CP configuration parameters, the user must first upload the CPs default
factory settings (configuration parameter values) to the Care@Home™ CMS software application. Then,
the user can use the tools provided by the Care@Home™ CMS software application to maintain the
configuration parameter, as needed.
13.1. Load the Factory Settings

The factory settings are defined in the Care@Home™ Control Panel (CP).provided by the manufacturer.
The CP configuration parameter values must be uploaded to the Care@Home™ CMS software application,
before the user can verify that the factory settings are correct.
13.1.1 Upload the Factory Settings

To upload the factory settings, perform the following procedure:
1. Open the Care@Home™ CMS software application. For information on opening the CMS software
application and using the user interface, see chapter 3 on page 31.
2. Connect to the Care@Home™ CP to the Care@Home™ CMS software application.
For information on connecting to the Care@Home™ CP, see section 2.6 on page 16.
3. Choose the COM Port as described in section 2.3 on page 13.
5. Click the button to upload the factory settings for the CP configuration parameter to
the CMS application.
See Table 4, on page 26, for more information about uploading the CP configuration parameter
values.
13.2. Verify the Factory Settings
Following the upload of the Care@Home™ CP configuration parameter values, the Care@Home™ CMS
software application is prepared for the user to verify that the factory settings are defined correctly in the
CP.

Figure 127: Factory Settings in CP Module
The user can view the factory settings of the CP in the Control Panel module of the Care@Home™ CMS
software application. Figure 127 above shows the Control Panel module of the Care@Home™ CMS
software application displaying an example of the factory settings of the CP.
For information about the Control Panel module, see chapter 4 on page 39.
Click the button, at the bottom of the page, upon completion of any modifications made in
this module.
13.2.1 Account Number

The CP Account Number should be set to the account number assigned to the customer for whom the
Care@Home™ system is allocated.
Verify that value displayed in the Account Number parameter is the account number assigned to the
customer. If not, modify the value in the parameter field accordingly.
For information about the Account Number, see section 4.1.2 on page 41.

13.2.2 APN Settings

The CP configuration parameters must include at least one Mobile Operator in the Mobile Operator
module. This Mobile Operator should be the cellular service for the SIM card used by the CP.
The cellular service for the SIM card inserted in the Control Panel determines the APN information
required.
Click the Transmitter (GSM) button to access the APN settings. Figure 128 below shows the
settings for the cellular service provider including the APN settings.
For information about the Transmitter (GSM) parameters and the APN settings, see section 4.1.4 on page
44.
Figure 128: SIM Card APN Information
The purpose of the Mobile Operators module is to provide the APN information for the chosen cellular
service. For example, Figure 129 below shows the APN information in the Mobile Operators module
needed for the cellular service used by the SIM card shown in Figure 128 above. The CP automatically
retrieves the APN information associated with the cellular service used by the SIM card.
Figure 129: Mobile Operators APN Information

For information about the Mobile Operators module, see chapter 10 on page 105.
13.2.3 Customize CP Configuration

The CP configuration covers all aspects of the Control Panel functionality for itself and for its peripheral
devices. The CP module, as in Figure 127 on page 121, allows the user to customize the capabilities of the CP
functionality according to the user’s needs.
For example, the user may want the siren on the premises to sound for a specific duration before the CP
contacts the Emergency call center.
Figure 130: The Internal Siren Duration
Figure 130 above shows the Sound fields that manage the siren on the premises. Modify the number of
seconds for the siren to sound the alarm.
For information about the Sound parameters, see section 4.1.6 on page 48.
Another example of customizing the CP configuration is redefining the number of rings the CP waits
before automatically answering a call from the Emergency call center.
Figure 131: Remote Call-In Rings

Figure 131 above shows the Remote Call-In fields that manage the receipt of external phone calls from the
Emergency call-center.
Choose the number of rings, from the dropdown list, for the CP to wait until automatically answering
external calls to the CP.
For information about the Remote Call In parameters, see section 4.1.5 on page 47.
NOTE: Remember to click the button, at the bottom of the Control Panel
module page, upon completion of any modifications made in this module.
13.3. Additional Configuration
If the Care@Home™ system installation includes additional peripheral devices, the user must verify that the
additional peripheral devices are pre-defined in the Care@Home™ CP.
If the Care@Home™ system installation includes optional peripheral devices to provide additional
capabilities (such as safety or emergency monitoring), the user must verify that the additional peripheral
devices are pre-defined in the Care@Home™ CP.
The user can use the Care@Home™ CMS software application to define all additional peripheral devices,
where needed, in the Care@Home™ (CP). The CMS software application includes dedicated modules for
this purpose.
13.3.1 Dialer Module
As part of the factory settings, the manufacturer assigns the ports and the Default Server’s IP address to
each of the communication channels. This is to insure that the Control Panel (CP) communicates
appropriately with the Default Server.

The CMS Dialer Module provides the user with the tools to maintain these settings for communications
with the CP. The ports and IP addresses along with other Dialer Destination information can be viewed and
verified in the Dialer Module.
Figure 132: Factory Settings in the Dialer Module
For example, Figure 132 above shows the factory settings for the communication channels included in a
Care@Home™ system configuration. Each communication channel is assigned Dialer Destination
information, such as:
 Destination ID
 IP Address for the Default Server
 Port
 Comm Type
 Comm Channel
For information about the Dialer Module and its functionality, see chapter 5 on page 56.
The user can maintain the destination information for each destination in the Destination list using the
tools provided in the Dialer Module.

NOTE: Click the button, to the bottom right of the Destination list, to
save the changes made to each line in the Destination list.
The following are examples for maintaining Dialer Destination information.
13.3.1.1 Altering IP Addresses

Although the port assignments should remain unchanged, the IP addresses associated with the ports can
be altered. Altering the IP addresses is only necessary if the Default Server is replaced by another Server
and Network.
NOTE: Do not change the port assignments without first consulting Essence
technical support personnel.
13.3.1.2 Add Dialer Destinations

Additional Dialer Destinations can be added to the Dialer module.
For example, an additional server can be configured if the user wanted to provide a Backup Server in the
event the Default Server fails to respond. The communication channels associated with an additional
Server must be added to the Dialer Destination list.
In this case, the user can use the tools provided in the Dialer module to add new destinations to the Dialer
Destination list.
13.3.1.3 Edit Dialer Information

Only the information for a communication channel assigned to the “Analytics Message” Comm Type
includes an Emergency call number. This is the number the CP calls when the Emergency Call button on
the CP is pressed.
For example, the user should verify that a valid Emergency call number is defined for the “Analytics
Message” Comm Type.

If no Emergency call number is defined for the “Analytics Message” Comm Type or the Emergency call
number defined is invalid, the user should re-define the Emergency call number.
In this case, the user can use the tools provided in the Dialer module to edit existing destinations in the
Dialer Destination list.
For information about maintaining the Dialer Destinations, see section 5.2 on page 62.
13.3.1.4 Re-defining Dial Sequence Retries

The factory settings include defining the dialing sequences for each Comm Type. The Dialer module
provides the tools to redefine the Dial Sequence parameters for each Comm Type. For example, the Dial
Sequence parameters include the number of retries when attempting to communicate with a Comm Type.
Figure 133: Re-define Number of Retries
Figure 133 above shows the tool for re-defining the parameters for the Dial Sequences for each Comm
Type.
Choose a number from the dropdown list to re-define the number of retries allowed to communicate
through a Comm Type. Click the button to save the modification.
For information about maintaining the dialing sequences, see section 5.3 on page 62.

13.3.2 Activity Sensors Module
As part of the factory settings, the manufacturer defines each of the peripheral devices in the
Care@Home™ system configuration as Activity Sensors. Each peripheral device is defined according to the
role the device is to play in the Care@Home™ system.
The CMS Activity Sensors module provides the user with the tools to maintain the definitions and
characteristics of each of the CP’s peripheral devices. The Activity Sensor definitions and characteristics
information can be viewed and verified in the Activity Sensors module.
Figure 134: Activity Sensors Module
For example, Figure 134 above shows the factory settings for the peripheral devices included in a
Care@Home™ system configuration. Each peripheral device is defined as an Activity Sensor. The
definitions and characteristics information defined for each peripheral device determines the device’s
purpose or role in the Care@Home™ system configuration.

The definitions and characteristics are displayed in the parameters, such as:
 Device ID
 Serial Number
 Device Type
 Activity Type
For information about the Activity Sensors module and its functionality, see chapter 6 on page 67.
The user can maintain the definitions and characteristics information for each Activity Sensor in the
Activity Sensor list using the tools provided in the Activity Sensors module.
The following are examples for maintaining Activity Sensor information.
13.3.2.1 Adding Activity Sensors

Additional Activity Sensors can be added in the Activity Sensors module.
For example:
 The user may require additional peripheral devices in other rooms on the premises.
 Additional peripheral devices are added to the Dialer module as new Dialer Destinations. These
peripheral devices must be defined as Activity Sensors in the Activity Sensors module.
 An optional Camera (IPD) device is installed as part of the Care@Home™ system configuration
In this case, the user can use the tools provided in the Activity Sensors module to add new Activity
Sensors to the Activity Sensors list.
13.3.2.2 Altering the Activity Type

The default Care@Home™ system configuration is comprised of two (2) MGLS devices and five (5) PIR
devices. Each device is pre-defined for its Activity Type, which determines the purpose of the device and
where the device is installed.

NOTE: Do not change the activity type definitions of the Activity Sensors without
first consulting Essence technical support personnel.
If the addition of devices to the Care@Home™ system configuration changes a device’s role or purpose,
the Activity Type for that device must be re-defined.
If a camera (IPD) device (s) is added to the Care@Home™ system configuration, the characteristics of the
PIR devices can be revised to enable the camera option. When the camera option is enabled, the IPD
photographs events when the PIR detects motion.
In Figure 135 on page 131, the user can choose the device identification number for the IPD that is to be
triggered:
 First Priority IPD
 Second Priority IPD
Choosing “NONE” disables the camera option for the device.
See page 69 for instructions about enabling the camera option.
In these cases, the user can use the tools provided in the Activity Sensors module to edit the existing
Activity Sensors in the Activity Sensors list.
13.3.2.3 Resetting the Send Detections Capability

Characteristics of a device can be altered. Characteristics are defined by the parameter fields to the right
of the Activity Sensor list.
For example, it is important to set the characteristic parameter that determines whether or not to send
detections from a device to the Server.

Figure 135: Device Characteristic Parameters
Mark the Send Detections checkbox to enable sending detections from the device to the Server. Click the
Update button to save the revision.
For information about maintaining the Activity Sensors, see section 6.2 on page 70.
NOTE: Click the button, at the bottom of the Activity Sensors module
page, to save the changes made to each line in the Activity Sensors list.
13.3.2.4 Configuring a Camera Device
If a camera device (IPD) is added to the Care@Home™ system configuration, the user must not only define
the IPD device in both the Dialer module and the Activity Sensors module but also configure the IPD
device to be triggered automatically by specific events or other triggers that occur in the Care@Home™
system.

The tool for configuring an IPD device is in the Photo Configuration tab of the More Options window of
the Control Panel module.
Figure 136: Photo Configuration
The user must mark the SOS checkbox to automatically trigger the IPD device when the Emergency
button is pressed. The user can mark the Alarm checkbox to automatically trigger the IPD device when
the Alarm is sounded.
Click the button to save the changes.
For information about configuring a camera device, see section 4.1.7.1 on page 50.
13.3.3 Safety and SOS Module
The default Care@Home™ system configuration does not include safety and emergency devices. If the
user decides to add safety devices or emergency devices or both as part of the customer’s Care@Home™
system configuration, the manufacturer will include the definition of these devices in the factory settings.
The devices are defined as safety or emergency devices in the CMS Safety and SOS module. The Safety
and SOS definitions and characteristics information can be viewed and verified in the Safety and SOS
module.

Figure 137: Safety and SOS Module
Figure 137 above shows the safety and SOS devices defined in the Safety and SOS module. To the right of
the list of safety and SOS devices, the user can find the definitions and characteristics for each of the safety
and SOS devices.
For information about the Safety and SOS module and its functionality, see chapter 7 on page 75.
The Safety and SOS module provides the tools for user to maintain the safety and emergency devices.
For information about maintaining the safety and emergency devices, see section 7.3 on page 80.
13.3.4 Log Events Module

The purpose of the Log Events module is to allow the user to view the log of events that occurred during
the current session of the Care@Home™ system.
If an error occurs in the Control Panel (CP), the user can retrieve information from the events log file that
may be able to explain the error and aid in recovery and solving the problem.
The user can:
 Download the log file from the CP (Read Log)
 Display the log file (Read Log).
 Save the log file to an external file in a readable format (Save Log)
For information about the Log Events module and its functionality, see chapter 12 on page 114.

Software Updates
14. Software Updates
Software and firmware updates for the Control Panel and its peripherals are performed by the Remote
Boot Feature.
14.1. The Remote Boot Feature

The Remote Boot feature allows the management of the CP, the voice announcements, and the CP
software and peripheral firmware updates.
14.1.1 Launching the Remote Boot Feature
To launch the Remote Boot feature, perform the following procedure:
1. Click the Care@Home™ CMS icon. The Care@Home™ CMS software application opens the home
page. The Connect window automatically appears, as shown in Figure 8 on page 15.
2. Select the Remote Boot Protocol option.
3. Select the COM port according the connection method.
4. Click the button at the bottom of the Connect window.

Following the successful completion of the connection procedure, the Remote Boot window
appears, as shown in Figure 138 on page 135.
14.1.2 Remote Boot Setup

The Remote Boot setup is required to prepare for the software and firmware updates.
The Remote Boot Setup includes:
 Setting the Boot Options
 Selecting the update (.esi) file

Software Updates
Figure 138: The Remote Boot Window
The following are the Boot Options:

 Verify – If the checkbox is marked, the CP automatically verifies that the software/firmware
(.esi) file transfer completed successfully.
 Automatic Firmware Update – If the checkbox is marked, the CP automatically performs the
software/firmware update.
 Target – Allows you to specify the target device for which the Remote Boot feature is to update
the firmware.
Table 24 below lists the target devices and their usage instructions.
Target Device Usage

Main CPU Choose this option to upgrade the CP software.
SK2 CPU Choose this option to upgrade the smoke detection peripheral device.
EP CPU Choose this option to upgrade the portable panic button.
SPB CPU Choose this option to upgrade the stationary panic button.
Voice File Choose this option to update the recording of the voice announcements.
Table 24: Target Devices

Software Updates
Following the definition of the Boot Options, use the button to locate and select the
update file.
14.1.3 The Software/Firmware Update Procedure

Perform the following procedure to run the software and firmware updates. Use Figure 138, on page 135, as
a reference to the Remote Boot window.
1. Define the Boot Options, located on the right-side of the Remote Boot window.
2. Click the button, located on the left-side of the Remote Boot window. The Open
ESI File window appears, as in Figure 139 below.
Figure 139: Open ESI File Window
3. Using the browser, select the update (.esi) file for the target device chosen in the Boot Option setup.
The file details appear in the Details box at the bottom of the Remote Boot window, as in
4. Verify that the selected .esi file is the file, received from the PSO team, for the target device.

Software Updates
Figure 140: ESI File Details
5. Click the Start Download button. The application verifies that the .esi file is the file for the target
device.
If the file is not for the target device, the download process aborts and an error message appears, as
in Figure 141 below.
Figure 141: Wrong ESI File

Software Updates
6. If the file is for the target device, the update download process begins.
Information about the progress of the download process appears in the View System Log box and in
the Details box, as in Figure 142 below. Note that there is a progress bar at the bottom of the window.
Figure 142: Download Process Details
The information displayed includes:
 File Name - The name of update file

 File Size – The amount of data to be transferred
 Sending – The amount of data transferred
 Time Left – The estimated time remaining
 Speed (bps) – The data transfer rate

Software Updates
If you need to abort the update process, click the Stop button. The update process aborts and an
error message appears, as in Figure 143 below.
Figure 143: Download Process Aborted
To restart the update process:
1. Click the Exit button

2. Disconnect from the Control Panel
3. Re-connect to the Control Panel.
4. Launch the Remote Boot feature
5. Click the Start Download button.
When the update process ends, Success confirmation appears along with the information displayed
in both the View System Log box and in the Details box, as in Figure 144 below.

Software Updates
Figure 144: Download Process Ends
The CMS automatically disconnects from the Control Panel and issues the message in Figure 145
below.
Figure 145: Panel Disconnect Message
Table 25 below summarizes the functionality of the Remote Boot action buttons and boxes.
Required or Default
Optional Value
Select the file for the target device. A browser dialog window appears
to allow location and selection (‘open’) of the relevant update file (.esi Optional Enabled
file).
Click the button to perform the update file transfer and update the
Optional Disabled
software/firmware, according to the Boot Options.

Software Updates
Required or Default
Optional Value
Click this button to manually initiate the software/firmware update. Optional Disabled
Click this button to verify that the existing software for the Main CPU
updated successfully. Optional Disabled
NOTE: This button is enabled only when the Main CPU is selected.
Click this button to stop the Remote Boot process. Optional Disabled
Click this button to exit the Remote Boot window. Optional Enabled
Displays the system messages and the error messages issued during the
View System Log N/A Display Only
Remote Boot processing.
When a file is selected, the details of the file selected appear in this
Details N/A Display Only
field.
Table 25: The Remote Boot Parameters

Terms, Abbreviations and Acronyms
Appendix A Terms, Abbreviations and Acronyms
Term Description
3G 3G is a short for 3rd Generation.
This is a term used to represent the 3rd generation of mobile telecommunications
technology.
AES Advanced Encryption Standard.
A specification for the encryption of electronic data in a symmetric-key encryption
format based on a design principle known as a substitution-permutation network, and is
fast in both software and hardware.
API Application Programming Interface.
APN Access Point Name.
The name of a gateway between a GPRS (or 3G, etc.) mobile network and another
computer network, frequently the public Internet.
ASP Active Server Pages.
Microsoft's first server-side script engine for dynamically generated web pages.
CP An Essence Term.
Control Panel.
DIY Do-It-Yourself
DMZ Demilitarized Zone.
In computer security, a DMZ is a physical or logical sub-network that contains and
exposes an organization's external-facing services to a larger and untrusted network,
usually the Internet. The purpose of a DMZ is to add an additional layer of security to an
organization's local area network (LAN).
ECS An Essence Term.
Essence Connect Server.
FCC Federal Communications Commission.
An institute that regulates interstate (USA) and international communications via radio.
FL An Essence Term.
A Flood Detector peripheral device.
FTP File Transfer Protocol.
A standard network protocol used to transfer files from one host to another host over a
TCP-based network, such as the Internet.
GPRS General Packet Radio Service.
A packet oriented mobile data service on the 2G and 3G cellular communication system's
global system for mobile communications (GSM).

Term Description
GSM Global System for Mobile Communications.
A standard set developed by the European Telecommunications Standards Institute
(ETSI).
The GSM standard describes protocols developed for second generation (2G) digital
cellular networks which are used by mobile phones.
IPD An Essence Term.
A Motion Indoor Photo Detector peripheral device. Also referred to as Camera.
KF An Essence Term.
A Key Fob peripheral device.
LSU An Essence Term.
Local Software Update.
MGL/MGLS An Essence Term.
An Indoor Magnetic Sensor peripheral device.
OS Operating System.
Software that manages computers’ basic functions.
PIR An Essence Term.
A Motion Detector peripheral device.
RF Radio Frequency.
RFID Radio-Frequency Identification.
A wireless, non-contact system using radio signals to transfer data from a tag attached to
an object for automatic identification.
RIA Rich Internet Application.
Web application with many characteristics of desktop application software.
Typically delivered by way of a site-specific browser, a browser plug-in, an independent
sandbox, extensive use of JavaScript, or a virtual machine.
RSU Remote Software Update
SHA-1 Secure Hash Algorithm.
In cryptography, SHA-1 is a cryptographic hash function designed by the US National
Security Agency and published by the US NIST as a U.S. Federal Information Processing
Standard.
SIM A small card placed in a mobile phone in order to identify the phone to the cellular
carrier.
SK2 An Essence Term.
A Smoke Detector peripheral device.
SMPP Short Message Peer-to-Peer.
An open, industry standard protocol designed to provide a flexible data communication
interface for the transfer of short message data between External Short Messaging
Entities (ESME), Routing Entities (RE) and Message Centers.
SMS A text message on a mobile device.

Term Description
SMSC Short Message Service Center.
A cellular operator’s infrastructure for sending/receiving SMS messages.
When sending SMS messages, the user may connect directly to a provider’s
infrastructure for this purpose.
SMTP Simple Mail Transfer Protocol.
An Internet standard for email transmission.
SOAP Simple Object Access Protocol.
A protocol specification created for exchanging structured information in the
implementation of Web Services in computer networks.
SRN An Essence Term.
An Indoor Siren peripheral device.
SSL Secure Sockets Layer.
A protocol that provides secure communication over the Internet.
STUN Session Traversal Utilities for NAT.
STUN is a standardized set of methods and a network protocol to allow an end host to
discover its public IP address if it is located behind a NAT.
STUN is used to permit NAT traversal for applications of real-time voice, video,
messaging, and other interactive IP communications.
STUN is documented in RFC 5389. STUN is intended to be a tool to be used by other
protocols, such as ICE.
Telnet Telnet is a network protocol that allows users to log into other computers on the same
network.
TR5 An Essence Term.
A Tag Reader wireless access control peripheral device.
UT An Essence Term.
A Universal Transmitter peripheral device.
VPN Virtual Private Network.
VPN extends a private network across a public network, such as the Internet.
The Virtual Private Network enables a computer to send and receive data across shared
or public networks as if it were directly connected to the private network, while
benefitting from the functionality, security and management policies of the private
network.
Table 26: Terms, Abbreviations and Acronyms

End User License Agreement and Terms & Conditions
Appendix B End User License Agreement and Terms & Conditions
BY USING THE APPLICATION AND/OR THE SOFTWARE, YOU INDICATE YOUR AGREEMENT WITH THE FOLLOWING TERMS AND CONDITIONS. IF YOU DO NOT
AGREE WITH THE END USER LICENSE AGREEMENT and THE TERMS AND CONDITIONS, (hereinafter called the “Terms and Conditions”), DO NOT USE THE
APPLICATION AND/OR THE SOFTWARE.
_Definitions_
The following terms will have the meaning ascribed to them in this Terms and Conditions:
“The Company”: Essence SmartCare Ltd.
“The System”: related social alarm product(s) and monitoring applications, products and solutions for home or any control systems or any part thereof.
“Device”: A mobile phone, personal computer, tablet or any other device or any other application interface that you own and/or use and/or hold and/or control, which may enable access to third parties services
and applications.
“Service Provider”: the entity (not being the Company) that provides services and/or call-center services and/or other services through the System and enables you to use the Application.
“Monitored Party”: the third party whose activities of daily living are being monitored.
The Company provides a user interface application (including any updates and/or upgrades and/or patches thereto) subject always to the terms hereto for monitoring and/or controlling the System via your
Device(s) (hereinafter, respectively, the “Application”). By downloading the Application, installing or using the Application or any part thereof, you irrevocably agree to the following terms and conditions in this
Terms and Conditions.
Certain information about you or otherwise is subject to the Privacy Policy; for more information, see the full Privacy Policy at ADDENDUM A.
_Article I – SCOPE OF USE_

a. The Company grants you non-exclusive, non-transferable, non-sub-licensable, non-assignable, limited right to use the Application solely and exclusively for your personal use via your Device(s) license for the
intended purpose of monitoring the consenting Monitored Party for a limited time period as specified herein below (the “License”). For the avoidance of doubt, the License allows you to install and use the
Application on several Devices provided that such are owned at all times solely by you;
b. You agree that you shall be solely responsible for (and that the Company has no responsibility to you or to any third party) the use of the Application, for any breach of the obligations under the Terms and
Conditions, and for the consequences (including any loss or damage which the Company and/or you and/or any third party may suffer and/or incur) as a result of any such breach.
c. As a condition to using the Application, you agree that certain updates, upgrades and/or patches to the Application may be automatically received and installed on your Device(s) from time to time.
d. As a condition to using the Application, you agree that you will receive certain messages from the Company and/or the Service Provider and/or the System , including notifications sent from the System to your
Device(s); modifications, improvements and patches of the Application; information with respect to the Company's other products; personalized information, including advertisements, from third parties, unless
you elect not to receive such third party contents (“opt out”); and such other messages as the Company believes may be to your benefit or interest from time to time.
_Article II – PROPRIETARY RIGHTS_

a. You hereby agree and acknowledge that (a) the Application contains Intellectual Property Rights as well as other proprietary and confidential information that is protected by applicable intellectual property and other
laws, and (b) The Company owns all rights, title and interest in and to the Application and content, including without limitation upgrade, modification thereto including without limitation all Intellectual Property Rights
therein and thereto. “Intellectual Property Rights” means any and all rights existing from time to time under patent law, copyright law, trade secret law, trademark law, unfair competition law, and any and all other
proprietary rights, and any and all applications, renewals, extensions and restorations thereof, now or hereafter in force and effect worldwide. You agree that you will not, and will not allow any third party to, (1) copy, sell,
license, distribute, transfer, modify, adapt, translate, prepare derivative works from, decompile, reverse engineer, disassemble or otherwise attempt to derive source code from the Application or content that may be
presented or accessed through the Application for any purpose, without the express written consent of the Company, (2) take any action to circumvent or defeat the security or content usage rules provided, deployed
or enforced by any functionality (including without limitation digital rights management functionality) contained in the Application , (3) use the Application to access, copy, transfer or retransmit content in violation of
any law or third party rights, or (4) remove, obscure, or alter the Company's copyright notices, trademarks, logos or other proprietary rights notices affixed to or contained within or accessed in conjunction with or
through the Application.
b. USERNAME AND PASSWORD: In order to access and use the Application you must obtain a valid username and password. You are solely responsible for maintaining the confidentiality of your username and password.
For security reasons and to avoid unauthorized access, you are required to logout in an orderly manner from the Application at the end of each session. In any case, the Company shall not be liable for any damage or loss
of any kind or nature incurred and/or suffered by you and/or by any third party as a result of the Application being accessed and/or used by unauthorized user/s.
c. TERMINATION: The License is effective until terminated by the Company for any reason whatsoever (including without limitation in case that the agreement between the Company and the Service Provider expires or
terminates for any reason), and will terminate automatically without notice from the Company if you fail to comply with any Terms and Conditions; in any such event the Company may block you from using and/or
accessing the Application and you shall not have any claim against the Company in connection with such restriction.
_Article III – DISCLAIMER OF WARRANTIES_

a. YOU EXPRESSLY ACKNOWLEDGE AND AGREE THAT USE OF THE APPLICATION IS AT YOUR SOLE RISK AND THAT THE ENTIRE RISK AS TO SATISFACTORY QUALITY, PERFORMANCE, ACCURACY AND EFFORT IS
WITH YOU. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE APPLICATION IS PROVIDED “AS IS” AND “AS AVAILABLE”, WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND, AND THE
COMPANY HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS WITH RESPECT TO THE APPLICATION , EITHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES AND/OR CONDITIONS OF MERCHANTABILITY, OF SATISFACTORY QUALITY, OF FITNESS FOR A PARTICULAR PURPOSE, OF ACCURACY, OF QUIET ENJOYMENT, AND NON-INFRINGEMENT OF THIRD
PARTY RIGHTS. THE COMPANY DOES NOT WARRANT AGAINST INTERFERENCE WITH YOUR ENJOYMENT OF THE APPLICATION, THAT THE FUNCTIONS CONTAINED IN, OR PERFORMED OR PROVIDED BY THE
APPLICATION WILL MEET YOUR REQUIREMENTS, THAT THE OPERATION OF THE APPLICATION WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE APPLICATION WILL BE CORRECTED. THE
COMPANY DOES NOT WARRANT THAT THE APPLICATION SHALL BE COMPATIBLE WITH EACH WEB BROWSER (AND EACH VERSION THEREOF) AND YOU ARE SOLELY RESPONSIBLE FOR OBTAINING A BROWSER
SUPPORTING THE APPLICATION FROM YOUR APPLICABLE PROVIDER. USAGE OF THE APPLICATION MAY REQUIRE DOWNLOADING AND INSTALLING A THIRD PARTY SOFTWARE (E.G., PDF VIEWER APPLICATION)
AND YOU ARE SOLELY RESPONSIBLE FOR OBTAINING SUCH THIRD PARTY SOFTWARE, WITH COMPANY ASSUMING NO LIABILITY WHATSOEVER IN CONNECTION WITH SUCH SOFTWARE INCLUDING ITS
AVAILABILITY (OR LACK THEREOF), PERFORMANCE, COST, OR ANY RESULTS CAUSED BY THE OPERATION OF SUCH SOFTWARE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY THE COMPANY OR
ITS AUTHORIZED REPRESENTATIVE SHALL CREATE A WARRANTY, OTHER THAN SUCH AS EXPLICITLY SET FORTH IN WRITING IN THESE TERMS AND CONDITIONS. SHOULD THE APPLICATION PROVE DEFECTIVE,
YOU ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
b. YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE(S), OR LOSS OF DATA THAT RESULTS FROM USING THE APPLICATION.
c. YOU EXPRESSLY UNDERSTAND AND AGREE THAT THE COMPANY CANNOT ASSURE AND TAKES NO RESPONSIBILITY THAT SOME OR ALL OF THE INFORMATION SENT VIA THE APPLICATION WILL BE SENT
AND/OR REACH THE INTENDED RECIPIENT AND/OR NOT BE SENT AND/OR NOT REACH OTHER THIRD PARTIES, IN WHICH CASE THE COMPANY WILL NOT BE LIABLE FOR ANY DAMAGE AND/OR LOSS OF ANY
KIND OR NATURE INCURRED AND/OR SUFFERED BY YOU AND/OR BY ANY THIRD PARTY AS A RESULT THEREOF.
d. YOU EXPRESSLY UNDERSTAND AND AGREE THAT THE COMPANY CANNOT ASSURE AND TAKES NO RESPONSIBILITY THAT THE APPLICATION WILL SUCCESSFULLY PROVIDE NOTICES TO YOUR DEVICE OR TO
YOUR SERVICE PROVIDER, NOR THAT THE SYSTEM AND/OR ANY PART OF THE SYSTEM WILL SUCCESSFULLY TRIGGER NOTICES OR OTHERWISE WILL CONFORM OR OPERATE, IN WHICH CASE THE COMPANY
WILL NOT BE LIABLE FOR ANY DAMAGE AND/OR LOSS OF ANY KIND OR NATURE INCURRED AND/OR SUFFERED BY YOU AND/OR BY ANY THIRD PARTY AS A RESULT THEREOF.
e. YOU EXPRESSLY DECLARE: THAT YOU HAVE RECEIVED THE MONITORED PARTY’S PRIOR WRITTEN CONSENT TO VIEW AND/OR MONITOR THE SYSTEM INFORMATION AS DEFINED HEREIN; THAT YOU WILL
TREAT THE SYSTEM INFORMATION WITH THE UPMOST DISCRETION; AND, THAT YOU WILL NOT STORE AND/OR SHARE AND/OR PUBLISH THE SYSTEM INFORMATION OR ANY PART THEREOF. YOU
UNDERSTAND AND AGREE THAT THE INFORMATION GATHERED AND/OR STORED BY THE SYSTEM OR THE APPLICATION (THE “INFORMATION”) (INCLUDING BUT NOT LIMITED TO VIDEO SEGMENTS FILMED
AND/OR STORED AND OR GATHERED BY THE SYSTEM (THE “VIDEO SEGMENTS”) (THE “INFORMATION” AND THE “VIDEO SEGMENTS” COLLECTIVELY TOGETHER: THE “SYSTEM INFORMATION”) IS STORED ON
THE COMPANY'S AND/OR THE SERVICE PROVIDER SERVERS. THE SYSTEM INFORMATION INCLUDING THE VIDEO SEGMENTS IS THE SOLE PROPERTY OF THE COMPANY AND/OR THE SERVICE PROVIDER IN
ACCORDANCE WITH THE AGREEMENTS BETWEEN THE COMPANY AND THE SERVICE PROVIDER.THE COMPANY SHALL HAVE ACCESS TO ALL OF THE SYSTEM INFORMATION AT COMPANY’S SOLE DISCRETION
AND SHALL, FROM TIME TO TIME, AT THE REQUEST OF THE SERVICE PROVIDER FOR SUPPORT, MAINTENANCE, SYSTEM UPGRADES OR MODIFICATIONS AND ALIKE, REVIEW THE VIDEO SEGMENTS. COMPANY
SHALL NOT LET OTHER PARTIES (OTHER THAN THE SERVICE PROVIDER) REVIEW THE VIDEO SEGMENTS, WITHOUT YOUR OR THE MONITORED PARTY’S PRIOR CONSENT, EXCLUDING DISCLOSURE THAT IS
REQUIRED BY LAW, REGULATION OR ORDER OF A COMPETENT AUTHORITY.
f. YOU EXPRESSLY UNDERSTAND AND AGREE THAT THE COMPANY CANNOT ASSURE AND TAKES NO RESPONSIBILITY FOR MEASURES TAKEN AND/OR NOT TAKEN BY YOUR SERVICE PROVIDER IN ORDER TO
PROTECT THE SYSTEM INFORMATION, AND IN NO CASE WILL THE COMPANY BE LIABLE FOR ANY DAMAGE AND/OR LOSS OF ANY KIND OR NATURE INCURRED AND/OR SUFFERED BY YOU AND/OR THE
MONITORED PARTY AND/OR BY ANY THIRD PARTY IN CASE THE SYSTEM INFORMATION GATHERED AND/OR STORED BY YOUR SERVICE PROVIDER IS EXPOSED TO THIRD PARTIES.
g. YOU EXPRESSLY UNDERSTAND AND AGREE THAT ALTHOUGH THE COMPANY WILL TAKE REASONABLE MEASURES IN ORDER TO PROTECT THE SYSTEM INFORMATION STORED ON THE COMPANY'S SERVERS
AND PREVENT PENETRATION OF THE COMPANY'S SERVERS BY THIRD PARTIES, THERE IS A POSSIBILITY THAT SOME OR ALL OF THE SYSTEM INFORMATION MAY, FOR WHATEVER REASON, WITHOUT THE
COMPANY'S AND/OR YOUR SERVICE PROVIDER'S CONSENT, BE EXPOSED TO THIRD PARTIES, IN WHICH CASE THE COMPANY WILL NOT BE LIABLE FOR ANY DAMAGE AND/OR LOSS OF ANY KIND OR NATURE
INCURRED AND/OR SUFFERED BY YOU AND/OR THE MONITORED PARTY AND/OR BY ANY THIRD PARTY AS A RESULT THEREOF.
h. YOU EXPLICITLY ACKNOWLEDGE THAT THE APPLICATION: (I) ENABLES AND PROVIDES THE TRACKING AND MONITORING ITS USERS’, AS WELL AS THIRD PARTIES’ ACTIVITIES, INCLUDING WITHOUT
LIMITATION, THEIR WHEREABOUTS, DAILY ACTIVITIES AND HABITS, WHETHER BY VISUAL OR BY OTHER TYPES OF METHODS (THE “DATA”); (II) ENABLES AND PROVIDES THE ABILITY TO COLLECT AND

COMPILE, AND ANALYZE THE DATA; (III) MAY FACILITATE , ENABLE OR OTHERWISE ASSIST GENERATION OF FILES CONTAINING THE DATA; (IV) ENABLE AND ALLOW FURTHER USES AND ACTIVITIES FOR WHICH
YOU WERE ADVISED AND MADE AWARE OF BY THE COMPANY OR THE SERVICE PROVIDER OR BY ANY OTHER MEANS BECOME AWARE OF FROM TIME TO TIME.
i. YOU EXPLICITLY ACKNOWLEDGE THAT USE OF THE APPLICATION MAY VIOLATE OR INFRINGE UPON YOUR AND/OR THIRD PARTIES RIGHTS (INCLUDING THE MONITORED PARTY), INCLUDING WITHOUT
LIMITATION THE RIGHT FOR PRIVACY.
j. YOU EXPLICITLY ACKNOWLEDGE THAT THE APPLICATION IS NOT A MEDICAL OR LIFESAVING DEVICE, PRODUCT OR SERVICE; DOES NOT PROVIDE ANY MEDICAL, LIFE SAVING OR OTHERWISE PREEMPTIVE
MEASURE AGAINST INJURY OR OTHERWISE BODILY HARM OR DEATH; NOR ASSUME IN ANY WAY TO REPLACE OR BE IN LIEU OF ANY SUCH.
j. IN ADDITION TO AND WITHOUT DEROGATING FROM ANY AND ALL OTHER LIMITATION OF LIABILITY PROVISIONS HEREIN, IN NO EVENT SHALL THE COMPANY BE LIABLE FOR ANY INCIDENTAL, INDIRECT,
COLLATERAL, SPECIAL, THIRD-PARTY, PUNITIVE, EXEMPLARY OR CONSEQUENTIAL DAMAGES OR LOSSES OF ANY KIND. EXCLUDED DAMAGES OR LOSSES INCLUDE, BUT ARE NOT LIMITED TO, BODILY INJURY
AND/OR DEATH, COST OF REMOVAL OR REINSTALLATION, ANCILLARY COSTS TO THE PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LABOR COSTS, LOSS OF GOODWILL, LOSS OF PROFITS, LOSS OF
SAVINGS, LOSS OF USE, LOSS OF DATA, OR BUSINESS INTERRUPTION, OR OTHER PECUNIARY LOSS ARISING OUT OF THE USE OF THE APPLICATION , OR OTHERWISE ARISING OUT OF, OR IN CONNECTION
WITH, THESE TERMS AND CONDITIONS, WHETHER OR NOT COMPANY WAS ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
_Article IV – SYSTEM AND SERVICE LIMITATIONS_
a. The Application is designed to provide information regarding the Monitored Party and related and/or additional activities and as such may be provided from time to time. Company shall have no responsibility for
failure of data transmission, corruption or unauthorized access.
b. You are responsible for supplying high speed Internet access. Company does not provide Internet service; maintain Internet connection, wireless access or communication pathways, computer, smart phone,
electric current connection or supply. As long as the Service Provider makes payments to the Company for remote access for your use of the Application as well as to the System, Company will authorize your
access. Company is not responsible for your access to the Internet or any interruption of service or down time of remote access caused by loss of Internet service, radio or cellular or any other mode of
communication used by you for the Application and the access of the System. You acknowledge that the System can be non-functional or compromised if the Internet codes or devices used for access are lost or
accessed by others and Company shall have no liability for such third party unauthorized access. Company is not responsible for the security or privacy of any wireless network system or router. Wireless systems
can be accessed by others, and it is your responsibility to secure access to the system with pass codes and lock outs.
c. The Application is designed to utilize your enabled cellular Device to access the System. The Device will work only in areas where the cellular service has coverage and Company has no control over such
coverage. Company is authorized to record and maintain audio transmissions, data and communications, and shall be the exclusive owner of such property. You are responsible for all permits and permit fees, if
any, and agree to file for and maintain any permits required by applicable law and indemnify or reimburse Company for any fines relating to permits. Should Company be required by existing or hereafter enacted
law to perform any service or furnish any material not specifically covered by this Terms and Conditions you agree to pay Company for such service or material Company does not monitor signals and
communications received by or from your enabled cellular device excluding information regarding login/ logout from the Application and all Application usage.
d. You acknowledge that signals which are transmitted over telephone lines, wire, air waves, internet, VOIP, or other modes of communication pass through communication networks wholly beyond the control of
Company and are not maintained by Company and Company shall not be responsible for any failure which prevents transmission signals from reaching your Internet enabled Device or damages arising therefrom,
or for data corruption, theft or viruses to your Internet enabled Device.
_Article V – INDEMNITY_
To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless the Company, its affiliates and their respective directors, officers, employees, representatives and agents from and
against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including attorneys’ fees) arising out of or accruing from your use of the Application ,
including your downloading, installation, or use of the Application , or your violation of the Terms and Conditions.
_Article VI – MODIFICATION_
The Company reserves the right to modify without prior notice the Application, and the Terms and Conditions governing its use, at any time, including but not limited to charge fees in order to access and/or use
the Application. The Company also reserves the right to terminate any or part of the Application or any use thereof at any time on its sole discretion without prior notice.
_Article VII – LICENSE CHANGES_
a. The Company reserves the right to update and change, from time to time, these Terms and Conditions and all documents incorporated by reference. At all times, you can find the most recent version of the
Terms & Conditions on the Company’s website or request a copy from Company’s support team. Use of the Application after such change constitutes acceptance of such changes.
b. This Terms and Conditions, and any new versions, between the Company and you, cover all your use of the Application, including, without limitation, the Application. You can accept this Terms & Conditions by
clicking on such acceptance buttons or links as may be designated by the Company. If you disagree with any of the terms below, the Company does not grant you a license to use the Application.
_Article VIII – MISCELLANEOUS_
a. Your contractual relationship with your Service Provider and/or other third parties, including payment, delivery of goods or services, and any other terms, conditions, privacy policies, warranties or
representations associated with such dealings, are solely between you and such provider and/or third party. You agree that the Company will not be responsible or liable for any loss and/or damage of any kind or
nature incurred and/or suffered by you and/or any third party as a result of the presence of such provider and/or third parties on the Application.
b. These Terms and Conditions constitute the entire agreement and understanding between you and the Company relating to the Application and govern your use of the Application, and completely replace and
supersede any prior or contemporaneous agreements between you and the Company regarding the Application.
c. The failure of the Company to exercise or enforce any right or provision of these Terms and Conditions does not constitute a waiver of such right or provision, which will still be available to the Company.
d. The provisions of these Terms and Conditions are independent of and severable from each other. If any provision is found to be invalid or unenforceable for any reason, that provision shall be deemed modified
to the extent necessary to make it valid and operative, or if it cannot be so modified or eliminated, the remainder of these Terms and Conditions shall continue in full force and effect as if these Terms and
Conditions had been signed with the invalid portion so modified or eliminated.
e. These Terms and Conditions and your limited relationship which is only specified herein with the Company under these Terms and Conditions will be governed by the laws of the State of Israel without regard to
its conflict of laws’ provisions. You and the Company agree to submit to the exclusive jurisdiction of the courts located within the Tel-Aviv district, Israel, to resolve any legal matter arising from these Terms and
Conditions.
_ADDENDUM A – PRIVACY POLICY_
Company is providing this Privacy Policy to inform you of our policies and procedures regarding the collection, use and disclosure of information we receive when you do either of the following:
All terms shall have the same meaning as defined in the Terms and Conditions to which this Addendum A is part hereof.
You visit the Company website (the “Site”) or the Service Provider’s website.
By downloading or using the Application or by entering the Site, you fully understand and unambiguously consent to the collection and processing of such information and to the terms of this Privacy Policy. If you
do not agree to the terms of this Privacy Policy, you must not use the Application or Site.
This Privacy Policy may be amended or updated from time to time. If we make any material changes to this Privacy Policy, Service Provider shall update you of these changes. Our website will reflect changes in the
Privacy Policy as well and you are advised to consult this Privacy Policy regularly for any changes.
_Information Collection_
Personally Identifiable Information
In the course of using the Application, we might ask you to provide us with certain personally identifiable information that can be used to contact or identify you (“Personal Information”). Personal Information may
include, but is not limited to, your name, country of residence, email address and website address.
Non-Personally Identifiable Information
When you use the Application (whether such use is performed on the System or a Device, on the Site or on a website of one of our partners or other third parties), we collect information regarding your use of the
Application, and information that your browser sends whenever you visit a site or online service, including, without limitation, your computer's Internet Protocol (IP) address, browser type, the web page you were visiting
before, and information for which you search.
When you use a widget or any other tool offered by us, whether on the System or a Device, on the Site or on a third party website, including a website owned or operated by you, we may record data related to that
activity, the deployment of the widget or tool, your location and any other account related data.
Like many websites, we use “cookies” to collect information. A cookie is a small data file that we transfer to your computer's hard disk for record-keeping purposes. You can instruct your browser, by changing its options,
to stop accepting cookies or to prompt you before accepting a cookie from the website you visit. If you do not accept cookies, however, you may not be able to use all portions of the Site or all functionality of the
Application.
We may present links in a format that enables us to keep track of whether these links have been followed.
Third Party Sites
This Privacy Policy applies only to the Application functionality on the System or a Device under your control, or on the Site. The Site may include links and references to the websites of others or third party advertisers.
These other sites may place their own cookies or other files on your computer, collect data or solicit personal information from you. Other websites follow different rules regarding the use or disclosure of the Personal
Information that you submit. We encourage you to read the privacy policies and other terms of the other websites. We do not review, approve, monitor, endorse, warrant, or make any representations with respect to
such websites. In no event will we be responsible or liable, directly or indirectly, to anyone for any loss or damage arising from such sites, including without limitation for your use of such website and for any information
submitted by you, or otherwise collected by such websites.

1. Our Policy towards Children

We do not knowingly collect personally identifiable information from children under the age of 18. If a parent or guardian becomes aware that his or her child has provided us with Personal Information without
their consent, he or she should contact us at info@essence-grp.com. If we become aware that a child under 18 has provided us with Personal Information, we will delete such information from our files.
2. Security
We are concerned with safeguarding your information. We employ a variety of safety measures designed to protect your information from unauthorized access and disclosure. However, we cannot guarantee that
your personal information or private communications will always remain private and secure.
3. International Processing or Transfer
Your information may be processed or transferred outside of your state, where the privacy laws may not be as protective as those in your jurisdiction.
4. Disclosure
We reserve the right to disclose any information obtained by us, including but not limited to Personal Information and Non Personally Identifiable Information, (i) if required by law or by any governmental
authority; or (ii) in case of emergency; or (iii) to a successor entity in connection with a merger, acquisition, bankruptcy or sale of all or substantially all of our assets.
5. Contacting Us
If you have any concerns or questions about this Privacy Policy, please contact us at info@essence-grp.com.
Copyright © 2015, Essence SmartCare Ltd., All rights reserved.
ESUG05076 Rev. 2.0

Care@Home™ System Terms of Use
Appendix C Care@Home™ System Terms of Use

In this Terms of Use (hereinafter the “Terms of Use”) the term “you or your” refers to the user of the System. The term “Company” refers to Essence SmartCare
Ltd.
The term “Service Provider” refers to the entity (not being the Company) that sold or leased to you the System and provides you services and/or call center
services and/or other services that enable you to use the System (as defined below).
Terms of Use applies to the System, consisting of the control panel which includes a cellular model (for data transmission and for voice calls), related social
alarm system and remote monitoring applications which may be hosted by a third party, products and solutions for home or any control systems or any part
thereof and any related products or equipment (including but not limited to a Stationary emergency button) all of which are manufactured by the Company
(the “System”). This is the only express warranty for this System and is in lieu of any other warranty or condition. Should the System be defective your exclusive
remedy should be rendered solely by the Service Provider at the Service Provider’s discretion as per the terms of the limited warranty provided to you by the
Service Provider from time to time. For avoidance of any doubts, no such limited warranty or any other document provided to you as aforementioned, by the
Service Provider, may alter revise, add, remove, modify, terminate, condition, or otherwise change in any way the terms and conditions in this Terms of Use,
and the sole exclusive method of modifications of this Terms of Use shall be valid only if made by the Company, in writing and pursuant to as provided herein.
In case of any contradiction between this Terms of Use and any limited warranty or any other document provided to you by the Service Provider, the Terms of
Use shall prevail.
This Terms of Use does not cover:

batteries, or any problem that is caused by accident, vandalism, negligence or mistake, flood, water, lightning, fire, abuse, misuse, acts of god, and casualty or
electrical surges.
To receive service or replacement or any other service for the System under this Terms of Use, please contact your Service Provider. Company will not provide
You with any such service or otherwise activity, other than as through the Service Provider and always pursuant to the agreement terms and conditions, as such
exists from time to time, and to the extent any such exists, between the Service Provider and the Company.
YOUR RESPONSIBILITIES FOR SYSTEM OPERATION:

By use of the System you agree to the terms of this Terms of Use. You agree that the System requires AC power supply and that it is your sole responsibility to
provide electrical outlet and receptacle, cellular SIM card with an internet connection. The System uses RF communication technology, elements beyond the
Company’s control such as (but not limited to) bad weather that may cause interferences to the System’s performance. You are solely responsible for providing
communication pathways for the System to communicate upon activation. Notwithstanding the forgoing, Company shall not be responsible for loss of System
connectivity or data due to cellular network disconnections. The System must be used as intended and for no other purpose. The System contains small
particles and electricity wires and is not intended for use by children or anyone who is not capable of understanding the System’s purpose and how to use the
System and monitoring services. Pendants may have attachments which can cause strangulation if not used properly. You agree that the System communicates
over cellular network which pass through communication networks wholly beyond the control of Company and are not maintained by Company and the
Company is not be responsible for any failure which prevents transmission signals from communicating your emergency condition. You have selected the
communication pathway to be used with the System and you are solely responsible for continuous communication. Do not attempt to open the System and/or
fix it yourself and/or change the System in any way including but not limited to the System’s antenna or any additional component thereof.
The System communicates by wireless cellular transmission.
Company does not provide wireless access or communication pathways or electric current connection.
THE SYSTEM IS DESIGNED TO PROVIDE INFORMATION INCLUDING WITHOUT LIMITATION, YOUR WHEREABOUTS, DAILY ACTIVITIES AND HABITS, WHETHER
BY VISUAL OR BY OTHER TYPES OF METHODS (THE “INFORMATION”); (II) ENABLE AND PROVIDE THE ABILITY TO COLLECT AND COMPILE, AND ANALYZE
THE INFORMATION; (III) MAY FACILITATE , ENABLE OR OTHERWISE ASSIST GENERATION OF FILES CONTAINING THE INFORMATION; (IV) ENABLE AND
ALLOW FURTHER USES AND ACTIVITIES ; ALL AS YOU MAY DECIDE PURSUANT TO YOUR SPECIFIC AGREEMENTS WITH THE SERVICE PROVIDER. YOU
SPECIFICALLY ACKNOWLEDGE THAT THE COMPANY SHALL HAVE NO RESPONSIBILITY FOR FAILURE OF INFORMATION TRANSMISSION, CORRUPTION OR
UNAUTHORIZED ACCESS TO THE INFORMATION.
YOU EXPLICITLY ACKNOWLEDGE THAT USE OF THE SYSTEM MAY VIOLATE OR INFRINGE UPON YOUR RIGHTS, INCLUDING WITHOUT LIMITATION THE RIGHT
FOR PRIVACY.
YOU EXPRESSLY DECLARE THAT YOU ARE RENDERING YOUR CONSENT TO THE SERVICE PROVIDER AND/OR OTHER AUTHORIZED THIRD PARTIES ON YOUR
BEHALF TO VIEW AND/OR MONITOR THE INFORMATION.
YOU UNDERSTAND AND AGREE THAT THE INFORMATION GATHERED AND/OR STORED BY THE SYSTEM (THE “INFORMATION”) (INCLUDING BUT NOT
LIMITED TO VIDEO SEGMENTS FILMED AND/OR STORED AND OR GATHERED BY THE SYSTEM (THE “VIDEO SEGMENTS”) (THE “INFORMATION” AND THE
“VIDEO SEGMENTS” COLLECTIVELY TOGETHER: THE “SYSTEM INFORMATION”) IS STORED ON THE COMPANY'S AND OR THE SERVICE PROVIDER SERVERS.
THE SYSTEM INFORMATION INCLUDING THE VIDEO SEGMENTS IS THE SOLE PROPERTY OF THE COMPANY AND/OR THE SERVICE PROVIDER IN
ACCORDANCE WITH THE AGREEMENTS BETWEEN THE COMPANY AND THE SERVICE PROVIDER. THE COMPANY SHALL HAVE ACCESS TO ALL OF THE
SYSTEM INFORMATION AT COMPANY’S SOLE DISCRETION AND SHALL, FROM TIME TO TIME, AT THE REQUEST OF THE SERVICE PROVIDER FOR SUPPORT,
MAINTENANCE, SYSTEM UPGRADES OR MODIFICATIONS AND ALIKE, REVIEW THE VIDEO SEGMENTS. COMPANY SHALL NOT LET OTHER PARTIES (OTHER
THAN THE SERVICE PROVIDER) REVIEW THE VIDEO SEGMENTS, WITHOUT YOUR PRIOR CONSENT, EXCLUDING DISCLOSURE THAT IS REQUIRED BY LAW,
REGULATION OR ORDER OF A COMPETENT AUTHORITY.
YOU EXPLICITLY ACKNOWLEDGE THAT THE SYSTEM IS NOT A MEDICAL OR LIFE SAVING DEVICE, SYSTEM; DOES NOT PROVIDE ANY MEDICAL, LIFE SAVING
OR OTHERWISE PREEMPTIVE MEASURE AGAINST INJURY OR OTHERWISE BODILY HARM OR DEATH; NOR ASSUME IN ANY WAY TO REPLACE OR BE IN LIEU OF
ANY SUCH. COMPANY’S WARRANTIES UNDER THIS TERMS IF USE (ARE EXCLUSIVE AND IN LIEU OF ALL OTHER WARRANTIES, WHETHER WRITTEN OR ORAL,
EXPRESS IMPLIED OR STATUTORY, INCLUDING ANY WARRANTY OF SATISFACTORY QUALITY, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE,
OR WILL MEET YOUR SPECIFIC REQUIREMENTS. COMPANY DOES NOT REPRESENT THAT THE SYSTEM IS ERROR FREE OR OPERATES WITHOUT INTERRUPTION.

YOU EXPRESSLY UNDERSTAND AND AGREE THAT THE COMPANY CANNOT ASSURE AND TAKES NO RESPONSIBILITY THAT THE SYSTEM WILL SUCCESSFULLY
PROVIDE NOTICES TO YOUR SERVICE PROVIDER, NOR THAT THE SYSTEM WILL SUCCESFULLY TRIGGER NOTICES OR OTHERWISE WILL CONFORM OR
OPERATE, IN WHICH CASE THE COMPANY WILL NOT BE LIABLE FOR ANY DAMAGE AND/OR LOSS OF ANY KIND OR NATURE INCURRED AND/OR SUFFERED
BY YOU AND/OR BY ANY THIRD PARTY AS A RESULT THEREOF.
IN ADDITION TO AND WITHOUT DEROGATING FROM ANY AND ALL OTHER LIMITATION OF LIABILITY PROVISIONS HEREIN, IN NO EVENT SHALL THE
COMPANY BE LIABLE FOR ANY INCIDENTAL, INDIRECT, COLLATEROL, SPECIAL, THIRD PARTY, PUNITIVE, EXEMPLARY OR CONSEQUENTIAL DAMAGES OR
LOSSES OF ANY KIND. EXCLUDED DAMAGES OR LOSSES INCLUDE, BUT ARE NOT LIMITED TO, BODILY INJURY AND/OR DEATH, COST OF REMOVAL OR
REINSTALLATION, ANCILLARY COSTS TO THE PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LABOR COSTS, LOSS OF GOODWILL, LOSS OF PROFITS,
LOSS OF SAVINGS, LOSS OF USE, LOSS OF DATA, OR BUSINESS INTERRUPTION, OR OTHER PECUNIARY LOSS ARISING OUT OF SOFTWARE OR PRODUCTS THAT
WERE FAULTY OR WERE MANUFACTURED NEGLIGENTLY; AND ALSO ARISING OUT OF THE USE OF THE SYSTEM, OR OTHERWISE ARISING OUT OF, OR IN
CONNECTION WITH, THIS TERMS OF USE, WHETHER OR NOT THE COMPANY WAS ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Please note that the Company System does not include any other components other than such are specified in System definition. Therefore and for sake of
clarity:
(1) Company is not responsible for your ability to use the System including without limitation, access to the cellular service or any interruption of service or
down time caused by loss of cellular or any other mode of communication. Company is not responsible for the security or privacy of any wireless network
system.
(2) The system requires voice and data connection (via cellular network) and electric power supply which shall not be provided by the Company. As long as the
Service Provider makes payments to Company for remote access for your use of the System as well as to the System, Company will authorize your access.
Company is not responsible for your access to the Internet or any interruption of service or down time of remote access caused by loss of Internet service, or
cellular used by you for the System and the access of the System. You acknowledge that the System can be non-functional or compromised if the Internet
codes or devices used for access are lost or accessed by others and Company shall have no liability for such third party unauthorized access.
(3) The System will work only in areas where the cellular service has coverage and Company has no control over such coverage. Company is authorized to
record and maintain data, and shall be the exclusive owner of such property. You are responsible for all permits and permit fees, if any, and agree to file for and
maintain any permits required by applicable law and indemnify or reimburse Company for any fines relating to permits. Should the Company be required by
existing or hereafter enacted law to perform any service or furnish any material not specifically covered by the terms of this agreement you agree to pay
Company for such service or material.
(4) You acknowledge that signals which are transmitted over cellular network, internet communication pass through communication networks wholly beyond
the control of Company and are not maintained by Company and Company shall not be responsible for any failure which prevents transmission signals from
reaching you or from the system or damages arising therefrom, or for data corruption.
You agree that Company is the manufacturer of the System and provides no installation, services or monitoring of the System and makes no recommendation
regarding those who do provide such services, all of whom are not affiliated with Company. Who you decide to obtain the System from, install and or monitor
the System, is entirely your decision.
_EXCULPATORY AND LIMITATION OF LIABILITY_

You agree that Company is not an insurer, that the System is designed to reduce certain risks, though Company does not guarantee that its System will enable
communication to reach or cause response by an appropriate party including the Service Provider. You agree that Company is not assuming liability, and, THE
SOLE EXCLUSIVE REMEDIES, SERVICE OR SOLUTIONS, IF ANY ARE AND WILL BE AS PROVIDED TO YOU BY THE SERVICE PROVIDER.
ACCEPTANCE OF Terms of Use: By use of the System you agree to the terms of this Terms of Use.
_ADDENDUM A – PRIVACY POLICY_

Company is providing this Privacy Policy to inform you of our policies and procedures regarding the collection, use and disclosure of information we receive
when you do either of the following:
All terms shall have the same meaning as defined in the Terms and Conditions to which this Addendum A is part hereof.
By using the System you fully understand and unambiguously consent to the collection and processing of such information and to the terms of this Privacy
Policy. If you do not agree to the terms of this Privacy Policy, you must not use the System.
This Privacy Policy may be amended or updated from time to time. If we make any material changes to this Privacy Policy, Service Provider shall update you of
these changes. Our website will reflect changes in the Privacy Policy as well and you are advised to consult this Privacy Policy regularly for any changes.
_Information Collection_
Personally Identifiable Information
In the course of using the System, we might ask you to provide us with certain personally identifiable information that can be used to contact or identify you
(“Personal Information”). Personal Information may include, but is not limited to, your name, country of residence.
Non-Personally Identifiable Information
When you use the System your home and your activities are monitored by the Service Provider.
You hereby acknowledge and approve that, the System collects various types of information regarding your daily activities such as but not limited to: your
whereabouts inside your home, the duration of time you spent in the different sections of your home, the System monitors whether someone is present in the
home and may photograph you or any other third party who enters your home without notice, the System may actively record any sounds or verbal
communications in your home, The system may enable remote voice communication between you and the Service Provider.
_Third Party Sites_

You are obligated to notify any third party who enters your home, and if said third party is a child or is under a legal guardian’s responsibility, their legal
guardian, that they may be monitored and/or photographed and/or recorded without their knowledge and prior authorization.
1. Security

We are concerned with safeguarding your information. We employ a variety of safety measures designed to protect your information from unauthorized access
and disclosure. However, we cannot guarantee that your personal information or private communications will always remain private and secure.
2. International Processing or Transfer
Your information may be processed or transferred outside of your country, where the privacy laws may not be as protective as those in your jurisdiction.
3. Disclosure
We reserve the right to disclose any information obtained by us, including but not limited to Personal Information and Non Personally Identifiable Information,
(i) if required by law or by any governmental authority; or (ii) in case of emergency; or (iii) to a successor entity in connection with a merger, acquisition,
bankruptcy or sale of all or substantially all of our assets.
4. Contacting Us
If you have any concerns or questions about this Privacy Policy, please contact us at info@essence-grp.com.
Copyright © 2015, Essence SmartCare Ltd., All rights reserved.

USB to RS232 Adapters
Appendix D USB to RS232 Adapters
If the personal computer (PC) on which the Care@Home™ CMS software application is installed has no
available RS232 communications (COM) ports, the user is instructed to use a RS232-USB adapter to
connect the Control Panel (CP) to the PC.
Essence technical support recommends the following two alternatives:

 USB Gear Serial Adapter
 VScom USB-COM Mini
These are the descriptions and special features of the adapters.
The USB Gear Serial Adapter
Figure 146: The USB GEAR USB to Serial Adapter
The following is a list of some of the features of this USB to serial adapter:
 Over 500 kbps of data transfer capability
 Works with Modems, PDA's, Cell phones, Digital Cameras and more serial legacy devices
 LED visuals for transmit and receive between devices
 Compatible with: Windows 98, 2000, 2003, ME, XP, Vista, Windows 7 (32/64Bit) Microsoft
Certified Drivers Provided/ MAC 8.6, 9.0, 9.1/Linux

USB to RS232 Adapters
The USB Gear's 12" USB Serial Converter, with its powerful Hi-Speed DB9 Serial adapter, comes with
software drivers and a manual. The customer can download the software drivers and the user manual from
the following link: http://www.usbgear.com/Serial-usb-adapter/index.cfm
The VScom USB-COM Mini
Figure 147: The VScom USB-COM Mini Adapter
The VScom USB-COM Mini adapter provides a high speed RS232 serial port with 128 byte FIFO to allow for
high speed communications, even for heavy loaded systems. The RS232 serial port on this adapter also
enables high speed settings such as 500,000 bps.
The following is a list of the key features of this USB to serial adapter:
 1 x RS232 DB9 male port
 Speed up to 921.6 kps
 No external power supply
The customer can access VS Com and more information about this adapter by following this link:
http://www.vscom.de/619.htm

Voice Announcements
Appendix E Voice Announcements
Table 27 below includes all the text for the vocal announcements listed by Announcement Group.
Announcement Group Announcement Text

Vocal Reminders "Attention, it is time to take your medication. Please take them and press the Reset button"
"Attention, your appointment is at [hour, minute AM/PM]. (Please press the Reset button)"
"Attention, your ride will arrive at [hour, minute AM/PM]. Please press the Reset button)"
"Attention, alarm reminder. (Please press the Reset button)"
"Attention, it is time to test your pendant, Please press pendant button"
Medical "Activity alarm"
"Emergency Alarm"
"Activity timer will expire soon, Please press the reset button"
Safety "Flood alarm"
"Fire alarm"
"Temperature alarm"
Technical "Attention, communication with monitoring station is lost"
"Console on"
"Activity timer on"
"Console shutting down"
"Activity timer off"
"Device added successfully"
"Battery missing in console"
"Attention, low battery in console"
"Attention, a device is tampered"
"Attention, phone line is disrupted"
"Could not add device, please try again"
"Attention, console switched to backup battery"
"Attention, low battery in a device was detected"
"Attention, console backup battery needs to be replaced"
"Attention, supervision loss of a device was detected"
"Device already paired with console"
"Memory full, additional device cannot be added"
"Attention, RF jamming Was detected"
"RF jamming restored"
"Console Performed Software Reset"
"Pendant recognized"
"Attention, cellular signal strength is [X] (Percent)
"Attention, supervision loss of" "Passive Infrared Detector (PIR)" "was detected"
"Input Magnet Detector (MGI)"
"Shock Magnet Detector (MGLS)"
"Panic Button (SPB)"
"Emergency Pendant (EP)"
"Smoke Detector (SK2)"
Table 27: Vocal Announcements

Care Home CMS PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Care Home CMS PDF

Enviado por

Direitos autorais:

Formatos disponíveis

™

For more information, please contact: Essence SmartCare Ltd.

Care@Home™ CMS User Guide 3

4.1.4 The Control Panel Communications Module ............................................................. 44

9.2.3 Day of the Month Schedule Type ................................................................................95

14. Software Updates.................................................................................................................................134

6 Care@Home™ CMS User Guide

Care@Home™ CMS User Guide 7

1.1. The Control Panel Parameter File

The purpose of the .cpf file is two-fold:

The tools to manage the CMS parameter file are:

The data downloaded from the CMS application includes:

8 Care@Home™ CMS User Guide

1.2. Minimum System Requirements

NOTE: 512 Mb RAM is recommended for a better response time.

 At least 1 Gb free hard disk space

Care@Home™ CMS User Guide 9

2. CMS Implementation Process

2.1. CMS Installation

2.1.1 Running the Installation Wizard

Figure 1: Installation Wizard Window

To install the Care@Home™ CMS software application:

10 Care@Home™ CMS User Guide

Figure 2: Installation Wizard Finish Window

Figure 3: The Care@Home™ CMS Icon

2.2. Administrator Privileges

Care@Home™ CMS User Guide 11

Figure 4: Right-click Icon Menu

Figure 5: Properties Window Compatibility Tab

3. Click the Compatibility tab in the Properties window.

12 Care@Home™ CMS User Guide

2.3. Identify the Communications Port

Figure 6: Care@Home™ CMS Connect Window

1. Click the Windows Start icon.

2. Click Control Panel option on the Windows menu.

Care@Home™ CMS User Guide 13

Figure 7: Ports listed in the Device Manager

2.4. CMS Connect to the CP

c:\Program Files (x86)\Essence\Care@Home CMS\

2.5. The Connect Window

14 Care@Home™ CMS User Guide

 To activate the Remote Boot feature.

Figure 8: The Care@Home™ CMS Connect Window

Name Definition and Instructions Data Required or Default

Care@Home™ CMS User Guide 15

Table 1: Connect Window Parameters

Figure 9: CMS Connect Window Buttons

Table 2 below describes the functionality of these action buttons.

Name Definition and Instructions

Table 2: The Connect Window Action Buttons

2.6. Local Connection

16 Care@Home™ CMS User Guide

2.6.1 Local Connection to the CP

Figure 10: Essence ES7000BACMS Cable

Care@Home™ CMS User Guide 17

2.6.2 Configuration File

Figure 11: The Configuration File

Figure 12: COM Ports on Local PC

18 Care@Home™ CMS User Guide

Figure 13: SERIAL1 Defined as COM1

Figure 14: SERIAL1 Defined as COM5

Care@Home™ CMS User Guide 19

Figure 15: Connect Default Port COM5