npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

nodealarmproxy

v1.0.2

Published

Use this to communcate to an envisalink 3 module for home alarm monitoring.

Downloads

24

Readme

##Setup##

npm install nodealarmproxy

the nap-example.js shows a setup configuration. Replace the init parameters with your own.

Available commands:

initConfig(Object) will create the server and a proxy for other things to connect to (Envisalink only allows one connection... this allows for multiple connections via proxy). The object needs to be of the form:

{ password:'password', //required
    serverpassword:'serverpassword', //optional, will re-use password if not provided
    actualhost:config.host, //required
    actualport:config.port, //optional, will use default port if not provided
    serverhost:'0.0.0.0', //optional, will use '0.0.0.0' if not provided
    serverport:config.port, //optional, will use default port if not provided
    zone:7, //required, this is the number of sensors you have
    partition:1, //required, this is the number of partitions... usually 1
    proxyenable:true, //enable the proxy or not
    atomicEvents:false //optional, will default to false. If true, specific zone/partition/user events will be broadcast.
}

getCurrent() will tell the nodealarmproxy to transmit the last known values.

manualCommand(command) will send a command to the Envisalink 3 (do not include the checksum). Command will be a string based on the envisalink 3 third party interface.

Note: If you don't want to run the proxy, set proxyenable:false or omit it entirely

Note: My config file has:

exports.password = '';  //Envisalink password
exports.serverpassword=''; //Password you want for proxy server
exports.host = '';  //host IP Address
//exports.host = 'localhost';
exports.port = 4025;
exports.app_id = ""; //smartthings app_id
exports.access_token = ""; //smartthings access_token

Changes were mostly done to the nap-example.js, however if you're adding SmartThings integration... you'll need to setup your own app by following instructions similar to this (I've contributed to this project as well)... smartthings-dsc-alarm