Skip to content
My Home Assistant configuration files
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
alarm Automated update at 2018-07-14 20:03 Jul 14, 2018
alerts
automation Automated update at 2019-03-16 16:04 Mar 16, 2019
binary_sensors Automated update at 2019-03-15 12:04 Mar 15, 2019
camera
climate Automated update at 2018-07-11 12:03 Jul 11, 2018
custom_components Automated update at 2018-05-31 12:03 May 31, 2018
device_tracker Automated update at 2019-03-15 12:04 Mar 15, 2019
etc/nginx/conf.d
hadashboard Automated update at 2019-03-15 12:04 Mar 15, 2019
history_graph Automated update at 2019-03-15 12:04 Mar 15, 2019
input_boolean
input_datetime
input_number Automated update at 2018-02-23 22:06 Feb 23, 2018
input_select Automated update at 2019-03-15 12:04 Mar 15, 2019
intent_scripts Automated update at 2018-02-23 22:06 Feb 23, 2018
light Automated update at 2018-10-10 21:00 Oct 10, 2018
local/bin
lovelace
media_player
notify
panel_iframe Automated update at 2019-03-15 12:04 Mar 15, 2019
panels
proximity Automated update at 2018-10-03 15:51 Oct 3, 2018
scenes Automated update at 2019-03-15 12:04 Mar 15, 2019
scripts
sensors Automated update at 2019-03-15 12:04 Mar 15, 2019
shell_commands
switch
weather Automated update at 2019-02-23 20:04 Feb 23, 2019
www
LICENSE Initial commit Sep 18, 2017
README.md
automations.yaml Initial commit for configuration upload Sep 18, 2017
cloud.yaml Automated update at 2019-01-07 00:03 Jan 7, 2019
configuration.yaml Automated update at 2019-03-16 16:04 Mar 16, 2019
customize.yaml Automated update at 2019-03-08 00:04 Mar 8, 2019
floorplan.html
floorplan.yaml Automated update at 2019-03-12 16:04 Mar 12, 2019
frontend.yaml Automated update at 2017-11-20 04:03 Nov 20, 2017
google_assistant.yaml Automated update at 2019-01-29 20:04 Jan 29, 2019
groups.yaml
influxdb.yaml
ui-lovelace.yaml Automated update at 2019-03-15 12:04 Mar 15, 2019
zwave_device_config.yaml

README.md

Home Assistant (0.88.2) configuration

This is my Home Assistant configuration, I'm currently running 0.88.2. It is installed on a Raspberry Pi 3, using the old All in One installer (effectively a manual install like this, on a 16 GB card, that I've upgraded to Python 3.6. I use a Razberry board for Z-Wave control.

To limit the risk brought by SD card corruption (a known risk with Pi3) I store the Home Assistant database on a USB stick, and use a multi-port USB charger with sufficient power for all ports, but have left one unused. The power cables are short, and high quality, to minimise issues with voltage drop. Of course, I also take many different backups to reduce the risk of losing anything.

This is one of a number of Pi3s I've got, and they're all in a Multi-Pi stackable case, to keep the footprint down. They share an HDMI cable to a nearby monitor, and an old USB keyboard I've got kicking around, because having a Pi fail to respond isn't that uncommon.

Each directory has a short readme explaining what's in there, and the purpose of each file or group of files.

On the Pi itself I run

  • Home Assistant
  • Floorplan for a high level overview
    • Screenshot of floorplan
    • Showing:
      • The blue bin is being collected tomorrow (yellow outline), and the brown bin in 2 or more days (green outline). The grey bin isn't currently scheduled for collection.
      • The background lighting in the lounge is on, as is the light by the house number.
      • The utility door is open, and the garden lights are on. Other exterior doors are closed.
      • The TV and Chromecast are off, as are the Sonos speakers.
      • The TV and X-Box in the family room are on.
      • All the mobiles are home, as is the tablet.
      • Oh, and the printer isn't yet low on consumables.
    • The floorplan was created in Inkscape, by importing the image of the house's floorplan from the purchase paperwork, then drawing over it. If you look at it you'll see that I built it up in layers, one for the foundation (ground), one for the structure, and one for the sensors. I don't really use those currently, other than to ensure that the right things are on top (sensors).
  • nginx to provide remote access, in conjunction with Let's Encrypt
  • Mosquitto for the MQTT broker

I used to run the following, but don't currently:

  • HA Dashboard for a "finger friendly" interface, but it's been replaced by the new Google Home app (for now anyway)
    • Screenshot of HA Dashboard

