Remote Access - Revision history

71.237.248.220 at 02:09, 21 May 2015

2015-05-21T02:09:31Z

204.10.16.29: /* Talking to your remote AlarmDecoder */

2014-01-07T19:11:40Z

‎Talking to your remote AlarmDecoder

204.10.16.29: /* How do I set up remote access with the AlarmDecoderGUI? */

2014-01-07T19:11:23Z

‎How do I set up remote access with the AlarmDecoderGUI?

204.10.16.29 at 19:10, 7 January 2014

2014-01-07T19:10:46Z

204.10.16.29: /* Can I remotely access my AlarmDecoder? */

2013-12-20T21:39:53Z

‎Can I remotely access my AlarmDecoder?

204.10.16.29 at 21:38, 20 December 2013

2013-12-20T21:38:59Z

204.10.16.29 at 21:33, 20 December 2013

2013-12-20T21:33:58Z

204.10.16.29 at 21:32, 20 December 2013

2013-12-20T21:32:40Z

204.10.16.29: Created page with "Category:Documentation Category:FAQ =Can I remotely access my AlarmDecoder?= You sure can! There are currently two ways to do so: using [http://github.com/nutechsoft..."

2013-12-20T21:32:09Z

Created page with "Category:Documentation Category:FAQ =Can I remotely access my AlarmDecoder?= You sure can! There are currently two ways to do so: using [http://github.com/nutechsoft..."

New page

[[Category:Documentation]]
[[Category:FAQ]]

