Connecting to MyQttHub through AT Commands

[phildunphy]

Hello!

We are trying to send messages to our mqtt hub using an LTE module from Nimbelink, through the method of “Socket Dials”, these are AT Commands issued to the modem which uses an internal TCP/IP stack.

We would basically enter

at#xtcpconn=3,“node02.myqtthub.com”,1883

which the modem answers with success

after that the only other command to use is at#xtcpsend=3, which opens a promt to enter whatever is going to be sent, we have tried sending mosquitto_pub string without success.

Sadly, Nimbelink only has an example using HTTP POST, sending to the promt something like this POST /dweet/for/xxxxxxxxxxxxxxx?hello=world, which works without a problem.

We wonder if you have an idea of what should be sent to the promt to actually send de data to the hub. Thanks in advance!

[ricardo.hortet]

Hello,

With those basic operations, you should be able to mount login+publish+logout operation

using the API and HTTP 1883/tcp port:

REST API to manage MyQttHub service

Table of contents 1. Intro: login and logout 1.1) REST API to manage MQTT service (ReactiveMyQtt v6.7.764 1.2) Login into the API and getting a tokenId 1.3) Logout from the API (cancelling tokenId) 2. User management 2.1) Change my password (for a logged device) 2.2) Get user information (for a logged device) 2.3) Get connected devices to your domain (for a logged domain admin device) 3. Domain and device management 3.1) Get connected devices to your domain (for a logged domain admin de…

The general idea is to mount every request over your TCP Connection with:

HTTP HEADERS
\r\n
MyQttHub Message

Http headers should be something very simple declaring POST method that associated

to the API [1], plus Host and optionally token received from login.

MyQttHub Message will be raw json declaration required by the service.

[1] REST API to manage MyQttHub service

Use these notes to workout a solution. With a bit of time, you shouldn’t have any stopper

that makes this idea impossible.

Best Regards,