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

support MQTT-SN #180

Closed
ghost opened this issue Dec 18, 2018 · 3 comments
Closed

support MQTT-SN #180

ghost opened this issue Dec 18, 2018 · 3 comments
Labels

Comments

@ghost
Copy link

ghost commented Dec 18, 2018

MQTT-SN uses UDP.
Its normally used for sensor data and it would be most useful to me.

I found a few implementations, and have not tried them yet.
https://github.com/Kmotiko/ceratopoGon

Please let me know if your open to eventually adding this to your roadmap.

@kelindar
Copy link
Contributor

kelindar commented Jan 6, 2019

Thanks @gedw99 for suggesting MQTT-SN, I had a look and it wouln't fit very nicely with emitter directly as from what I gather MQTT-SN is supposed to be used as a gateway and have MQTT broker behind. Seems like more appropriate usage of MQTT-SN would be in a some sort of a gateway appliance (eg: Alexa-like)

I do see the use for sensor networks and UDP, but we still need to find a way to properly secure this. Currently in the MQTT-SN specification you'd need to pre-register topics and then provide topic IDs which sounds almost impossible to secure in an unsecure network.

Maybe instead of doing that, supporting full MQTT publish over UDP would be more useful? Given that emitter doens't actually require authentication and has channel keys, we could have a separate UDP listener on the same port which only listens for publish operations - this would allow sensor networks to publish messages to emitter without any connection drama.

@kelindar
Copy link
Contributor

@gedw99 I'm thinking about implementing an "emitter-gateway" sometime in future. Here's something which maybe able to alleviate some of the sensor network headaches (still TCP though): #183

@stale
Copy link

stale bot commented May 15, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label May 15, 2019
@stale stale bot closed this as completed May 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant