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 🙏

© 2026 – Pkg Stats / Ryan Hefner

node-red-contrib-thekey

v1.0.5

Published

Node to pilot theKeys locks through theKeys Gateway (https://store.the-keys.fr/)

Readme

node-red-contrib-thekey

This package contains nodes to communicate with lockers from the French theKeys' firm through its gateway product (https://store.the-keys.fr/en/accessories/11-gateway.html)

It's compose of :

  • 1 configuration node thekeys-gateway that contains properties of the gateway use to pilot locks.
  • 1 node thekeys-lock that represent a lock to remotly pilot

requirements

Thispackage depends on crypto-js and requestnodes.

thekeys-gateway

The configuration contains 4 properties :

name : the name you decide to give to the theKeys gateway

host: the gateway IP adress. It can contains an hostname. Default value isthekeys.local

port (optional) : the port used to communicate with the gateway (in case of using NAT rules on router)

checkState : it define if you want the node to avoid posting to gateway an open (or close) command while the state of the desitnation lock is already opened (or closed). When checked (set to true), the node will not send open command to lock considered opened (stored state set to opened). This will avoid unusefull url call to gateway and then will not charge it unusefully. If this property is not checked (se to false), command will be post to gateway unconditionely.

thekeys-lock

properties

name: Specify a name for the configuration node

controller: Select the config node corresponding to the gateway linked to the lock.

identifier: ID of lock to command. It correspond to the "ID serrure" stored in the table you can obtain in this url https://api.the-keys.fr/fr/compte/serrure

sharecode: Code of sharing between Gateway and Lock. Code obtain in you api.the-keys account at https://api.the-keys.fr/fr/compte/partage/accessoire/< gateway ID >/get.

periodReadingState: Specify a delay in second between each periodicly state reading of the lock. Default value is 300 sec (5mins). Minimum value is 30sec.

node input

The node can receive 3 commands on its input. Commands are strings with this allowed values : open: to unlock the locker close : to lock the locker locker_status : to get the locker state (opened=unlock, closed = lock). See outputs section below.

node outputs

output n°1

First output, outputs JSON object containing the command posted and its result in this forrmat

{ 
"command": "open" or "closed" or "locker_status",
"status": a string describing the lock state or, in case of error, the string return by the http post command to gateway
}

exemple :

{
"command":"locker_status",
"status":"Door closed"
}

output n°2

Second output produce the lock state after command It can be :

  • opened
  • closed
  • jammed