core
core copied to clipboard
Harmony Integration Stopped Working
The problem
The Harmony integration has stopped working. The logs are showing "Unable to determine if XMPP is enabled"
What version of Home Assistant Core has the issue?
core-2023.10.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Harmony
Link to integration documentation on our website
No response
Diagnostics information
Logger: aioharmony.harmonyclient Source: components/harmony/data.py:123 First occurred: 2:05:50 PM (13 occurrences) Last logged: 2:18:37 PM
192.168.68.105: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('192.168.68.105', 5222)
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @ehendrix23, @bramkragten, @bdraco, @mkeesey, @aohzan, mind taking a look at this issue as it has been labeled with an integration (harmony
) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of harmony
can trigger bot actions by commenting:
-
@home-assistant close
Closes the issue. -
@home-assistant rename Awesome new title
Renames the issue. -
@home-assistant reopen
Reopen the issue. -
@home-assistant unassign harmony
Removes the current integration label and assignees on the issue, add the integration domain after the command.
(message by CodeOwnersMention)
harmony documentation harmony source (message by IssueLinks)
Has this been picked up? Currently no Harmony service calls are working. The Harmony itself is fine with the native app. Would appreciate an update. Thanks.
had the same issue, deactivated the integration since 2 weeks. today i made the core update to 2023.10.5. and activated again and the integrations seems to work again. Onlything i changed in my network is disable pmf in the WIFI.
Mine has also failed, can't re-add. Just get Failed to connect on setup. The hub still works and says XMPP is on. Logs have the line:
2023-10-27 14:33:07.577 ERROR (MainThread) [aioharmony.harmonyclient] 192.168.1.68: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('192.168.1.68', 5222)
I updated to 2023.10.5 (OS 11.1) and it started working again. Then a day or so later I noticed it's stopped responding. Perhaps the update/restart temporarily fixed it.
@ehendrix23, @bramkragten, @bdraco, @mkeesey, @Aohzan - it would be good know if one of you has picked this up. Thanks.
Mine has also stopped working.
Tried to restart the integration but it failed to unload!
Iam now on 2023.11.1 and have the same problem
The same has occured here. Any progress on this issue? Currently on: Home Assistant 2023.10.5 Supervisor 2023.10.1 Operating System 11.0 Frontend 20231005.0 - latest
As before, after updating to 2023.11.0 today, the issue has resolved itself temporarily, but for how long? I'll try to determine if a simple restart of HA or reboot of the system also resolves, if/when it breaks again.
Another update installed today to 2023.11.1 and it's stopped working again. I've yet to identify a pattern.
Edit: I restarted (not a full reboot) and Harmony commands now work again. Will continue to monitor, but it would be nice to know if anyone is actually looking at this.
my workaround is, to restart the harmony hub. After that it will work instantly again
I've tried restarting the hub and HA, no luck.
Has anyone had any luck resolving this? It stopped working about three weeks ago. Just updated to current version and still will not work. Same errors as others have mentioned.
Core 2023.12.1 Supervisor 2023.11.6 Operating System 11.2
I have seen the same issue, I am attempting an update from operating system 11.0 to 11.2, but it seems the above comment indicates this won't be the fix either.
I have put a powerplug between the Harmony hub and made an automation to resart the hub when not available in HA.
As i wrote in October, i had this Issue. but until then no problems at all. what i tried:
- deleting the integration and reinstall -> no scuccess
- reinstall a backup from a Point as there was no issue -> no success
- downgrade HA to a Version where there was no issue -> no success
- new install without backup with new setup -> no success in all that four ways i also restartet the hub a few times After that i deactivated the integration and changed all the automations ....for round about 2 weeks I didn't like this solution and after this two weeks i took a look through my network if there is a problem. In my accesspoint I found some logs mentioned and I researched what the Problem might be and the Logs were related to PMF (Protected Management Frames). so i deactivated PMF on my accesspoint for testing, activated the integration again and everything is working since this moment.
Sme issue at my side. Any solution? It worked perfectly since a couple of days ago.
Same here. Any luck with a solution?
I have the same problem. Unplugging and plugging in the harmony hub from the wall solves the issue for me, at least for a couple of days until it stops working again.
I made an automation with a powerplug for that.
Abraham Valenzuela @.***> schreef op 6 februari 2024 00:42:43 CET:
I have the same problem. Unplugging and plugging in the harmony hub from the wall solves the issue for me, at least for a couple of days until it stops working again.
-- Reply to this email directly or view it on GitHub: https://github.com/home-assistant/core/issues/101797#issuecomment-1928514567 You are receiving this because you are subscribed to this thread.
Message ID: @.***> -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Same issue, stopped working over night. Restarted Harmony and HA, didn't solve it.
Logger: aioharmony.harmonyclient
Source: components/harmony/data.py:123
First occurred: 00:28:23 (25 occurrences)
Last logged: 08:53:49`
192.168.xxx.xxx: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('192.168.xxx.xxx', 5222)`
out of no where I am getting this error and the integration has stopped working:
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.