NotifierLight is a Windows application that supports multiple types of notification lights and notification sources, including TAPI & OBDC. It’s been in development since 2012, is open-source, and has a nice plugin architecture for new notification sources.
As of a month ago, NotifierLight now supports blink(1)!
If you are a .NET aficionado, you can write your own plugins pretty quickly.
The creator of NotifierLight also made these great door hanger or desk displays to let your co-workers know what the colors mean.
Youtube review channel KevinsTechHelp did a nice unboxing and quick review of blink(1). Check it out below:
Hackaday, one of the oldest hacker blogs on the Net, is celebrating its 10th anniversary on 4 Oct 2014. There will workshops, build-offs, a party, and a mini-conference in the afternoon.
The event will be held at the location of Hackaday’s new “HackASpace” hackerspace, before they do the build out.
A few days ago ThingM friend Rusty, operator of the wonderful SomaFM, wondered if there would ever be a “blink(16)”: a blink(1) with a 4×4 grid of LEDs. Well it turns out that due to a secret feature of all blink(1) mk2s, it’s actually pretty easy to make, if you have some WS2812-style LED strip laying around.
Making a blink(1) mk2 use 16 extra LEDs is pretty easy because it has a hidden 3-pin port for wiring up WS2812/NeoPixel-type LED strips. In this photo, you can see the three holes: one each for Gnd, +5V, and data.
Below is a video showing it in action. The two ‘blink1-tool’ commands used in the video are:
blink1-tool --random=1000 -l 18 -m 50 -t 50 blink1-tool --running -l 18 -m 200 -t 200
Notice the “-l” option. Using this option, you can control a single LED in a blink(1) mk2. For instance, on a regular blink(1) mk2, you can do:
blink1-tool -l 1 --red blink1-tool -l 2 --blue
to make the top LED red and the bottom one blue. For the “random” and “running” commands, the “-l” option means how many LEDs to use.
As he says:
— David Barker (@davb5) September 8, 2014
Our little gadget-that-could, blink(1), has been seeing a lot of exposure and press. And we’ve been selling a bunch!
Instead of having just a sub-page on our main website, we decided it was time that blink(1) got a website of its own. It has general info about what blink(1) is and why you want one, but also links to downloads, the start of a Getting Started section, an ever-growing FAQ, and a list of ways to contact us with questions or comments. It also gives us the needed space to build out more instructional material for blink(1), like How-Tos and Project Galleries.
Check it out: blink1.thingm.com
You can now get blink(1)s in our online store: http://buy.thingm.com/!
Each blink(1) mk2 comes with a 5ft USB extension cable so you can put notifications where you want them. blink(1) comes with a complete GUI application called Blink1Control that hooks in with IFTTT. And blink(1) is entirely open source.
For a limited time, we are also stocking the cool gooseneck USB extension cable that we shipped to our Kickstarter backers. Unlike normal cables, this one stays in the shape you bend it. It’s a lot of fun.
Node-RED is an interesting visual tool for wiring the Internet of Things. It runs in Node.js and looks to have incredible potential. blink(1) user dceejay wrote a Node-RED package for blink(1) called node-red-node-blink1.
As he says, it:
“Sends the msg.payload to a Thingm Blink(1) LED device. The payload can be any of the following:
- a three part csv string of r,g,b – e.g. red is 255,0,0
- a hex colour #rrggbb – e.g. green is #00FF00
- a @cheerlights colour name – e.g. blue
- The @cheerlights colours are – red, amber, green, blue, cyan, magenta, yellow, orange, pink, purple, white, warmwhite, black”
Get it here: https://www.npmjs.org/package/node-red-node-blink1