- Tue Mar 28, 2017 8:04 am
#64334
Hi, yes, we have modified the MQTTClient to work with WebSockets. We didn't have time to upload it on git yet. Did you find any other solution or would you be interested in our implementation?
- Tue Mar 28, 2017 7:58 pm
#64351
Can you tell us why you want mqtt client via websocket?
what is the whole picture?
what is the whole picture?
- Wed Mar 29, 2017 1:59 am
#64356
For the simple reason that we want to use port 80 to hit an Apache server before reaching the MQTT Broker.
The solution has already been implemented. We will upload to git shortly. I will update this post once that's done.
The solution has already been implemented. We will upload to git shortly. I will update this post once that's done.
- Thu Mar 30, 2017 7:28 am
#64400
Hi, unfortunately we didn't find any other solutions, so we're thinking to develop a similar one. If it is possible, we'll wait for your git library.
Our needs is to develop a firmware that can connect to a message broker in order to send and receive messages in real time (avoiding "polling").
Our needs is to develop a firmware that can connect to a message broker in order to send and receive messages in real time (avoiding "polling").
