core: Radarr Integration loads without error but all sensors Unavailable

The problem

As per the title the Radarr Integration is not giving any errors and is loading but all sensors show as unavailable

What is version of Home Assistant Core has the issue?

2021.6.x

What was the last working version of Home Assistant Core?

one of the 2021.6 betas and certainly 2021.5.5

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Radarr

Link to integration documentation on our website

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

Example YAML snippet

sensor:
  - platform: radarr
    api_key: !secret my_radarr_api
    host: !secret my_radarr_host
    port: !secret my_radarr_port
    monitored_conditions:
      - movies
      - upcoming
      - commands
      - status
    days: 10


### Anything in the logs that might be useful for us?

```txt
nothing at all

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 10
  • Comments: 53 (15 by maintainers)

Most upvoted comments

This still is not working

Like @DavidFW1960 says it is still not working.

The Sonarr integration uses the sonarr [^1][^2] Python library, but there isn’t an identical library for Radarr which would make code copy&paste possible.

Instead, I think that building a new Radarr integration based on pyarr [^3][^4] would be the best solution. The library has one pull request that’ll cause breaking changes [^5], but once that’s done, I’m considering taking up the mantle and building a new plugin myself.

What’s exciting is that the pyarr library currently supports Sonarr & Radarr, but Readarr[^6], Lidarr[^7] and Prowlarr[^8] are coming soon.

This means that a successful Home Assistant plugin for Radarr based on the pyarr library should be relatively easily modified to provide support for Sonarr, Lidarr, Readarr, and Prowlarr.

References: [^1]: https://pypi.org/project/sonarr/ [^2]: https://github.com/ctalkington/python-sonarr [^3]: https://pypi.org/project/pyarr/ [^4]: https://github.com/totaldebug/pyarr [^5]: https://github.com/totaldebug/pyarr/tree/80-add_readarr_support [^6]: https://github.com/totaldebug/pyarr/issues/80 [^7]: https://github.com/totaldebug/pyarr/issues/81 [^8]: https://github.com/totaldebug/pyarr/issues/82

still not working on last version

Hey, I am having a similar issue. If you guys are anywhere near getting this resolved I wouldn’t mind beta testing whatever you got.

You can download a working version as a custom component from my repo

Keep in mind that if you use this custom component, to remove it and re-setup the integration when it is officially released. The config entries will be different.

@tkdrob The API is a little bit different than how I planned to structure it on totaldebug/pyarr but kudos to the fork!

Do you mind if we adopt your tests configuration into our branch? We’ve been putting off developing tests for PyArr for a bit too long.

Not at all, go ahead. All I ask is for a mention. There is a bug I noticed with the host config ignoring custom ports so I’ll have to fix that.

Thanks. It’s really weird because just using an API Call I think I can get the same data as the integration anyway by using a rest sensor so I dunno why HA is doing it the way that it currently is.

A change has been made on how timeouts are handled. The timeout context is no longer used with aiohttp. That’s why.

Actually, the loop argument is more the problem here and is deprecated.

Check discord. I sent you my copy.

Are you by any chance also using Sabnzbd? This is erroring in 2021.12.0.x as well. I raised an issue there #61306 but it seems an upstream library is the culprit for that.

No. But I may look into it. I’m currently working no some new integrations.

Check discord. I sent you my copy.