=Can I remotely access my AlarmDecoder?=
You sure can! There are currently two ways to do so: using [http://github.com/nutechsoftware/ser2sock ser2sock] or the [[AlarmDecoderGUI]]. It's also likely possible with another Serial-to-IP interface, though this is untested.

We generally recommend using [http://github.com/nutechsoftware/ser2sock ser2sock] to expose your AlarmDecoder. Currently this only works under Linux and OSX, so you'll need to use the [[AlarmDecoderGUI]] if you need to do so under Windows. By using [http://github.com/nutechsoftware/ser2sock ser2sock] it also gives you the ability to use the built-in SSL encryption and authentication.

=How do I set up remote access with ser2sock?=
# Grab a copy of [http://github.com/nutechsoftware/ser2sock ser2sock].
#* <tt>git clone http://github.com/nutechsoftware/ser2sock.git</tt>
# Read the INSTALL file for installation and configuration instructions.
# Confirm that [http://github.com/nutechsoftware/ser2sock ser2sock] is working:
#* <tt>telnet localhost 10000</tt>

=How do I set remote access with the AlarmDecoderGUI?=
# Install a copy of the [[AlarmDecoderGUI]].
# Open and click <tt>System -> Configure</tt>.
# Check the ''Serial Port Enabled'' box and fill in your device name. This can be either something like <b>COM1</b> for Windows, or <b>/dev/ttyUSB0</b> for Linux/OSX.
# Check the ''Socket Server Enabled'' box.
# Click OK.
# Confirm that the AlarmDecoderGUI is functioning:
#* <tt>telnet localhost 10000</tt>

=Talking to your remote AlarmDecoder=
At this point your device should be working so you can connect to it a couple of ways.

* [[AlarmDecoderGUI]]
*# Open <tt>System -> Configuration</tt>
*# Check ''Socket Client Enabled''.
*# Fill in hostname and port.
*# Optional: Enable secure socket (SSL) support. See [[SSL]] for more information.
*# Click OK.
* [http://github.com/nutechsoftware/alarmdecoder Python API]
*# See the <tt>examples/socket_example.py</tt> and <tt>examples/ssl_example.py</tt>.
* AlarmDecoder Android app - Coming Soon!

← Older revision		Revision as of 02:09, 21 May 2015
Line 8:		Line 8:

	This is currently possible by using either [http://github.com/nutechsoftware/ser2sock ser2sock] or the [[AlarmDecoder_Keypad\|AlarmDecoder Keypad]]. It'll also likely work with another Serial-to-IP interface though this is untested.		This is currently possible by using either [http://github.com/nutechsoftware/ser2sock ser2sock] or the [[AlarmDecoder_Keypad\|AlarmDecoder Keypad]]. It'll also likely work with another Serial-to-IP interface though this is untested.
		+
		+	There is also the [[AlarmDecoder_WebApp\|AlarmDecoder WebApp]] which works in a web browser, including browsers on phones and tablets.

	We generally recommend using [http://github.com/nutechsoftware/ser2sock ser2sock] to expose your AlarmDecoder since it also gives you the ability to use the built-in SSL encryption and authentication. See [[SSL]] for more information on SSL support. Currently this only works under Linux and OSX, so you'll need to use the [[AlarmDecoder_Keypad\|AlarmDecoder Keypad]] if you need remote access via Windows.		We generally recommend using [http://github.com/nutechsoftware/ser2sock ser2sock] to expose your AlarmDecoder since it also gives you the ability to use the built-in SSL encryption and authentication. See [[SSL]] for more information on SSL support. Currently this only works under Linux and OSX, so you'll need to use the [[AlarmDecoder_Keypad\|AlarmDecoder Keypad]] if you need remote access via Windows.

@@ Line 7: / Line 7: @@
 You sure can!
-This is currently possible by using either  [http://github.com/nutechsoftware/ser2sock ser2sock] or the [[AlarmDecoderGUI]].  It'll also likely work with another Serial-to-IP interface though this is untested.
+This is currently possible by using either  [http://github.com/nutechsoftware/ser2sock ser2sock] or the [[AlarmDecoder_Keypad|AlarmDecoder Keypad]].  It'll also likely work with another Serial-to-IP interface though this is untested.
-We generally recommend using [http://github.com/nutechsoftware/ser2sock ser2sock] to expose your AlarmDecoder since it also gives you the ability to use the built-in SSL encryption and authentication.  See [[SSL]] for more information on SSL support. Currently this only works under Linux and OSX, so you'll need to use the [[AlarmDecoderGUI]] if you need remote access via Windows.
+We generally recommend using [http://github.com/nutechsoftware/ser2sock ser2sock] to expose your AlarmDecoder since it also gives you the ability to use the built-in SSL encryption and authentication.  See [[SSL]] for more information on SSL support. Currently this only works under Linux and OSX, so you'll need to use the [[AlarmDecoder_Keypad|AlarmDecoder Keypad]] if you need remote access via Windows.
 =How do I set up remote access with ser2sock?=

@@ Line 7: / Line 7: @@
 You sure can!
-There are currently two ways to do so: using [http://github.com/nutechsoftware/ser2sock ser2sock] or the [[AlarmDecoderGUI]].  It's also likely possible with another Serial-to-IP interface, though this is untested.
+This is currently possible by using either  [http://github.com/nutechsoftware/ser2sock ser2sock] or the [[AlarmDecoderGUI]].  It'll also likely work with another Serial-to-IP interface though this is untested.
 We generally recommend using [http://github.com/nutechsoftware/ser2sock ser2sock] to expose your AlarmDecoder since it also gives you the ability to use the built-in SSL encryption and authentication.  See [[SSL]] for more information on SSL support. Currently this only works under Linux and OSX, so you'll need to use the [[AlarmDecoderGUI]] if you need remote access via Windows.

@@ Line 31: / Line 31: @@
 At this point your device should be working so you can connect to it a couple of ways.
-* [[AlarmDecoderGUI]]
+* [[AlarmDecoder_Keypad|AlarmDecoder Keypad]]
 *# Open <tt>System -> Configuration</tt>
 *# Check ''Socket Client Enabled''.

@@ Line 18: / Line 18: @@
 #* <tt>telnet localhost 10000</tt>
-=How do I set up remote access with the AlarmDecoderGUI?=
+=How do I set up remote access with the AlarmDecoder Keypad?=
-# Install a copy of the [[AlarmDecoderGUI]].
+# Install a copy of the [[AlarmDecoder_Keypad|AlarmDecoder Keypad]].
 # Open and click <tt>System -> Configure</tt>.
 # Check the ''Serial Port Enabled'' box and fill in your device name.
@@ Line 25: / Line 25: @@
 # Check the ''Socket Server Enabled'' box.
 # Click OK.
-# Confirm that the AlarmDecoderGUI is functioning:
+# Confirm that the AlarmDecoder Keypad is functioning:
 #* <tt>telnet localhost 10000</tt>

@@ Line 1: / Line 1: @@
 [[Category:Documentation]]
 [[Category:FAQ]]
 =Can I remotely access my AlarmDecoder?=