Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

Add port for mqtt downlink #127

Closed
tftelkamp opened this issue Apr 5, 2016 · 4 comments
Closed

Add port for mqtt downlink #127

tftelkamp opened this issue Apr 5, 2016 · 4 comments
Labels
feature

Comments

@tftelkamp
Copy link

Application should be able to specify port for downlink messages, either via the topic or json.
@htdvisser htdvisser modified the milestone: Doing Apr 6, 2016
@htdvisser htdvisser self-assigned this Apr 6, 2016
@htdvisser htdvisser removed their assignment Apr 8, 2016
@KtorZ
Copy link
Contributor

KtorZ commented Apr 9, 2016

What do you mean exactly?
Application being able to connect to the mqtt server on the port they want ?

@htdvisser
Copy link
Contributor

htdvisser commented Apr 9, 2016 via email

@htdvisser htdvisser modified the milestones: Doing, Next Up Apr 13, 2016
@htdvisser htdvisser removed this from the Next Up milestone May 11, 2016
@htdvisser
Copy link
Contributor

This is relatively easy to implement, but requires a migration of the database in which packets are scheduled. As this database is not easy to migrate, it might be better to wait until we switch from our current binary datastore (Bolt) to Redis.

kersing added a commit to kersing/ttn that referenced this issue Jun 10, 2016
@kersing
Add port to MQTT json messages. Implements TheThingsArchive#127.
2f17675
@htdvisser htdvisser mentioned this issue Jul 7, 2016
Closed
20 tasks
@htdvisser
Copy link
Contributor

This has been implemented in the refactor branch. See #199 for more info.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@htdvisser @KtorZ @tftelkamp