3 ms·
They are probably using "systemd-lightd", so the right command would be "lightctl status".
by Sandhose 6y ago
They are probably using "systemd-lightd", so the right command would be "lightctl status".
- scrps 6y agoBe aware you need to pass: lightctl --user --room # command Per room session otherwise you'll control all the lighting and annoy other users.
- the8472 6y agoSingle-user deployments are fairly common in the gnu lightblub crowd.
- renewiltord 6y agoVery 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.
- UnpossibleJim 6y agoIf electricity isn't your worry, might I suggest installing your lightbulbs in a complete virtual environment?
- rolandog 6y agoInstructions unclear; burnt fingerprint on incandescent lightbulb.
- kwargs 6y agoYou forgot to dockerize and Kubernetize stuff
- Anarch157a 6y agoUnless you're the father, the you can run sudo lightctl status room to check that bulb.
- vincent-manis 6y agoAn additional 68 to argue about systemd and pulseaudio.