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

ut330t

v1.0.0

Published

JS/TS library to interface with the UT330T USB temperature logger

Readme

ut330t

This is a simple JS/TS library to interface with the UT330T USB temperature logger.

The UT330T is a nifty little USB temperature logger that I purchased to monitor the temperature of my root cellar. Problem is the software that comes with it is Windows only. So I decided to reverse engineer the protocol and write a little library to interface with it. Reverse engineering was done by sniffing the USB traffic between the official Windows software and the device using SerialMon. I made multiple captures while changing various settings in the official software to get a good idea of how the protocol works. Those captures are included in the captures directory.

The names of the functions (i.e. getDeviceParameters etc) are taken from strings I found in one of the dlls that comes with the software.

The protocol is rather quirky, like when encoding a date it'll write each "component" of the date as a separate byte. So the year 2025 is encoded as 0x05 (20+5) followed by month, day, hour, minute, and second each in their own byte. Having reverse engineered a few protocols in the past I expected the date to be encoded as seconds since some epoch for efficiency.

There's also some apparent bugs in the protocol, like when requesting the config date it'll say that the message length is 7 bytes when it's actually 6

Examples

Configure the device to log once every hour and start logging when the play button is pressed

const client = await Client.autoDiscover()
if (!client) {
  throw new Error("No device found")
}

const deviceParameters = await client.getDeviceParameters()
console.log("Current device parameters:")
console.log(deviceParameters.toString())

deviceParameters.startMode = "key"
deviceParameters.samplingInterval = 3600

const newParams = await client.setDeviceParameters(deviceParameters)

console.log("Updated device parameters:")
console.log(newParams.toString())

await client.close()