diyhue / diyhue

Main diyHue software repo

diyHue - A Hue Bridge Emulator

diyHue provides a Ecosystem for several Smart Home Solutions, eliminating the need for vendor specific Bridges and Hardware. Written in Python and Open Source, you are now able to import and control all your Lights and Sensors into one System.

Lightweight and resource friendly, to run on small devices like the RPi .... 24/7

The Best part? No Cloud connection by Design!

Enjoy your diyHue enlighted Home.

Stats

Getting Started

All documentation and instructions can be found over at diyhue.readthedocs.io

Requirements

• coap-client: i.e. via apt install libcoap2-bin
• Python 3
• Python modules: ws4py, requests, astral, paho-mqtt see requirements.txt
• faketime: i.e. via apt install faketime

or

• Docker

Recommendation - minimal setup

You need a System that can run the python script or Docker Image 24/7!

Emulator	Lights	App
RaspberryPi 3B	WS2812 Strip + Wemos D1 mini Board	Hue Essentials (iOS & Android)

Working diyHue features

Functions	Devices	Apps	Lights	Smarthome
Control lights (all functions)	Amazon Alexa (control only the lights)	Hue Essentials	WS2812B and SK6812 smart led strips	Home Assistant
Control groups (all functions)	Deconz (Conbee 1 & 2)	Hue App	Phillips Hue	Openhab
Scenes (all functions)	Trådfri Gateway	hueManic	Ikea Trådfri	Jeedom
Routines	Hue Bridge (original + other emulators)	Kodi Hue Ambilight	Yeelight	Domoticz
Wake up	Logitech Harmony	OnSwitch	MiLight	Home Assistant Add-on
Go to sleep	Philips Ambilight TV's	LampShade	Hyperion.ng
Switches (custom esp8266 switches)		Hue Sync for PC	MQTT lights see mqtt
Autodiscover lights		HueSwitcher	any PWM(CCT, RGB, RGBW) incl. Dimming
Hue entertainment			On/Off 433Mhz devices (multiple devices for every esp8266)
			LYT8266
			WLED

Support

All documentation and instructions can be found over at diyhue.readthedocs.io

If you need help with diyHue you can get support from other users, aswell as the maintainer.

Slack

Use Slack for a general chat or fast live support.

However: Since Slack is faster at providing live Support but not as good when it comes to save and show known Issues, we kindly ask you to open a Topic at our Discourse group. This will provide Help for others in the future.

Discourse

Our Board might already have your fix and answer ready. Have a look!

General Note: Please provide some Logs to make it easier for all of us. Enable Debug by manually starting diyHue with additional --debug true argument.

Stability

Starting in Dec. 2020 we will introduce one Master and one Dev Branch. The Master will have the most stable code.

If you want to tinker and experiment you can try the dev Branch. Active development will take place here.

You want to get the latest features? Try the experimental Branch. Use at own Risk!

Please post on our Slack team any other device/application that you find to work with this emulator.

Contribute

diyHue is Opensource and maintained by volunteers in their free time. You are welcome to contribute and become a recognised member of the diyHue community. Feel free to add PR and Commits to our Dev Branch. If you are experienced in

• Webdesign
• Python
• Arduino
• Coding in general

We highly appreciate your support, making diyHue even better!

Support

diyHue is and will be Free to use. However it does take a lot of time to maintain the code etc etc.

Long story short.... you can support us at Ko-Fi

Thank you very much!

Credits

• Ben (@cheesemarathon) All fancy github integrations
• Stephan van Rooij - zigbee2mqtt integration
• @avinashraja98 - Hue Entertainment server
• Federico Zivolo (@FezVrasta) Internal WebGUI
• @J3n50m4t - Yeelight integration
• Martin Černý (@mcer12) - Yeelight color bulb
• probonopd https://github.com/probonopd/ESP8266HueEmulator
• sidoh https://github.com/sidoh/esp8266_milight_hub
• StefanBruens https://github.com/StefanBruens/ESP8266_new_pwm
• Cédric @ticed35 for linkbutton implementation
• @cheesemarathon - Help with Docker images
• @Mevel - 433Mhz devices
• @Nikfinn99 - PCB designs
• @crankyoldgit - IR Remote library

Additional Projects and Ideas

Hue living color light project for 3D printing: Thingiverse 2773413

License

diyhue's Issues

Startup failes with MiLight configuration

Traceback (most recent call last):
File "/opt/hue-emulator/HueEmulator3.py", line 1752, in
updateConfig()
File "/opt/hue-emulator/HueEmulator3.py", line 116, in updateConfig
if bridge_config["lights"][light]["manufacturername"] == "Philips": #update config lights firmware version

Reason: The MiLight configuration does not contain a field "manufacturername".

Workaround: Adding the field manually to the config.json file in the lights section

Solution: Check the existence of the key before accessing

How to use Google Assistant

When attempting to log into phillips hue account for linking with google assistant or out of home control. no bridge is found. but when in phillips hue app the bridge is found and can control lights.

my setup is ubuntu vm running bridge.

any help would be appreciated.

Cheers

Expose software version, add updater script

Suggestion:

• 1. make Software version of hue emulator "visible" within web ui, cli, etc.
     this way you will know if you need to run a update.
• 2. Adding a "update.py" to be run from web ui or cli makes it easier to run a update via easy_install.py script.

Can't connect to HueManic

So this is slightly related to #19 as well because I can't connect to the Sleep app either (not from the app itself and not via HueManic.) Is there a way in which I can tweak the config so that I can still connect to huemanic or maybe use a previous version of the app?

steps to reproduce
Use the latest version of both diyHue and HueManic. Enter the diyHue IP address (because for me it isn't detected automatically). While pairing click the pairing button in the diyHue UI and see the pairing bar freeze in HueManic.

Problems with IP configuration in docker container

Hello :)

