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.
* 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
* Improved zwave security network key description
As someone adding a zwave device securely for the first time I found there were some gaps in the documentation.
* ✏️ Corrected small typo
* Adding remark pertaining to secure devices
Per experience with Schlage locks, you need to 1st exclude them from the previous network/hub before you can enroll them in a new network. This seems to be true for secure zwave devices with anti-theft protection
* Clarification
Added clarification, that you may need to use the previous setup for the exclusion process,
* Minor changes
* Z-Wave documents refactoring
* Continuing to update documentation for Z-Wave
* Wakeup correction
Note that it only applies to devices that can be battery powered (for example, my Aeotec sensor is USB powered, but as it supports Wake the option is shown)
* Polling impact notes
Example of what the impact of polling can be
* Fix object_id to entity_id
