home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.26k stars 30.24k forks source link

xmpp integration stopped working with the new notify component #121547

Closed dadosch closed 2 months ago

dadosch commented 3 months ago

The problem

After update of HASS to 2024.7.1, the xmpp integration stopped working: Automations using a configured xmpp connections complain about not found services:

Service notify.jabber not found

with a unchanged config, previously working:

notify:
  - name: jabber
    platform: xmpp
    …

This is probably related to the new entity component: https://github.com/home-assistant/core/pull/110950

What version of Home Assistant Core has the issue?

core-2024.7.1

What was the last working version of Home Assistant Core?

core-2024.5.4

What type of installation are you running?

Home Assistant Core

Integration causing the issue

xmpp

Link to integration documentation on our website

https://www.home-assistant.io/integrations/xmpp/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 3 months ago

Hey there @fabaff, @flowolf, mind taking a look at this issue as it has been labeled with an integration (xmpp) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `xmpp` 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 xmpp` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


xmpp documentation xmpp source (message by IssueLinks)

dadosch commented 2 months ago

This sounds extremely stupid, but in the end the culprit was two integrations (UPNP and mobile) loading a device twice each. This caused that the whole notify.* services which were configured were not available, not just xmpp (it happened to be the only one I had configured). The solution is to see which integrations are "not loaded" and delete all devices in them.

There was no error message in any of the log files.