Software: Home Assistant Version: 0.90.1
special note: If user gets completely locked out Remove both .storage/auth and .storage/onboarding to restart the onboarding process and create a new user.
- As most of the modded cards for lovelace don't allow you to realign on the fly, the following pages don't view well on my mobile. This page is specifically to allow easy vision of the most likely options wanted.
- This page is for toggling states and getting an overview of the switchable components.
- This page provides vision for the devices on the network, and adjust alert thresholds etc.
I am using a Raspberry Pi 3B+ using HassOS and HassIO.
I run headless, and use Samba to update the configuration.
-
HassIO Add-ons in use;
-
To update the configuration over the network - Samba Share
-
To keep the appropriate IP address for the dynamic DNS - Duck DNS
-
Occasionally I need to SSH into the Pi, this isn't always turned on - SSH & Web Terminal
-
Some of the more complicated automation is done here - Appdaemon
-
To do network wide ad-blocking - Pi-hole
-
Before updating to the new version, run this to make sure you won't get odd results - Check Home Assistant configuration
-
To keep up to date with the lovelace cards and supported custom components - Custom_Updater and/or HACS
-
To get a better view of the Buses in Canberra I use the updated code and the recommendations on adjusting the size of the database - GTFS
-
To get access to the Hue remote controls, I use - HueSensor
-
Statements with additional information - homeassistant: / frontend: / lovelace: / recorder: / http: / logger: / tts:
-
Statements with no additional information - introduction: / config: / updater: / discovery: / conversation: / history: / logbook: / map: / system_health: / sun: / person:
-
Statements I don't use - cloud:
- Samsung Smartthings Wifi Hub, motion sensors, multifunction sensors, washing machine & dryer
- Phillips Hue Lights, motion sensors, remote controls
- Logitech Harmony Hub Remote control
- Kevo Locks Locks (through custom python code in appdaemon)
- Nest Protect Fire Alarms
- Netgear Orbi Orbi Mesh Router
- Chamberlain Myq Myq Garage Door Opener
- Bond.io IR Fan controller (through IFTTT Webhooks)
- Google Home & Chromecast Media controls, alarms and timers
- TP-Link Switches Switches
- GPSLogger - integration
- Nmap - configuration.yaml
- Netgear - configuration.yaml
- trackr - configuration.yaml
- huesensor - configuration.yaml
- Zone - zone.yaml
- Proximity - proximity.yaml
- BOM Sensor - sensor.yaml
- Dark Sky Weather - configuration.yaml
- Dark Sky Sensor - sensor.yaml
- Season - sensor.yaml
Devices (Fire alarms, garage door, lights, motion & multifunction sensors, switches, remote controls, streaming, locks, printer)
-
Appdaemon - appdaemon/apps.yaml AND appdaemon/apps/kevo/locks.py This also requires pykevoplus & bs4 python libaries to work
-
Nest - integration via configuration.yaml
-
Myq - configuration.yaml
-
Phillips Hue - configuration.yaml AND integration
-
Huesensor - custom component
-
Smartthings - integration
-
TP-Link - integration
-
Google Cast - integration
-
Epson Printer - sensor.yaml (command line)
-
Batteries - sensor.yaml (template)
-
GPS last updated - sensor.yaml (template)
-
TP-Link Switch Energy Usage - sensor.yaml (template)
-
Torque - sensor.yaml (DOES NOT WORK through HTTPS, not being used)
-
Hue Motion Sensors - sensor.yaml
- System Monitor - sensor.yaml
- Pi-hole - sensor.yaml
- Check External IP - sensor.yaml (This is used to check, and if the ip has changed, it reconnects hangouts)
- Waze Travel Time - sensor.yaml
- GTFS - custom_component AND sensor.yaml
- Google Home - configuration.yaml
- Timers - timer.yaml
-
IFTTT - configuration.yaml for sending webhooks
-
IFTTT - integration for receiving webhooks
-
Appdaemon - appdaemon/apps.yaml AND appdaemon/apps
-
Automation - automation yaml files in /automations
-
Script - scripts.yaml
-
Input Select - input_select.yaml
-
Input Boolean - input_boolean.yaml
-
Input Number - input_number.yaml
-
Binary Sensor - binary_sensor.yaml
- Google Hangout Intents - integration AND hangouts.yaml AND hangout_intent_scripts.yaml
- Google Assistant - ga.yaml ***this is recorded as google_assistant: in configuration.yaml
- Google Hangouts - integration
- Pushbullet - notify.yaml
- SMTP - notify.yaml
- Google Calendar - calendar.yaml ***this is recorded as google: in configuration.yaml
- Calendars - sensor.yaml
- Time & Date - sensor.yaml
- Group - groups.yaml
- Lovelace - configuration.yaml AND ui-lovelace.yaml
- Tracker Card - ui-lovelace.yaml
- Waze Card - ui-lovelace.yaml
- Card Tools - ui-lovelace.yaml
- Card Modder - ui-lovelace.yaml
- Fold Entity Row - ui-lovelace.yaml
- Layout Card - ui-lovelace.yaml
- Vertical Stack in Card - ui-lovelace.yaml
- HA Dashboard - appdaemon/dashboards
- Picture Elements - ui-lovelace.yaml
These different concepts spawn alerts, automations or just update the UI
There are four (4) time modes for the house to be in, Morning, Day, Evening & Night.
Morning starts at 6am and turns on a number of lights and resets switches and motion sensors if they have been turned off. Morning can be triggered through a calendar entry #morning if you need it to start earlier for a certain day.
Day starts at 9am and turns all the lights off. Day is automatically triggered when everyone is 'not_home' and it is before 6pm.
Evening starts 30mins before sunset, different lights and switches are triggered.
Night starts at 10pm, turning off all lights (except for the bedroom lights). Lights will be turned on if the presence changes to a home state on a 10 min timer.
There are a number of different presence options, All Home, All Away, Someone Home, Guest.
All Home is set when all the watched devices are in the home zone or connected to the wifi.
All Away is set when all the watched devices are not in the home zone and not connected to the wifi.
Someone Home is set when at least one watched device or the Guest flag is turned on.
Guest can be set either manually or by placing a calendar entry #guest (turning on at start and turning off at end of event).
There are two main options for messaging, Hangouts or Pushbullet, the house will default to Hangouts, but it can be manually changed to Pushbullet if it is noticed that the notifications are not working and a restart cannot be performed.
There are quite a few different travel options, entering and leaving zones can start timers and if other zones are entered within a certain time, assumptions are made about buses that people may be on.
Bus times from a number of bus stops are shown as well as the house trying to 'guess' if people are travelling in the car or walking/bus to determine what to do with locks and the garage door when arriving home.
The latest method uses Tasker/IFTTT to see if someone is reaching home while connected to the car, and will open the garage door. These are works in progress with a number of different options having been tried, with proximity sensors and torque (which would be the most effective but doesn't seem to work with https).
A large number of mutually exclusive values that can then be used by entity-filter cards in lovelace to only show the current state of those items in a glance view for a mobile. Covers whether doors are closed and locked, lights, fans, switches, TV, whose is cooking, messaging option, certain errors are available.
Uses a calendar entry using #cook, to set the person cooking that day.
Tasker/IFTTT notify HA when a person is connected to the car bluetooth (assumed to be driving).
A number of different alerts, for printer ink, cpu and disk usage and batteries low trigger messages and show on the mobile glance page.
A mechanism to let us know if the heating and cooling should be on or off (only done in particular seasons), and turns the fans on and off based upon an 'optimal' temperature range in and outside the house. A second option to trigger to turn on bed warmers is yet to be tested when we can get the appropriate electric blankets/throws and additional switches.
A set of sensors that looks at the devices on the network and if certain hubs/devices disappear a notification will be shown on the glance mobile page.
This sensor aims to see how long since the GPSLogger has updated while away from home, if it has not reported for an hour it warns the individual that their logging is not working correctly. This seems to work intermittantly, think it needs something to trigger it.