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

azure-iothub-receiver

v2.0.0

Published

friendly abstractions for processing Azure IoT Hub d2c events

Downloads

17

Readme

azure-iothub-receiver

📟✉☁✔

This package provides a succinct NodeJS API for receiving device-to-cloud messages from an Azure IoT Hub instance without a lot of boilerplate. It's fast to get up and running, but configurable where it counts if needed.

It will combine receivers on all partitions (or a filtered set of partition IDs that you specify) within a consumer group, and supplies a single message event to attach a handler to.

I wrote this because I found myself writing the same receiver boilerplate code for every NodeJS project that handled telemetry from devices in some way. It's not for every use case, but it's great when you just want to act on every message coming in from devices out in the field.

For an example of how I'm using it with a physical device, see my study-temp project, where I use websockets to create a Twitch widget to report the temperature of my room. For more examples using a simulated device, check out the section in the CONTRIBUTING.md doc that details the samples in the examples folder.

Installation

  1. Install NodeJS version 4.2 or higher
  2. Run npm install --save azure-iothub-receiver in your project folder

Example usage

The following example will get you up and running with the basics. You'll need a connection string for your Azure IoT Hub instance. You can find this under the 'Shared Access Policies' link when viewing the IoT Hub within your Azure Portal.

const Receiver = require('azure-iothub-receiver');

const options = {
  connectionString: '<your Azure IoT Hub connection string>' 
};

const receiver = new Receiver(options);

receiver.on('data', (message) => {
  console.log('annotations:', message.annotations);
  console.log('body:', message.body);
});

receiver.on('error', (error) => {
  console.error(error);
});

Extended options

The options object passed in on Receiver instantiation accepts the following properties:

|Property |Required? |Default | |--------------------|------------|---------------| |connectionString |Yes | | |consumerGroup |No | '$Default' | |startTime |No | Date.now() | |partitionFilter |No |[] |

License

MIT