mqttui-publish(1) | General Commands Manual | mqttui-publish(1) |
NAME
mqttui-publish - Publish a value quickly
SYNOPSIS
mqttui publish [-r|--retain] [-v|--verbose] [-b|--broker] [-u|--username] [--password] [-i|--client-id] [--client-cert] [--client-key] [--insecure] [-h|--help] <TOPIC> [PAYLOAD]
DESCRIPTION
Publish a value quickly
OPTIONS
- -r, --retain
- Publish the MQTT message retained
- -v, --verbose
- Show full MQTT communication
- -b, --broker=URL [default: mqtt://localhost]
- URL which represents how to connect to the MQTT broker.
Examples: `mqtt://localhost` `mqtt://localhost:1883` `mqtts://localhost` `mqtts://localhost:8883` `ws://localhost/path` `ws://localhost:9001/path` `wss://localhost/path` `wss://localhost:9001/path`
- -u, --username=STRING
- Username to access the mqtt broker.
Anonymous access when not supplied.
- --password=STRING
- Password to access the mqtt broker.
Consider using a connection with TLS to the broker. Otherwise the password will be transported in plaintext.
Passing the password via command line is insecure as the password can be read from the history! You should pass it via environment variable.
- -i, --client-id=STRING
- Specify the client id to connect with
- --client-cert=FILEPATH
- Path to the TLS client certificate file.
Used together with --client-key to enable TLS client authentication. The file has to be a DER-encoded X.509 certificate serialized to PEM.
- --client-key=FILEPATH
- Path to the TLS client private key.
Used together with --client-cert to enable TLS client authentication. The file has to be a DER-encoded ASN.1 file in PKCS#8 form serialized to PEM.
- --insecure
- Allow insecure TLS connections
- -h, --help
- Print help (see a summary with '-h')
- <TOPIC>
- Topic to publish to
- [PAYLOAD]
- Payload to be published.
Reads from stdin when not specified. This allows file content to be sent via pipes like this (bash):
`mqttui publish some/topic </etc/hostname`
`cowsay "I was here" | mqttui publish some/topic`
publish |