-
Notifications
You must be signed in to change notification settings - Fork 638
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
Message is not matching listener as expected #504
Comments
@mininobu the information you have given about the functionality working when triggered by manually using Slack to send the message (as a human), and not working when the message is originating from the IFTTT webhook, is very helpful. can you check the logs once again when triggering the command using the Slack client to see what comes after the log line you shared already?
After this line, I'd expect another line that looks similar to the following:
If this line exists, can you share the contents? Please mask any sensitive data or IDs you don't want to share. I think understanding the structure of those values will be important in debugging further. |
@aoberoi
OK.
Just to be sure, after logging in hubot, share all logs until RM - mini 3 runs.
Thank you. |
@aoberoi hubot-slack ver 4.4.0 debug log
hubot-slack 4.5.0 debug log
|
okay i've been debugging with @shanedewael and we think we understand the root cause! there's no need to provide us with any more logs, we're working on a patch with a fix. |
for the record, it turns out the IFTTT sends messages with no |
Description
This issue is to track the problem first described in #500. In that issue, a bug was uncovered with the attachment formatting, and fixed. But @mininobu is still having a problem with a listener (created by the
hubot-broadlink-rm
script package) not matching messages it is meant to match. The key details are in this commentRequirements (place an
x
in each of the[ ]
)Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
hubot-slack version: 4.5.2
node version: 8.11.3
OS version(s): Raspbian 9.1(Raspberry Pi 3)
Steps to reproduce:
IFTTT "that" info
Which channel? => Direct Message / @homebot
Message => send tv:on
※The message was sent from the Android application of IFTTT.
Expected result:
RM Mini to operate.
Actual result:
RM Mini is idle.
Attachments:
The text was updated successfully, but these errors were encountered: