Right now the suggestion is to put '0x' in front of the generated hex keys which is great, but when I followed the instructions I didn't realize it didn't put the comma between the items already and it caused me problems for awhile until I realized. I'm proposing a change to also suggest adding a comma so people, like me, following the instructions will see it.
* Add the network key to options.xml file
For the z-wave secure devices to connect properly. In addition to modifying the configuration.yaml file, the options.xml file network key must be set as well:
* Update source/_docs/z-wave/installation.markdown
Co-Authored-By: Klaas Schoute <klaas_schoute@hotmail.com>
* ✏️ Tweak
Co-authored-by: Klaas Schoute <klaas_schoute@hotmail.com>
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
* Be consistent with Home Assistant spelling
* Refer to the Configurator without "HASS"
That's what's it calls itself and how it is in the add-on store.
* Be consistent with Hass.io spelling
* Tell vscode to spell HassOS like that
Users experiencing issues / interference by ModemManager are still commonly popping up in the forum. I changed the wording, so hopefully users will more easily recognize this applies to them.
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
