core: Sabnzbd not loading after 0.88.0

0.88.0 Home Assistant release with the issue:

Last working Home Assistant release (if known): 0.87.1

Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io on debian Component/platform:

Description of problem:

Getting an error in the log Connection to SABnzbd API failed

But then I get a notification to enter the api key once home assistant is started

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):


# SABnzbd
sabnzbd:
  api_key: !secret sabnzbd_api
  host: !secret my_sab_host
  sensors:
    - current_status
    - speed
    - queue_size
    - queue_remaining
    - disk_size
    - disk_free
    - queue_count
    - day_size
    - week_size
    - month_size
    - total_size

Traceback (if applicable):

Additional information: If I manually enter the API key it then shows unknown for the sensors and then after a minute of so they update. I see also it has created a sabnzbd.conf file with the API password in it in plain text.

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 63 (4 by maintainers)

Most upvoted comments

For anyone having this issue, it is a simple fix. First, put in all of the fields in your yaml that you can, just to make sure it’s setup properly, including “path”. Also, you will want to use the internal IP address of the computer running SABnzdb and not “localhost”.

Now, the reason it’s not going to be working for most people is that it doesn’t work if SABBnzbd is asking for authentication (the username and password) under security in general settings. So if you don’t access SABnzbd from outside your network, and don’t have a port forwarded, you can just delete your username and password and it would work. You CAN have authentication on, but you need to make sure you select “Full Web Interface - Only external access requires login”. But you ALSO need to make sure under settings in the “special” section, that you have “local_ranges()” setup correctly. My network is 192.168.1.0… so I put “192.168.1.0/24” in this setting. If you aren’t sure what to put, there is help on the SABnzbd site.

I was getting the API Key error after every reboot, and even then it wasn’t accepting it if I had authentication turned on Turning it off fixed it, as did the second process I listed.

Maybe the documentation for this should be updated.

julianrinaldi on Aug 31, 2021

Even with version 2021.5.5 I still have the same issue

ChefkeGremmen on May 22, 2021

This is still happening for me (as of 0.95.4) and I have the sabnzbd.conf file present.

aptonline on Jul 10, 2019

@RobHofmann very good. Perhaps my comment will help someone else.

Key point here is that if for any reason Sabnazbd is unreachable, you will see the notification asking you to “configure”. Which imo is a bug :p

mafrosis on Jun 19, 2019

I am closing this issue as the main issue described here is fixed in 2022.5.50.

If anyone still has an issue not listed in Sabnzbd issues, please create a new issue.

Thanks 👍

thecode on May 5, 2022

Hey there @shaiu, mind taking a look at this issue as it has been labeled with an integration (sabnzbd) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

probot-home-assistant[bot] on May 4, 2022

Also if you actually have a sabnzbd.conf file with the API key in it then it should use that first anyway. Why bother writing the key to a file if it’s going to just ignore it?

DavidFW1960 on Jun 20, 2019