Original HA installation on VM on server

click here for HA Yellow

Virtual machine notes

The virtual machine configuration files are stored in “C:\ProgramData\Microsoft\Windows\Hyper-V”.

The virtual hard drives are stored in “C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks”.

Ubuntu notes:

 Home Assistant directory: cd /home/homeassistant/.homeassistant

System operation notes:

Most issues where the system does not work right are fixed with a restart.
You can restart Home Assistant within it's menu, but sometimes it needs to have the service restarted.
The other common issue for me is if I disconnect one of the serial controllers, it can no longer connect with that controller.

Restart HomeAssistant service:

sudo systemctl restart homeassistant - works more consistently that restarting from GUI

Restart Digi One serial ports (services):

sudo systemctl restart dgrp

if you unplug the serial port from the x10 transmitter, or cycle power on the ethernet <> serial dongle, you need to restart this service

note well: you should restart the home assistant service after this

To check serial ports are ok:

check serial ports exist:
ls /dev directory

you should see two devices:

/dev/ttyX00 x.x.x.250
/dev/ttyZ00 x.x.x.251

If restarting serial port services does not work:

The script to link the com port to an IP address is in in /home/greg/.scripts

The script creates a device and a symbolic link to the device, and then sets rights and ownership

I create 2 devices, one X for X10 (250) and one Z for Z-Wave (251)

Here's the script: in /home/greg/.scripts

sudo ./start_virt_serial.sh

#!/bin/bash
sudo dgrp_cfg_node init X 192.168.10.250 1
sudo dgrp_cfg_node start X 192.168.10.250 1
sudo chown -R homeassistant /dev/ttyX00
sudo chown -R homeassistant /dev/tty_dgrp_X_0
sudo chmod 755 /dev/ttyX00
sudo chmod 755 /dev/tty_dgrp_X_0
sudo dgrp_cfg_node init Z 192.168.10.251 1
sudo dgrp_cfg_node start Z 192.168.10.251 1
sudo chown -R homeassistant /dev/ttyZ00
sudo chown -R homeassistant /dev/tty_dgrp_Z_0
sudo chmod 755 /dev/ttyZ00
sudo chmod 755 /dev/tty_dgrp_Z_0

  sudo journalctl -xe

baud on x10 CM11A 4800 baud

use dmsg to debug

service is defined in /etc/systemd/system/dgrp.service

scripts are in

If the system is really messed up, full restart:

stop homeassistant service
delete Z-Wave config file ( /home/homeassistant/.homeassistant/zwcfg_0x003d0b40.xml )
(re)start serial services
(re)start homeassistant service
check Z-Wave service (how?)

Undocumented quirks:

Often you will need to restart the system if new Z-Wave devices are not added after a restart. It's common for just one to be added every time you restart the system.

When this happens, I can see the Z-Troller sending data, as you can see the node numbers, but it's like the system needs a couple of restarts to fully read in the new device.

Configuring the Home Assistant application

Using the GUI

there are devices and entities. Devices are easy to control, entities may not be able to be used directly.

Other Configuration

Most files are in /home/homeassistant/.homeassistant$

sudo vim filename  (since files are owned by ha user)

the icons are in: https://cdn.materialdesignicons.com/5.3.45/

https://community.home-assistant.io/t/z-wave-xml-config-files/109118/2

X10 Configuration:

configuration.yaml - put new x10 devices - be very careful on syntax

Z-Wave Configuration:

zwc.xml - zwave config file, can be deleted
zwc.log - duhh

Automations:

automation.yaml - automations

date and time can be tricky

https://community.home-assistant.io/t/trigger-an-action-on-specific-date-time/13524

Scripts:

scripts.yaml - guess

icons? don't know the directory