Skip to content

snieking/HueServer

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

46 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

HueServer

1. Prerequisites

  1. General API knowledge

    1. API keys for Philips Hue, and Twitter

    2. Get scenes IDs from Philips Hue.

  2. A computer/server that is online 24/7. Personally, I use a Raspberry Pi which barely eats any electricity.

2. Download

Version

Link

Notes

1.0.3

bit.ly/2kHkJXR

External config should now work. Renamed config file and moved to config/ path.

1.0.2

bit.ly/2ldRr7g

Improvements for the configuration

1.0.1

bit.ly/2l0P59i

Better at dealing with Twitter duplicate tweets

1.0.0

bit.ly/2lF8Pzr

First release

3. Instructions

  • Open up config/application.yml and configure your system.

    • The comments in the file describes how you should configure.

  • If you want to enable the Twitter scanning to blink lights when match found, you need to fill in the spring.social.twitter fields in the config.

    • spring.social.twitter.appId:

    • spring.social.twitter.appSecret:

  • In this file you can also change the port that the program runs on with the following command:

    • server.port:

application:
  general:
    # Specify how many hours before or after UTC you are. (For example: 1 or -5)
    timeZone:
    # Specify the location that HueServer uses for getting sun hours. (For example: 59.200197)
    latitude:
    longitude:
  twitter:
    # Scan twitter and blink lights when message found that matches pattern.
    enabled: false
    # List of users to scan for regex pattern in message,
    # see the example below how to add users.
    users:
    # - User1
    # - User2
    # Regex pattern to scan (For example: .*Saturday.* to scan for messages that include Saturday)
    regex:
    group:
  hue:
    # Your username for your Hue bridge API. See https://developers.meethue.com/documentation/getting-started
    user:
    # IP to your Hue bridge, check your router (For example: 192.168.1.85)
    ip:
    scene:
      # Runs everyday at sunrise and sunset.
      sunstatus:
        enabled:
        # Scene that will be set on sunset.
        id:
        group:
        # How many minutes before or after sunset it should enable (Ex: Before -60, After 60)
        sunsetAdjustedMinutes:
        # How many minutes before or after sunset it should enable (Ex: Before -60, After 60)
        sunriseAdjustedMinutes:
      # Enables lights in the morning.
      goodMorning:
        enabled:
        # Time that lights will turn on in the morning.
        time:
        # Id of the scene that will be set.
        id:
        # Group of lamps that will be enabled.
        group:
      # Disables lights in the night.
      goodNight:
        enabled:
        # Time that lamps will be disabled.
        time:
        # Group of lamps that will be disabled.
        group:
      evening:
        enabled: true
        # Time that lamps will set eveing scene.
        time:
        # Group of lamps that will be set to a scene.
        group:
        # Id of the scene that will be set
        id:
# This needs to be specified in order to use the twitter scan.
# See dev.twitter.com to create an App to receie appId & appSecret.
spring:
  social:
    twitter:
      appId:
      appSecret:
# Default port is configured to 9080, you can switch this if you
# have some other service already running on that port.
server:
  port: 9080

4. Contact

You can best reach me via Twitter or drop me an email at viktorplane.sonie@gmail.com.

4.1. Requests and report bugs

To ask for requests or report bugs and issues, please use the Issues page here on GitHub.

About

Philips Hue Automation Server

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published