A few more DSC questions

General Discussion

A few more DSC questions

Postby dot850 » Wed Apr 22, 2015 7:17 am

Now that I have this running, I have a two questions (maybe more to come) on some of the features:

1. Zone naming -- how do I find the Zone ID for each zone on a DSC system?
2. Custom buttons on the keypad -- how do I find these? For example, there is a scroll button on the keypad (< and >) that I would like to be able to duplicate. I see there are custom buttons I can add to the keypad, I just don't know what to fill in for the "code" field.

Thanks again for all your support!
dot850
newt
newt
 
Posts: 9
Joined: Fri Apr 17, 2015 2:05 pm

Re: A few more DSC questions

Postby kevin » Wed Apr 22, 2015 8:28 am

The > and < buttons are there, just hidden because we have not implemented them yet.

Custom buttons can be created through the settings interface - you literally just put in exactly what you want to send to the alarm.


As far as zone naming goes, I'll have to have somebody else elaborate on that.
Not an employee of the company. Just here to help and keep things clean.
kevin
Platinum Nut
Platinum Nut
 
Posts: 994
Joined: Fri Aug 16, 2013 10:10 am

Re: A few more DSC questions

Postby dot850 » Wed Apr 22, 2015 8:36 am

Is there a way to snoop these buttons?

Like say I push one of the "extra" buttons on the keypad, is there a way to see how to implement those as a custom button?

Or is the custom button more for macro purposes?
dot850
newt
newt
 
Posts: 9
Joined: Fri Apr 17, 2015 2:05 pm

Re: A few more DSC questions

Postby kevin » Wed Apr 22, 2015 9:09 am

Custom button is for whatever you want, but an example use case would be a macro - such as "quick disarm" - just send your user code in the definition of the custom button.


You can see what each of the buttons sends by looking at the template file in templates/keypad/dsc.html

Code: Select all
bindButtonEvents('#button-stay',  's', '', '', '', '');



stay button sends 's' for example

The > and < buttons don't have events bound to them and they are hidden with css as the firmware of the AD2USB has not implemented them yet.

Code: Select all
        <div id="keypad-button-row">
            <!-- Arrow Keys -->
            <input id="button-left" class="half_keypad-button_arrow" type="button" value="<" style="visibility: hidden"></input>
            <input id="button-right" class="half_keypad-button_arrow" type="button" value=">" style="visibility: hidden"></input>
            <!-- Normal Keys -->
            <img id="button-1" class="keypad-button"/>
            <img id="button-2" class="keypad-button"/>
            <img id="button-3" class="keypad-button"/>
            <input id="button-stay" class="half_keypad-button" type="button" value="Stay"></input>
        </div>



For custom buttons, the label is what the button displays on your user interface such as "Quick Arm" and code is what to send to the panel, such as your user code "1234" no quotes, then in keypad view, clicking 'Quick Arm' will send "1234" to the panel
Not an employee of the company. Just here to help and keep things clean.
kevin
Platinum Nut
Platinum Nut
 
Posts: 994
Joined: Fri Aug 16, 2013 10:10 am


Return to General

Who is online

Users browsing this forum: No registered users and 39 guests

cron