I didn’t run into any issues particular to setting this up in Docker. The other services just get accessed via the machine hostname and port since they are only used internally. I also didn’t bother with a reverse proxy for any of this, since I already have one for HASS sitting in my DMZ (yet to be Dockerised). This then gets rolled into my normal backups. The only other parts worth noting are that I mount all my volumes under /mnt/docker-data, which is an NFS share onto the ZFS array of the virtual machine host. I eventually found the XML file which lists all the available voices and extracted the URL of the one I wanted (the online demo helps to decide). The official way to download them is a GUI tool that won’t run inside the container. Actually finding the voices is a little interesting. The main point of interest is that I mount the voice file for my preferred MaryTTS voice inside the container. There’s nothing particularly earth shattering here. mnt/docker-data/marytts/lib/voice-dfki-poppy-hsmm-5.2.jar:/marytts/marytts-5.1.2/lib/voice-dfki-poppy-hsmm-5.2.jar:ro mnt/docker-data/home-assistant:/config mnt/docker-data/mosquitto/logs:/mosquitto/logs mnt/docker-data/mosquitto/data:/mosquitto/data mnt/docker-data/mosquitto/config:/mosquitto/config The full docker-compose.yml file for my new stack is given below: version: '3' I still have a big network re-organisation to do, so hopefully it will get done then. If I can get Avahi/mDNS working across VLANs at some point I will move it. However, my main worry over not doing that was the mDNS used by ESPHome. I was a little reserved about doing this, since it means everything in that VLAN (most of which is blocked from the internet) can see the full HA server. I set up a new clean VM inside my home automation VLAN. However, I think I’ll look into updating that at some point. Luckily, this isn’t an externally facing application so it isn’t too critical from a security standpoint. This reinforces my point about random images from Docker Hub. Looking at this image, it hasn’t been updated in three years which. It was recommended that I use the silversniper/marytts image. This is due to the lack of PicoTTS inside the HASS Docker image. I also ended up running a MaryTTS container to replace PicoTTS that I had been running for my voice announcements. Looks like I have a few devices to update! I had previously just been using the command line tool to build and upload to them. In addition to the four services above I wanted to run the ESPHome dashboard in order to manage my devices better. I also wanted to avoid building custom Docker images for now, until I work out a decent update strategy. This was useful as I’m always pretty reticent to use some questionably maintained image from the Docker Hub, mainly due to the lack of security updates. Luckily for me, the four main components of my system all have official/recommended Docker images available. I therefore decided to cut my losses with that and not reinstall it (for now). However, something broke in my setup and I hadn’t got around to fixing it. I had also been running InfluxDB and Grafana. Zigbee2mqtt: this is a fairly recent addition and provides a bridge between my zigbee devices and MQTT/Home Assistant.Although I call this the main instance, it doesn’t do a whole lot and mostly gets used for testing right now. Node-RED: the home automation server also houses the main Node-Red instance (others are scattered around on various Raspberry Pis).MQTT: via the Mosquitto broker, which is used to connect many of the devices in the house.Home Assistant: provides the main brains of the system and integrates all my devices as well as driving most of the automation.I’ve written about my home automation setup before, but here is a brief recap of what I’m running (only the server side stuff): As it turned out, I waited long enough for the awesome HASS developers to make all my problems go away (or at least the Lovelace related ones). The main reason for this was the switch to Lovelace as the default UI, which I was dreading. The motivation behind upgrading the home automation system first was to do it at the same time as I did a large update to Home Assistant, since I’d been holding back on updating. This post details the second stage of my road to Docker, although really was is the first stage since I’m writing these out of order! I actually converted my home automation systems over to Docker before tackling the web stack. This would consist of virtual machines (in various VLANs), with most of the services running in Docker. In my first post of this series, I outlined my plan to convert my infrastructure over to a layered setup. This post is part of a series on this project. Please see the disclaimer for more information. Tweet reddit Email reddit Share Share Pinterest
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |