mqtt

I was wondering if the MQTT protocol is suited for some high refresh rate data streaming. As it was designed for low-bandwidth high-latency application I was wondering how it would perform in a high-bandwidth low-latency application. What I want is to send sensor data at a rate of 60-120 times per second. Is this something feasible or will some design decisions in MQTT prevent that from working in a usable manner? I would have full control over the broker in this scenario and it would happen at QoS level 0. The payload would be a single 32bit float or 32 integer. All devices would connect over

In the below, when i run it and intentionally turn the WiFi off, the callBack clientCallBack.connectionLost displays the message Log.d(TAG, "@connectionLost: MQTT Server connection lost"); twice. And When I re connect, the message Log.i(TAG, "@onSuccess: Connection Successful."); in the client_1.connect callback is displayed only once. anyone can expain why i receive the message from the calback twice? Code @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.mqtt_proj_01_layout); sdCard = Environment

My Question is regarding TLS/SSL MQTT connection. I've installed moaquitto broker from this website. http://www.eclipse.org/mosquitto/download/ and done with simple subscribe/publish using paho eclipse library in java. then I created X509 certificates using bouncycastle in java. but now I am stuck at server configurations regarding these certificates.I need to use different certificates for different topics on same broker. What I found is the following mosquitto-auth-plug. https://github.com/jpmens/mosquitto-auth-plug But here in mosquitto_auth_plugin we need to define backend databases

In Node-Red, I would like to be able to send a message and wait for its response using MQTT, in between an HTTP input node and a response one. I think a picture is more relevant to explain this: The problem is an HTTP response node has to be directly linked to an input one somehow, so I thought of saving the whole message in context after receiving an HTTP input, then restore it before sending the response. The problem is that apparently, the structure of the message is circular, hence I can't directly convert it to a string, to store it in context. I've tried different things to solve this