tuya-convert VS arch-qbittorrentvpn

First of all I've tried Tuya-Convert but it was never able to find the device. I've also tried TuyOTA with similar results, it just seems like it can't detect the device at all - neither in pairing mode, nor in normal operation mode.

I was about to say a similar thing. Companies closing off their devices with paywall and other closed API are calling for a hack. I found this repo on GitHub

Mit tuya-convert.

Is it possible to run custom firmware on them? Like using https://github.com/ct-Open-Source/tuya-convert (not sure if this one is compatible with the newer lamps). Or maybe something else?

If it has an ESP chip, it probably won't OTA with https://github.com/ct-Open-Source/tuya-convert since that doesn't work on recent Tuya firmware, hence the blakadder page showing manual flashing.

> They cost >2x the Meross ones. Got 2. They work so far. Crossing my fingers they're legit, though my guess is they won't last.

FYI - there are cheap Tuya devices that can be flashed with alternative firmware[1] which works locally. More generically, there a lot of ESP32-based switches that work with Tasmota open-source firmware[2]. There breadth of devices is annoying because it makes configuration difficult because because different manufacturer wire up the relays differently, so it took me trial and error to figue out which device "port" the firmware needs to toggle to turn the switch on/off

1. https://github.com/ct-Open-Source/tuya-convert

2. https://github.com/tasmota

If you're already comfortable with Docker, setting up ESPHome and Home Assistant should be fairly easy for you, and will unlock lots of options. Depending on the hardware revision of your smartbubls, you might even be able to use Tuya-Convert to install ESPHome or Tasmota on your existing bulbs, and completely cut ties with Tuya and the cloud.

Maybe you could try this one instead: https://github.com/binhex/arch-qbittorrentvpn

I got it to work with OVPN for the time being. I have no idea what I could have done differently with Wireguard though. There is an open issue on github involving Mullvad with Wireguard, maybe its related?

If you're planning on using a new VPN you'll need to update your docker container w/ the new VPN info (account, pass, wireguard/openvpn, etc) and that should do it. I've heard decent things about proton vpn and airvpn but I'm sure there are plenty of acceptable options out there, just not many with decent port-forwarding capabilities if you care about that. airVPN is a good vpn for port-forwarding, binhex's github has a walkthrough for setting up airVPN as an example, shouldn't be much different from how you setup mullvad

I recommend https://github.com/binhex/arch-qbittorrentvpn. Simply because dyonr seemingly abandoned the project in 2022.

Third, better, option: run something like this https://github.com/binhex/arch-qbittorrentvpn

So I'm running Radarr 4.4.4.7068 (docker) and a modified version of qBittorrent which includes a VPN (https://github.com/binhex/arch-qbittorrentvpn). When I add a file via Radarr, qBittorrent complies with the "Maximum Seed Time" selected in Radarr and marks the torrent as "completed". However Radarr doesn't remove it from qBittorent, even if the option "Remove completed" is enabled.