Home

Awesome

Philips Hue light control plasmoid for KDE (Stand alone version)

This plasmoid enables you to control Philips Hue light bulbs. The idea of the stand alone version is that it requires no compiled backend and thus can be deployed as is, e.g. via Get Hot New Stuff.

It allows you to

License

This software is distributed under the LGPL 2.1 License. See COPYING for details.

Requirements

Compile and install

git clone https://github.com/Fuchs/hoppla-sa.git
cd hoppla-sa

Global installation

mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
make
sudo make install

Local installation (per user)

plasmapkg2 -i package

to install the plasmoid

and

plasmapkg2 -r package

to remove it again.

Control lights from outside your network

You have to set up a public reachable proxy, I recommend apache httpd or nginx / lighttpd over a secured (TLS) connection with basic auth. A possible apache httpd configuration would be

<IfModule mod_ssl.c>
        <VirtualHost _default_:443>
                ServerName hue.mydynamicdnsdomain.org
                ProxyRequests On
                <Proxy *>
                   Order deny,allow
                   Allow from localhost
                </Proxy>

                SSLEngine on

                SSLCertificateFile /etc/ssl/certs/apache.pem
                SSLCertificateKeyFile /etc/ssl/private/keys/apache.key

                <Location "/">
                        AuthType Basic
                        AuthName "Restricted Content"
                        AuthUserFile /etc/httpd/some/place/.htpasswd-hue
                        Require valid-user
                </Location>
                # Set IP to your internal hue bridge IP
                ProxyPass / http://192.168.1.1/
                ProxyPassReverse / http://192.168.1.1/
        </VirtualHost>
</IfModule>

where mydyanmicdnsdomain.org is a domain pointing at your public address from your home network. Please read your httpd documentation on how to set it up, especially on how to add basic authentication. Note that due to the higher delay between requests and replies to the bridge, this can lead to the plasmoid being sometimes not up to date about the current state until the next background update occurs. Updates can always be forced with the refresh button.