Changes between Version 9 and Version 10 of WikiStart
- Timestamp:
- 2011-04-19 05:20:07 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v9 v10 83 83 This can happen, for example, if someone triggers a motion sensor event as Vera is starting up the plugin during a Vera reboot. 84 84 * To reduce the number of Zones created, the Plugin will look for "Empty" or "Default" Labels. 85 An Empty /Default Label on a Zone indicates that we'll skip over it. If you want a Zone to be mapped to a !MotionSensor Device then it must have a non-empty, non-default label. This was done to avoid having up to 48, 96 or 192 "unused" !MotionSensor events in Vera.85 An Empty / Default Label on a Zone indicates that we'll skip over it. If you want a Zone to be mapped to a !MotionSensor Device then it must have a non-empty, non-default label. This was done to avoid having up to 48, 96 or 192 "unused" !MotionSensor events in Vera. 86 86 * Zone-based !MotionSensor Devices are created without the [http://wiki.micasaverde.com/index.php/Luup_Lua_extensions#function:_append embedded] flag, so they can be placed in Rooms. 87 87 These devices are still Parented to the Alarm Panel Device, but can be placed in any Room defined by Vera. The downside of this is that immediately after the installation of the Plugin, all Zones ''must'' be placed into a Room, as defined by the Vera UI. … … 92 92 93 93 ==== Alarm Area Scene Events ==== 94 The Alarm Device creates one "Area" child device per Alarm Partition /Area managed by the Alarm Panel. This "Area" child device is used to create Scene behaviors for the Alarm Panel.94 The Alarm Device creates one "Area" child device per Alarm Partition / Area managed by the Alarm Panel. This "Area" child device is used to create Scene behaviors for the Alarm Panel. 95 95 96 96 During Scene creation, the following ''Events'' are exposed by each "Area" device: