User Guide. Hyperion Version 2.3

User Guide

Hyperion Version 2.3

United States FCC Approval

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

• Reorient or relocate the receiving antenna

• Increase the separation between the equipment and receiver

• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected

• Consult the dealer or an experienced radio/ TV technician for help

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions.

(1) This device may not cause harmful interference, and

(2) This device must accept any interference received, including interference that may cause undesired operation.

Warning: Changes or modifications not expressly approved by the party responsible.

Canada IC Approval

This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device.

Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and

maximum (or lesser) gain approved for the transmitter by Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary for successful communication.

French

Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes : (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.

Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pour l'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillage radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pas l'intensité nécessaire à l'établissement d'une communication satisfaisante.

FCC/IC Approved Antennas

This equipment uses the following Antennas and may not be used with other antenna types or with antennas of higher gain:

Manufacturer Part Number Type Gain (dBi)

Data Alliance A9D2RA Omni-directional 2

L-com HG908UP-NF Omni-directional 8

Wren Solutions HYP-HMG1WA2 Omni-directional 2.3

RF Exposure FCC

This equipment complies with FCC RF Exposure requirements and should be installed and operated with a minimum distance of 20cm between the radiator and any part of the human body.

IC

This equipment complies with the ICES RF radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with a minimum distance of 20cm between the radiator and any part of the human body.

Cet équipement est conforme aux limites d'exposition aux radiations ICES définies pour un environnement non contrôlé . Cet équipement doit être installé et utilisé à une distance minimale de 20 cm entre le radiateur et une partie de votre corps.

Contents

Product Overview ... 4

Hyperion Gateway Configuration ... 4

Gateway Discovery ... 4

Login ... 5

Network Settings ... 6

Date & Time ... 7

System Updates ... 7

Schedules ... 8

Users ... 10

Device Management and System Operations ... 10

Devices ... 10

External Devices ... 13

Audio ... 14

Automations ... 14

Reporting ... 17

Product Overview

Hyperion enables control of various input and output devices for intelligent, automated response to events. This document outlines the setup and configuration of the Hyperion application. For hardware setup instruction, refer to the product specific installation guides that are provided with the equipment.

Supported Browsers

The Hyperion app is accessed through a browser on a PC, Tablet or Phone. The following browsers and versions were certified for use with Hyperion at the time of the publication of this guide. Other browsers and versions may not present a seamless user experience.

Google Chrome PC Version 92.0.4515.131/ Tablet & Phone Version/ 92.0.4515.131 Mozilla Firefox PC Version 90.0.2 / Android Version 91.1.0/ iOS Version 36

Safari Tablet & Phone iOS Version 13.3.1 Samsung Internet Mobile Version 14.2.3.14

Hyperion Gateway Configuration

This section details the steps for an Administrator to configure the Hyperion Gateway on a local network, setup system schedules and manage users.

Gateway Discovery

The Hyperion application is hosted on the Hyperion Gateway. In order to access the app, users must connect a PC or mobile device to the same network as the gateway and login to Hyperion using a web browser. The gateway is configured at the factory with a wireless router that can be used to connect to Hyperion. It is also setup to use DHCP when connected to a network. Follow the steps below to locate and connect to the gateway through the network that matches the location configuration.

Stand Alone Gateway Configuration

Connect to Hyperion through the built-in wireless router on the Hyperion Gateway. This option is only available for Hyperion gateways that were equipped with version 2.3 from the factory.

1. Power on the Hyperion Gateway

2. Open the Wi-Fi Settings on a PC or Mobile device 3. Browse the available networks

4. Select Hyperion

5. Enter the password. The default password is provided with the gateway and can be changed by Admin users.

6. When the page loads to redirect to the Hyperion login page, select Continue.

7. This will open a browser to the Hyperion Login

page.

Local Area Network (LAN) Configuration

Connect to Hyperion through the local area network.

1. From a PC connected via ethernet to the gateway or to the same network segment, open a supported browser to http://hyperion

OR

1. Download the discovery tool from the following page:

https://www.wrensolutions.com/hyperion/hyperion- support/

2. Extract the files in the Discovery zip file to a folder on a PC

3. Attach the PC to the same network the gateway is plugged into (this can be a wired ethernet or Wi-Fi network)

4. Click on the hyperion-discover.exe file to launch the discovery tool 5. Click the Discover button

6. Click on the IP address next to the desired Hyperion host. This will open a browser to the Hyperion Login page.

Login

From the login screen, enter the user credentials provided with your Hyperion installation package or

assigned by the Hyperion administrator.

Network Settings

The gateway is configured at the factory to use DHCP when connecting to a network. Admin Users can optionally change to a static IP address and configure a Wi-Fi connection.

1. Login as an Admin User and open the Gateway Settings page.

2. From the Gateway Settings page, Admin Users can optionally enable SSL. Note: When enabling this option, all users will need to add the Hyperion certificate to their Trusted CA Authorities list to avoid security warnings in the browser.

3. Select Edit Network Settings to configure the Gateway’s network settings.

Wi-Fi Settings

The gateway is configured at the factory with a wireless router that can be used to connect to Hyperion. You can change the password or disable the router and configure the Wi-Fi for connection to a local wireless network.

1. Login as an Admin User and open the Gateway Settings page.

2. Select Edit Network Settings.

3. Click on the WiFi connection to configure the wireless options.

Backup & Recovery

The gateway creates a backup file nightly and stores it on the SD card in the gateway. Admin users can create additional backup files and download a local copy to a connected device to be used for disaster recovery or other restore options later.

The restore function returns the database to a previous state with all devices and system configurations.

If the Hyperion software was upgraded after a backup file was created, the Admin user will need to reapply the software update after the restore has been completed.

Date & Time

The gateway is configured at the factory to use NTP Servers to keep accurate time. Admin Users can optionally set a local time if the gateway will not be connected to external networks. Additionally the time zone preference can be updated for use in reports.

1. Login as an Admin User and open the Gateway Settings page. Select the desired settings and click Apply.

System Updates

Admin Users can view the current version of the software on the Gateway Settings page. From here, software updates can be administered.

Software Update

1. Login as an Admin User and open the Gateway Settings page

2. Click Update

3. Click Choose File and select the Hyperion update file. Note: The update will be a secured,

compressed file with a .zip extension. Do not extract.

4. Click the Update button to update the software.

The gateway will reboot during this process and

will return to the Login screen when update is

complete.

Open SSH Port

On rare occasions, it might be necessary to temporarily enable SSH on the gateway for troubleshooting purposes. An Admin User can turn on temporary access and the gateway will reset and close access after the time set.

1. Login as an Admin User and open the Gateway Settings page

2. Click Update

3. Click the option to Temporarily Turn SSH On and enter the desired time period.

4. Click the Apply to open the port.

The port will be open immediately and will close after the desired time period has passed. To force the port to close ahead of the time period expiration, reboot the gateway.

Schedules

Schedules are used in defining the operational periods for Hyperion automations. Automations can be activated by a time based period or external digital input.

From the Schedules menu, Administrators can view and manage schedules.

1. Click on the Schedules menu.

2. Click on the row of a named schedule to view or edit details.

Add Schedules

1. From the Schedules page, click Add to create a new schedule.

2. Enter a Name, an optional Description and select a Schedule Type.

Note: Schedules determine when Automations are active, similar to a traditional intrusion panel.

When not active, the input conditions will not set off the responses.

a. If time based, select and add time periods for each day of the week

b. If Input Triggered, select the Input Device, the active state and optionally add a delay after activation.

3. Click Add.

Users

From the Users menu, Admin Users can create and manage system users.

➢ Users with User permissions can view reports plus manage devices, audio files, and automations.

➢ Users with Administrator permissions have the same access as Users plus they can manage the gateway settings, users, and schedules.

Device Management and System Operations

This section provides the steps for Users to configure devices and set up system operations.

Devices

From this page, Users and Administrators can view and manage connected devices.

1. Click on the Devices Menu to view a list of Enabled, connected devices.

3. Click on the row of a device to view or edit device details.

4. From this page, you can view the device range, test device components and optionally,

disable/enable the device and individual device components. Some components like the Light Bar

and Strobes can be turned ON to always run.

Add Devices

Hyperion wireless devices utilize a 915 Mhz wireless signal to communicate with the local gateway.

Locate wireless devices to add and configure in the system.

1. Power on a Hyperion device and position it where desired.

2. From the Devices page, click Add to begin.

3. A. To add a wireless device, click on the row of a discovered wireless device from the list to add it.

B. To add a wired device, click Wired Device > type.

4. Enter the required information including the Type of device and Hyperion Port # for wired devices.

5. Click Add.

6. Repeat steps 2-5 to add additional devices.

External Devices

Hyperion can accept HTTP inputs from 3

party devices to be used as sources to activate Automations.

An example of an external device is a camera with a motion analytic setup. Hyperion can receive

messages from any device that is capable of sending an HTTP GET method. Follow the syntax guidelines below to setup the messages on the external device.

1. From Hyperion Devices page, click Add to begin 2. Click External Device > type

3. Enter the IP Address of the device, a Device Name, optional Description and click Add.

4. On the external device, configure the specific event, such as motion analytic, with the message syntax to match the following:

Address: http://{hyperiongatewayIP}/external GET Command: ?Input1=On

Full Message: http://{hyperiongatewayIP}/external?Input1=On

Audio

Add and manage audio files for use in audio channel output.

1. Click on the Audio menu to view a list of audio files stored on the gateway.

2. Click Add to upload new audio files.

3. Click Choose Files and select one or more .mp3 formatted files.

Note: .mp3 file format is required for all audio files.

4. Optionally, rename the files. Click Add.

System Volume: You can modify the default volume setting and test audio files under either Audio Channel from the Devices page.

Automations

Define conditional, escalating device responses. Automations can be triggered with manual response through a Push Button device and through automated detection of activity using input devices. All automations are tied to a schedule to determine the active periods for the conditional responses.

1. Click on the Automations menu.

2. Click on the row of a named automation to view or edit an automation.

Automations allow users to create two types of response:

Escalating response – Used with a conditional input device(s) to trigger a set of responses, increasing in severity of response with each stage until the condition is removed. The last stage is repeated until the condition is removed.

Independent, non-escalating response – Commonly used with manual response selection, Associates can select the appropriate response to a situation with a button selection on a 4 Button keypad.

Add Automation

1. From the Automations page, click Add to create a new automation.

2. Enter a Name, an optional Description and select a Schedule.

Note: Schedules must be configured by a user with Administrator permissions. Schedules determine when Automations are active, similar to a traditional intrusion panel. When not active, the input conditions will not set off the responses.

3. If an existing automation should take priority when active over the current automation, optionally select the automation under Priority Interrupt. This will stop the current automation if active when the priority automation goes active.

4. In Response – Stage 1, select one or more devices under If to trigger a response. If multiple devices are added, any one of the devices will trigger the related responses. It is an OR operation.

5. Select one or more responses under Then. If multiple devices are added, all will be activated simultaneously. It is an AND operation. If one or both Audio Channels are added, one audio file can be selected to play per stage.

+

6. Select the duration in seconds for all devices in the stage to respond.

7. To add an additional response option, click the + button.

The next response stage will default to utilizing the same input trigger(s) from Response – Stage 1 in an escalating response setup. Optionally, you can toggle this option off to setup an independent, non-escalating response.

8. Repeat step 6 until the automation is fully defined.

9. Optionally, add an expiration for the automation so that the system will stop an active automation after a defined amount of time or number of cycles. Note: the

automation can be retriggered after an expiration in the event of a new event based on a PIR Motion trigger or Digital Input state change.

10. Click Add.

Note: Installers can test escalating system responses by triggering the automation inputs even if the

set Schedule isn’t active. For example, if the schedule is based on an activated alarm panel and the

system is being configured and tested when the panel is not active, this feature would allow the entire

automation to be tested. Enable a Temporary Schedule in the Automation header for the desired

amount of time, then head out to trigger the responses. Users can monitor the amount of time

remaining on the temporary schedule from the automation header and reset the time as needed.

Reporting

Users can report on Automations, Device Status and System Events. Records can be exported from the app to be used for event investigations and reporting purposes. The Automation Summary shows the highest stages reached for each automation activation by date for the last 14 days.

1. From the Reports menu, view all recorded events.

2. Optionally use the Date and Type filters to narrow your search.

3. Click Download to export a file that includes the current filtered data in a .csv format.