**Host Examples**

For Broker running on localhost

send an S1F3 to the tool for svid 33008

<code bash>
mosquitto_pub -h localhost -t "gemhost/svidrequest/svid" -m "33008"
mosquitto_pub -h localhost -t "gemhost/svidrequest/sendmessage" -m "1"
</code>

subscribe to the value list in the S1F4 reply

<code bash>
mosquitto_sub -h localhost -t "gemhost/svidresponse/svidlist"
</code>

Remote Broker

To start the MQTT Server using a remote (not localhost) broker do this:

<code bash>
java -DMQTTBroker=ipaddress deploy.XXXXXX.EquipmentController
</code>

where ipaddress is the location of the broker (for example, 192.168.5.150)

the -h command on the subscribe and publish will be -h 192.168.5.150

for example:

<code bash>
mosquitto_sub -h 192.168.5.150 -t "gemhost/svidresponse/svidlist" 
</code>

<code javascript>
{ "values": [] }
</code>

<code bash>
mosquitto_pub -h 192.168.5.150 -t "gemhost/svidrequest/svid" -m "33008"
</code>
<code bash>
mosquitto_pub -h 192.168.5.150 -t "gemhost/svidrequest/sendmessage" -m "1"
</code>
results in a value appearing in the subscription for svidlist:

<code bash>
mosquitto_sub -h 192.168.5.150 -t "gemhost/svidresponse/svidlist" 
</code>

<code javascript>
{ "values": [] } 
</code>

<code javascript>
{ "values": [ "2019031221054472" ] , type:"20 }
</code>

**MQTT Downside**

MQTT has no built in way to indicate data quality.