Administration of the We.R™ System 4. Administration of the We.R™ System Daily usage of the We.R™ system involves: Basic terms of operation: Arming modes of operation Handling alarms Receiving notifications Panic situations Monitoring the premises Managing Users Managing Devices Log of Events (System History) 4.1. Arming Modes of Operation The We.R™ system supports four (4) security arming modes for the system.
Administration of the We.R™ System Figure 161: The We.R™ Mobile Application’s Home Status Screen 4.1.1. Types of Security Arming Modes The We.R™ system provides four (4) possible security arming modes of operation: 4.1.1.1. Full Arm Simply referred to as – Arm. Full arm is triggered by clicking over the _Full Arm_ button in the We.R™ Web Application’s Status/Activation Bar, or by tapping over the Home Status screen. 198 button in the We.R™ Mobile Application’s ™ We.
Administration of the We.R™ System Change of arming status is acknowledged by the status icon. In this mode of operation, the We.R™ system protects ALL zones. This mode arms all of the sensor devices on the premises and an alarm will be triggered by any of them upon detecting an intrusion. 4.1.1.2. Day Arm Day arm is triggered by clicking over the _Day Arm_ button in the We.R™ Web Application’s button in the We.R™ Mobile Application’s Status/Activation Bar, or, tapping over the Home Status screen.
Administration of the We.R™ System 4.1.1.4. Disarm In addition to the above described status icon changing its face and color to acknowledge the trigger of specific arming mode, the buttons used for the triggering also changes: The left-most arming button will change its color to in the We.R™ Web Application’s Status/Activation Bar green and its title text will change into _Disarm_.
Administration of the We.R™ System Full Arm Disarm Day Arm Night Arm Figure 162: Triggering Arm Modes with Devices Disarming with the Wireless Access Control Tag Reader device is done by putting the Tag in close proximity with the Tag Reader. 4.1.1.6. Force Arming If attempt is made to arm the system (full arm, night arm and day arm), where one or more of the sensor devices is opened (i.e.
Administration of the We.R™ System Panic Alarms 4.2.1. Security Alarms Once the system is armed (full arm or night arm or day arm), an alarm will be triggered in the following security events: A Magnetic Sensor (MGL) monitored window/door was opened. A Motion Detector (PIR) or a Motion Indoor Photo Detector (IPD) detected some motion within its detection range, or, if any device is tampered while the system is armed.
Administration of the We.R™ System Figure 164: Security Alarm Notification on the We.R™ Mobile Application The Home Status screen will display: Figure 165: Security Alarm Screen on the We.R™ Mobile Application Where: A Burglary Alarm title will be presented along with the triggering device identification and a time stamp. The status icon ™ We.
Administration of the We.R™ System Three (3) new buttons will be presented at the bottom of the screen to allow: – monitor the premises by watching video-like images taken if the triggering device was a Motion Indoor Photo Detector (Camera). Alarms triggered by a Camera allow monitoring of the premises by the image presentation screen which, upon tapping this button, opens to display the area in front of the Camera.
Administration of the We.R™ System Figure 167: Sending Images to Email Acknowledgement Window Tapping over the button will terminate the email operation. Tapping over the button will send the images via email to the User. Upon completion, the following confirmation message window will pop-up: Figure 168: Email Confirmation Message Window Tapping over the button will conclude the send images by mail operation and return the screen to the Security Alarm Image Presentation Screen (see above Figure 166).
Administration of the We.R™ System 4.2.2. – disarming the system. Safety Alarms Beside security, the We.R™ system also provides for safety features, utilizing devices like the: Smoke Detector (SK2) Flood Detector (FL), and Universal Transmitter interfacing between the We.R™ system and safety device from 3rd party manufacturers. Setup, scenarios of operation and alarm notifications of these safety devices are incorporated into the system by means similar to the security devices.
Administration of the We.R™ System On the We.R™ Mobile Application, the following notification message window will pop-up to draw the User’s attention: Figure 170: Safety Alarm Notification on the We.R™ Mobile Application The Home Status screen will display: Figure 171: Safety Alarm Screen on the We.R™ Mobile Application Where: A Flood (or Smoke) Alarm title will be presented along with the triggering device identification and a time stamp. ™ We.
Administration of the We.R™ System The status icon will blink in orange, and Two (2) new buttons will be presented at the bottom of the screen to allow: 4.2.3. – making emergency phone calls from the smartphone, – dismissing the alarm and, if the system was armed – disarm it. Panic Alarms The We.R™ system also supports panic alarming for personal emergency cases.
Administration of the We.R™ System If a Panic Alarm was triggered, the User will receive an Alarm Notification on his We.R™ Web Application (assuming the User is logged in) and on his smartphone (where the We.R™ Mobile Application software was installed). On the We.R™ Web Application’s Status/Activation Bar: Figure 173: Panic Alarm Status Display on the We.
Administration of the We.R™ System Figure 175: Panic Alarm Home Status Screen Where: A Panic Alarm title will be presented along with the triggering device identification and a time stamp. The status icon will blink in red, and Three (3) new buttons will be presented at the bottom of the screen to allow: – monitoring the premises by watching video-like images taken by the Motion Indoor Photo Detectors (Cameras).
Administration of the We.R™ System Figure 176: Last Security Videos Selection Screen Where: Tapping over the button refreshes the displayed list of available videos and their related data (triggering device, time stamp, etc.). Tapping over the button terminate this Watch Video procedure and switches the display back to the Home Status Panic Alarm Screen (see Figure 175 above).
Administration of the We.R™ System Figure 177: Camera Display Screen The button at the bottom of the screen switches the display between video-like and freeze modes of display. The button sends the captured images to the User email address. Tapping over this button will pop-up the acknowledgement window: Figure 178: Sending Images to Email Acknowledgement Window Tapping over the 212 button will terminate the email operation. ™ We.
Administration of the We.R™ System Tapping over the button will send the images via email to the User. Upon completion, the following confirmation message window will pop-up: Figure 179: Email Confirmation Message Window Tapping over the button will conclude the send images by mail operation and return the screen to the Camera Display screen (see above Figure 177).
Administration of the We.R™ System This type of system usage is usually referred to as “Comfort Video”. 4.3.1. Monitoring with the We.R™ Web Application The center pan of the main screen (the Dashboard) data zone provides the means for comfort video: Figure 180: The Dashboard’s Camera Presentation The bottom half of the center pane presents all system available cameras, out of which the desired camera need to be selected by clicking once over its icon.
Administration of the We.R™ System To see these images in video-like mode, click over the button. It will run the images for about 40 seconds, in sequential mode, providing realistic monitoring of the premises. Figure 181: Camera’s Captured Images Presentation Once clicked upon, the presentation. 4.3.2. button turns into a button allowing the User to halt the Monitoring with the We.R™ Mobile Application Similar to the We.R™ Web Application, the Video Tab/screen of the We.
Administration of the We.R™ System Figure 182: The Take Video Screen To refresh the Available Cameras list – tap over the button. Tapping over one of the cameras in the list selects the camera and switches the screen into a camera display screen presenting the view in front of the camera: Figure 183: Comfort View of Camera 216 ™ We.
Administration of the We.R™ System The button at the bottom of this screen is the Play/Pause switch. Tapping over the button will terminate the comfort video session. The images presented by the comfort view may be sent to the email address provided during the We.R™ Mobile Application Registration procedure by clicking over the button.
Administration of the We.R™ System Tapping over the button will terminate the email process and return the ™ We.R Mobile Application to the Comfort View of Camera screen (see above Figure 183) where tapping over the button will terminate the comfort video session and return the display to the Home Status (Main) screen. 4.4. Managing Users Note: Managing Users is possible only through the We.R™ Web Application and by Master User only. The We.
Administration of the We.R™ System c) Maximum total of 32 Users are supported by a single system (the two Masters included). 2. Is the User going to use a Remote Control Unit (Key Fob) or a Tag to activate the system? 3. Does this User has a smartphone and is he going to use the We.R™ Mobile Application? 4. What language does this User need for his notifications and push-messages? Also, there is a need to prepare password and User Code for this User. 4.4.2.
Administration of the We.R™ System To add a new User, click over the button. A new empty row will open in the left pane while its empty data fields – in the right pane. Type-in the User’s data as follows: The User name. The User Email address (for notifications). Figure 187: The Users Page Data Pane The User Password (minimum of six alpha-numeric characters, case sensitive). This password needs to be re-typed in the next row for confirmation. The User Profile – select Standard or Master.
Administration of the We.R™ System Once all the above data fields have been filled; click over the button to store the new data into the system configuration files. The new empty row opened on the left pane will display the User name and type once the new User data is accepted by the system. Note: Assigning Remote Control Unit (Key Fob) or a Tag to this User is done via the Devices page (see paragraph 4.5. below). 4.4.3.
Administration of the We.R™ System 4.5. Managing Devices Note: Managing Devices is possible only with the We.R™ Web Application. The We.R™ system requires detailed definition of the Devices included in the system. 4.5.1. Adding New Devices Note: Adding Devices is possible only by a Master User utilizing the We.R™ Web Application. New Devices may be added (up to the system’s limitation, see Table 5 on page 194), to the system at any time following its initial installation.
Administration of the We.R™ System 2. The Device to be installed should be selected out of the menu list. 3. Once selected, the Add New Device window will pop-up and its timer will start running. 4. Use this window’s title to verify that the Device Type is the type selected from the roll-down menu. Figure 189: Add New Device Timer Window 5. The down-counter provides a time-frame of three (3) minutes within which the batteries should be installed to power-up the Device.
Administration of the We.R™ System Figure 190: Add New Device Timeout Error Message Click over the button to re-initiate the Add New Device process. Clicking over the button will terminate the Add New Device process. 8. If the new Device was properly detected by the CCU, the counter will freeze and a Device Properties sub-window will appear where the Device’s system name/location needs to be typed-in as well as other features’ data (see paragraph 4.5.3 below) upon clicking over the button. 9.
Administration of the We.R™ System A Device may be removed by selecting its row in the left pane of the Devices page and clicking over the 4.5.3. button. Editing Devices’ Properties Note: Editing Devices’ properties is possible only by a Master User and with the We.R™ Web Application. The We.R™ Web Application also enables editing of Devices already installed. The editable data include the Device’s Name/Location as well as the Devices’ operational data (Arming/Disarming Scenarios and special features).
Administration of the We.R™ System Name/Location Arm Scenarios Disarm Scenarios Special Features Figure 191: Right Pane of Door/Window Magnetic Sensor Once all Device definitions are provided, the store the data in the system. button needs to be clicked upon to Advanced Configurations of the We.R™ Devices 4.5.4. 4.5.4.1. Entry/Exit This feature provides the owner with time gap to arm (or disarm) the system while entering (or exiting) the premises without triggering an alarm.
Administration of the We.R™ System In case the system was not disarmed within the 30 seconds delay period – an alarm will be triggered and a burglary alarm flow will start (notifications, emails etc.) A premises exit delay of 30 seconds will be triggered only once the system was armed via a Tag Reader. This delay allows the User to arm the system and leave the premises without triggering an alarm on the way out.
Administration of the We.R™ System Once the Walk-Through feature is enabled: Throughout the 30 seconds delay period of an Entry/Exit configured device, the device configured as Walk-Through will trigger an alarm only if triggered before the device defined as Entry/Exit. The detection of the Walk-Through device will be logged in the Recent Events report. In case of Entry/Exit – if the system is not disarmed within the 30 seconds delay period, the Walk-Through device will trigger an alarm.
Administration of the We.R™ System Once the Chime feature is enabled: Whenever the system is disarmed, the Siren will emit a bell-like sound whenever the Magnetic Sensor is opened. Common use of the Chime feature – if a Magnetic For Users who likes to get an audible warning upon a door being opened (i.e. in small shops/offices). ™ We.
Administration of the We.R™ System This page was intentionally left blank 230 ™ We.
Maintenance of the We.R™ System 5. Maintenance of the We.R™ System The We.R™ system is almost maintenance-free; the only maintenance-oriented activities required for its continuous operation are: 1. Replacing Batteries – an indication of the need for batteries replacement is provided by both the We.R™ Web Application and the We.R™ Mobile Application utilizing their different status displays. 2.
Maintenance of the We.R™ System Figure 192: Releasing the Back Cover Figure 193: Removing the Battery 232 ™ We.
Maintenance of the We.R™ System 5.1.1.2. Installing a New Battery 1. Insert the new backup battery into the battery compartment, above the SIM-card, as demonstrated in Figure 194 below: Note: Battery’s label should be facing up and the battery’s contacts should be aiming towards the base of the CCU. Figure 194: Insertion of the Backup Battery 2. Return the battery cover back to place and click it firmly in. 3.
Maintenance of the We.R™ System 5.1.2. Replacing the Camera (IPD) Batteries For its operation, the Camera needs three (3) 1.5V AA-size Alkaline batteries (not supplied with the Camera). Note: Rattling sounds might be heard during the batteries’ replacement process. Nothing to worry about – it is the tampering prevention mechanism. 5.1.2.1. Removing the Old Batteries Figure 195: Dismounting the Camera 234 ™ We.
Maintenance of the We.R™ System To replace the old batteries of the Camera, first, there is a need to dismount it from its install site (the wall). 1. To dismount the Camera, press the wall mounting base's tab at the bottom of the Camera and slide it downwards simultaneously as demonstrated in Figure 195 above. 2.
Maintenance of the We.R™ System 2. Close the inner batteries’ cover and click it back to place. 3. Return the Camera back onto its mounting base. The insertion of batteries into the Camera triggers a bonding process in which the Camera communicates with the CCU to re-instate it into the CCU peripherals’ inventory. Note: There is no need to perform “Add Device” process following batteries replacement since the Camera is already defined in the We.R™ system.
Maintenance of the We.R™ System Figure 198: Dismounting the Motion Detector 2. The batteries’ (back) cover is the mounting base of the Motion Detector therefore dismounting it also reveals the Motion Detector batteries compartment. 3. Remove the batteries by pressing them slightly towards the negative (–) pole (towards the bottom end of the Motion Detector) and extracting them out, one at a time. 5.1.3.2. Installing New Batteries 1.
Maintenance of the We.R™ System Figure 199: Inserting Batteries into the Motion Detector 2. Return the Motion Detector back onto its mounting base. The insertion of batteries into the Motion Detector triggers a bonding process in which the Motion Detector communicates with the CCU to re-instate it into the CCU peripherals’ inventory. Note: There is no need to perform “Add Device” process following batteries replacement since the Motion Detector is already defined in the We.R™ system.
Maintenance of the We.R™ System 1. Insert a flat screw driver (or coin) into one of the edge slots as demonstrated in Figure 200 below. 2. Twist it to raise the cover (body) edge. 3. Pull the body strait out of the base’s shoulders. Figure 200: Dismounting the Magnetic Sensor’s Transmitter 5.1.4.2. Removing the Old Battery Once opened, the Magnetic Sensor’s battery is free to be removed out of the case.
Maintenance of the We.R™ System Figure 201: Inserting a Battery into the Transmitter Unit The insertion of battery into the Magnetic Sensor triggers a bonding process in which the Magnetic Sensor communicates with the CCU to re-instate it into the CCU peripherals’ inventory. Note: There is no need to perform “Add Device” process following battery replacement since the Magnetic Sensor is already defined in the We.R™ system. 5.1.5.
Maintenance of the We.R™ System Figure 202: Dismounting the Siren 2. The mounting base (back cover) of the Siren is the batteries’ cover as well and, therefore, dismounting the Siren also reveals its batteries compartment. 3. Remove the batteries by pressing them slightly towards the negative (–) pole (note that each battery is in opposite direction to the adjoining battery) and extracting them out, one at a time. 5.1.5.2.
Maintenance of the We.R™ System To discharge the Siren, insert the back cover’s tab into the niche at the bottom of the batteries’ compartment as demonstrated in Figure 203 below. Figure 203: Discharging the Siren’s Electronic Circuit 1. Install the new batteries as demonstrated in Figure 204 below. Note: Each battery is in opposite direction to the adjoining battery and the correct polarity is engraved onto the bottom of the batteries’ compartment. 2. Return the Siren back onto its mounting base.
Maintenance of the We.R™ System Figure 204: Inserting Batteries into the Siren The insertion of batteries into the Siren triggers a bonding process in which the Siren communicates with the CCU to re-instate it into the CCU peripherals’ inventory. Note: There is no need to perform “Add Device” process following batteries replacement since the Siren is already defined in the We.R™ system. 5.1.6.
Maintenance of the We.R™ System 5.1.6.1. Removing the Old Battery 1. Release the cover of the KF battery compartment by inserting a coin into the slot and turning the cover a quarter of a circle (90o) counter-clockwise until the two small bumps face each other as demonstrated in Figure 205 below. Figure 205: Releasing the KF’s Battery Cover 2. Remove the cover by tapping it upside-down on your palm. 3. Remove the old battery. 5.1.6.2.
Maintenance of the We.R™ System Figure 206: Inserting the New KF’s Battery Note: There is no need to perform “Add Device” process following battery replacement since the KF is already defined in the We.R™ system. 5.1.7. Replacing the Tag Reader (TR5) Batteries For its operation, the Tag Reader needs three (3) 1.5V AA-size Alkaline batteries. 5.1.7.1. Removing the Old Batteries To replace the old batteries of the Tag Reader, first, there is a need to dismount it from its install site (the wall). 1.
Maintenance of the We.R™ System Figure 207: Dismounting the Tag Reader Note: The Tags are passive components and need no power source (battery). Therefor there is no maintenance required for the Tags. 5.1.7.2. Installing New Batteries 1. Install the new batteries as demonstrated in Figure 208 below. Note that the correct polarity is engraved onto the bottom of each of the batteries’ compartment. 246 ™ We.
Maintenance of the We.R™ System Figure 208: Inserting Batteries into the Tag Reader 2. Return the Tag Reader back onto its mounting base. The insertion of batteries into the Tag Reader triggers a bonding process in which the Tag Reader communicates with the CCU to re-instate it into the CCU peripherals’ inventory. Note: There is no need to perform “Add Device” process following batteries replacement since the Tag Reader is already defined in the We.R™ system. 5.1.8.
Maintenance of the We.R™ System Figure 209: Dismounting the Flood Detector’s Transmitter 5.1.8.1. Removing the Old Battery Once opened, the Flood Detector’s battery is free to be removed out of the case. Apply slight pressure on the battery towards the negative (–) pole to ease the release of the battery. 5.1.8.2. Installing a New Battery 1.
Maintenance of the We.R™ System 2. Verify battery polarity match to marking within the unit body. 3. Return the cover onto the base and click it in. The insertion of battery into the Flood Detector triggers a bonding process in which the Flood Detector communicates with the CCU to re-instate it into the CCU peripherals’ inventory. Note: There is no need to perform “Add Device” process following battery replacement since the Flood Detector is already defined in the We.R™ system. 5.1.9.
Maintenance of the We.R™ System 3. Pull the body strait out of the base. Figure 211: Dismounting the Smoke Detector 5.1.9.2. Removing the Old Batteries Remove the batteries by pressing them slightly towards the negative (–) pole and extract them out, one at a time. 250 ™ We.
Maintenance of the We.R™ System 5.1.9.3. Installing New Batteries 1. Install the new batteries as demonstrated in Figure 212 below. Note that the correct polarity is engraved onto the bottom of each of the batteries’ compartment. Figure 212: Inserting Batteries into the Smoke Detector 2. Return the Smoke Detector back onto its mounting base.
Maintenance of the We.R™ System 5.1.10.1. Dismounting the Universal Transmitter There is a need to dismount the Universal Transmitter (Transmitter unit only) to allow replacement of the battery. To dismount the Universal Transmitter: 1. Insert a flat screw driver (or coin) into one of the edge slots as demonstrated in Figure 213 below. 2. Twist it to raise the cover (body) edge. 3. Pull the body strait out of the base’s shoulders. Figure 213: Dismounting the Universal Transmitter’s Transmitter Unit 5.
Maintenance of the We.R™ System 5.1.10.3. Installing a New Battery 1. The battery should be installed, as demonstrated in Figure 214 below (the positive () pole as marked within the device body): Figure 214: Inserting a Battery into the Transmitter Unit 2. Verify battery polarity match to marking within the unit body. 3. Return the cover onto the base and click it in.
Maintenance of the We.R™ System 5.2. Cleaning the System Devices The Smoke Detector’s sensor is protected from dust and other particles with a metal filter. This filter accumulates dirt which must be removed periodically Carefully remove any dust residing on the Smoke Detector's components applying special attention to the openings of the detection chamber.
Security Aspects 6. Security Aspects 6.1. Secured Communication between User and Application Server Authentication: Mobile authentication is performed via email, password and User Code for the activation of the Mobile Application. Password and User codes are encrypted on the mobile handset utilizing SHA1 algorithm. The encrypted value is calculated and sent as identifying credentials.
Security Aspects This page was intentionally left blank 256 ™ We.
Security Aspects 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. Also called Tri-Band 3G. This is a set of standards used for mobile devices and mobile telecommunication services and networks that comply with the International Mobile Telecommunications-2000 (IMT-2000) specifications issued and maintained by the International Telecommunication Union.
Terms, Abbreviations and Acronyms Term Description C2DM Android Cloud to Device Messaging. C2DM, which is now deprecated (GCM replaces the beta version of Android C2DM), is a push notification service that helps developers send data from servers to their applications on Android devices and launched together with Android 2.2 by Google. An Essence Term. A We.R™ system Central Control Unit. Also referred to as Control Panel (CP). An Essence Term. Control Panel. See Central Control Unit (CCU).
Security Aspects Term Description ECS An Essence Term. Essence Connect Server. Enhanced Data rates for GSM Evolution. Also known as Enhanced GPRS (EGPRS), or IMT Single Carrier (IMT-SC), or Enhanced Data rates for Global Evolution. This is a digital mobile phone technology that allows improved data transmission rates as a backward-compatible extension of GSM. An Essence Term. The protocol used to send encrypted messages between We.R™ CCUs and the We.R™ servers. Federal Communications Commission.
Terms, Abbreviations and Acronyms 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. Hypertext Transfer Protocol. This is an application protocol developed for distributed, collaborative, hypermedia information systems.
Security Aspects Term Description LAN Local Area Network. A computer network interconnecting computers in a limited area (i.e. home, laboratory or office) using network media. Light Emitting Diode. An Essence Term. Local Software Update. An Essence Term. A We.R™ system Indoor window/door Magnetic Sensor peripheral device. Militarized Zone. See DMZ. Network Address Translation. Software process of modifying IP address information in IPv4 (IP version 4.
Terms, Abbreviations and Acronyms Term Description Replicate A Z-Wave® Term. To transfer or copy the setup and configuration information between a handheld Primary Controller and a Secondary Controller. 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. A Z-Wave® Term.
Security Aspects Term Description SK2 An Essence Term. A We.R™ system Smoke Detector peripheral device. 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. Short Message Service. A text messaging service component of phone, web, or mobile communication systems.
Terms, Abbreviations and Acronyms Term Description Status Reply A Z-Wave® Term. The process of a device transmitting its current state (ON, OFF, DIM, etc.) in response to an individual node or unit change command from a controller. At the present time, Z-Wave® devices ONLY respond with their status to the specific controller which generated the command for their change. Secondly, Z-Wave® devices DO NOT respond with their status when a Group or Scene command is issued.
Security Aspects Term Description UTC Universal Time Coordinated. This is the primary time standard by which the world regulates clocks and time. It is one of several closely related successors to Greenwich Mean Time (GMT). URL Uniform Resource Locator. Also known as Web Address. A specific character string that constitutes a reference to a resource. In most web browsers, the URL of a web page is displayed on top inside an address bar. An example of a typical URL would be "http://en.example.
Terms, Abbreviations and Acronyms Term Description XML Extensible Markup Language. A markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. Table 6: Terms, Abbreviations and Acronyms 266 ™ We.
Security Aspects Appendix B End User License Agreement (EULA) Definitions The following terms will have the meaning ascribed to them in this EULA: "The Company": Essence Security International (E.S.I.) Ltd. "The System": Security systems 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.
End User License Agreement (EULA) c. As a condition to using the Application and/or the Service, you agree that certain updates, upgrades and/or patches to the Application may be automatically received and installed on your system from time to time, and the Company will attempt to ensure that the interference to your daily use of the application by such installments is kept to a necessary minimum. d.
Security Aspects 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 and/or the Service being accessed and/or used by unauthorized user/s. c. TERMINATION: The License is effective until terminated by you or by the Company by written notice.
End User License Agreement (EULA) WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE APPLICATION AND/OR THE SERVICE 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 SERVICE PROVIDER. USAGE OF THE APPLICATION MAY REQUIRE DOWNLOADING AND INSTALLMENT OF THIRD PARTY SOFTWARE (E.G.
Security Aspects (EXCLUDING THE VIDEO SEGMENTS). HOWEVER, THE COMPANY WILL NOT REVIEW OR LET OTHER PARTIES REVIEW THE VIDEO SEGMENTS, WITHOUT YOUR PRIOR CONSENT, EXCLUDING DISCLOSURE THAT IS REQUIRED BY LAW, REGULATION OR ORDER OF A COMPETENT AUTHORITY. f.
End User License Agreement (EULA) acknowledge that your We.R™ security 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.
Security Aspects of any cause whatsoever, regardless of whether or not such loss, damage, or personal injury was caused by or contributed to by Company's negligence to any degree or failure to perform any obligation or strict products liability, such liability will be limited to an amount equal to six (6) times the monthly payment paid by you to Company at the time such liability is fixed, or to the sum of $250.00, whichever is greater.
End User License Agreement (EULA) all documents incorporated by reference. At all times, you can find the most recent version of this License at http://www.essence-grp.com/vault/documents/EULA.pdf .The Company may change this License by posting a new version and sending you notice by e-mail (to the address listed with the Company). Use of the Application or Service after such change constitutes acceptance of such changes. b.
Security Aspects Terms and Conditions. ADDENDUM A – PRIVACY POLICY Essence Security International (E.S.I.) Ltd.
End User License Agreement (EULA) 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 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.
Security Aspects 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.
End User License Agreement (EULA) This page was intentionally left blank 278 ™ We.
Security Aspects Appendix C Technical Specifications Central Control Unit (CCU) – ES8000CP Communication Maximum RF range 600m (1968ft.) open air ECOP bi-directional radio protocol Modulation and Frequency: DSSS, 2.
Technical Specifications Certification FCC Y4I-ES8000CP YXG-ES8000GP IC Comments 11061A-ES8000GP no cellular version cellular (3G) version Motion Indoor Photo Detector (IPD) – ES800IPD Communication Maximum RF range 500m (1640ft.) open air ECOP bi-directional radio protocol Modulation and Frequency: DSSS, 2.
Security Aspects Diagonal shooting angle: 67o Shooting Range – up to 10m (32.8ft.) Power Consumption Efficient power consumption to extend the operation period Three (3) AA-size alkaline batteries Up to one year batteries’ lifetime Optional 5VDC power adaptor Size and Weight H: 60mm (2.36in.), L: 122.7mm (4.84in.), W: 58mm (2.36in.) Weight – 160 grams (0.35lbs.) + 45 grams (0.1lbs.
Technical Specifications Security 4G DragonFlyEye™ technology Tamper Alarm – when unit is tilted Data Security – 128-bit AES encryption Unique electronic serial number Supports automatic over-the-air software upgrade (RSU) programming and configuration Temperature compensation for the PIR element Optional up to 30 Kg (66lb.) pet immune lens Detecting Range – up to 12m (39.4ft.
Security Aspects Door/Window Magnetic Sensor (MGL) – ES800MGL Communication Maximum RF range 500m (1640ft.) open air ECOP bi-directional radio protocol Modulation and Frequency: DSSS, 2.
Technical Specifications Certification FCC IC Y4I-M800MGL 11061A-ES800MGL Comments Indoor Siren (SRN) – ES800SRN Communication Maximum RF range 500m (1640 ft.) open air ECOP bi-directional radio protocol Modulation and Frequency: DSSS, 2.
Security Aspects Operating Ambient Temperature range with battery: 0oC – +50oC (32oF – +122oF) RF transmitter humidity: Up to 95% non-condensing Certification FCC IC Y4I-M800SRN 11061A-ES800SRN Comments Remote Control Unit (KF) – ES800KF Communication Maximum RF range 600m (1968ft.) open air ECOP bi-directional radio protocol Modulation and Frequency: DSSS, 2.
Technical Specifications Operating Ambient Temperature range with battery: -5oC – +55oC (23oF – +131oF) Humidity: Up to 95% non-condensing Certification FCC IC Y4I-M801EKF 11061A-ES800KF Comments Wireless Access Control Tag Reader (TR5) – ES800TR5 Communication Maximum RF range 500m (1640ft.) open air ECOP bi-directional radio protocol Modulation and Frequency: DSSS, 2.4GHz RFID band: ISO 14443A/MiFare, 106kbps, 13.
Security Aspects Weight – 135 grams (0.3lbs.) + 45 grams (0.1lbs.) batteries Tag – H: 9.9mm (0.39in.), L: 46.7mm (1.84 in.), W: 33.4mm (1.31in.) Weight – 10 grams (0.02lbs.) Environment Storage Ambient Temperature range: -20oC – +50oC (-4oF – +122oF) Operating Ambient Temperature range with battery: 0oC – +50oC (+32oF – +122oF) RF transmitter humidity: Up to 95% non-condensing Certification FCC IC Comments YXG-ES800TR5 11061A-ES800TR5 (In lab.
Technical Specifications Up to two years battery’s lifetime Size and Weight RF Transmitter size – H: 29.2mm (1.15in.), L: 71.9mm (2.83in.), W: 24.6mm (0.97in.) Weight – 25 grams (0.55lbs.) + 15 grams (0.33lbs.) battery Detector size – H: 22.4mm (0.88in.), D: 49.9mm (1.96in.) Weight – 25 grams (0.55lbs.) Cable length – 30cm (11.8in.
Security Aspects Data Security – 128-bit AES encryption Unique electronic serial number Supports automatic over-the-air software upgrade (RSU) programming and configuration Power Consumption Efficient power consumption to extend the operation period Two AA-size alkaline batteries Over two years battery’s lifetime Size and Weight H: 46.7mm (1.84in.), Diameter: 135mm (5.32in.) Weight – 210 grams (0.46lbs.
Technical Specifications Modulation and Frequency: DSSS, 2.4GHz Security Data Security – 128-bit AES encryption Unique electronic serial number Supports automatic over-the-air software upgrade (RSU) programming and configuration Power Consumption Efficient power consumption to extend the operation period One AA-size alkaline battery Up to two years battery’s lifetime (based on usage) Size and Weight H: 29.3mm (1.15in.), L: 71.9mm (2.83in.), W: 24.6mm (0.97in.) Weight – 25 grams (0.
Security Aspects Z-Wave® Controller (ZWD) – ES800ZWD Communication Maximum RF range 500m (1640ft.) open air Z-Wave® bi-directional radio protocol (onboard) Frequency: 868.4/908.4/921.4MHz Bit Rate: 9.6/40kbps Security Data Security – 128-bit AES encryption Unique electronic serial number Power Consumption Efficient power consumption to extend the operation period Size and Weight Z-Wave® controller: H: 5mm (0.2in.), L: 58mm (2.28in.), W: 24mm (0.94in.) Cable length: 15cm (5.9in.
Technical Specifications This page was intentionally left blank 292 ™ We.
Security Aspects Appendix D Port Checking To check the availability of port 43001, exercise the following steps: 1. Click over the Start button. a) Click over the Run menu option. b) Type: “cmd” in the command box. Figure 216: Staring a COMMAND mode (cropped) c) Press the Enter key. The Terminal screen's Window will open. Figure 217: COMMAND Window (cropped) d) Type “telnet wersys.com 43001” in the command line. ™ We.
Port Checking Figure 218: Telnet Search Command e) Press the Enter key. If the port check is successful, a blank window will open. Figure 219: Telnet Blank Window If the port check is not successful – an error message will pop-up. This means that port 43001 is blocked and needs to be opened on the router. To unblock the port please refer to the router's configuration documentation.
Security Aspects Appendix E Enable Telnet Program in Windows 7 and 8 Exercise the following steps to enable the Telnet Program: 1. Click over the Start button. 2. Click over the Central Control Unit menu option. 3. Click over the Programs and Features icon. 4. Click over the Turn Windows features on or off menu option. The Turn Windows features on or off dialog window will open. Note: If prompted for an administrator password or confirmation, type the password and/or confirm the action. 5.
Enable Telnet Program in Windows 7 and 8 This page was intentionally left blank 296 ™ We.
Security Aspects Appendix F Screws and Dowels Except for the Central Control and its Remote Control Units, as well as the Z-Wave® Controller, all We.R™ devices have the option to be installed with screws (not the pre-attached doublesided tapes). The following Table 7 is a summary of Essence recommendations regarding these optional parts.
Screws and Dowels This page was intentionally left blank 298 ™ We.
Security Aspects Appendix G Pairing and Bonding Motivation Many of the services offered over wireless communication such as Bluetooth® and Z-Wave® can expose private data or allow the connecting party to control the involved devices. For security and reliability reasons it is necessary to be able to recognize specific devices and thus enable control over which devices are allowed to connect to a given device.
Pairing and Bonding Wireless services generally require either encryption or authentication, and as such require pairing before they allow a remote device to use the given service. Some services, such as the Object Push Profile, elect not to explicitly require authentication or encryption so that pairing does not interfere with the user experience associated with the service use-cases. 300 ™ We.
Security Aspects Appendix H Owner’s Records This appendix was added for the system owner to concentrate all records of the system. Item Data CCU Serial Number User Email User Password User Name User Mobile Phone Number User Code for We.R™ Mobile Application APN Name APN User APN Password SIM-Card Telephone Number Table 8: Owner’s Records ™ We.
Owner’s Records This page was intentionally left blank 302 ™ We.
