nesurion / milight-daemon Goto Github PK

add a function to connect boblight to the milight-daemon to extend the light from the tv to the whole room.
boblight will be a mode like night or disco in the daemon.

Possible implementation could be: use a pipe the transfer data from boblight to milight fast.

After sending a lot commands to the daemon, it will be very slow, or sometimes the daemon dont work anymore.. I thought the bridge is crashing but i can use the app to control the lights, so the issue is here

Explain how to:

• install package
• compile and cross-compile
• config
• flags
• api endpoints

add a version system. version number stored in file.

milight-daemon --version => 0.0.1

milight-daemon

=== Milight Daemon ===
Version 0.0.1
Running on 0.0.0.0:8080

this needs to be done before #4

Attempting to run the milight-daemon in terminal on osx. I've configured the config file with the IP and a port, and when I run the file in terminal I get the following when I send an HTTP request:

GIN] 2015/12/08 - 05:56:43 | 404 | 6.895µs | 127.0.0.1:60024 | GET /off

However, the bulb doesn't turn off or change in any way. Any suggestions?

add an ping endpoint, so tools can check if milight daemon is running or not.
on http get /ping the daemon will respond with 200 : milight-daemon [Version number]

We cant set the brightness for group 0.
http://jane:8080/brightness?group=0&level=100 will be accepted but dont change the brightness. Also i recognized huger delays for group=0 brightness ~230ms. Changing brightness for group=[1-4] works fine with ~1-15ms delay

To be able to start the daemon with ease including the systemd unit file. It might look like this:

[Unit]
Description=MilightDaemon

[Service]
TimeoutStartSec=0
ExecStart=[path to milight-daemon bin]

http convention is that the order of url params don't matter.
The api endpoint rgb only works correctly when the order matches:

1. r
2. g
3. b

i.e: r=255&b=0&g=0 will not result in changing the color to red, nothing happens.