shayaantx / botdarr

Slack/Discord/Telegram/Matrix bot for accessing radarr, sonarr, and lidarr
GNU General Public License v3.0
151 stars 13 forks source link

Messages not sent with Slack integration #92

Closed tubbo closed 1 year ago

tubbo commented 1 year ago

I believe I followed the documentation steps correctly, and my Docker-installed Botdarr is able to see messages in the Slack room as evidenced by its slack.log and these messages from the audit log:

2023-Mar-15 19:55:37 PM [pool-4-thread-1] DEBUG com.botdarr.clients.ChatClientBootstrap - Processing command !status for username tubbo with prefix !
2023-Mar-15 19:55:37 PM [pool-4-thread-1] DEBUG com.botdarr.clients.ChatClientBootstrap - Processing command response com.botdarr.commands.responses.StatusCommandResponse@533aca15

However, I don't see any response in my Slack channel:

Screenshot 2023-03-15 at 4 01 26 PM

Here's my properties file, sans secret tokens:

slack-bot-token=#REDACTED
slack-user-token=#REDACTED
slack-channels="#requests"
radarr-url=http://radarr:7878
radarr-token=#REDACTED
radarr-default-profile=Any
radarr-path=/mnt/movies
sonarr-url=http://sonarr:8989
sonarr-token=#REDACTED
sonarr-default-profile=Any
sonarr-path=/mnt/tv
lidarr-url=http://lidarr:8686
lidarr-token=#REDACTED
lidarr-default-quality-profile=Lossless
lidarr-default-metadata-profile=Standard
lidarr-path=/mnt/music
log-level=all
max-downloads-to-show=20
max-results-to-show=20
command-prefix=!
timeout=5000

(note: all of my other services are running in the same docker-compose env so I am addressing them by their container names)

I also surmised that I had to add quotes around slack-channels= so that Java wouldn't think that was a comment...but that didn't seem to work either. At least with log-level=all I can see what's going on...setting $LOG_LEVEL didn't really seem to work in this way.

One other thing I should point out is that this bot, just like my aggregators, has no open ports. The Docker example didn't seem like it needed them, and since you're connecting to Slack over WS, I figured it's probably fine...but I'm just mentioning because I really have no idea what's going on here.

I also tried adding some scopes to the bot user but no dice:

Screenshot 2023-03-15 at 4 05 17 PM

shayaantx commented 1 year ago

I haven't tried slack integration in awhile (and unaware if anyone uses it :) )

Let me try it myself tonight or tomorrow and see what happens (it could be broken)

One other thing I should point out is that this bot, just like my aggregators, has no open ports

@tubbo There is no open port, cause there is nothing to serve to an open port. All the protocols don't need open ports at the current time, they all use some form of RTTM or some protocols where its not necessary to have an open port.

tubbo commented 1 year ago

@shayaantx

@tubbo There is no open port, cause there is nothing to serve to an open port. All the protocols don't need open ports at the current time, they all use some form of RTTM or some protocols where its not necessary to have an open port.

That's what I figured.

Let me try it myself tonight or tomorrow and see what happens (it could be broken)

If you need me to supply any other logs, I can definitely do that. Not sure how much help I'll be with the Java code as I'm incredibly rusty (no pun intended), but I can at least compile stuff and try it out from here.

shayaantx commented 1 year ago

@tubbo so your slack setup looks right, can you try with below

slack-channels=requests

Pretty sure thats why, so I added this check that prevents bot from starting if you put special chars (other than number/alpha and "-") https://github.com/shayaantx/botdarr/pull/93 (the slack.log would have the message now indicating why)

tubbo commented 1 year ago

I changed my properties file to slack-channels=requests and that worked, thanks!