Skip to content
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

Topic returning topic filter, not message topic #40

Closed
fiLLLip opened this issue May 7, 2020 · 2 comments
Closed

Topic returning topic filter, not message topic #40

fiLLLip opened this issue May 7, 2020 · 2 comments
Assignees
Labels
response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days.

Comments

@fiLLLip
Copy link

fiLLLip commented May 7, 2020

When trying out the sample, and listening to MQTT on a wildcard topic, the topic set in the on_publish is set to the filter, not the actual topic that the message appeared on. How to deal with this, and get the actual topic?

E.g. '$aws/things/+/shadow/update/accepted' should give topic '$aws/things/my_test_device/shadow/update/accepted'

const on_publish = async (topic: string, payload: ArrayBuffer) => {

Edit: Maybe this should be directed at the https://github.com/awslabs/aws-crt-nodejs project?

@KaibaLopez
Copy link
Contributor

Hi @fiLLLip ,
Sorry for the lack of response here, i see that you linked a closed issue on crt-nodjs, does that mean you've figure this out? Do you still have other questions?

@KaibaLopez KaibaLopez self-assigned this May 12, 2020
@KaibaLopez KaibaLopez added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days. label May 12, 2020
@fiLLLip
Copy link
Author

fiLLLip commented May 13, 2020

Yes, I used the .on('message') event instead after subscribing. This supplied the message topic.

@fiLLLip fiLLLip closed this as completed May 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days.
Projects
None yet
Development

No branches or pull requests

2 participants