search

home-assistant / home-assistant.io

:blue_book: Home Assistant User documentation
https://www.home-assistant.io
Other
4.87k stars 7.24k forks source link

[help] Jabber notifier not working because different Xmpp server port #33729

Closed maxbarmet closed 1 week ago

maxbarmet commented 3 months ago

Feedback

Hello, I've tested the jabber integration in HA to send notification on my xmpp servers on the first server the xmpp port is 5220 and on the second one the xmpp port is the classical port 5222 The notification failed on the first server and successfully run on the second one. It is due to the xmpp port So question : is there an entry in the configuration.yaml to indicate the port number for the target xmpp server ? I tried to add port: 5220 and restart HA but when testing a send notif nothing happened !

URL

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

Version

2024.7.2

Additional information

No response

home-assistant[bot] commented 3 months ago

Hey there @fabaff, @flowolf, mind taking a look at this feedback 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 feedback. - `@home-assistant rename Awesome new title` Renames the feedback. - `@home-assistant reopen` Reopen the feedback. - `@home-assistant unassign xmpp` Removes the current integration label and assignees on the feedback, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information) to the feedback. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information) on the feedback.
black-roland commented 2 months ago

As far as I know, XMPP retrieves server's host and port from the SRV record. I'd suggest setting up the port by updating DNS records.

github-actions[bot] commented 3 weeks ago

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. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.