Re-create smart house - Githubissues

vigeeking / homeAutomation

My goal is to create a pipeline that is built exclusively with tools I either already know, or am only learning because they provide added value to the project

https://github.com/vigeeking/homeAutomation

0 stars 0 forks source link

Re-create smart house #14

Closed vigeeking closed 4 years ago

vigeeking commented 4 years ago

Part of the reason I am hesitant to make any changes to the smart house is because there is physical work involved in re-creating the network. Each wall switch has to be added, but is currently tied to the usb zwave/zigbee controller. This task is done when I can comfortably plug in that controller to another device, and control the house from there.

This spawned issue #41

vigeeking commented 4 years ago

This will be useful when it comes time to add the USB zwave stick: https://chrisschuld.com/2019/09/running-home-assistant-with-docker/

vigeeking commented 4 years ago

I successfully spiked on using a pi as a VM. Next step is to create a new VM, and see if I can get hassio setup as a cold spare. Once that is done, I'll create a 3rd vm that is hassio with actual pipeline integration in it.

vigeeking commented 4 years ago

Had to do a brief spike to mount the current hassio data files (currently located on a live qcow2 image on the main server). I copied them, and am going to try to mount them locally so I can copy over the needed data. I had to install qemu-tools to do so. Instructions were found here: https://www.randomhacks.co.uk/how-to-mount-a-qcow2-disk-image-on-ubuntu/

vigeeking commented 4 years ago

Found my first "not my fault" bug. Apparently there are problems with tp-link/kasa integration with home assistant. I ran into a lot of trouble trying to figure out why the networking was failing and I couldn't talk to the tplink devices. I may need to list out the tp-link devices manually, so I am pasted the needed code here for future reference I am relatively sure about the plugs and switched, not sure about the dimmer (it's a fan, that may complicate things):

/edit to update, all of the devices are switches, I am deleting what I pasted below and updating as of this timestamp. tplink: discovery: false switch:

host: 10.42.100.101
host: 10.42.100.102
host: 10.42.100.103
host: 10.42.100.114
host: 10.42.100.115
host: 10.42.100.116
host: 10.42.100.118
host: 10.42.100.119
host: 10.42.100.127
host: 10.42.100.104
host: 10.42.100.105
host: 10.42.100.106
host: 10.42.100.107
host: 10.42.100.110
host: 10.42.100.117

vigeeking commented 4 years ago

Needed to copy the lovelace files, so I created a lovelaceCustom file in the repo, I manually need to copy and paste this in to the ui in order for my config to work. I'm also still having to paste the secrets.yaml file into the repo after I download. I want there to be a skeleton value that I just have to update instead of having to recreate the files all the time.

In the meantime, I am currently struggling with passing the USB device to the docker container in unraid, but everything else is working. I am currently operating under the assumption that the problem is related to naming the device, since I have been using the /dev/ttyUSB0/1/2 and it looks like I should be using the direct address, per this comment: https://forums.unraid.net/topic/91533-unraid-683-pass-usb-webcam-into-docker/

vigeeking commented 4 years ago

Ran into a roadblock with the zwave stick. It appears unraid doesn't have the drivers for the zwave stick I use. It works as a vm, because I'm loading the drivers manually. As a container though, it won't work with unraid. My workaround for this is to create a new linux vm, and have it pass the device through so docker can use the device. The definition of done is being changed to require a stock ubuntu server with docker-compose installed.