HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
TeMPOraL
hju
Common Lisp2017–2021
TeMPOraL / hju

hju

Simple command line (CLI) controller for Hue lights, written in Common Lisp.

2Distinct people
5Mentions
0Explicit recommenders
1GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Simple command line (CLI) controller for Hue lights, written in Common Lisp.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year5 dated mentions

Observed mentions: 2017-03-16 08:52:01 UTC to 2021-03-11 09:39:37 UTC.

0122017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

5 sources
I think Feynman's engineering team was right, mid-to-long-term. Playing was a good choice, because as they were finding their footing with new technology, they gained the necessary know-how to do calculations that would be infeasible to be done by hand - ultimately expanding both capabilities and efficiency. I bet you could trace parts of modern CFD all the way back to those engineers "playing with computers". IoT doesn't offer that kind of growth, though. These are all tightly packaged appliances, their whole raison d'etre is to trick you into a subscription to a cloud service. Unless you're running custom software on DIY IoT connected to Home Assistant, or buying a custom deployment from an old-school home automation company, there's no space to grow here. You aren't going to make your home more ergonomic to use than you could with dumb
Read the rest
switches, dumb thermostats, remotes and electric outlet timers. You'll just spend a lot of money and tweak a few trivial settings on an app to get something approximating your needs, and then have half of it stop working whenever your ISP drops your Internet connection for a few minutes; you'll have to replace appliances piece by piece as services backing them thank you for your incredible journey together, and eventually redo your setup/configuration with the next big cycle of upgrades. So no, I think it's not playing like Feynman's engineers. It's playing like buying very expensive clothes and jewelry - it's paying for status, and has no lasting value beyond what you can make out of your temporary boost in status. -- EDIT: FWIW had my phase of smart lights controlled from a watch - in my case it was Hue lights hooked up to my Pebble. It was more streamlined than you could ever do with Apple Watch, by virtue of Pebble having actual buttons, and control going purely through LAN (Pebble -> Tasker on Android -> Hue Bridge -> Lightbulb). After a week of fun, I realized that most of the time, it's still the second least ergonomic option (the absolute worst was controlling from an app). What I settled on is a combination of dumb switches when on the move (usually faster to reach than even my watch), and a CLI script when near my computer[0]. Also this taught me that the most important component in IoT lights is... smart light switches. Which weren't cheap or easy to get those 6 years ago when I bought my Hue lights, so I had none. With dumb switches, whenever I used them - or my guests used them - they'd screw up the light setup and made bulbs inaccessible over network. I ended up putting a bit of Lisp code on Raspberry Pi, that monitored for lightbulbs that just reappeared on the network, and immediately reconfigured them to a desired state. It's a kind of workaround that you don't get to do if you just buy into neatly packaged, cloud-powered IoT appliances. -- [0] - https://github.com/TeMPOraL/hju
In I guess I have to watch ads everywhere on my $1,500 LG TV now
Read the rest
ded development https://cliki.net/embedded http://www.ulisp.com/ (not technically Common Lisp per se AFAICT, but seems to have very similar semantics) > Building common lisp is a pain, because packaging/ASDF is terrible and you don't easily get a nice and small statically linked executable out either. https://www.xach.com/lisp/buildapp/ http://www.sbcl.org/manual/#index-save_002dlisp_002dand_002d... https://ccl.clozure.com/manual/chapter4.9.html
In Modern, functional Common Lisp: myths and best practices
SBCL mostly. I probably should give GCL a try here. SBCL is fast as hell once it starts up, and bare SBCL starts up quickly, but once you add Quicklisp and start loading external systems, the startup time gets noticeable - though again, this gets reduced quickly iff you dump a binary of your image with dependencies already loaded. The one CL script I wrote that I actually use[0] (for controlling Hue lamps) I have dumped into binary just to cut down startup time to below the point I notice. -- [0] - https://github.com/TeMPOraL/hju/
In Scripting in Common Lisp
I'm using my own CLI script to control Hue lights[0] and I confirm that you can set the state of your lights directly, without referring to or even knowing the previous one. The API is pretty straightforward. I suspect that even the vanilla Hue app on Android does that - given the way I often manage to switch the lights before the app UI figures out what's their current state. -- [0] - https://github.com/TeMPOraL/hju
In Apple has proven me wrong about HomeKit

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.