-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception: 'SonarrQueueDetail' object has no attribute 'timeleft' #81508
Comments
Hey there @ctalkington, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) sonarr documentation |
This seems to stem from this PR merged in aiopyarr: tkdrob/aiopyarr#56 Looking at the python code, not every model class seems to implement |
I've narrowed this down to having stalled qBittorrent downloads in your queue as you can see in the issue linked in aiopyarr above. You can either remove your stalled downloads, or move them out of the Sonarr download category if you have that set; that fixes the error for me. |
Thanks. Seems like a good workaround until a fix is merged. I see you submitted a PR, so hopefully that resolves it |
More on what @NanoSector was saying, this appears to differ between download clients. I don't use qBittorrent and am not having this issue. |
Nor do I - I am using transmission |
I see it's been added to the 2022.11.2 milestone - thanks @tkdrob ! |
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. |
I was seeing this regularly before, and I haven't seen this in some time, so I suspect it's been resolved by the above releases, though I don't have any technical insight to back that up. |
Issues is also present in Lidarr (built on same common code). Will attempt to move stalled qBit torrents to another catagory to test but both can confirm issue is still preset….. I’ll post follow up after testing the relocation of torrents and can provide logs if desired but it seems the problem was well understood just yet to see fix pushed for this. Thanks ! |
Have you updated to the latest Home Assistant? |
Apologies for the brevity in my earlier post. I opened an issue directly under Lidarr (referenced above). With further details and referring back here for potential context. To answer your question, yes I am on HA:latest, and Lidarr:latest, pulled earlier this morning before regression testing above. Specifically Lidarr Version: 1.0.2.2592, HA docker: 2023.3.6 |
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. |
The problem
After upgrading core, the Sonarr integration has started throwing the following exception.
What version of Home Assistant Core has the issue?
2022.11.0
What was the last working version of Home Assistant Core?
2022.10.x
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Sonarr
Link to integration documentation on our website
https://www.home-assistant.io/integrations/sonarr
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: