shortbloke / home_assistant_config Goto Github PK

Wemo insight plugs don't like high load situations and have 2 have melted and died. Switching over to TP Link HS110 devices which claim a higher max load. Wemo insight support is woven into sensors and templates and automations.

New sensor: https://home-assistant.io/components/sensor.version/

This page: https://github.com/shortbloke/home_assistant_config/blob/master/docs/backup.md is incomplete and needs to be more detailed.

Show crontab settings explain reasons behind each method and and relevant script/commands.

Per: http://philhawthorne.com/making-dumb-dishwashers-and-washing-machines-smart-alerts-when-the-dishes-and-clothes-are-cleaned/

It would be good to translate the motion state values from z-wave sensors to a specific more meaningful state, for both display and automation purposes.

Move configuration from config dir to packages dir and sensors. Derive sensors from:
Air Quality

air_quality.bedroom:
 - air_quality_index: 12 
 - attribution: Dyson purifier air quality sensor
 - nitrogen_dioxide: 0 
 - particulate_matter_10: 8 
 - particulate_matter_2_5: 12 
 - volatile_organic_compounds: 4 
 - friendly_name: Bedroom

Fan

fan.bedroom: 
- speed: medium 
 - speed_list: low,medium,high 
 - oscillating: false 
 - night_mode: false 
 - auto_mode: false 
 - angle_low: 157 
 - angle_high: 202 
 - flow_direction_front: true 
 - timer: OFF 
 - hepa_filter: 88 
 - carbon_filter: 88 
 - dyson_speed: 6 
 - dyson_speed_list: 1,2,3,4,5,6,7,8,9,10 
 - friendly_name: Bedroom
 - supported_features: 3

Customise names and icons

Using automation to monitor sensors for memory and disk space, and perhaps high CPU usage. To send an alert to my IOS device when there is a potential problem.

Need to investigate why after ~24hrs HomeAssistant stops showing new values for a range of sensors. Most obviously temperature and humidity.

I've reduced the amount of data recorder is collecting and that logbook and history components collect, however I suspect this won't address the issue as I think something is crashing.

Currently using central history and recorder config. Might be good if this could be kept with the relevant packages.

I've purchased a couple of sonoff devices for controlling the fan in the loft and maybe some other things. Seems I need to change the firmware to one that supports MQTT.

• https://community.home-assistant.io/t/sonoff-homeassistant-alternative-firmware-for-sonoff-switches-for-use-with-mqtt-ha/2332
• https://github.com/KmanOz/Sonoff-HomeAssistant

Having implemented packages, update repo docs to reflect the new world.

Probably not automatically, but nice to be able to do it from GUI.
https://community.home-assistant.io/t/script-that-stops-hass-updates-hass-and-starts-hass-again/3330/17

Try and see if this helps: https://www.splitbrain.org/blog/2017-08/10-homeassistant_duckdns_letsencrypt

Git Pull HASSIO addon is currently pulling changes as they appear on github. However they don't wait for successful build.
Existing automation script trigged a pull via a shell script. Need to update to see if HASSIO addon can be called instead.
Requires that addon be set to not automatically update on change, instead would be triggered by automation.

Work in progress
Sort of a master slave configuration
Using MQTT and/or Home Assistant API (once known)

Pi provides support for RF433, ZWAVE and Zigbee

This change: home-assistant/core#8934
is listed as a breaking change in 0.52.1
Specifically as a change related to Sonoff device running the same custom firmware I'm using.

New feature:
https://home-assistant.io/docs/scripts/editor/

Check my scripts.yaml works with it.

Currently github is used to store configuration files, except those excluded by .gitignore thus some key content is not uploaded and therefore not backed up

• secrets.yaml, nest.conf, plex.conf which store passwords and API keys
• home-assistant_v2.db - which stores all event and sensor history/data
• home-assistant.log - the log file created in the current running instance.

These files need to be kept secure, but also backed up to my on-prem storage server and/or to an offsite file storage solution, i.e. dropbox, OneDrive etc. This needs to be done automatically and periodically.

Watch for API being added for 3rd Gen Nest Thermostats (UK) which control hot water too, but no API yet.
Watch: https://nestdevelopers.io/t/api-for-hot-water-control-3rd-gen-nest-thermostat/197

Investigate https://github.com/pkozul/ha-floorplan

Moving to hassio has meant my previous model of writing images, file backups etc to a SMB share is no longer valid.

I've added a dropbox sync add-on: https://github.com/danielwelch/hassio-dropbox-sync however this needs to be combined with a service to automate the creation of the snapshot: https://community.home-assistant.io/t/hassio-0-61-snapshot-service/39690

Which would also call https://github.com/danielwelch/hassio-dropbox-sync to sync the newly created backup to dropbox.

History component isn't great as its graphs get very cluttered when multiple sensors which trace the same unit of measurement are added.
Investigate different visualising options and configuration options.
Investigate to use DB on RPi vs moving it to separate server. Graphing is meant to be more intense than just storing the data, and ultimately less critical.

• InfluxDB and Grafana
• Setting up InfluxDB and Grafana using Docker
• DIY IoT Central – Home Assistant / InfluxDB / Grafana
• InfluxDB and Grafana for sensor time series
• https://www.van-porten.de/blog/2016/03/home-assistant/

The current automation scripts to turn of sockets if no moment detected for > 30mins AND the socket is drawing current (i.e. so we know the appliance is on, and don't turn off at the wall).

However this is open failure as if the appliance, in my case an Iron, which has a thermostat which turns on and off. So at the 30min point it's possible the current draw is low enough not to trigger.

Need to review at reversing the check as whilst power state may fluctuate a timer for how long the room has been empty would continue to grow. Needs some research into what the existing automation structure can provide, or if a new template sensor needs to be defined to capture the idle state/time.

Example automation script:

- id: a_IronOn_2
  alias: Ironing Room No Motion Turn off Irons Left
  trigger:
    - platform: state
      entity_id: sensor.aeotec_zw100_multisensor_6_burglar
      to: '0'
      for:
        minutes: 30
  condition:
    - condition: template
      value_template: '{{ states.sensor.tp_hs110_2_power.state | int > 10 }}'
  action:
    - service: homeassistant.turn_off
      entity_id: switch.tp_hs110_2
    - service: notify.notify
      data:
        title: "Ironing Room Alert!"
        message: "No Motion Detected Turning off Ironing room Irons (Left)"

Meant to be faster performance with MySQL compared to SQLite (default)

Either through different UI or setting up Default View and different groupings.

Install new sonoff switch for fan that draws air from outside and blows it on to the front of the microserver. Add automation scripts to trigger based on ambient loft temp and/or HPiLO measurements.

Error logged:

2020-01-13 09:25:45 ERROR (MainThread) [homeassistant.components.automation] Error while executing automation automation.house_unoccupied. Invalid data for call_service at pos 1: extra keys not allowed @ data['operation_mode']

Since multiple devices are shown on the map as Mi, add a picture or change names via customize: https://community.home-assistant.io/t/known-devices-local-picture/2051/8