mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-13 12:26:50 +00:00
Remove commercial brokers from MQTT documentation (#18063)
* Remove commercial brokers from MQTT documentation * Remove stale note
This commit is contained in:
parent
2caaf07de7
commit
fa493b59bd
@ -92,68 +92,6 @@ mqtt:
|
||||
certificate: /home/paulus/downloads/mosquitto.org.crt
|
||||
```
|
||||
|
||||
### HiveMQ Cloud
|
||||
|
||||
HiveMQ Cloud is a fully managed MQTT broker that provides you a private broker.
|
||||
A free plan for up to 100 devices is available. You can see all of HiveMQ's
|
||||
different plan options here: <https://www.hivemq.com/mqtt-cloud-broker/>
|
||||
|
||||
Home Assistant is not affiliated with HiveMQ Cloud and does not receive any kickbacks.
|
||||
|
||||
1. [Create an account](http://console.hivemq.cloud) (links to sign up).
|
||||
2. When sign up you will receive automatically the free plan that allows you to
|
||||
connect up to 100 devices.
|
||||
3. Create MQTT credentials in the "Access Management" tab of your
|
||||
"Cluster Detail View" you can use to connect Home Assistant
|
||||
and any MQTT device.
|
||||
4. [Download](https://letsencrypt.org/certs/trustid-x3-root.pem) the trusted
|
||||
certificate from let’s encrypt to ensure secure communication between
|
||||
Home Assistant and your HiveMQ Cloud cluster.
|
||||
5. Copy the broker info to your `configuration.yaml`. You can find the
|
||||
"Broker Hostname" in the "Cluster Overview". Use the credentials you just
|
||||
created as username and password and the path from the downloaded certificate:
|
||||

|
||||
|
||||
```yaml
|
||||
mqtt:
|
||||
broker: "HIVEMQ_BROKER_HOSTNAME"
|
||||
port: 8883
|
||||
username: "MQTT_USERNAME"
|
||||
password: "MQTT_PASSWORD"
|
||||
certificate: PATH_TO_STORED_CERTIFICATE
|
||||
```
|
||||
|
||||
After restarting Home Assistant, your MQTT integration connected to HiveMQ Cloud
|
||||
will appear.
|
||||
|
||||
### CloudMQTT
|
||||
|
||||
[CloudMQTT](https://www.cloudmqtt.com) is a hosted private MQTT instance. Plans start at 5$ per month.
|
||||
|
||||
<div class='note'>
|
||||
Home Assistant is not affiliated with CloudMQTT nor will receive any kickbacks.
|
||||
</div>
|
||||
|
||||
1. [Create an account](https://customer.cloudmqtt.com/login)
|
||||
2. [Create a new CloudMQTT instance](https://customer.cloudmqtt.com/subscription/create)
|
||||
3. From the control panel, click on the _Details_ button.
|
||||
4. Create unique users for Home Assistant and each phone to connect<br>(CloudMQTT does not allow two connections from the same user)
|
||||
1. Under manage users, fill in username, password and click add
|
||||
2. Under ACLs, select user, topic `#`, check 'read access' and 'write access'
|
||||
5. Copy the instance info to your configuration.yaml:
|
||||
|
||||
```yaml
|
||||
mqtt:
|
||||
broker: CLOUDMQTT_SERVER
|
||||
port: CLOUDMQTT_PORT
|
||||
username: CLOUDMQTT_USER
|
||||
password: CLOUDMQTT_PASSWORD
|
||||
```
|
||||
|
||||
<div class='note'>
|
||||
Home Assistant will automatically load the correct certificate if you connect to an encrypted channel of CloudMQTT (port range 20000-30000).
|
||||
</div>
|
||||
|
||||
<div class='note'>
|
||||
|
||||
If you experience an error message like `Failed to connect due to exception: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed`, then add `certificate: auto` to your broker configuration and restart Home Assistant.
|
||||
|
Binary file not shown.
Before Width: | Height: | Size: 56 KiB |
Loading…
x
Reference in New Issue
Block a user