The devices, services, and software I use (with HA)

  • Sandisk Extreme micro SD cards
  • Z-Wave
    • Z-Wave.me Razberry Z-Wave board - it has the advantage of not using a USB port, but does require that the onboard Bluetooth is disabled
    • Aeotec MultiSensor 6
    • Fibaro motion sensor in the living room
    • Fibaro FGK10x door sensors (previous generation, superseded by the FGDW-002) on the garage doors
    • Sensative door/window strips on the external house doors
    • TKB TKB TZ69E - metering wall plugs
    • Foxx Project Smart Switch (which identifies itself as an Aeotec ZW075, aka Smart Switch Gen5). These are cheap, but there's no local switch control for the attached device. Mostly I'm using these as range extenders.
    • NodOn Octan Remote in the master bedroom to provide manual control of the Yeelight. It was originally used by the kitchen door, where the next item is now mounted.
    • NodOn Soft Remote in the second bedroom, to also provide manual control of that room's Yeelight.
    • Z-Wave.me WALLC-S wall controller, to provide a wall switch for the garden lights
  • Lighting
    • Yeelight component and led strips, one mounted behind the headboard in the master bedroom, and one along the wall side of the bed frame in the second bedroom. These provide good enough lighting to read by at night, and also to help wake us in the morning.
    • Outdoor mains 240V LED strip which we turn on and off with one of the wall plugs
    • Philips Hue compatible LED strips built following this guide, using the Gledopto GL-C-008 RGB+CCT LED Controller, a roll of RGB-CCT LED tape, and a 24V power supply
    • Philips Hue bridge (v2)
  • Nabu Casa cloud, which is a paid service, instead of the previous Google Assistant component. I use this with a bunch of Google Home Minis, a couple of Google Home Hubs, and a Lenovo Smart Display
  • Media
  • Notifications:
    • Pushover for lightweight notifications to phones/tablets, and I'm looking at replacing it with the REST notifier and Discord
    • LaMetric for notifications "in person", and it's a clock the rest of the time
    • TTS with the Google Home Mini's, Sonos, and Squeezeboxes
  • Presence detection:
    • Back to using Nmap for device tracking. While I did switch to Fritz!Box device tracking when I upgraded my router, the router ran out of memory
    • Monitor on another Pi3, and a Pi Zero W. This has completely replaced the use of the built in Bluetooth device tracker, and more than halved the startup time of HA.
    • GPS Logger for remote device tracking
      • I used to use OwnTracks for device tracking, using the HTTP interface, but not only did it have an annoying bug that caused it to randomly disable reporting, but it had been abandoned by the developer. Version 2.0 of the app solved both of those, but I've seen no reason to go back.
  • TransportAPI for information on the local train service with the UK transport component
  • DarkSky for weather data, alongside the Met Office, along with the associated sensor components
  • Plex for watching media, on TV, tablets and mobiles. I don't currently use the component
  • Xbox Live sensor which uses the XBoxAPI to track when one of us is on the XBox
  • Google Travel Time component which uses the Google Distance Matrix to provide estimated time to home
  • Getmail with a script that acts as the message delivery agent, to parse the recycling collection emails
    • I gave up on the the IMAP email content sensor since it doesn't keep state through restarts (which isn't unique to it, Home Assistant doesn't have a persistence mechanism other than for the input_* entities)
  • A HiWatch IPC-T140 dome camera, using the generic camera component. It's a 4K camera, and the Pi3 can't keep up when I use the FFMPEG component. I use the camera's built in motion detection, writing to a 200 GB SMB share (there's a firmware issue apparently, if the share is above that the camera gets confused and won't write).

Other software

  • PiVPN for remote access to my network
  • Pi Hole for blocking those pesky adverts
  • netdata so I can keep an eye on the performance
  • rpi-clone for bootable backups
  • rclone for offsite backups
  • rsnapshot runs on another system, and pulls backups

Presence detection

  • If you were following along, you'll note I use three different device trackers, two for home (nmap, bluetooth) and one for away (GPSLogger). I explain more about this here, with an update here, and another update (there will be a fourth update now I'm using monitor). Short version - I don't use groups, or merge the trackers. Both of those approaches have major shortcomings, for the first if you have a misbehaving sensor that's stuck at home you'll never be marked as away. For the second, the last one to update wins, so you can flip flop between two states. I'm experimenting with the Bayesian sensor and some automation logic - so far it's the automation logic that's winning for me.

Notes

  • These are (automatically) modified versions of my actual configurations
  • The goals with Home Assistant have been:
    1. Minimise human actions, and where that isn't possible streamline those human actions
    2. Provide voice control where the automations don't get it right (but try to fix that)
    3. Have a minimal UI to provide manual control (this is currently the Google Home app)

Future plans

A large amount of this will require a rewire of the lighting circuits, so that all the light switches have a neutral wire.

Devices

  • Dimmer modules at most light switches, the exception will be the toilet (since there's a fan linked to it) and the outside light
  • Switch modules for the extractor fans
  • Multisensors (light/motion/humidity/temperature) in the bedrooms and bathrooms
  • Multisensors (light/motion/temperature) in all other rooms
  • Lots more door and window sensors, including on the garden gate
  • Some form of distance sensor (ultrasonic or laser) in the garage
  • BLE beacons
  • Digital LED strip for the front of the garage, based upon the Bruh Automation work
  • Analogue LED strips (likely with a Z-Wave controller) for accent lighting and pathway lighting

Automation thoughts

  • Turn on extractor fans when the humidity is more than 5 points above the adjacent room, turning off once they drop to within 5 points
  • During darkness, if a bathroom door is opened, turn the bathroom light on at a low level, turning up to medium when the door closes, turning it off when the person leaves
  • Turn on the outside front light when the front door opens, the doorbell rings, or somebody is less than 5 minutes away, and coming home
  • Other than bedrooms, when the room is in darkness and there's movement turn on the light at a very low level
  • During daytime, if the lights are on for too long turn them off
  • Seasonal use of the digital LED strip
  • Flash the relevant section of the LED strip red if the garage door is opening or closing

Useful links

  • Home Assistant documentation and component list
  • Problems with Z-Wave delays and inconsistencies? Try this script in the dev-states section and you'll see if you've problem devices - shown by an RTT value of 1,000 or more, and retries significantly more than other devices
  • My blog on home automation and other things

Coffee

If I've helped you, and you really want to, you can buy me a coffee, but don't feel obliged - I'm not doing this for free coffee ;)

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.