lifx-lan: LIFX LAN API

[ bsd3, library, unclassified ] [ Propose Tags ]

Downloads

Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

Versions [RSS] 0.0, 0.1.0.0, 0.1.0.1, 0.1.0.2, 0.2.0, 0.3.0, 0.4.0, 0.4.0.1, 0.5.0, 0.5.0.1, 0.5.1, 0.5.1.1, 0.6, 0.6.0.1, 0.6.1, 0.6.2, 0.7, 0.7.1, 0.8.0, 0.8.1, 0.8.2, 0.8.3 (info)
Change log CHANGELOG.md
Dependencies ansi-terminal (>=0.11.1 && <0.12 || >=1.0 && <1.2), base (>=4.16 && <4.21), binary (>=0.8.8 && <0.9), bytestring (>=0.10.8 && <0.13), colour (>=2.3.6 && <2.4), composition (>=1.0.2.1 && <1.1), containers (>=0.6.2.1 && <0.8), extra (>=1.7.1 && <1.8), monad-loops (>=0.4.3 && <0.5), mtl (>=2.2.2 && <2.4), network (>=3.1.1.1 && <3.3), random (>=1.2.0 && <1.3), safe (>=0.3.19 && <0.4), text (>=1.2.3 && <1.3 || >=2.0 && <2.2), time (>=1.9.3 && <1.15), transformers (>=0.5.6 && <0.7) [details]
License BSD-3-Clause
Author George Thomas
Maintainer georgefsthomas@gmail.com
Revised Revision 1 made by GeorgeThomas at 2024-09-18T17:27:22Z
Home page https://github.com/georgefst/lifx-lan
Source repo head: git clone git://github.com/georgefst/lifx-lan.git
Uploaded by GeorgeThomas at 2024-09-03T10:26:43Z
Distributions NixOS:0.8.2
Downloads 2046 total (38 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2024-09-03 [all 1 reports]

Readme for lifx-lan-0.8.3

[back to package description]

⚠️ Looking for maintainers! ⚠️

Now that LIFX have given up on Europe, I'm less inclined to work on this project. Let me know if you're interested.

Haskell bindings to the LIFX LAN API.

This library provides a reasonably high-level interface, but doesn't try to be too clever. For example, it doesn't check message delivery, and throws an error if a light takes too long to respond. Messages and response types map directly to the low-level API (with links provided in the documentation).

It does not yet cover the full API, but PRs are very welcome and some functionality may be added on request.