Difference between revisions of "AlarmDecoder WebApp"

(Initial Setup)
(Add Users)
Line 78: Line 78:
  
 
==Add Users==
 
==Add Users==
 +
Coming soon..
 +
 +
==Configuring SSL==
 
Coming soon..
 
Coming soon..
  
 
==Disclaimers==
 
==Disclaimers==
 
; All other trademarks are the property of their respective owners.
 
; All other trademarks are the property of their respective owners.

Revision as of 14:43, 20 May 2015

Contents


AlarmDecoder WebApp

Overview

The official AlarmDecoder WebApp. Control your alarm system from your web browser on nearly any device. Supports all of the AlarmDecoder devices including the AD2USB, AD2SERIAL, and AD2PI.

Features

  • Multiple User Accounts
  • Web-based keypad for your alarm system
  • Notifications on alarm events
  • Per-user notifications
  • IP Camera integration
  • Supports all functionality of AlarmDecoder devices
  • Configure your AlarmDecoder device
  • Configure network sharing of your AlarmDecoder device

Installation

The easiest way to install the WebApp is by downloading our pre-built Raspbian image here. However, you can follow the manual installation instructions provided on our github repository here

Initial Setup

Once the AlarmDecoder WebApp is started you may connect to the Application via a web browser and pointing the URL to http://alarmdecoder.local - if this name resolution fails and you are on a Windows System, please download Bonjour For Windows and try again. This will take you to our first setup screens which will be detailed below. The device is initially configured for DHCP.

Setup Process Detail

This is your first setup screen when you first visit via your browser

First Setup Screen

Click "Start!" to continue


Next we will be taken to the device selection screen

Device Type Screen

Here you are able to select what type of device (AD2USB, AD2SERIAL, AD2PI) as well as the device's location.
  • #Local Device means the device is connected to the same computer running the WebApp
  • #Network Device means you have already exposed an AlarmDecoder via ser2sock


Local Device

If you choose Local Device, this next screen is what you are presented with

Local Device Settings

Here you will choose your device path and baud rate, usually defaults are fine for the device you chose
If you choose "Share AlarmDecoder on your network?" you will be taken to configure ser2sock shown below

Setup Ser2sock

On this screen you are able to specify the path to your ser2sock configuration file, your hostname or IP address to listen on, as well as the ser2sock port to listen on. Defaults will work fine. SSL will force ser2sock into SSL mode - this is typically not needed for your internal network.

#Configure Device


Network Device

If you chose network device instead of local device, you are presented with this screen instead

Network Device Setup

If you have an AlarmDecoder device shared on your network already via ser2sock, here you can specify the hostname and port for the WebApp to connect to the shared device.


Configure Device

Once you have told the WebApp what kind of device you have and where it is, you will be presented with a page to configure the AlarmDecoder device itself

AlarmDecoder Device Settings

Make sure to set your address correctly! 31 for SE Panels, and for 20P Panels you will have to program an address spot into your panel and assign the AlarmDecoder the newly enabled address. See [Panel Configuration]



After you have completed all of the above steps, you will be taken to a Device Testing screen

Device Testing

If any of these tests fail, please make sure your device is configured properly and installed properly.


Once the device is communicating properly, you will be redirected to a page to create an initial user to log in to the WebApp

Initial User Creation

After you have created your user, feel free to login and use the WebApp!

Configure Notifications

Coming soon...

Configure IP Cameras

Coming soon..

Add Users

Coming soon..

Configuring SSL

Coming soon..

Disclaimers

All other trademarks are the property of their respective owners.