Z-Wave secure inclusion uses more bandwidth for communications and can slow down your network. This adds a note to the docs to mention that as we've seen performance issues in discord with too many chatty nodes that were secure included.
* centos
* Update source/_docs/installation/centos.markdown
Fine with me. I did like having the "venv" in there to make it more obvious as to what is going on.
Co-Authored-By: Fabian Affolter <mail@fabian-affolter.ch>
* Update source/_docs/installation/centos.markdown
Co-Authored-By: Fabian Affolter <mail@fabian-affolter.ch>
* Update with working instructions
Old instructions failed to include virtualenv, also failed to actually start HA as the config directory it default creates was wrong, and empty.
* Minor changes
* automation troubleshooting.markdown
Add explanation of making check config visible
* withings.markdown
Add explanation of how to make the check config tool visible
* configuration.markdown
Add explanation to display the check config tool
* Fix broken link
* fix link OwnTracks platform
* fix link in lights built-in profiles
* fix link in Configurator the source
* fix link in Todoist determine....
determine what task in each project is "most" important
S2 still not supported in OZW as of 10/2019
Update config github link to the OZW1.4 branch since HA is still on 1.4 and the master branch is for OZW1.6
Minor tweak.. This used the previous Services icon which is no longer in use... Services is now a tab (text only) within Developer Tools since Home Assistant 0.96.
* Clarified the behavior of conditions.
The current reading of the documentation indicates that if a condition evaluates to true it stops executing. Added additional context to the first line to describe the actual behavior.
* Updated docs to clarify conditions behavior
The current reading of the documentation indicates that if a condition evaluates to true it stops executing. Added additional context to the first line to describe the actual behavior.
* Renamed script to automation
* Changed to script or automation for consistency.
Clarified that you MUST define the `certificate` parameter to enable TLS connections to the MQTT server. This was not clear to me and was fighting with getting the right PEM/CRT file setup as commections were failing. When I then selected 'auto' it worked as designed. It would be better if there was an 'enable_tls' config parameter that would enable it and default to 'auto', but that;s a code change.
