great job
muy buena explicacion de todo, hice unas pruebas con cloudmqtt con un wemos d1 esp8266 y funciona perfecto todo.
la extension es muy buena.
gracias por toda la informacion.
16.- Basic example of Subscribe and Publish to HiveMQ.
Normally MQTT is used in IoT, example: a sensor in a hardware sends a short message to a Broker and in real time an app receives it, or an app sends a short message to a Broker and this information is received by a hardware that performs a certain function.
We are going to see a basic example of Publish and Subscribe in the HiveMQ Broker.
We will not use hardware, only the application and the Broker.
AcceleratorSensor "Publish" in HiveMQ xAccel,yAccel,zAccel with topic: juan/acelerometer
and "Subscribe" juan/acelerometer, receive: xAccel,yAccel,zAccel
why port at hivemq not same with port at mit app?
if i write at hivemq, host : broker.hivemq.com. , at mit app must be broker: broker.hivemq.com . it right?
the topic at publish should be title that my project right?
please help me how to get updated data on mqtt server
Hello friend I'm studying the mqtt protocol
my project is to turn the room lights on and off with every button publish and subscribe
publish to send data values and subscribe to receive data but there is a problem when the application is disconnected with the subscriber data broker not being successfully updated
if anyone in the mqtt extension can request a request to the broker to update the missed data, I really need advice. thanks
sorry I just want to receive input and suggestions from different forums , because the two platforms are almost the same implementation . is this against the rules? thanks
You should explain a "little bit" what you are doing.
There are several examples, I tried n. 18 and is working ok:
press connect to broker
press subscribe
press start accel
after a few seconds press stop accel
( this example is sending too much data to the broker and hivemq asks not to "abuse" their free broker )
The first 3 labels show the "accel data" read from your phone.
The last 3 labels show the same data read back from the broker
P.S.
I added also a status label just to see what's going on, during connection and subscription
P.P.S.
You can also "interact" withe the phone using the hivemq mqtt web client ( just subscribe or publish to the same topic as set in the aia, which is juan/acelerometer )