-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
[FEAT] Include paho-mqtt to enable Apprise mqtt:// support #146
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Bumping to express my continued interest. |
You can use the universal package install mod to install it |
@aptalca Oh that's perfect, thank you! Sorry for the noise. |
This issue is locked due to inactivity |
Is this a new feature request?
Wanted change
I would like for the
paho-mqtt
Python module to be included in this image.Reason for change
It would be helpful to me if Bazarr's Apprise feature would support
mqtt://
URIs. Thelinuxserver/docker-sabnzbd
image already supports this (https://github.com/linuxserver/docker-sabnzbd/blame/4.3.0-ls160/package_versions.txt#L80)At present, attempting to configure a notification in Bazarr that uses "Apprise API" with an "mqtt://" URI results in an error:
That error is the result of bazarr attempting and failing to import the
paho-mqtt
module (https://github.com/morpheus65535/bazarr/blob/v1.4.5/libs/apprise/plugins/NotifyMQTT.py#L48-L56)Proposed code change
I'm not too familiar with LSio's image building system so I'm afraid I don't know how to add this. It appears that with
linuxserver/docker-sabnzbd
, it was automatically pulled in by sabnzbd's ownrequirements.txt
with their introduction of the Apprise integration (sabnzbd/sabnzbd#2796). Does this issue needs to be taken upstream to bazarr for them to update theirrequirements.txt
?The text was updated successfully, but these errors were encountered: