I had a look at the SecuritySystem object and found where it constrains the passcode to 4 digits. It appears to default to 4 digits but can handle longer passcodes using a property called "CodeLength". The problem is that "CodeLength" is not a native property of SecuritySystem. To fix this the 'right way' requires alterations to SecuritySystem's defining class as well as the ELK M1 driver. To fix this ASAP, you can simply 'patch' AutomationBrowser; all you need to do is change one value.
The attached image shows the location of the subroutine that you must modify.
- Using Builder, navigate to Modules > AutomationBrowser > ControlPanelmanager > GlobalScripts > Global.
- Scroll the content pane until you find "Sub OnEnterOrCancel(key)".
- Find the following line of code and replace the "4" with a "6".
- Press F12 (Function Key 12) and the change will be committed to the server.
The latest version of MiniBrowser (
see the Downloads section) does not display SecuritySystem and SecurityZone objects. I'll look into a means of enhancing MiniBrowser so it can be used to display and control a SecuritySystem object.
With regards to security sensors, here's how I have my Premise Home structured (see attached image):
----------------------------------------------------------------------------------------------------------------------------
You can have several Home objects bound to the same ELK M1 Zone. In my case, I have a
SecurityZone object and a
DoorSensor object bound to the M1
Zone representing the Front Door.
I have a Home > SecuritySystem object and its children are all SecurityZone objects. Each SecurityZone object is bound to a Zone of an M1_Panel device. One of the SecurityZone objects represents the Front Door. The SecurityZone objects are not visible when viewed via AutomationBrowser (because they are children of the SecuritySystem object) nor via MiniBrowser (because it simply does not know how to render them).
Naturally, I do want to see the status of my Front Door, via AutomationBrowser and MiniBrowser, so I added a DoorSensor object (named FrontDoor) to the Foyer room. I bound it to the corresponding Zone of the M1_Panel device.
----------------------------------------------------------------------------------------------------------------------------
The primary reasons for adding SecurityZone objects as children of a SecuritySystem object is it satisfies a requirement of the Enhanced SecuritySystem ControlPanel module I created (
see Downloads). This module improves upon the existing SecuritySystem object and lists all open (i.e. violated) SecurityZones in Premise Browser. To accomplish this, the SecurityZones must be child-objects (children) of the SecuritySystem object.
Another benefit is that it is easier to view all the security-related sensors in Builder because they are grouped together.
I should point out that the object I'm using to represent my Front Door is not a
DoorSensor but a custom-made object called a Composite Door. It is a more comprehensive model of a real-world door and includes a door sensor, lock opener/closer, deadbolt sensor, and a history of door openings/closings.
