Strong Password Generator to create secure passwords that are impossible to crack on your device without sending them across the Internet, and learn over 40 tricks to keep your passwords, accounts and documents safe.

If you have been following along, you now have a Hass.io installation setup up and ready to begin creating automations.

Random Password Generator. This form allows you to generate random passwords. The randomness comes from atmospheric noise, which for many purposes is better than the pseudo-random number algorithms typically used in computer programs. See full list on home-assistant.io.

As I said in my article about deciding on your home automation setup, you now need to set up the Z-Wave antenna so your various home automation equipment can talk to your Raspberry Pi and the Home Assistant software.

I recommend the Aeotec Z-Stick Gen5, Z-Wave Plus USB (affiliate link), but you theoretically can get any Z-Wave antenna and it will work.

Plug this USB device into your Raspberry Pi (and restart just to be safe).
Login to the Hass.io configuration using Putty
You need to figure out what the USB drive is called on your installation. Run the following command.

You need to tell Home Assistant that it should expect to see Z-Wave communication on this device.
Open the configuration.yaml file using vim

Scroll down to the bottom of the file and enter the following command. Save and close vim (:wq)

This command will tell Home Assistant to look enable the Z-Wave component and to look for its configuration in a separate file in the same directory as configuration.yaml called zwave.yaml.

Create a new file using vim and enter the name of the Z-Wave USB stick you found before. Save and close vim.

Now, you will begin to “test” your configuration before actually running it. It is very easy to mess up the format of the .yaml files and cause Home Assistant to not start.

Generate zwave network key random number

Luckily, Home Assistant has an easy way to check to see if configuration files are valid.

This tells Home Assistant to scan all of the .yaml files and see if there are any configuration issues that would cause it to not be able to restart and load. In typical Linux philosophy, if it reports no status, everything is good. This is because Linux “pipes” the output from one command to another and “chatty” output messages make it harder to pipe commands together.

You can also do this in the Home Assistant web portal.

Navigate to the web portal
Click on Configuration
Click on General
Click on Check Config
You will get

If everything is good, you will see a green “Configuration valid” message.

You can either reboot the Docker container or use the GUI. Note, as you add more and more automations, this will slow down (several minutes to reboot). This is why the GUI has options for just reloading pieces of the system.

After Docker reports success (by printing out homeassistant), you will have to wait a few minutes for Home Assistant to finish loading.

You need to push you new changes to Github so they are saved. Log back into the Docker container and check the status of the files

Check the status of your modified configuration files.

Wireless Network Key Netgear

Add these files (stage them) to your git changset so you can commit them.

Commit the changes

Push your changes to Github

You are now finally ready to begin adding devices to your home automation!

By default your Zigbee network isn’t as secured as possible. The following settings are recommeded to apply to your configuration.

Disable joining #

To disable joining it’s important that permit_join: false is set in your configuration.yaml. Otherwise rogue devices are able to join allowing them to send and receive Zigbee traffic.

Change Zigbee network encryption key #

Changing the network key requires repairing of all devices!

Generate Zwave Network Key Random Password

Zigbee2MQTT uses a known default encryption key (Zigbee Transport Key). Therefore it is recommended to use a different one. To use a different encryption key add the following to your configuration.yaml:

Do not use this exact key.

The network encryption key size is 128-bit which is essentially 16 decimal values between 0 and 255 or 16 hexadecimal values between 0x00and 0xFF.

Generate Zwave Network Key Random Name

If you need to transform your decimals to hexadecimals (or vice versa) please use a converter. Example: 92 (decimal) would become 5C (hexadecimal).

To let Zigbee2MQTT generate a new network key on next startup, add the following to configuration.yaml: