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

smarthome

v1.1.2

Published

RWE Smarthome API

Downloads

6

Readme

RWE Smarthome API

Scrapes the RWE Smarthome Mobile Web Interface and implements the long polling mechanism that the site uses to be notified of changes.

The biggest problem is that it seems to timeout after a while and receives invalid response from the server (unfortunately with status 200).

Use it like this:

var smarthome = require('smarthome');
smarthome.setLogLevel("debug");

smarthome.connect(USERNAME, PASSWORD, function( error, api ) {
  if (error) {
    console.log("error:" + error);
    process.exit();
  }

  //list sensors
  //(the same works for api.devices and api.locations)
  for (var i = 0; i < api.sensors.length; i++) {
    var s = api.sensors[i];
    console.log("Found sensor " + s.name + " in " + s.location.displayName);
  }

  //you can search for devices or locations by id
  var bath = api.location("dead1-beef2-cafe3-1234-5678");
  var x = api.device("dead1-beef2-cafe3-1234-5678");

  //or by name (case insensitive substring search, return first match)
  var livingroom = api.location("livingroom");
  //even on a location
  var windowinlivingroom = livingroom.sensor("window");

  for (var i = 0; i < api.locations.length; i++) {
    var loc = api.locations[i];
    console.log( loc.displayName + ": " + loc.temperature() );
  }

  //watch for changes like this:
  windowinlivingroom.on("change", function(window, oldValue) {
    console.log("Window in living room changed from " + oldValue + " to " + window.value);
  });

  //or for all changes. displayValue() gives human readable values 
  api.on("change", function(device) {
    console.log(device.name + " changed to " + device.displayValue());
  });

  //You can set values like this:
  var actuator = api.actuator("dead1-beef2-cafe3-1234-5678");
  actuator.setValue(1, function(error, newvalue) { ... } );
  //the callback is not required - simply watch the device for changes when you need to be informed 

  //finally, very very rough error handling:
  api.on("error", function(error) {
    console.log(error);
  });
  
  //To automatically reconnect, hook on "disconnect" event
  api.on("disconnect", function() {
    //create new connection, reinitialize listeners, etc
  });

});