473604f567
Please read b/108 to make sense of this. This gets rid of the explicit list of exposed packages from nixpkgs, and instead makes the entire package set available at `third_party.nixpkgs`. To accommodate this, a LOT of things have to be very slightly shuffled around. Some of this was done in already submitted CLs, but this change is unfortunately still quite noisy. Pay extra attention to: * overlay-like functionality that was partially moved to actual overlays (partially as in, the minimum required to get a green build) * modified uses of the package set path, esp. in NixOS systems Special notes: * xanthous has been disabled in CI because of issues with the Haskell overlay * //third_party/nix has been disabled because of other unclear dependency issues Both of these will be tackled in a followup CL. Change-Id: I2f9c60a4d275fdb5209264be0addfd7e06c53118 Reviewed-on: https://cl.tvl.fyi/c/depot/+/2910 Reviewed-by: glittershark <grfn@gws.fyi> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI |
||
---|---|---|
.. | ||
idual | ||
default.nix | ||
idualctl | ||
README.md | ||
setup.py |
iDual light control
This folder contains some tooling for controlling iDual LED lights (which use infrared controls) using a "Broadlink RM Pro" infrared controller.
The supported colour codes of the iDual remote are stored in
codes.txt
.
The point of this is to make it possible for me to automate my lights in the morning, so that I can actually get out of bed.
Capturing codes
Capturing codes is relatively easy, assuming that the broadlink device is set up:
import broadlink
import base64
devices = broadlink.discover(timeout=5)
devices[0].auth()
For each code, the procedure is as follows:
devices[0].find_rf_packet()
# wait until this returns True
devices[0].check_data()
# this will return the code