Yesterday I set up the docker image of diyHue but I can't find my odeMCU/ESP8266 lights.

I'm running docker on a Raspberry Pi 3b+ and I used this command to create the container:

docker create --name=diyhue --network=pub_net --ip=192.168.178.151 --restart always -e "DEGUB=true" -v '/home/pi/hue-emulator/export/':'/opt/hue-emulator/export/':'rw' diyhue/core:latest

I can access the bridge without a problem. I can also link it with the hue app but I just can't find my lights.

I used the latest Arduino file to flash the lights.

I also don't know how to acces the debug logs. In the documentation it only states that I should add the attribute to the run command but it doesn't do anything.
Even when I read the docker logs to the container there is nothing mentioning debug.

I also think there may be something missing in that regard in the docker container?
Because in the repo there's a debug folder where the .py file is. But that folder is absent in the container.

Milight Setup

Hello how can I get the device ID of my Milight lights for input in milight setup?

How to remove diyHue

Today i tried to install diyHue with the Automatic install. I got the message that another instance was using port 443 (this is my Domoticz). I stopped Domoticz and tried the automatic install again. This worked, got the diyHue running. But when i started Domoticz again the Hue app didnt connect to the brigde again. Also tried to connect the bridge again in the app but now it doenst connect anymore.

What i tried till now: cleared the Hue app chache, removed the cert.pem and started the automatic install again. Without result.

Can you help me to fix this? I would really love to control my Yeelights with my Harmony Elite :)

