core: qBittorrent Does Not Refresh After Connection Failure
The problem
if qBittorrent becomes unavailable, the system no longer tries to reach it and stays in a perpetual state of “unavailable” with no further status updates. The log reports “Connection lost” even though the server is back up again.
To reproduce: quit qBittorrent so that the sensor shows it as unavailable, then bring it back up again. In my case, I restarted qBittorrent at 9:43am and by 10:15am it is still unavailable and the sensor shows a last changed of 9:43am, with logs after that continuing to say it is unavailable.
The only way to get the sensor to connect again is to restart HA.
What is version of Home Assistant Core has the issue?
2021.3.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
qbittorrent
Link to integration documentation on our website
https://www.home-assistant.io/integrations/qbittorrent/
Example YAML snippet
# Put your YAML below this line
Anything in the logs that might be useful for us?
# Put your logs below this line
2021-03-20 09:57:16 ERROR (SyncWorker_8) [homeassistant.components.qbittorrent.sensor] Connection lost
2021-03-20 09:57:16 ERROR (SyncWorker_7) [homeassistant.components.qbittorrent.sensor] Connection lost
2021-03-20 09:57:16 ERROR (SyncWorker_6) [homeassistant.components.qbittorrent.sensor] Connection lost
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 50 (9 by maintainers)
I am still the maintainer, I will take a look at this later on after my holiday’s. I know the PR has been closed, but you must know I’ve maintained the PR for 2 years before a review came.
I’ll take a look at it! The heavy work has already been done I think (the configflow and making it async). I will probably have to fix a few deprecations, but nothing big. I will take a look at it first thing when I come back from holidays (beginning of September)
still happens on 2022.4.7
We can go for one year with this one, come on guys I know you can do it. So we have the solution, we have dev that fixed everything, and for some unknown reason this is not pushed in core HA …
Hey all, actually this workaround, only possible due to the new version of HA 2023.5, works perfectly! It restarts the gbittorrent integration when it detects that it needs to. Make sure and follow all the “Requirements” steps first before adding the automation.
How about putting this in HACS instead of relying on the core team?
In my opinion, HACS is the way to go. There’s 1400 open issues and 440 PRs. Core team is too overwhelmed and shouldn’t be worrying about these integrations.
Thank you for the clarification @geoffreylagaisse ! If you need something, just let us know, I’ll be glad to help.
@hellcry37 I think the integration has enough love from the author and users. Without the author, there’s no integration, so we need to pay respect to him, his time and effort. So in terms of strict love, I think we are all ok. In terms of open source develpment cicle of life, well, things went too slow on the modernisation of the integration, then the review of the PR from the core team was too slow, and is understandable if misscommunication occurs after all that. Geoffrey surely has a life outside this, and core devs have a business to run over their open source project. But I have to be clear: My question to the maintainer was strictly administrative, we need to respect his time and will, even if he want to pull the plug off at some time. I don’t want to start a riot against the maintainer followed by an endless list of user complaints after my request. I just needed to know if he pulled the plug because I was considering to fork or carry this to HACS, were it can be free from core team slow responses.
this really needs more love and more ppl to work on it
3 months? really? 😃)))))