This is a couple of questions in one post. About 18 months ago I purchased a NUC to run HA. I installed Ubuntu and installed HA directly on to that. It has been running well. However, I recently noticed that I was using a massive 3% of the processor so inspired by the many posts on here I decided to go the Docker route. I wiped the machine, installed Ubuntu 18.04 and installed Docker and docker-compose.
I started a home-assistant container from the command line and let it generate the default files. I stopped the container and copied my backup in to the config directory. HA wouldn’t complete the start up. Spent way too long yesterday trying to figure out why so today I decided to start from scratch. I recreated the container and started adding things in to the config one by one. It started well but then I added in the nest configuration. My config is as straightforward as
nest:
client_id: !secret nest_client_id
client_secret: !secret nest_client_secret
But restarting HA just causes it to freeze. Remove this directive, it starts up fine.
Added a few more things (Hue lights, mqtt and so on which were all fine) and decided to start on my zwave stuff.
I decided to do a hard reset of my Aeotec ZW090 Z-Stick Gen5, connect it up, add the zwave: directive with the USB port and restart. This worked because I can see the controller in HA. So I proceeded to add a Multisensor device. Reset it, added it and it appeared in HA. Went to the Customization section and renamed everything to do with this new node to Hallway. Every time I clicked Save I got
It seems that your configuration.yaml doesn’t properly include customize.yaml Changes made here won’t affect your configuration.
Which isn’t correct. On Googling this error message you find a couple of people who have reported it but the tickets have closed automatically because there’s been no response to them. And it does seem to save the changes so I assume this isn’t a relevant problem.
I also remembered to do the the Command Options > Binary Sensor Report thing.
This seemed to go well so I added another couple of nodes (Bathroom and Kitchen). At this point I realised I was being a bit over confident because they’re not working properly - and I can’t figure out why. First, they seem to be reporting their values as a string so I get graphs like this
Secondly, I’m in the UK. I don’t have the heating on and it’s currently (2245 BST) 9°C outside so there’s no way it’s 24°C in my hallway. It’s also currently 28°C in my kitchen which could be possible if someone was cooking but no-one is cooking at this time of night.
I’m using nginx with letsencrypt certificates to forward traffic from https://house.domain.com/ to my HA box. When I was running HA direct on the box this worked fine so all I did - or all I thought I needed to do - was change the IP address in my hass-proxy.conf file. Now whenever I log in to HA there’s a panel saying
Login attempt or request with invalid authentication from 192.168.105.22
I never used to get this with the old setup. I assume it has something to do with where HA thinks the connection is coming from? HTTP connection looks like this:
http:
api_password: !secret httppass
base_url: !secret base_url
use_x_forwarded_for: True
trusted_proxies:
- 192.168.105.22
trusted_networks:
- 192.168.0.0/24
- 127.0.0.1
- 192.168.101.0/24
- 192.168.102.0/24
- 192.168.103.0/24
- 192.168.104.0/24
- 192.168.105.0/24
I don’t think this is breaking anything per se but as part of testing the motion sensors I was trying to walk around with my iPhone and the HA App - but now it doesn’t load, it just shows “Loading data…”. Again, I can’t figure out why. Neither the client or the server produces an error.
So - did anyone else come across network problems and zwave problems with Docker? I’m pretty sure that the zwave problems aren’t going to be Docker related but I can’t rule it out completely because I never had these problems when HA had direct access to the controller. Also, are there any other tweaks I have to make to HA or nginx to get the proxy to work with HA in a container?
Very grateful for any suggestions
Steve