Changes between Version 23 and Version 24 of WikiStart

Timestamp:

2012-02-29 16:34:49 (12 years ago)

Author:

guessed

Comment:

Fix the CamelCase escaping.

WikiStart

@@ -12 +12 @@
 '''WARNINGS: 
 * This plug-in ''will probably not'' work with the "UI3" (versions 1.1.x) of Vera's firmware.
-* If the Plugin is updated from the files contained here >0.35, or if it automatically updates from an app store based version, then it will change the device ID's of any sensors that are set up as "D\doorZones"
+* If the Plugin is updated from the files contained here >0.35, or if it automatically updates from an app store based version, then it will change the device ID's of any sensors that are set up as "!DoorZones"
   The above will only be a problem if these doorZone sensors have been set up at all as triggers for scenes, and these will have to reset after updating
   To avoid the above scenario the following changes should be made prior to updating:
@@ -44 +44 @@
 * Direct Connection to a USB to RS232 serial adapter thats supported by Vera such as [http://www.futureelectronics.com/en/Technologies/Product.aspx?ProductID=UC232R10FUTURETECHNOLOGYDEVICES2297802 this ] one.
 * Wired Ethernet Connection via an IP to RS232 serial adapter such as WIZnet device like [http://www.sparkfun.com/commerce/product_info.php?products_id=9476 this] one.
-* WiFi to RS232 serial adapter such as [http://www.mouser.com/ProductDetail/Roving-Networks/RN-134/?qs=sGAEpiMZZMvdqMP%2faZ%252bGClQs06owUsC0 this] one.
+* !WiFi to RS232 serial adapter such as [http://www.mouser.com/ProductDetail/Roving-Networks/RN-134/?qs=sGAEpiMZZMvdqMP%2faZ%252bGClQs06owUsC0 this] one.
 
 [[Image(2DS.png, align=center)]]
@@ -102 +102 @@
 
 
-  === Event processing ===
+=== Event processing ===
 
-After startup, the system is set running. It receives events and, for those of interest, it translates them into MotionSensor values to set upon it's Child Devices, in addition to setting Variables directly on the Alarm Area device
+After startup, the system is set running. It receives events and, for those of interest, it translates them into !MotionSensor values to set upon it's Child Devices, in addition to setting Variables directly on the Alarm Area device
 
 
@@ -126 +126 @@
 
 ==== Alarm Area Variables ====
-This Alarm Panel implements a DeviceType that gives it the following Variables (through it's ServiceStateTable).  These can be used for Luup scripting:
+This Alarm Panel implements a !DeviceType that gives it the following Variables (through it's !ServiceStateTable).  These can be used for Luup scripting:
   
-    * ''Disarmed'' - Set whenever the Alarm Area is Disarmed (not Armed and not StayArmed)
+    * ''Disarmed'' - Set whenever the Alarm Area is Disarmed (not Armed and not !StayArmed)
     * ''Armed'' - Set when the user requests the Alarm Area to Arm, Force Arm, Stay Arm or Instant Arm the Area
-    * ''StayArmed'' - Set when the user request the Alarm Area to Stay Arm or Instant Arm the Area
+    * ''!StayArmed'' - Set when the user request the Alarm Area to Stay Arm or Instant Arm the Area
     * ''Breach'' - set when the Alarm Area is in Breach (Siren, Silent etc)
 
@@ -150 +150 @@
  Note you will need to know which Zones are set up which on your panel. They may not be in sequence (per the above), and can be entered depending on their type in any of the three Zone variables.
 
-If remote Arming and Disarming is not required from Vera, then exit and save; however if this is required then stay in this screen and enter one of the following into the ''EnableRemoteArm'' variable:
+If remote Arming and Disarming is not required from Vera, then exit and save; however if this is required then stay in this screen and enter one of the following into the ''!EnableRemoteArm'' variable:
 
 * '''disarm''' (Least secure as all functions are available including disarm)
@@ -181 +181 @@
  
  
- = Discussions =
+= Discussions =
 
   * [http://forum.micasaverde.com/index.php?topic=5154.0 Main thread]