rogales

I need the Python library qbittorrent-api (PyPI package), not the built-in Web API. My Python script uses import qbittorrentapi which isn't available in the container by default. Should I install it via pip or rewrite my script to use requests + Web API directly?

I would like to ask what's the easiest, and best way to install qbitorrent-api (it's necessary for a script I use every time when new torrent is added). Thanks

I apologize if there already was a thread, or post about it, but I'd like to ask if there is any possibility to downgrade libtorrent version?

I guess you're right. Was just happy that I made it work.. PS. Good to see you. It's been a while. 🤜🤛

If You want any assist in my person to make it work, dont hesitate, and ping me. :)

Im not sure how did You install this script. Because I have just created a docker container for this script with compose manager and here is my code which I've pasted there. services: autoremove-torrents: image: ghcr.io/nelsondane/autoremove-torrents:${VERSION:-latest} container_name: autoremove-torrents environment: CRON_SCHEDULE: "${CRON_SCHEDULE:-0 * * * *}" volumes: - /mnt/user/appdata/autoremove-torrents/config.yml:/app/config.yml - /mnt/user/appdata/autoremove-torrents/logs:/app/logs restart: unless-stopped of course at first You have to create config.yml

Which newer version of deluge? If we talk about latest binhex-deluge docker then it still works without any problems. Secondly, IF you want an alternative (which I personally use for binhex-qbittorrent) You should check: 1. https://github.com/jerrymakesjelly/autoremove-torrents 2. https://autoremove-torrents.readthedocs.io/en/latest/

I'm using autoremove plugin which can be installed through deluge interface. AutoRemovePlus-0.6.3.egg

Hey, well You tell me... Have no idea why it was a problem. Unfortunately I'm not that good, or even decent when it comes to linux, so my knowledge is at low level, but with small help of AI promts I've manage to find where my problem was. I just used grep "02:00\|09:00" /var/log/syslog command (with time forks which I was interested in) and there were a lot of inquiries about this share. I use "Unassigned Devices" plugin, in which I've just unmounted this specific share (it's my only one to be precise), and after that voilà! mover tuning script worked as it should - it checked the threshold, which wasn't passed, and it finished it's job - just as it should work.

@Masterwishx I found my issue. I don't know if it's a bug, or there is any option to disabled it in Mover Tuning, but my earlier mounted smb share was the problem. It's my personal PC, which is powered off - mover tuning is set to start always at night when I'm asleep, but the script have tried all the time to connect with this SMB share. I had to unmount this share, and after that there was no issue, or any kind of pause like it was earlier. Hope that will help You. Thanks.

I see. Well would love to help You but it's beyond my capabilities.

Even if You would check it via terminal command? For example with: du -h --max-depth=2 /mnt/yourcachepool/ | sort -hrYou can change depth for more detailed information. But I bet You know that already. :)

If that's important to You; that's why I wrote a script which stops, and after mover process finishes its job, it starts a.o. deluge client.

For a test I've deleted script path's in mover tuning, and set script for a daily check at 2 am. (just for a test!) There was the same situation, please take a look. There is a strange time break between 2 am and 10 am - its almost 8.30 hours. I have absolutely no idea where is the issue. //EDIT: I think, that I have found the source of the problem, but will confirm it tomorrow, after scron runs script again. ca.mover.tuning-debug-20250916-1044.zip

That's my script: #!/bin/bash docker stop binhex-deluge sleep 1 docker stop binhex-lidarr sleep 1 docker stop bazarr sleep 1 docker stop binhex-plexpass /usr/local/emhttp/plugins/dynamix/scripts/notify -s "Mover Tuning" -d "Mover Tuning has started @ `date +%H:%M:%S`." and that's my script after mover finish it's job: #!/bin/bash docker stop binhex-deluge sleep 1 docker stop binhex-lidarr sleep 1 docker stop bazarr sleep 1 docker stop binhex-plexpass /usr/local/emhttp/plugins/dynamix/scripts/notify -s "Mover Tuning" -d "Mover Tuning has started @ `date +%H:%M:%S`." No, parity check was disabled.