-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update MQTT broker docs for clarity #3573
Conversation
Adding words to note that the reason a "run your own" broker is the most private is because the embedded broker doesn't support TLS/SSL. Also updating to use the new configuration tags.
hbmqtt supports SSL/TLS. Thus, the embedded broker support it but requires configuration. |
Ah, their documentation makes no reference to it, but now you've mentioned it I had a poke at the source and see it. Will update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 🐦
It does...Features and configuration. |
Darn it. Clearly my ability to RTFM is failing :/ |
This pr broke the travis tests: https://travis-ci.org/home-assistant/home-assistant.github.io/builds/286374091 |
@Danielhiversen I know...should be fixed soon. |
* Update MQTT broker docs for clarity Adding words to note that the reason a "run your own" broker is the most private is because the embedded broker doesn't support TLS/SSL. Also updating to use the new configuration tags. * Update to reference hbmqtt supporting TLS
Adding words to note that the reason a "run your own" broker is the most private is because the embedded broker doesn't support TLS/SSL.
Also updating to use the new configuration tags.