Harmony Hub can't find hue emulation #110
Replies: 4 comments 39 replies
-
|
Are you able to try the previous troubleshooting steps mentioned in the old issue? Specifically, there were some commits to try in the dev add-on. Interested to know if this is some regression with the code or if this has something to do with harmony being flaky. Personally I had mixed results with harmony discovery. Sometimes it works and sometimes it doesn't, although I try to avoid trying it since I don't really want to have to setup everything again ;). If you can, perhaps try a factory reset of harmony as well while you are testing the other commits. (Not necessary though because I know the pain this could cause) I don't believe we have made any major changes that would impact harmony though. |
Beta Was this translation helpful? Give feedback.
-
|
Ouch!
Would probably just buy a new one to test to avoid reseting mine 😬
Was able to discover with the #e1cd378 It took almost 10 minutes since I hit the discovery button until it finished. Got a few popus in app saying it was going to send the error report back to harmony but eventualy got paired. Pairing process: (.206 HA/ .9 Harmony Hub) Regarding usability it works, with a huge lag, and sometimes a turn_off to a specific bulb turned all my lights off (can't really proceed with more testing now or I'll be in trouble. I'll continue during the day. 😅 This is the log when turning on and off |
Beta Was this translation helpful? Give feedback.
-
|
This is exactly what I needed to know! I just looked back at the commit history and it seems like I had reverted the changes made in e1cd378 though 4933804. To test this theory, can you try those two commits? Seems that after that revert, it should no longer work from my understanding of the comments here. Why harmony didn't pair when you tested e1cd378 is very strange. As I mentioned, harmony is flaky when pairing sometimes and can require multiple tries and maybe a reboot of the device itself to pair. As that changes was reverted before ever being merged, that would make sense why it's not working now. I'll look into reimplementing those changes. |
Beta Was this translation helpful? Give feedback.
-
|
Looking back, I do see the reason for reverting that change. Another user mentioned that it broke discovery for the Phillips TV interestingly... #57 (comment) |
Beta Was this translation helpful? Give feedback.
-
sorry crazy week. I'll try those two and report later today |
Beta Was this translation helpful? Give feedback.
-
|
I've committed some new changes to see if we can track down this issue. Please try each of these and ensure debug logging is enabled and please attach the log here for each trial. This commit should work as it reapplies changes originally in the old commit. From @terminusxx 's testing, this should work, but this likely breaks Phillips TV discovery as mentioned by @Mr-Groch. Commit 2: Commit 3: |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I've checked those commits on my TV: Commit 1: Breaks Philips TV Discovery |
Beta Was this translation helpful? Give feedback.
-
|
Since I'm on the new version of hassio both 4933804 and e1cd378 fail to even start with the error Commit 2: Commit 3: I restarted before each attempt and after the 3rd commit failed I went back to commit 1 and was able to repair without restarting. Sorry, forgot to grab logs but I was watching them and the commits that failed only ever outputted |
Beta Was this translation helpful? Give feedback.
-
|
Can you all give this a try? Hopefully, this works without causing problems. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, but still my TV does not discover bridge.. 2 search attempts, and only this in logs: |
Beta Was this translation helpful? Give feedback.
-
|
@Mr-Groch Can you try it again at this commit? I added some more verbose logging to hopefully see what's happening. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@Mr-Groch Additionally, try this. Its should work. |
Beta Was this translation helpful? Give feedback.
-
|
3bea3be is working! But e4627b4 don't, here is log from e4627b4 : |
Beta Was this translation helpful? Give feedback.
-
|
it Works 👍 Do you need logs? |
Beta Was this translation helpful? Give feedback.
-
|
Nope seems good. I just did a refactor of this fix so try this If that doesn't work, then try this |
Beta Was this translation helpful? Give feedback.
-
|
@Mr-Groch @tmarquespt @terminusxx Please test this final commit so we know it works before merging |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
as requested @alexyao2015 i'm opening a new discussion.
So I've tried to replace the original hue emulation on homeassistent with this one. It works fine with the apps on my phone that are able to find it but my Harmony Companion Hub is unable to do so.
As I wrote I can see the addon trying to talk with the hub but on the harmony side it allways says he couldn't find the bridge. This is what I see when I try to pair:
(...)
2021-02-03 22:55:12,040 DEBUG emulated_hue.discovery -- Serving SSDP discovery info to ('10.11.5.206', 53738)
2021-02-03 22:55:12,041 DEBUG emulated_hue.discovery -- Serving SSDP discovery info to ('10.11.5.206', 53738)
2021-02-03 22:55:25,514 DEBUG emulated_hue.discovery -- Serving SSDP discovery info to ('10.11.5.9', 55913)
2021-02-03 22:55:25,595 DEBUG emulated_hue.discovery -- Serving SSDP discovery info to ('10.11.5.9', 55913)
(....)
10.11.5.206 is HA's IP and 10.11.5.9 is harmony's.
I also tried a fresh install of HA with only the hass-emulated-hue addon installed but with the same result with both the normal and the edge version.
I'm available to do further debugging if you tell me how :)
Beta Was this translation helpful? Give feedback.
All reactions