Link-Button not working #1020
Comments
|
It may sound wired but the clock on the device what you use to click the linkbutton must be in sync with the device where bridge emulator is running. This is because the web-ui of diyhue is also an app andit is sending the current timestamp (on browser device) to bridge emulator config. If the difference between this timestamp and local bridge emulator timestamp is less than 30 seconds then the bridge emulator allow device pairing. |
|
Both, my server and my phone have the identical time. The server as well as my phone uses a time service to synchronize. //Edit I have been thinking about your tip, so I checked the different times on the server, the Docker container, and the web interface. Using Unfortunately, the connection still wasn't possible. When I compared the container's time with the time from the web UI, I noticed a discrepancy of approx. 1 minute. Unfortunately, I haven't yet found a way to fix this.
//Edit 2 Even after adding the local files, the time in the Web UI lags behind. |
|
Do you also have an original Hue Bridge on the same network? |
|
I have an original Hue Bridge on the same network, I have also tested switching the original Bridge off during the whole process. When I search for the diyhue bridge, I explicitly search for the IP. The logs during the pairing process: |
|
If you try Hue Essentials app it will pair? |
Didn't worked unfortunately. |
|
|
Thank you, then it is still a problem with time. How can I fix the time lag? Can I extend the time to connect? |
|
Javascript (the webui) uses date.now, this comes from the local machine running the webui(the browser you push link) you can add 1 minute to youre time to fix this. Also 1 thing i noticed with windows is that over time the clock is out of sync and i have to re sync the clock every month. |
Genius. Let me set up a new VM and I'll test two approaches I have:
|
|
I was able to partially solve the problem. I didn't know that the timestamp from the local system was relevant. Anyway, thanks to a tip from hendriksen-mark, I checked my Windows clock, and indeed the time was asynchronous compared to the atomic clock. I then set the NTP server to de.pool.ntp.org and synchronized the time. With both synchronized and unsynchronized time and a changed value of the last_button_press variable (in my case from 30 seconds to 90 seconds), I was able to connect to the bridge. I tested the same with the Docker variant, leaving the value at the default value of 30 seconds. Despite the synchronized and correct time, there was no successful synchronization. I then used my MacBook to click the link button, and surprisingly, a connection with the Hue app was immediately established. It would definitely be helpful to update the documentation to mention that the local system time is relevant for establishing the connection. Thank you both for your quick responses and good ideas <3 |
Same trouble, all is well synchronized but same issue with latest version an HA docker integration... |
|
hi, did you setup the right timezone in the webui> diyhue> bridge> bridge config? |
|
Yes i did, localtime is correct 👍 |
|
What else do you see in the logs? |
Operation appears to be successful then app tell me there is no bridge found ... |
|
are you using diyhue withou a hue account? |
|
With official app i don't see how to use bridge without any account |
|
It worked ! Thank you :-) |
|
now that it works its best to disable app updates in the app store/play store |
Issue does not already exist?
I have searched and found no existing issue
Select Environment
Docker
Home Assistant related?
No
Description
I am currently having issues with my diyhue installation. I cannot add my diyhue bridge in the Hue app nor does the link button work.
I have already tried several approaches: complete reinstallation, using Docker, using docker-compose, automatic installation script without Docker, changing the MAC address for the VM, deleting the Philips Hue app along with its cache, changing IP addresses, and trying an older version of diyhue.
The diyHue server is not running on a Raspberry Pi, but on a Debian 12 VM under Proxmox. Everything was working fine until a few days ago when the diyhue bridge suddenly became unreachable in the Philips app without any changes or restarts.
docker-compose.yml
docker command
HTTPS certificate check
Errorlog:
Steps to reproduce
Please enter your operating system details here
What DiyHue version(branch) are you using?
master (latest)
The text was updated successfully, but these errors were encountered: