Skip to content

Remove Nanoleaf API key and make it configurable instead of hardcode #11

@chpapa

Description

@chpapa

A quick change at Hackathon of X'mas 2017, we added Nanoleaf support to the code (at branch nanoleaf), however it hardcode the API key which is the URL to the Nanoleaf, and the theme to open in code. It should be configurable. (And not give up the API key of our office's nanoleaf! To avoid people come to our office / VPN and show red all the time lol)

Tasks:

  • Make Nano Leaf URL (IP, port, API key) and effects name configurable
  • Make daemon-opendoor fire trigger of door unlock / door lock, instead of hard code nanoleaf code in the middle of the code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions