Skip to content
This repository has been archived by the owner on May 7, 2020. It is now read-only.

[LIFX] Add optional host configuration parameter, support new products and improvements #4231

Merged
merged 5 commits into from Sep 25, 2017
Merged

[LIFX] Add optional host configuration parameter, support new products and improvements #4231

merged 5 commits into from Sep 25, 2017

Commits on Sep 9, 2017

  1. [LIFX] Add optional host configuration parameter, support new products 

    * Add host configuration parameter for lights that do not respond to UDP broadcasts (fixes #3913)
* Add support for new products (most notably the new Downlights)
* Add deviceId configuration parameter pattern to prevent mistakes/exceptions
* Fix static code analysis findings

Signed-off-by: Wouter Born <eclipse@maindrain.net>
    @wborn
    wborn committed Sep 9, 2017
    Copy the full SHA
    412d008 View commit details
    Browse the repository at this point in the history

Commits on Sep 10, 2017

  1. Make broadcastEnabled final 

    Signed-off-by: Wouter Born <eclipse@maindrain.net>
    @wborn
    wborn committed Sep 10, 2017
    Copy the full SHA
    37a425b View commit details
    Browse the repository at this point in the history

Commits on Sep 22, 2017

  1. Periodically update available network interface information 

    * Makes the LIFX Binding periodically update network interface information. This for instance resolves the issue that network interfaces are not (or still) being used for broadcasts after they go up (or down).
* The code for this information was duplicated across the LifxLightDiscovery and LifxLightCommunicationHandler classes and has now been extracted into LifxNetworkUtil.
* All utility classes have now been grouped in the .util package.

Signed-off-by: Wouter Born <eclipse@maindrain.net>
    @wborn
    wborn committed Sep 22, 2017
    Copy the full SHA
    6cf433e View commit details
    Browse the repository at this point in the history

Commits on Sep 23, 2017

  1. Make Device ID an optional configuration paramater, use lambdas and f… 

    …ix updating properties

* Update Thing status to configuration error when Device ID and Host are null
* Introduce logId property so logging identifies light depending on MAC/IP configuration
* Add logId where missing to simplify debugging
* Use lambdas for listener registration and iteratating over listeners
* Resolve @nonnull warnings
* Fix properties not always being updated
* Use a LifxLightContext for sharing common variables between handler helper objects
* Improve exception handling by catching specific exceptions and using more specific error messages

Signed-off-by: Wouter Born <eclipse@maindrain.net>
    @wborn
    wborn committed Sep 23, 2017
    Copy the full SHA
    2a173e0 View commit details
    Browse the repository at this point in the history

  2. Don't set host property on discovered lights 

    Signed-off-by: Wouter Born <eclipse@maindrain.net>
    @wborn
    wborn committed Sep 23, 2017
    Copy the full SHA
    c789bc9 View commit details
    Browse the repository at this point in the history