I`m using port 443 for Domoticz and Controlicz.

This is the output of command curl https://127.0.0.1/api/nouser/config -k -v

*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=NL; ST=MyState; O=Domoticz; L=Domoticz; CN=*.domoticz.com; OU=Unit                                                                                                             51; [email protected]
*  start date: May 23 06:49:02 2015 GMT
*  expire date: May 20 06:49:02 2025 GMT
*  issuer: C=NL; ST=MyState; O=Domoticz; L=Domoticz; CN=*.domoticz.com; OU=Unit5                                                                                                             1; [email protected]
*  SSL certificate verify result: self signed certificate (18), continuing anywa                                                                                                             y.
> GET /api/nouser/config HTTP/1.1
> Host: 127.0.0.1
> User-Agent: curl/7.52.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Content-Length: 85
< Content-Type: text/html;charset=UTF-8
< Last-Modified: Sun, 13 Jan 2019 20:31:06 GMT
<
* Curl_http_done: called premature == 0
* Connection #0 to host 127.0.0.1 left intact
<html><head><title>Not Found</title></head><body><h1>404 Not Found</h1></body></

Zigbee radio options

Are any other zigbee radios supported? I have one of these and would love to use it with this project: https://www.tindie.com/products/Elelabs/elelabs-zigbee-raspberry-pi-shield/

I planned to use that radio to control some Ikea lamps (I don't have the Ikea gateway).

I'm willing to help test whatever to try and get this working if it's not currently supported.

Adding Hue Dimmer Switch

Hi there, I have set up DIYHue on my Pi a few weeks ago and everything has been running smoothly so far.
Today I bought a Hue Dimmer Switch thinking I could just add this via the Hue App Accessory tab, but if the Hub I'm connected to on the app is the RaspberryPi, it just searches for the accessory for ages and does not find it.
If I switch to the Hue Hub, this is found within 10 seconds.
Can I not add the original Hue Dimmer switch to the emulator?

I have found the schematics for the DIY Hue Switch, but I rather use the original one if I can.

Your assistance is much appreciated!

Start Level Change Not Working

When using the "Start Level Change" command to a bulb connected to the diyHue bridge, the bulb immediately reports an off state. I'm trying to figure out if this is being caused by my hub or being caused by diyHue. Here are the logs when I issue the command. The bulb responds correctly but it briefly reports as off and takes a while to respond with the correct level.

192.168.1.12 - - [13/Dec/2018 20:11:31] "GET /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/ HTTP/1.1" 200 -
192.168.1.12 - - [13/Dec/2018 20:11:41] "GET /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/ HTTP/1.1" 200 -
192.168.1.2 - - [13/Dec/2018 20:11:41] "GET /description.xml HTTP/1.1" 200 -
2018-12-13 20:11:42,240 - root - DEBUG - sync with lights
2018-12-13 20:11:42,304 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.44
2018-12-13 20:11:42,346 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.44:80 "GET /get?light=1 HTTP/1.1" 200 93
2018-12-13 20:11:42,414 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.19
2018-12-13 20:11:42,538 - root - DEBUG - Sending M-Search response to 192.168.1.6
2018-12-13 20:11:43,582 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.19:80 "GET /get?light=1 HTTP/1.1" 200 93
2018-12-13 20:11:43,658 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.10
2018-12-13 20:11:43,783 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.10:80 "GET /get?light=1 HTTP/1.1" 200 94
2018-12-13 20:11:43,835 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.20
2018-12-13 20:11:43,871 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.20:80 "GET /get?light=1 HTTP/1.1" 200 95
2018-12-13 20:11:44,443 - root - DEBUG - Sending M-Search response to 192.168.1.2
2018-12-13 20:11:45,849 - root - DEBUG - Sending M-Search response to 192.168.1.2
2018-12-13 20:11:48,877 - root - DEBUG - Sending M-Search response to 192.168.1.2
192.168.1.12 - - [13/Dec/2018 20:11:48] "PUT /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/5/state HTTP/1.1" 200 -
2018-12-13 20:11:48,904 - root - DEBUG - in PUT method
2018-12-13 20:11:48,911 - root - DEBUG - /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/5/state
2018-12-13 20:11:48,916 - root - DEBUG - b'{"bri_inc":254,"transitiontime":30}'
2018-12-13 20:11:48,978 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 127.0.0.1
2018-12-13 20:11:48,998 - root - DEBUG - {"e":"changed","id":"1","r":"lights","state":{"bri":254},"t":"event","uniqueid":"e2:0d:b9:ff:fe:06:79:5c-0a"}
2018-12-13 20:11:49,008 - requests.packages.urllib3.connectionpool - DEBUG - http://127.0.0.1:8080 "PUT /api/283145a4e198cc6535/lights/1/state HTTP/1.1" 200 41
2018-12-13 20:11:49,731 - root - DEBUG - LightRequest: http://127.0.0.1:8080/api/283145a4e198cc6535/lights/1/state
2018-12-13 20:11:49,744 - root - DEBUG - [
    {
        "success": {
            "/lights/5/state/bri_inc": 254
        }
    },
    {
        "success": {
            "/lights/5/state/transitiontime": 30
        }
    }
]
192.168.1.12 - - [13/Dec/2018 20:11:51] "GET /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/ HTTP/1.1" 200 -
192.168.1.12 - - [13/Dec/2018 20:11:55] "PUT /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/5/state HTTP/1.1" 200 -
2018-12-13 20:11:55,030 - root - DEBUG - in PUT method
2018-12-13 20:11:55,035 - root - DEBUG - /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/5/state
2018-12-13 20:11:55,038 - root - DEBUG - b'{"bri_inc":-254,"transitiontime":30}'
2018-12-13 20:11:55,081 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 127.0.0.1
2018-12-13 20:11:55,100 - root - DEBUG - {"e":"changed","id":"1","r":"lights","state":{"bri":1},"t":"event","uniqueid":"e2:0d:b9:ff:fe:06:79:5c-0a"}
2018-12-13 20:11:55,113 - requests.packages.urllib3.connectionpool - DEBUG - http://127.0.0.1:8080 "PUT /api/283145a4e198cc6535/lights/1/state HTTP/1.1" 200 39
2018-12-13 20:11:55,831 - root - DEBUG - LightRequest: http://127.0.0.1:8080/api/283145a4e198cc6535/lights/1/state
2018-12-13 20:11:55,841 - root - DEBUG - [
    {
        "success": {
            "/lights/5/state/bri_inc": -254
        }
    },
    {
        "success": {
            "/lights/5/state/transitiontime": 30
        }
    }
]
192.168.1.12 - - [13/Dec/2018 20:11:56] "PUT /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/5/state HTTP/1.1" 200 -
2018-12-13 20:11:56,368 - root - DEBUG - in PUT method
2018-12-13 20:11:56,376 - root - DEBUG - /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/5/state
2018-12-13 20:11:56,382 - root - DEBUG - b'{"bri_inc":0,"transitiontime":30}'
2018-12-13 20:11:56,438 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 127.0.0.1
2018-12-13 20:11:56,459 - requests.packages.urllib3.connectionpool - DEBUG - http://127.0.0.1:8080 "PUT /api/283145a4e198cc6535/lights/1/state HTTP/1.1" 200 39
2018-12-13 20:11:57,180 - root - DEBUG - LightRequest: http://127.0.0.1:8080/api/283145a4e198cc6535/lights/1/state
192.168.1.12 - - [13/Dec/2018 20:11:57] "PUT /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/5/state HTTP/1.1" 200 -
2018-12-13 20:11:57,203 - root - DEBUG - [
    {
        "success": {
            "/lights/5/state/bri_inc": 0
        }
    },
    {
        "success": {
            "/lights/5/state/transitiontime": 30
        }
    }
]
2018-12-13 20:11:57,220 - root - DEBUG - in PUT method
2018-12-13 20:11:57,230 - root - DEBUG - /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/5/state
2018-12-13 20:11:57,235 - root - DEBUG - b'{"bri_inc":0,"transitiontime":30}'
2018-12-13 20:11:57,275 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 127.0.0.1
2018-12-13 20:11:57,296 - requests.packages.urllib3.connectionpool - DEBUG - http://127.0.0.1:8080 "PUT /api/283145a4e198cc6535/lights/1/state HTTP/1.1" 200 39
2018-12-13 20:11:58,014 - root - DEBUG - LightRequest: http://127.0.0.1:8080/api/283145a4e198cc6535/lights/1/state
2018-12-13 20:11:58,029 - root - DEBUG - [
    {
        "success": {
            "/lights/5/state/bri_inc": 0
        }
    },
    {
        "success": {
            "/lights/5/state/transitiontime": 30
        }
    }
]
192.168.1.12 - - [13/Dec/2018 20:12:01] "GET /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/ HTTP/1.1" 200 -
192.168.1.2 - - [13/Dec/2018 20:12:01] "GET /description.xml HTTP/1.1" 200 -
2018-12-13 20:12:01,995 - root - DEBUG - Sending M-Search response to 192.168.1.2
2018-12-13 20:12:02,911 - root - DEBUG - sync with lights
2018-12-13 20:12:02,971 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.44
2018-12-13 20:12:03,011 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.44:80 "GET /get?light=1 HTTP/1.1" 200 93
2018-12-13 20:12:03,067 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.19
2018-12-13 20:12:03,239 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.19:80 "GET /get?light=1 HTTP/1.1" 200 93
2018-12-13 20:12:03,291 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.10
2018-12-13 20:12:03,446 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.10:80 "GET /get?light=1 HTTP/1.1" 200 94
2018-12-13 20:12:03,498 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.20
2018-12-13 20:12:03,532 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.20:80 "GET /get?light=1 HTTP/1.1" 200 95
2018-12-13 20:12:05,362 - root - DEBUG - Sending M-Search response to 192.168.1.2
192.168.1.12 - - [13/Dec/2018 20:12:05] "GET /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/ HTTP/1.1" 200 -
2018-12-13 20:12:08,138 - root - DEBUG - Sending M-Search response to 192.168.1.2
2018-12-13 20:12:09,745 - root - DEBUG - Sending M-Search response to 192.168.1.40
192.168.1.12 - - [13/Dec/2018 20:12:11] "GET /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/ HTTP/1.1" 200 -
192.168.1.12 - - [13/Dec/2018 20:12:11] "GET /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/ HTTP/1.1" 200 -
2018-12-13 20:12:17,289 - root - DEBUG - {"e":"changed","id":"1","r":"lights","state":{"bri":135},"t":"event","uniqueid":"e2:0d:b9:ff:fe:06:79:5c-0a"}
192.168.1.12 - - [13/Dec/2018 20:12:19] "GET /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/ HTTP/1.1" 200 -
192.168.1.12 - - [13/Dec/2018 20:12:19] "GET /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/ HTTP/1.1" 200 -
2018-12-13 20:12:20,569 - root - DEBUG - sync with lights
2018-12-13 20:12:20,629 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.44
2018-12-13 20:12:20,664 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.44:80 "GET /get?light=1 HTTP/1.1" 200 93
2018-12-13 20:12:20,737 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.19
2018-12-13 20:12:20,852 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.19:80 "GET /get?light=1 HTTP/1.1" 200 93
2018-12-13 20:12:20,904 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.10
192.168.1.2 - - [13/Dec/2018 20:12:20] "GET /description.xml HTTP/1.1" 200 -
2018-12-13 20:12:21,083 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.10:80 "GET /get?light=1 HTTP/1.1" 200 94
2018-12-13 20:12:21,135 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.1.20
192.168.1.12 - - [13/Dec/2018 20:12:21] "GET /api/a7ab75ae5e53dba6eea54b2f74a08bcb/lights/ HTTP/1.1" 200 -
2018-12-13 20:12:21,188 - requests.packages.urllib3.connectionpool - DEBUG - http://192.168.1.20:80 "GET /get?light=1 HTTP/1.1" 200 95
2018-12-13 20:12:21,745 - root - DEBUG - Sending M-Search response to 192.168.1.2
2018-12-13 20:12:24,826 - root - DEBUG - Sending M-Search response to 192.168.1.2
2018-12-13 20:12:27,791 - root - DEBUG - Sending M-Search response to 192.168.1.2

If there is anything else you need, let me know.

Future google home support.

My whole goal is to use this system with the system of google homes I have in my house and I’m wondering if there is a way to get this to work with google home or if some one is working one a way.

diyhue add support iConnectHue Discotainment ?

A very famous iOS app iConnectHue have the Discotainment feature, it found my Entertainment but unable to add the lights (Yeelights v2 in my case). I'm sure it will work well I wish diyhue add support for let iConnectHue detect it? (It asked for 'software update' for the bulbs in app)

Fail to start? KeyError: 'Type'

Traceback (most recent call last):
  File "./HueEmulator3.py", line 1847, in <module>
    updateConfig()
  File "./HueEmulator3.py", line 147, in updateConfig
    if bridge_config["groups"][group]["type"] == "Entertainment":
KeyError: 'type'

Just try to start manually in VM Ubuntu.

Hue update message

Describe the bug
I installed diyHue and Hue app on iPhone. Then I connect to the bridge and then cannot get out of this message.
If i press Update it say update fails and get back to this message. How to get out of this message?

To Reproduce
Steps to reproduce the behavior:

1. Open Hue iOS App
2. Connect to Bridge
3. Got this message
4. Press Update
5. It fails
6. Again see message for update

Sleep as android can no longer connect with diyHue

Describe the bug
DiyHue used to work fine with Sleep as android.

To Reproduce
Steps to reproduce the behavior:
Simply install sleep as android and attempt to connect it with diyHue, it will hang on attempting to add it.
I tried installing an older version, but with these it still fails.
As diyHue has been updated I assume the problem must lie here.

Expected behavior
Well, it should be working.

Suggestion for light discovery without external dependency to nmap

The external dependency to nmap has given me problems over the last few weeks.
The nmap system call for light discovery in scanForLights( ) is giving inconsistent results and is rather slow. The Hue-app almost always times out before discovery finishes and never finds all the lights in one go. Some lights may even never be found.

Suggested solution:
I wrote my own host discovery based on sockets instead. As all hosts are on the same network as diyHue you can set a rather short timeout value and still be able to connect.
It is fast enough to discover all hosts on a /24 network and register them before the Hue-app times out.
The code only supports /24 networks but could easily be changed to allow for /16 if needed (not without significant penalty to the time it would consume though).

import socket
...
def scanHost(host, port):
    sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
    sock.settimeout(0.01)
    result = sock.connect_ex((host, port))
    sock.close()
    return result

def findHosts():
    addr = 0
    validHosts = []
    host = HostIP.split('.')
    while addr <= 255:
        host[3] = str(addr)
        testHost = host[0]+"."+host[1]+"."+host[2]+"."+host[3]
        if scanHost(testHost, 80) == 0:
            validHosts.append(testHost)
        addr = addr+1

    return validHosts

Calling findHosts( ) from scanForLights( ) instead of the current nmap-based system call will do the trick.
Try it out and feel free to use it as you like.

RGB light not avalible

Hello, I am trying to get the lighting to work but getting little progress.
I am able to flash the 'generic on/off' on to my nodeMcu and it works perfectly with the hue app. But once i upload the RGB bulb, and i scan for the light it shows up and then says not avalible. If i deleted it and scan again for the light it shows up but i am unable to control it with the rgb bulb sketch. What could the problem be?

Belkin Wemo or general IFTTT support would be great

I have a Logitech Harmony remote.
Sadly, the only devices supported are Philips Hue.
It would be great if diyHue would support "virtual lightbulbs". So you can connect these with on/off with IFTTT (via URL in json file).
This way you can add all kinds of devices...
Please consider this. Thanks.

keeps crashing

after a few minutes the prograsm no longer works and a reinstall is needed

Connect Ikea light with Hue Bridge

I now have 2 Ikea lamps connected to my Hue Bridge and they are working as 'Hue Lights'. But they are not working in the entertainment rooms.

I found this project and I thought maybe with this I can add other lights besides Hue to use as lights in a entertainment room ( I don't want to buy expensive Hue lights for in garage but want to use sync for parties in the garage).

As I read it's possible with lights connected to this emulator to use in the entertaiment room. Is it possible to connect Ikea lights to my Hue bridge which is connect to this Hue bridge emulator and use that Ikea lights in a entertainment room or do I need to use the Raspbee module or the Ikea bridge to connect the Ikea lights to and then add them in the hue entertainment room?

MiLight sync error because of missing field "saturation"

** Config **

ESP_MiLight-Hub 1.8.5 (nodemcuv2), several bulbs and stripes rgb_cct and rgbw

** Output **

Docker Setup Initiated
Restoring Certificate
Certificate Restored
Restoring config
Config restored
Docker Setup Complete
ERROR:root:light 7 is unreachable
Traceback (most recent call last):
File "/opt/hue-emulator/HueEmulator3.py", line 835, in syncWithLights
bridge_config["lights"][light]["state"]["sat"] = int(light_data["saturation"] * 2.54)
KeyError: 'saturation'

** returned config 7 from esp-milight-hub **

{
"state": "ON",
"status": "ON",
"brightness": 255,
"level": 100,
"hue": 31,
"color": {
"r": 255
},
"bulb_mode": "color"
}

** Workaround for me **

line 835:
try:
bridge_config["lights"][light]["state"]["sat"] = int(light_data["saturation"] * 2.54)
except KeyError:
pass

HueEmulator3.scanForLights does not scan all found ips

Describe the bug
I'm using the WS2812B HueStrip example with a dockerized bridge. When I search for the lamp with the hue app, it is not found.

I found that there is a problem in the python code. It uses nmap to search for devices listening on port 80. From this list, the last element is deleted. See code snippet from HueEmulator3.py
760 - logging.info(pretty_json(device_ips))
761 - del device_ips[-1] #delete last empty element in list
I do not know why the last one is deleted - comment suggests that the last element should be empty - which is not the case for me. In fact, the last element is the device I'm searching.

I'm using the docker image hosted on a Windows 10 with Docker for Windows.

Logs
Logs after pressing the search button in the Hue App
172.17.0.1 - - [26/Dec/2018 11:57:13] "POST /api/a7161538be80d40b3de98dece6e91f90/lights HTTP/1.1" 200 -
2018-12-26 11:57:13,226 - root - INFO - in post method
2018-12-26 11:57:13,226 - root - INFO - /api/a7161538be80d40b3de98dece6e91f90/lights
2018-12-26 11:57:13,226 - root - INFO - b'{}'
172.17.0.1 - - [26/Dec/2018 11:57:13] "GET /api/a7161538be80d40b3de98dece6e91f90/groups HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:13] "GET /api/a7161538be80d40b3de98dece6e91f90/lights HTTP/1.1" 200 -
2018-12-26 11:57:13,648 - root - INFO - sync with lights
172.17.0.1 - - [26/Dec/2018 11:57:14] "GET /api/a7161538be80d40b3de98dece6e91f90/groups HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:14] "GET /api/a7161538be80d40b3de98dece6e91f90/lights HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:15] "GET /api/a7161538be80d40b3de98dece6e91f90/groups HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:15] "GET /api/a7161538be80d40b3de98dece6e91f90/lights HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:16] "GET /api/a7161538be80d40b3de98dece6e91f90/groups HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:16] "GET /api/a7161538be80d40b3de98dece6e91f90/lights HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:17] "GET /api/a7161538be80d40b3de98dece6e91f90/groups HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:17] "GET /api/a7161538be80d40b3de98dece6e91f90/lights HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:18] "GET /api/a7161538be80d40b3de98dece6e91f90/groups HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:18] "GET /api/a7161538be80d40b3de98dece6e91f90/lights HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:18] code 404, message not found
172.17.0.1 - - [26/Dec/2018 11:57:18] "GET /cm?cmnd=Status%200 HTTP/1.1" 404 -
172.17.0.1 - - [26/Dec/2018 11:57:19] "GET /api/a7161538be80d40b3de98dece6e91f90/groups HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:19] "GET /api/a7161538be80d40b3de98dece6e91f90/lights HTTP/1.1" 200 -
2018-12-26 11:57:19,947 - root - INFO - [
"192.168.178.1",
"192.168.178.22",
"192.168.178.26",
"192.168.178.31",
"192.168.178.47"
]
2018-12-26 11:57:20,084 - root - INFO - registration fail, is the link button pressed?
172.17.0.1 - - [26/Dec/2018 11:57:20] "GET /api/a7161538be80d40b3de98dece6e91f90/groups HTTP/1.1" 200 -
172.17.0.1 - - [26/Dec/2018 11:57:20] "GET /api/a7161538be80d40b3de98dece6e91f90/lights HTTP/1.1" 200 -

The last ip in the list is the correct one.

I commented the line with the del instruction and the app found the lamp! :)

Entertainment Area not working for me

Describe the bug
Cant create entertainment area

To Reproduce
Open the Offical Hue App
Settings >> Entertainment Area >> create entertainment area >> Select area >> Select lights >> Update required prompt

Expected behavior
The lights shouldnt be update

Logs

Additional context

Can we connect to Hue light strip without Hue Bridge

Is your feature request related to a problem? Please describe.
According to the schematic and documentation, looks like one can control / add hue lights only if they have a hue bridge, it would be nice to be able to use the emulator to directly discover new lights

Lights control / Link device broken=?

1st

I used "Import from Bridge" and I got the message, that 3 devices are found.
config.json shows them

"lights_address": { "1": { "ip": "192.168.1.211", "light_id": "1", "protocol": "hue", "username": "********" }, "2": { "ip": "192.168.1.211", "light_id": "2", "protocol": "hue", "username": "********" }, "3": { "ip": "192.168.1.211", "light_id": "3", "protocol": "hue", "username": "********" }

But in the Webinterface, on Lights control, I see nothing,...
I supose to see the 3 devices?

2nd

I try to use "Link Device".
In my app I find the diyHUE Bridge, but it tells me to press the round Button.
How are I am suposed to do this?

Hue Entertainment not unbinding correctly when timed out

Bug Description
The Hue Entertainment support does not handle the case in which the device/application syncing the lights with an entertainment area crashes unexpectedly/stops syncing without explicitly telling the bridge emulator that it is about to stop gracefully. This results in the bridge emulator thinking that sync is still active, even if no more packets are sent. This breaks functionality with the Hue Sync app for Windows across restarts.

Steps To Reproduce

1. Download Hue Sync for Windows
2. Start synchronizing with an Entertainment Area
3. Restart PC without stopping sync manually via the Hue Sync app
4. Notice how Hue Sync now states that the bridge is unreachable, and that someone else(really us, but the session hasn't been cleared) is syncing with our Entertainment Area
5. On the Pi, sudo systemctl restart hue-emulator.service in order to clear the entertainment session state
6. Hue Sync is now able to properly connect

This issue does not happen if the user goes into the Hue Sync app and manually disables sycing before shutting the computer down/restarting.

Expected behavior
When a Hue Entertainment host connects to the emulator and starts syncing, a "session timer" should be started, with a timeout of a few seconds that resets when packets are received. If the timeout is reached, the session should be cleared, thus handling the case in which the host has suffered a force close/crash. As of now, the Hue Sync app either needs to be manually closed before shutting down, or the emulator needs to be restarted after every non-graceful shutdown of a Hue Entertainment-enabled app.

How do you install the software on a Raspberry Pi?

Hello - I'm a noob here.
This is my second Raspberry Pi project..

I have a Raspberry Pi 3 B+.

How do you install this software on the device?

Thank you all for any help you can lend, and for all of your hard work!

Run on the philips hue bridge itself

Hi,

I was just wondering since this is python and the hue bridge runs openwrt, could you maybe develop a package that we can install via cli on the bridge ?

only 1 time-access on the pcb is needed to access the openwrt on the bridge.

And since this bridge (2.0) also has wifi HW but not activated we can use this to connect directly to devices.

Just a tought.

kind regards,
XtremeCoder007

Cannot connect to the hub anymore

Describe the bug
I installed the emulator on Pi succesfully a month ago more or less and everything works. Today the Hue app keep sayin "Could not connect".

To Reproduce

Expected behavior
A clear and concise description of what you expected to happen.

Cannot search any light?

Today I delete all lights in Hue app and unable to search them, is it diyhue problem? I can connect to the bridge but unable to search any lights. They are all turned on and they are Yeelight 2nd hen RGB and yeelight plus strip

Hue App wants update - App Fails to update - Can not use app without updating

Hello,
I am using hue emulator on ubuntu vm. has been up and running for some time. Now when i open hue app it asks for update. when i click update it fails and sends me back to update screen.
there does not seem to be a way to avoid update. I tried deleting cert file and updating hue bridge software. same issue persists.

help would be much appreciated.

Cheers

Support for Samsung smart things

Is there a way to make this interface with Samsung SmartThings hub?

Cant find DIY esp8266 light

I connected the hue app successful with the raspberry pi but i cant find my esp8266 board.
I use the Node Mcu 1.0 and can connect to its ip and set the state and everything but the Hue app doesnt find it. The nmap package is also installed.

Can't pair to Hue app

Describe the bug
When I enter the IP it asks me to press the link button, I press "activate" on the UI but nothing happens until the pairing process times out.

Expected behavior
The pair process should complete succssfully

Logs

/opt/hue-emulator   12s
❯ sudo python3 HueEmulator3.py 
10.0.0.231 - - [25/Dec/2018 17:15:14] "GET /hue/linkbutton?username=&password=&action=Activate HTTP/1.1" 200 -
10.0.0.2 - - [25/Dec/2018 17:15:23] "GET /description.xml HTTP/1.1" 200 -
10.0.0.186 - - [25/Dec/2018 17:15:28] "GET /api/nouser/config HTTP/1.1" 200 -
10.0.0.231 - - [25/Dec/2018 17:15:31] "GET /hue/linkbutton?username=&password=&action=Activate HTTP/1.1" 200 -
10.0.0.231 - - [25/Dec/2018 17:15:39] "GET /hue/linkbutton?username=&password=&action=Activate HTTP/1.1" 200 -
10.0.0.231 - - [25/Dec/2018 17:15:45] "GET /hue/linkbutton?username=Hue&password=Hue&action=Activate HTTP/1.1" 200-
10.0.0.231 - - [25/Dec/2018 17:15:49] "GET /hue/linkbutton?username=&password=&action=Activate HTTP/1.1" 200 -
10.0.0.2 - - [25/Dec/2018 17:15:53] "GET /description.xml HTTP/1.1" 200 -
10.0.0.231 - - [25/Dec/2018 17:15:56] "GET /hue/linkbutton?username=&password=&action=Activate HTTP/1.1" 200 -

Additional context

Home assistant and diy hue

Do I need to run home assistant on two different raspberry pi’s for this to work or can I run them on the same one. I believe you run in to issues with them trying to use the same up address. Is there a fix anyone knows for this?

Sleep / Wakeup activities (to turn light off or on) seems not working properly

Describe the bug
When I open the Hue app and set a new activity the behaviour is:
• in case of 'wake up' activity (lights should be turn on smoothly) nothing happens at the time I set
• in case of 'sleep' activity the Hue app crash (I don't know if the response of the hue emulator is wrong or it is a problem of the app itself)

To Reproduce
Steps to reproduce the behavior:

1. Download and open the HUE app on Android
2. Set new sleep/wake up activity

Expected behavior
Lights should turn on or off according with the type of the selected acitivity

Additional context
Add any other context about the problem here.

Service failing to start

Hey guys,
First of all, thanks for all your hard work on this project, I really love it.

I am having a few issues however, with the service failing to start.
This has happened a a few times now, where after a restart the hue-emulator service just fails to start on my Raspberry Pi.

The only way I have been able to resolve this was by renaming /opt/hue-emulator and re-running the install.
This obviously wipes my configuration, but I am able to start the service again. After I stop the service, I copy the config.json file to the newly generated /opt/hue-emulator folder, to no avail, the service continues to refuse to start.

I don't have a massive number of devices so I have reconfigured everything a couple of times, until today where this happened again.

Obviously this isn't sustainable so I would very much appreciate your help trying to resolve and understand what exactly is causing this.
After this happened the last time I created a cron job to backup the whole /opt/hue-emulator folder, I have restored this but unfortunately this did not help.

Please see below the journalctl output of when I try to start the service, and please do let me know if you need anything else in order to understand what's going on and how can I get the service to start again without wiping config.

pi@raspberrypi:/opt $ sudo journalctl -u hue-emulator.service
-- Logs begin at Fri 2018-12-14 20:41:29 GMT, end at Fri 2018-12-14 20:55:08 GMT. --
Dec 14 20:41:39 raspberrypi systemd[1]: Started Hue Emulator Service.
Dec 14 20:41:40 raspberrypi HueEmulator3.py[503]: Traceback (most recent call last):
Dec 14 20:41:40 raspberrypi HueEmulator3.py[503]: File "/opt/hue-emulator/HueEmulator3.py", line 1723, in
Dec 14 20:41:40 raspberrypi HueEmulator3.py[503]: updateConfig()
Dec 14 20:41:40 raspberrypi HueEmulator3.py[503]: File "/opt/hue-emulator/HueEmulator3.py", line 118, in updateConfig
Dec 14 20:41:40 raspberrypi HueEmulator3.py[503]: if bridge_config["groups"][group]["type"] == "Entertainment":
Dec 14 20:41:40 raspberrypi HueEmulator3.py[503]: KeyError: 'type'
Dec 14 20:41:40 raspberrypi systemd[1]: hue-emulator.service: Main process exited, code=exited, status=1/FAILURE
Dec 14 20:41:41 raspberrypi curl[522]: % Total % Received % Xferd Average Speed Time Time Time Current
Dec 14 20:41:41 raspberrypi curl[522]: Dload Upload Total Spent Left Speed
Dec 14 20:41:41 raspberrypi curl[522]: [147B blob data]
Dec 14 20:41:41 raspberrypi systemd[1]: hue-emulator.service: Control process exited, code=exited status=7
Dec 14 20:41:41 raspberrypi systemd[1]: hue-emulator.service: Unit entered failed state.
Dec 14 20:41:41 raspberrypi systemd[1]: hue-emulator.service: Failed with result 'exit-code'.
Dec 14 20:42:32 raspberrypi systemd[1]: hue-emulator.service: Service hold-off time over, scheduling restart.
Dec 14 20:42:33 raspberrypi systemd[1]: Stopped Hue Emulator Service.
Dec 14 20:42:33 raspberrypi systemd[1]: Started Hue Emulator Service.
Dec 14 20:42:34 raspberrypi HueEmulator3.py[573]: Traceback (most recent call last):
Dec 14 20:42:34 raspberrypi HueEmulator3.py[573]: File "/opt/hue-emulator/HueEmulator3.py", line 1723, in
Dec 14 20:42:34 raspberrypi HueEmulator3.py[573]: updateConfig()
Dec 14 20:42:34 raspberrypi HueEmulator3.py[573]: File "/opt/hue-emulator/HueEmulator3.py", line 118, in updateConfig
Dec 14 20:42:34 raspberrypi HueEmulator3.py[573]: if bridge_config["groups"][group]["type"] == "Entertainment":

Your help is greatly appreciated.

Can't Add Lights After App Update

After the latest app update, there is a prompt in the Hue app to update the software of the hub. This of course, fails. But when it does, it prevents you from accessing most of the functions of the Hue app, even ones that worked before. Are you planning on updating diyHue to at least let us use the functions that were working before, even if the new ones like power on memory, are not supported? Even if the app was tricked into thinking the hub was updated, I would think the old functionality would still work.

Using another Port?

Hello there,
I'm currently trying to set up diyHue on my raspberry pi.
I'm currently running a NGINX server on that device which definitely explains why I get "ERROR!! Port 80 already in use. Close the application that use this port and try again." when I try to use the installer.

Is there any possible thing I could do to change the port that diyHue uses?
I want to reroute everything with NGINX because I don't want to open a ton of ports for all the stuff I want to access on my raspberry pi.

I would really appreciate some help on this matter if it's possible...

Greetings

Hue Sync not working with lights?

Describe the bug
The app side all seems working fine, I playing some youtube video and the Hue Sync app did detect it and changing color in the app, but all my lights seem nothing happens, won't sync. I can change the scene, turn on/off , even using another app like Hue Disco, iLightShow, no problem, just any app related to Hue Entertainment, it able to detect my entertainment area, but the lights just won't do anything.

Unable to pair with Hue app (docker install on macOs)

Hi, I'm fairly new to python / docker. Currently, I'm trying to run the app on macOs using the docker method. I was able to open the /hue/linkbutton page, and manually find the bridge emulator in the hue mobile app. However the activate method within the linkbutton page doesn't seem to do anything. The mobile app doesn't register any 'push-link' events.

Generated SSL certificate valid for 30 days in some cases

The generated SSL certificate is only valid for 30 days if

• /opt/hue-emulator already exists but no cert.pem is available (first path in easy_install.sh)
• or the bridge is running as docker image

Is that by intention or an bug?

Help using the Raspbee module

Hi Team,

I was wondering if you could help me figure out what am I doing wrong while trying to set up an official Hue Switch to use with DiyHue.

I have acquired and installed the Raspbee module on my RaspberryPi, and followed the instructions to install Deconz.
I managed to install it, but this is where everything starts to get a little blurry.
While trying to follow the instructions on the Raspbee page, it is clear that these are mostly out of date...
The 1st time I opened http://rpi-ip:8080, the page loading up was clearly different to the one described on your page.
This loads the "Phoscon App", which seems to be a newer version of Deconz? Through trial and error though, I managed to find the old portal, and managed to click "Open Network" in "Settings" to search for devices.

This has found the Philips Hue Dimmer Switch, however I'm not sure how to tie it all together, (i.e. Deconz, Hue App and the Switch set up).

I have noticed that since having the Raspbee module, the Hue App detects a new accessory (it didn't before). If I dare click on it however, the app immediately crashes, so I can't set up the switch via the Hue App.
While the Deconz software has "Network Open" no other devices are found other than the Dimmer Switch (I have a Lightstrip Plus, Hue Iris and a standard Bulb that I was expecting to see there as well).

Can you please clarify how can I use the Hue Dimmer switch to control my Hue lights and Yeelight bulbs through the Hue App?
I thought the Switch could be added through the app if we had the Raspbee module, but this doesn't seem to be the case after all...

On another subject, I have tried using the Hue Essentials app as suggested to add the DiyHue emulator, I've selected Connect Manually when adding a Bridge, tried "DiyHue" and "Philips Hue" options and both crash the App after clicking "Activate" on the http://xxxxxx:8080/hue/linkbutton page...

Many thanks

Unable to connect to bridge

When attempting to connect to bridge emulator, connection fails and app reports unable to connect.
I have updated to newest emulator and problem has not been resolved. This issue has only recently started. I have not had this issue in the past. em running on ubuntu vm.

How to get this work on MacOS Mojave?

Hi, I'm a total newbie and I tried my very best to install but still failed.
Here's my log when I perform: python3 HueEmultator3.py

MacBook-Pro:BridgeEmulator chrischua$ python3 HueEmulator3.py File "/usr/local/bin/ip", line 39 print 'Executing: %s' % cmd ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print('Executing: %s' % cmd)? cat: /sys/class/net//address: No such file or directory Traceback (most recent call last): File "HueEmulator3.py", line 61, in <module> dockerMAC = check_output("cat /sys/class/net/$(ip -o addr | grep " + HostIP + " | awk '{print $2}')/address", shell=True).decode('utf-8')[:-1] File "/usr/local/Cellar/python/3.7.1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/subprocess.py", line 389, in check_output **kwargs).stdout File "/usr/local/Cellar/python/3.7.1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/subprocess.py", line 481, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command 'cat /sys/class/net/$(ip -o addr | grep 192.168.0.134 | awk '{print $2}')/address' returned non-zero exit status 1.

Logitech POP support

Currently, Logitech POP can't find the diyHue instance. It seems like that there's an implementation missing which makes the POP app not find the bridge at all. The implementation should probably not be too hard as both ha-bridge and the hue-emulation component from Home Assistant already have support implemented for it.

Merged code from Home Assistant: home-assistant/core#12833
Issue from ha-bridge: bwssytems/ha-bridge#623

With these information from the two links, we could most likely make diyHue compatible with POP

Alexa Color change support

Somehow i managed to add a light to my alexa so i can control the lights & dimm & color, and it did work. I was able to change the color & brightness!
But i needed to reinstall the bridge on my pi so they are now gone.
If i now try to add a Light from the Bridge its only accessable as a dimmable light.
Any solution?
Why did it work last time? i thought the color controll options were only accessable over the cloud?

Impossible to change timezone

Hi there! First of all, I would like to thanks the developer for his job, this project rocks!

I'm facing a little issue while trying to change the timezone set on Bucarest as default to the one of my country. In fact, if I try to change it in the setting of the Hue App, it displays an error saying it is impossible to load the timezones.

Updater point to old repo

HueEmulator3.py need to get config updates from this git repo instead of the old one.

Pairing issue with Philips TV

Describe the bug
I'm trying again to pair Hue Emulator to my old Philips TV but I can't manage to make the pair work.

Something I noticed is that when I scan for bridges through the TV, it finds "Philips hue" even if I renamed the hue emulator to "Hue Emulator" (and I can see the new name on the iOS app).

I already formatted the TV with the factory reset option but it always finds "Philips hue" and when I click the "activate" button nothing happens.

Logs

10.0.0.2 - - [25/Dec/2018 19:33:48] "GET /description.xml HTTP/1.1" 200 -
10.0.0.2 - - [25/Dec/2018 19:34:50] "GET /description.xml HTTP/1.1" 200 -
10.0.0.17 - - [25/Dec/2018 19:34:57] "GET /description.xml HTTP/1.1" 200 -
10.0.0.2 - - [25/Dec/2018 19:35:18] "GET /description.xml HTTP/1.1" 200 -
10.0.0.2 - - [25/Dec/2018 19:36:27] "GET /description.xml HTTP/1.1" 200 -
10.0.0.2 - - [25/Dec/2018 19:39:44] "GET /description.xml HTTP/1.1" 200 -
10.0.0.231 - - [25/Dec/2018 19:40:43] "GET /hue/linkbutton?username=&password=&action=Activate HTTP/1.1" 200 -