JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 4
  • Score
    100M100P100Q45695F
  • License ISC

Homebridge Plug-in for the FX Luminaire (Luxor) lighting controller

Package Exports

  • homebridge-luxor

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (homebridge-luxor) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

homebridge-luxor

This is a BETA module for the HomeBridge Platform to control FX Luminaire.

This plug-in enables power and brightness controls for FX Luminaire Luxor ZD light groups. There are a few know issues which are listed below and would appreciate help in fixing them! :-)

Installation

  1. Install homebridge using: npm install -g homebridge Full directions at HomeBridge page
  2. Install this plugin using: npm install -g homebridge-wemo
  3. Update your configuration file. See sample-config.json in this repository for a sample.
    • The name and groupName should be unique for each lighting group that you have or HomeBridge will think it is the same device and try to assign it the same UUID and throw an error. (See enhancement #2 below.)

Known Issues

  1. Plug-in is written only for the ZD controller (Zoning, Diming). It may work with the ZDC (Zoning, Dimming, and Color) but I have not tested it (the color selection is not currently coded). (See #1 in enhancements.)
  2. FIXED When using the app, Program A changes the on/off or brightness, Program B will need to refresh twice to see the changes take effect. This is because the getBrightness and getPowerOn functions return their values before the http post returns with its data.
  3. Refactor code.

Future enhancements (in no particular order)

  1. Add ZDC configurations/code (if there is a demand)
  2. Figure out the differences between the name, servicename, accessoryname, etc to enable proper HomeKit configuration and unique UUID
  3. Add manufacturer and model (at the service level?) for various apps' aesthetics.
  4. Module should be able to dynamically retrieve groupname and groupnumber (as this is exposed via an API) but for now it is in the configuration file.
  5. This module should really be converted to a platform. Effect will be that one controller can be defined in the configuration file and all the lights will be automatically added. 6?. Luxor controllers have Themes (preset configurations for groups of lights) but not sure if these should be included as they could duplicate the Zones functionality in HomeKit. Possibly Zones could be configured programatically but I haven't looked into that.
  6. There is no push notification (eg if I turn on the light manually at the controller, or via the native app, HomeKit won't get notified). Should I implement a timer to periodically check the state of the lights and update HomeKit?

Credit

  1. I knew that the FX controller had a minimal web interface, and discovered a couple of the API calls, but then found a full(?) list and implementation of the code in a Go library written by Scott Lamb.
  2. I used the original WeMo code from rudders as a template and hacked away at it until I got to this point.
  3. Of course, to nfarina for the HomeBridge and, in turn, KhaosT for the original HAP-NodeJS project.