Sonarr: URL field behaviour and clearer guidance

[jamesmacwhite]

Feedback

The installation documentation is missing important information around the URL field and how it works.

For the Sonarr app, the URL field by default assumes the port to connect to Sonarr is 8989, this is the default port and makes sense, but because the field is labelled as URL, it is not clear that the port must be specified in this field.

Furthermore, those using a reverse proxy i.e. to not have to expose port 8989, the value for the URL field must specify the port regardless of if it is TCP 443 for SSL/TLS i.e. http://sub.domain:443/sonarr. While not invalid, having to specify port 443 like this in URLs is uncommon and will catch users out, see: home-assistant/core#72372

The documentation could really be updated to highlight this to prevent others falling into the trap of getting "Failed to connect", basically because the app is trying to communicate over a port which is deliberately not exposed.

URL

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

Version

2024.5.2

Additional information

No response

[home-assistant]

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

Code owner commands

Code owners of sonarr 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 sonarr 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.