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

@taptrack/tappy-nobleblecommunicator

v0.0.3

Published

Node TappyBLE communicator based on Noble

Downloads

5

Readme

Communicator for using a Noble peripheral to communicate with a TappyBLE device in node.

Installation

NPM

npm install @taptrack/tappy-nobleblecommunicator

Usage

Note that this communicator is not intended to be used directly, rather it is to be used to back a Tappy object in order to provide an abstraction from the underlying communication method.

var NobleBleCommunicator = require("@taptrack/tappy-nobleblecommunicator");
var Tappy = require("@taptrack/tappy");
var SystemFamily = require("@taptrack/tappy-systemfamily");
var noble = require("noble");

/**
 * First, we have to scan for the Tappy, see 
 * Noble's documentation for additional details on 
 * this process
 */
noble.on('stateChange',function(state) {
    console.log(state);
    if(state === 'poweredOn') {
        noble.startScanning([NobleBleCommunicator.SERIAL_SERVICE_UUID]);
    } else {
        noble.stopScanning();
    }
});

noble.on('discover', function(peripheral) {
    if(NobleBleCommunicator.isAdvertisementForTappy(peripheral.advertisement)) {
        noble.stopScanning();
        connectToTappy(peripheral);
    }
});

function connectToTappy(peripheral) {
    var comm = new NobleBleCommunicator({peripheral: peripheral});
    var tappy = new Tappy({communicator: comm});

    tappy.setMessageListener(function(msg) {
        console.log("Received Message:");
        console.log("Command Family: "+msg.getCommandFamily());
        console.log("Command Code: "+msg.getCommandCode().toString());
        console.log("Payload: "+msg.getPayload().toString()+"\n");
    });

    tappy.connect(function() {
        var cmd = new SystemFamily.Commands.Ping();
        tappy.sendMessage(cmd);
    });
}