-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LinkButton does not work #947
Comments
Hi, Please note that all requests are coming from your computer (192.168.2.50). The pair requests are POST and not GET so for some reasons the Hue app don't even try to pair. Maybe you replaced the certificate and need to wipe hue app data or reinstall (iPhone) because it detect a certificate change (man in middle attack). |
Hi, I see! I thought it does not matter from which device I am pressing the link button ... 😊 I tried to press it from the same device as Hue app is running on (192.168.2.54 which is my phone), but unfortunately it did not help ... 😕 You also mentioned that it's POST, not GET - could you please share how the correct request should look like? I tried:
Thank you very much for your help! 😊
|
You are using iPhone or Android? Can you test also Hue Essentials to see there are no network issues? In the pair process the apps send a POST request every second and they are rejected every time until the link button is pressed. After the link button is pressed an username hash is returned and the app will start sending new requests using that username. |
A new commit to generate the certificare with faketime (as the original hue bridge) was made 2-3 months ago. If you use recent version and rename the cert.pem file a new certificate will be generated. After every certificate replacement the Hue app need to be reinstalled on iPhone because the certificate is cached to detect man in the middle attacks. Update: this is the PR |
I have the exact same issue, did you ever resolve this @vladimir-aubrecht ? :) |
Thanks @mariusmotea! It worked 😊 @joldenburgSOLITA Just now 😊 Solution from @mariusmotea worked. It turned out docker image I had was version just before the fix, so I enforced downloading of new docker image (docker-compose rm && docker-compose pull), deleted cert.pem, deleted and re-downloaded hue app and everything started to work 😊 |
Hi, I'm runnig DIY Hue in home assistant. I reinstalled the app more then 5 times, and remade the config files a lot of times (deleted and restarted firts). But for the life of me I can't get the Hue app running or other apps. Can't see what is going wrong. I'm a bit lost now. Anybody that can help? |
Can you see the logs of diyhue container? Are there any log lines added when you try to pair the Hue app? diyhue require ports 80 and 443 to be router to itself. |
Thanks for offering help! I tried to connect and made logs of that moment. Is this something you can work with? 024-01-18 07:11:41,746 - werkzeug - INFO - 192.168.1.75 - - [18/Jan/2024 07:11:41] "GET /description.xml HTTP/1.1" 200 - |
In the pasted logs there are no request from the app you want to pair, there are just from the browser where you pressed the linkbutton. Maybe https service has not started because the certificate was not properly generated. |
I did a full rebuild again, this time I removed everything from the PI and it worked. Thankyou so much! The only problem is now I can't get the lights to appear in DIY hue, but that the next thing to figure out! |
So you did a full new installation of home assistant to fix it ? |
In the past, I did a deinstall --> install --> remove the certificate, make new certificate. Now I removed everything that resembled diy hue. Full clean install and it worked. The only weird thing is that somehow I can't get the HA lights to propagate. Something that was not a problem in previous installs |
Thank you for your email. Due to my current work schedule, I am out of the project on Wednesdays and Fridays and unable to respond. I will address your message as soon as possible on my return. All the best, Jonatan Oldenburg, Solita Sweden.
|
Hi, I have the same problem. And I already tried everything .. I reinstalled diyhue about 100 times philips hue mobile app 30 times .. I checked certificates .. and still I can't pair diyhue with philips hue mobile app and not even essential.... please help me .. already I am desperate part of the log if it helps: 2024-08-03 19:06:07,042 - flaskUI.restful - 78 - INFO - {'devicetype': 'Hue#iPhone', 'generateclientkey': True} diyhue is on docker on a device with an ARM processor |
Hi, please check youre timezone in the webui, the local time represents your local time and what is used in the python code, if this is more then 1 hour off then it will not work. If this does not work please share your config_debug.tar |
ok, so when I log in to the philips hue account, it throws me the error that I mentioned in the comment before this one.. when I pair the bridge without logging in, it works.. as soon as I log in, the bridge throws me |
Diyhue does not work with philips cloud services, we can not connect to that service. With the hue essentials app you can use remote services but that is different then philips remote service. |
oh great.. thanks for your answers :) |
Issue does not already exist?
I have searched and found no existing issue
Select Environment
Docker
Home Assistant related?
No
Description
Hi,
I tried to search for the issue, but did not find anything up to date with same symptoms.
Problem
After installing DiyHue through Docker I can open Philips Hue app on iOS and I get screen: "Hue Bridge is found". After that I try to press Link Button through web interface to proceed, but nothing happens in that Philips Hue app.
I am sure my IP & MAC are filled properly, everything is running in Host network, running latest version. Anybody any clue what could be wrong?
Thanks in advance for any help! 😊
Docker-compose file
Errorlog:
Steps to reproduce
Please enter your operating system details here
Linux 5.15.61-v8+ aarch64
What DiyHue version(branch) are you using?
master (latest)
The text was updated successfully, but these errors were encountered: