Core: Sabnzbd not loading after 0.88.0

[DavidFW1960]

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.

[DavidFW1960]

Just loaded version 0.88.1 and it asks for the API key again despite having the conf file???

[DavidFW1960]

@fabaff and @balloob
You both seem to be the authors of this component? Can you advise why it's just started doing this?

[gbdavidx]

Doesn't work for me either, on latest version .88, no errors (not using SSL)
https://community.home-assistant.io/t/cant-configure-sabnzbd-with-home-assistant/101380

[DavidFW1960]

It seems intermittent... Restarted HA again yesterday and it didn't error out. Maybe it's a timing issue... perhaps the timeout needs to be a little longer?

[aptonline]

I too have been seeing the issues from time to time, having to enter the api key again (which is kept in my secrets.yaml)

[rboeters]

I too have this issue, it's still there with 0.91.0. A restart of HA gives 100% guarantee on having to enter the API key again via the configurator whilst it is already present in configuration.yaml.

[ArnoutVerbeken]

Me too. Every restart it asks for the api key again.

arch | armv7l
-- | --
dev | false
docker | true
hassio | true
os_name | Linux
python_version | 3.7.2
timezone | Europe/Brussels
version | 0.91.1
virtualenv | false

[benjgos]

Adding my own me too. Practically every single restart i need to re-enter the API key since 0.88.
Have the key it in config, have the sabnzbd.conf in place, still every restart i have to re-enter.

[officiallybob]

Hey folks, just a heads up. I was experiencing the same, but after updating SAB to 2.3.8 it seems to have gone away. Might be worth looking into.

[DavidFW1960]

Yeah nah. 2.3.8 here and still did it right now after a restart. It doesn't do it all the time. It has nothing to do with the sab version so far as I can tell.

[ChrisLStark]

Same here since a while back... be good to put this one to bed! :)

[DavidFW1960]

0.92.0b2 now and I have not seen it so far... fingers crossed... I don't know if anything has changed though

[benjgos]

Just upgrade to 0.92.1 and didn't see it. Restarted HA and it popped up again. :/

[DavidFW1960]

I haven’t seen it for a week or so... 0.92.1 now.

[benjgos]

You're luckier than me. just restarted again:
2019-04-28 05:23:04 ERROR (MainThread) [homeassistant.components.sabnzbd] Connection to SABnzbd API failed

[bartley69]

Also experiencing this issue and some googling led here. Has anyone found a fix?

[officiallybob]

I'm still on 0.91.4 due to emulated hue issues and still get this happening. Of course, I had time just now to do some testing so I turned on debug logging for the sab component. And wouldn't you know, after 5 restarts it is loading properly every time. I'll keep hammering at it until I get a failure, but it would help if others, especially those on 0.92.*, to do the same and get some logs together. Might be able to track down just where the issue is.

[DavidFW1960]

I have not had a failure for weeks now. 0.93.0b1 running now and still good here.

[benjgos]

running 0.93.1, still have issues on HA restart.. :/

[Phontana]

I'm having these issues as well.

[ps-tfriedl]

Same issue here.

[RobHofmann]

Same issue on HASSIO 0.94.1 (RPi)

[mafrosis]

I had this problem - turned out to be a DNS issue. I run HA in docker and by default docker doesn't use your local router as a nameserver; meaning hostnames on your local network will not resolve.

Update the following file if you are finding Sabnzbd via a local hostname:

cat /etc/docker/daemon.json
{"dns": ["192.168.1.1"]}

[RobHofmann]

For me it is not an DNS issue. I'm using IP's in my configuration (no hostnames at all).

[mafrosis]

@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

[DavidFW1960]

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?

[aptonline]

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

[benjgos]

Just upgraded to 0.97.2, same issue.

[Phontana]

Why is the sabnzbd.conf file created anyway? The API key is available as a property in the configuration. Having both seems unnecessary, and most other integrations don't use the .conf file approach anymore.

[JohanPotgieter]

I also have this issue in 0.99.2. It doesn't seem that anyone is interested in fixing or investigating this. This issue has been open for 7 months. I have tried all the things that worked for others without success. Sabnzbd updated to 2.3.9, have sabnzbd.conf and a bunch of other things. I will probably have to admit defeat and remove SABnzbd from my dashboard.

[officiallybob]

I've just gotten into the habit of re-pasting the API key into the configurator at every re-boot. It's not ideal, but I guess it works better than nothing.

[JohanPotgieter]

What do you do to see your stats? All my items are still "Entity not available"

[officiallybob]

What do you do to see your stats? All my items are still "Entity not available"

Once I put the API key in the configurator it creates the sensors I specified in the config and they appear on my front end. I would check to see if you yours is creating the sensors with "_2" appended to the names as it sometimes does with "duplicate" sensors.

[stale[bot]]

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 with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Phontana]

This is issue is still present in the latest version of Home Assistant (0.103.5).

[benjgos]

For a moment i was optimistic about 0.104.0, but it just happened to me again on a restart.

[benjgos]

Hasn't happened to me in 0.106.x yet. Crossing fingers.

[benjgos]

never mind, just happened to me again on 0.106.5.

[vmcosco]

I know this is an old topic but I just got SABnzbd set up in HA and wanted to report how I accomplished it just in case it helps someone else. I was getting the configurator popup and no sab sensors were being created.

I added my sabnzbd details as outlined in the documents. I deleted sabnzbd.conf from config/ (it was left over from prior attempts)
I added the following to my configuration.yaml. Was there maybe some legacy discovery going on?

discovery:
  ignore:
    - sabnzbd

I restarted HA and voila. No more API errors/requests up to this point.

[benjgos]

Unfortunately i've done that multiple times, and i also have discovery ignore sabnzbd, but i still get the error randomly (after most restarts).

[TheWidowLicker]

I am also getting this on every restart of HA.
I have the details in the configuration file but it still keeps asking for the PI key.
Even when I put the key in and click confirm the prompt still stays there and does nothing.
I have tried the ignore on discovery but it has done nothing also.

[TheWidowLicker]

Update:
After changing my sabnzbd to use http instead of https, setting ssl to false and keeping the discovery set to ignore sabnzdb. On reboot there was no request for APi key and all the sensors where there

[stale[bot]]

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 with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Phontana]

This is still an issue.

[masterxdk]

I got same issue. Pretty annoying

[xstrex]

Just chiming in, same issue here as well, incredibly annoying!