-
Notifications
You must be signed in to change notification settings - Fork 199
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
5.0.0 Harmony pairing not working because of HTTP302 issue #816
Comments
Which direction are you pairing the harmony hub? To the ha-bridge or from the ha-bridge... |
To the HA-Bridge, I use the MyHarmony configuration software to ask the Harmony Hub to scan the devices available on my network and, when discovered, I select the fake Hue bridge and when I click Next it asks me to push on the Sync Button on my Hue Bridge (which I manually do through the HABridge WebUI) and that's where it fails |
Hi, same problem here: When pairing Harmony Hub to ha-bridge i experience the same problem. Hub is sending "POST /api/ HTTP/1.1", ha-bridge replies with Any ideas? |
This is a duplicate of #797, Please update that thread with any info and close this. |
Thanks |
Hello,
I recently updated switched from a windows ha-bridge to a docker version in 5.0.0 and discovered that the Pairing process from my Harmony Hub could not complete.
To better understand if it was related to my docker, I did all the test using the official relaeses on my windows machine and found the following
While doing a quick network analysis on a working version (4.5.6), we see the request from my Harmony hub (.119) :
192.168.1.119:38225 192.168.1.115:3080 HTTP 235 POST /api/ HTTP/1.1 (application/json)
and then the reply
192.168.1.115:3080 192.168.1.119:38225 HTTP 66 HTTP/1.1 200 OK (application/json)
and then the pairing process starts and complete correctly.
Doing the same process in 5.0.0 shows that it's now using an HTTP 302 redirect :
192.168.1.115:3080 192.168.1.119:38225 HTTP 211 HTTP/1.1 302 Found Location : http://192.168.1.115/api
However the target (location) does not include the port, which is certainly one good reason for the pairing failure.
Best regards
pcap files.zip
The text was updated successfully, but these errors were encountered: