(→Setup Process Detail) |
(→Setup Process Detail) |
||
| Line 27: | Line 27: | ||
[[File:01_initial_setup.png|600px|First Setup Screen]] | [[File:01_initial_setup.png|600px|First Setup Screen]] | ||
; Click "Start!" to continue | ; Click "Start!" to continue | ||
| + | |||
| + | |||
; Next we will be taken to the device selection screen | ; Next we will be taken to the device selection screen | ||
| Line 33: | Line 35: | ||
* Local Device means the device is connected to the same computer running the WebApp | * 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 | * Network Device means you have already exposed an AlarmDecoder via ser2sock | ||
| + | |||
| + | |||
| + | |||
| + | ; If you choose Local Device, this next screen is what you are presented with | ||
| + | [[File:03_local_device_settings.png|600px|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 | ||
| + | [[File:04_ser2sock_configuration.png|600px|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. | ||
| + | |||
| + | |||
| + | |||
| + | ; If you chose network device instead of local device, you are presented with this screen instead | ||
| + | [[File:05_network_device_settings.png|600px|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 Notifications== | ==Configure Notifications== | ||
Revision as of 11:23, 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.
Setup Process Detail
- This is your first setup screen when you first visit via your browser
- Click "Start!" to continue
- Next we will be taken to the device selection 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
- If you choose Local Device, this next screen is what you are presented with
- 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
- 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.
- If you chose network device instead of local device, you are presented with this screen instead
- 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.