Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

They are probably using "systemd-lightd", so the right command would be "lightctl status".


Be aware you need to pass:

lightctl --user --room # command

Per room session otherwise you'll control all the lighting and annoy other users.


Single-user deployments are fairly common in the gnu lightblub crowd.


Very insecure to run all your light bulbs in the same user context. I use SELightBulb to isolate light bulb actions. If you add PAM and pam-fingerprint you can require a fingerprint to alter lightbulb state for better security. Advise two-factor unless you really don't care for electricity at all.


If electricity isn't your worry, might I suggest installing your lightbulbs in a complete virtual environment?


Instructions unclear; burnt fingerprint on incandescent lightbulb.


Unless you're the father, the you can run sudo lightctl status room to check that bulb.


An additional 68 to argue about systemd and pulseaudio.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: