8000 Logitech Harmony integration stopped working · Issue #57542 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Logitech Harmony integration stopped working #57542

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.

Sign up for GitHub

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

Jump to bottom
Closed
rjkruit opened this issue Oct 12, 2021 · 10 comments · Fixed by #57589
Closed

Logitech Harmony integration stopped working #57542

rjkruit opened this issue Oct 12, 2021 · 10 comments · Fixed by #57589
Assignees
@bdraco @bramkragten
Labels
integration: harmony

Comments

@rjkruit
Copy link
rjkruit commented Oct 12, 2021

The problem

Upgraded core and OS to the latest versions and now the harmony entities are unavailable. It turns out that home assistant can't connect to the XMPP server on the harmony hub. Connecting to the XMPP port 5222 with telnet from another host confirms the service is up and running. It may also have to do with the OS version as that was also updated. Perhaps some firewall rule?

supervisor-2021.10.0
core-2021.10.4
Home Assistant OS 6.5

What is version of Home Assistant Core has the issue?

core-2021.10.4

What was the last working version of Home Assistant Core?

core-2021.10.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Logitech Harmony

Link to integration documentation on our website

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2021-10-12 13:08:23 ERROR (MainThread) [aioharmony.harmonyclient] 172.16.5.100: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('172.16.5.100', 5222)
2021-10-12 13:08:23 WARNING (MainThread) [homeassistant.components.harmony.data] LivingRoomRemote: Unable to connect to HUB
2021-10-12 13:08:23 WARNING (MainThread) [homeassistant.config_entries] Config entry 'LivingRoomRemote' for harmony integration not ready yet: None; Retrying in background
2021-10-12 13:08:25 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Air Purifier Woonkamer' for xiaomi_miio integration not ready yet: Unable to discover the device 172.16.5.102; Retrying in background
2021-10-12 13:08:34 ERROR (MainThread) [aioharmony.harmonyclient] 172.16.5.100: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('172.16.5.100', 5222)
2021-10-12 13:08:34 WARNING (MainThread) [homeassistant.components.harmony.data] LivingRoomRemote: Unable to connect to HUB
2021-10-12 13:08:47 ERROR (MainThread) [aioharmony.harmonyclient] 172.16.5.100: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('172.16.5.100', 5222)
2021-10-12 13:08:47 WARNING (MainThread) [homeassistant.components.harmony.data] LivingRoomRemote: Unable to connect to HUB
2021-10-12 13:09:10 ERROR (MainThread) [aioharmony.harmonyclient] 172.16.5.100: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('172.16.5.100', 5222)
2021-10-12 13:09:10 WARNING (MainThread) [homeassistant.components.harmony.data] LivingRoomRemote: Unable to connect to HUB
2021-10-12 13:09:17 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities switch.livingroomremote_cctv, switch.livingroomremote_kodi, switch.livingroomremote_nintendo_switch, switch.livingroomremote_phono, switch.livingroomremote_ps5, switch.livingroomremote_tube_amp, switch.livingroomremote_watch_apple_tv, switch.livingroomremote_watch_tv_srnd, switch.livingroomremote_x_box_one
2021-10-12 13:09:53 ERROR (MainThread) [aioharmony.harmonyclient] 172.16.5.100: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('172.16.5.100', 5222)
2021-10-12 13:09:53 WARNING (MainThread) [homeassistant.components.harmony.data] LivingRoomRemote: Unable to connect to HUB
2021-10-12 13:11:16 ERROR (MainThread) [aioharmony.harmonyclient] 172.16.5.100: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('172.16.5.100', 5222)
2021-10-12 13:11:16 WARNING (MainThread) [homeassistant.components.harmony.data] LivingRoomRemote: Unable to connect to HUB
2021-10-12 13:12:40 ERROR (MainThread) [aioharmony.harmonyclient] 172.16.5.100: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('172.16.5.100', 5222)
2021-10-12 13:12:40 WARNING (MainThread) [homeassistant.components.harmony.data] LivingRoomRemote: Unable to connect to HUB
2021-10-12 13:14:03 ERROR (MainThread) [aioharmony.harmonyclient] 172.16.5.100: Unable to determine if XMPP is enabled: [Errno 113] Connect call failed ('172.16.5.100', 5222)
2021-10-12 13:14:03 WARNING (MainThread) [homeassistant.components.harmony.data] LivingRoomRemote: Unable to connect to HUB
2021-10-12 13:15:23 WARNING (MainThread) [slixmpp.stringprep] Using slower stringprep, consider compiling the faster cython/libidn one.
2021-10-12 13:15:24 WARNING (MainThread) [slixmpp.basexmpp] Legacy XMPP 0.9 protocol detected.
2021-10-12 13:15:54 ERROR (MainThread) [aioharmony.harmonyclient] LivingRoomRemote: Second Timeout trying to retrieve current activity.

Additional information

No response
@hdurdle
Copy link
hdurdle commented Oct 12, 2021

Just to note that I've just upgrade to the same versions, and don't see this error. My two Harmony Hubs are both responding as expected. This a VM running under Hyper-V.

@probot-home-assistant
Copy link

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!
(message by CodeOwnersMention)

harmony documentation
harmony source
(message by IssueLinks)

@bdraco
Copy link
Member
bdraco commented Oct 12, 2021

I've seen some instability on recent versions as well. I think it's actually related to discovery happening more frequently. It seems to overwhelm the devices.

@bdraco
Copy link
Member
bdraco commented Oct 12, 2021

Currently we fetch the device ID/unique ID When the Devices discovered so we can tell if it's already been set up and abort.

Unfortunately it doesn't look like there's a way with aioharmony to just fetch the id without connecting the websocket so we end up overloading the device

This was referenced Oct 12, 2021
Merged
Merged
@bdraco
Copy link
Member
bdraco commented Oct 13, 2021

Can you try this patch?
#57589

@rjkruit
Copy link
Author
rjkruit commented Oct 13, 2021

Can you try this patch? #57589

I just noticed that it started to work again overnight as this morning it was suddenly present again. The problem started after updating the core several times and then the OS again as I was some versions behind. You might be right that the hub was overloaded. However, unplugging it and plugging it back in had no effect.

@apmillen
Copy link

I'm having the same problem. When it wasn't working I removed the integration and tried to add again but now keeps failing.
How do I go about trying that patch? I'm running HA OS.

@apmillen
Copy link

Is there an update to this issue?
I've tried rolling back, removing 'discovery:' from my config.YAML and restarting HA multiple times. None have stopped the issue and it seems to be slowing down my system response and automations

@chrismanivong
Copy link
Contributor

I confirm the patch is working in my installation with 3 harmony hubs.

@apmillen
Copy link

Is there any instructions on how to use this patch?

@github-actions github-actions bot locked and limited conversation to collaborators Nov 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bdraco bdraco

@bramkragten bramkragten

Labels
integration: harmony
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Avoid setting up harmony websocket from discovery bdraco/home-assistant
7 participants
@bachya @bdraco @hdurdle @bramkragten @chrismanivong @apmillen @rjkruit
0