Hue Introduced a new Protocoll with latest swversion and Hue Sync 1.5.x.
The Protocoll is currently reverse engineered.
This will take some time.
We Recommend the abbove method until the new versions can be used.
So like it’s describe in post, first you should remove Hue Sync app from your PC, then delete config files from %appdata%/HueSync and %appdata%/../Local/HueSync after that install older version from exe file also don’t update it until diyHue will support new protocols
Does DIY hue need to be hardwired, or will this work on WIFI? None of those versions detect my DIYhue bridge (which is on wifi), only my original Hue bridge…
You can use any Network interface. Just make sure you select the correct one (incl. MAC adress) because Original Apps need a certificate generated with the Interface Macadress.
In docker make sure you pass the Macadress as ENV Variable. In Host install script select the correct Interface if you have multiple.
I did experience the same issues when connecting to Hue Sync 1.5 / 1.6.
So I did some network sniffing to see what’s going on.
Might be related to my setup, but what I noticed was that the SSDP responses took too long…
So I did 2 things in my diyhue branch:
add an MDNS listener as an alternative to ssdp to discover the diyhue bridge
reduce the sleep time of the SSDP
I used the beta branch btw:
I can now work with Hue Sync 1.6 without issues and my Ambilight TV now also detects my bridge (which didn’t work before due to the missed SSDP respones )
Hello guys. Is this working with samsung and the hue sync app to? That would be awesome, so you have a good capture and can build your one Ambilight but not ao expensive like direct from Phillips.