Using BlinkStick with Raspberry Pi
Productivity Sauce
Hooking up LEDs to Raspberry Pi's GPIO pins and controlling them using Python scripts is a great and fun way to learn the ropes. For more advanced projects, you might want to consider investing in BlinkStick, an open source USB LED kit that works with Raspberry Pi, or any other machine for that matter. BlinkStick plugs directly into a USB port, which eliminates the need for a breadboard and wires and makes the setup more tidy. The accompanying software can control multiple BlinkSticks, which you can hook up to a USB hub. More importantly, BlinkStick supports a long list of options, and you can put it to a variety of practical and not-so-practical-but-fun uses.
To get started with BlinkStick on Raspberry Pi, you need to install the BlinkStick Python interface first. To do this, run the following commands:
sudo apt-get install python-dev python-pip sudo easy_install pip sudo pip install blinkstick
Run then the sudo blinkstick -h command. If everything works properly, you should see a list of all available options. By default, you have to execute blinkstick commands with root permissions. To fix that, run the following command and reboot Raspberry Pi:
sudo blinkstick --add-udev-rule
So what can you actually do with BlinkStick? For starters, you can use it to visualize CPU usage, and the blickstick command has a dedicated option for that. Run the blinkstick --cpu-usage command, and BlinkStick will change its color depending on the CPU usage (Green = 0%, Amber = 50%, Red = 100%).
Of course, you can put BlinkStick to other uses, too. I'm using BlinkStick with Pygmyfoto running on my Raspberry Pi. Every time someone visits the gallery, BlinkStick blinks with random color. This solution consists of a simple Bash shell script which controls BlinkStick and logs visitor access to the blinkstick.log file:
#!/bin/bash blinkstick --set-color random --blink --repeats 3 blinkstick --set-color random DATE=$(date "+%F %T") echo "Yay! Someone visited your site on" $DATE >> blinkstick.log
The shell_exec ( './blinkstick.sh > /dev/null 2>/dev/null &' ) command embedded into the index.php page triggers the script.
For further info on using BlinkStick and more ideas on how to use this nifty kit, visit the project's GitHub repository. In the meantime, drop by dmpop.dyndns.org/pygmyfoto/ and blink to me. :-)
comments powered by DisqusSubscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
openKylin 3.0 Released with Expanded AI Integration
The latest release features a pre-installed AI agent to help perform tasks.
-
DigitalOcean Ends Open Source Credits Program
In a change that has surprised many open source developers, DigitalOcean has decided to sunset its Open Source Credits Program.
-
Office 365 Available for Testing on Linux via Bottles
Linux users can now test the official Office 365, thanks to Mirko Brombin's work on Bottles.
-
Dutch Government Turns to Open Source for Digital Sovereignty
Following in the footsteps of other European countries, the Netherlands is looking to increase its sovereign digital infrastructure with open source software.
-
Linux May Soon Work on Snapdragon X2-Based PCs
If you're thinking about buying a Snapdragon X2-based desktop or laptop, Linux may soon be an option.
-
KDE for People Initiative Calls for AI Ban in Plasma
A new community of KDE wants the project to adopt a strict no-AI policy for KDE Plasma.
-
KDE Sets Ambitious Goals for 2026 and Beyond
KDE Connect reveals the goals for the Linux desktop darling, with one of those goals long overdue.
-
It’s Time to Test Fedora 45 Beta
Fedora 45 beta has been released with updated Gnome, KDE Plasma, and kernel.
-
Ubuntu Stonking Stingray Gets Even Rustier
Ubuntu 26.10 has completed its migration to the Rust-based coreutils.
-
AI Fixes Linux Bottlenecks Using “Hideous” Code
A Linux developer used AI to fix bottlenecks that caused problems when building the kernel. The resulting AI-generated code needed a lot of work.
