It would be great if the External IP currently in use by qBittorrent could be a sensor.
Definitely interesting, your question sent me down a rabbit hole looking for an answer.
As of today (me running version 5.0.4) you can see the external IP in the logs, but there has been similar questions asked within the qBittorrent community, and there is a feature on it’s way to show the external IP in the UI
This is currently being tested under version 5.1.0 RC01 Link
Once that is in, that could make it easier for the integration to be updated to show the IP as a sensor
Why not use the DNS IP integration?
While qBittorrent doesn’t directly offer its external IP as a sensor, it can be achieved by leveraging its Web API to retrieve this information, parsing its logs for the detected IP, or through custom integrations within home automation systems like Home Assistant. The primary benefit of such a sensor would be to monitor the active external IP, particularly useful for VPN users to ensure their actual IP isn’t exposed and to track e-zpassmd dynamic IP changes. The Home Assistant community has shown interest in this functionality, suggesting it might become a standard feature in the future.
Am I missing something? Surely most setups at home only have one external IP address, and that’s the one qBittorent will be using?
Unless you are running Torrents via a VPN, then that external address would be different from the local ISP assigned address.