Remove instructions to install libopenzwave1.5 on Linux installs. This instruction causes a lot of problems as the installed files interfere with the Python openzwave installation.
* Sets front matter defaults
* Removes default front matter from section templates/pages
* Removes default front matter from addon pages
* Removes default front matter from integration pages
* Removes default front matter from posts
* Removes default front matter from docs pages
* Removes default front matter from other pages
* Fixes blog category pages
* Automatically create linkable headers
* Visually improve position of linkable header chain icon
* Do not auto link headers on homepage
* Remove linkable_title everywhere
* 🚑 Re-instante linkable_title plugin as NOOP
* Added another troubleshooting step
After a chat with petergebruers, these error messages are good ways of identify if you've made the mistake of running multiple things that access the controller, which breaks your system in strange and mysterious ways.
* Minor changes
The current structure leads to confusion, which parts apply to Hass.io, or Hassbian, or ... As discussed in the architecture issue, I've moved all the platform specific parts to the end, even for those that require no actions.
I've also:
* moved the details for how to find the appropriate device path, and highlighting the likely default paths
* linked to a useful site that'll generate the content for the key, for those not using Linux
* stripped out the duplication of statements about the first run
* reordered the Hass.io section to put the GUI actions first, with a "you can also use the command line" rather than the other way around
* added details of how to pass the stick through on Docker
* put in a Community install section for other Linux, and Mac. Removed RancherOS
* expanded the wall of text note explaining the `ls` output so that you can actually follow it
We should consider recommending a network key for all z-wave installations. As users begin to add more and more devices they may not think about adding this later on as the network grows. Many users come to Discord or elsewhere and get confused as to why their Z-Wave device is not functioning correctly and come to find out they needed a network key and to add the device securely. As more and more Z-Wave Plus devices come out there are more security enabled devices as well. All locks and sensors are pretty much security devices.
