From b260f2881e0721f3844a40b22ae859210097ee85 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 29 Oct 2015 00:09:11 -0700 Subject: [PATCH] Site updated at 2015-10-29 07:09:11 UTC --- .jekyll-metadata | Bin 0 -> 4 bytes atom.xml | 3907 +++++++---------- blog/2014/12/18/website-launched/index.html | 81 +- .../index.html | 112 +- .../index.html | 122 +- .../index.html | 91 +- blog/2015/01/13/nest-in-da-house/index.html | 105 +- blog/2015/01/24/release-notes/index.html | 102 +- .../2015/02/08/looking-at-the-past/index.html | 108 +- blog/2015/02/24/streaming-updates/index.html | 91 +- .../index.html | 86 +- blog/2015/03/08/new-logo/index.html | 88 +- blog/2015/03/11/release-notes/index.html | 151 +- blog/2015/03/22/release-notes/index.html | 269 +- blog/2015/04/25/release-notes/index.html | 286 +- .../05/09/utc-time-zone-awareness/index.html | 106 +- blog/2015/05/14/release-notes/index.html | 321 +- blog/2015/06/10/release-notes/index.html | 435 +- .../index.html | 357 +- .../index.html | 311 +- .../index.html | 125 +- .../index.html | 364 +- .../index.html | 298 +- .../index.html | 588 ++- .../13/home-assistant-meets-ifttt/index.html | 367 +- .../index.html | 184 +- .../alarm-sonos-and-itunes-support/index.html | 203 +- .../index.html | 123 +- .../index.html | 718 ++- .../index.html | 104 +- .../index.html | 142 +- blog/archives/index.html | 352 +- blog/categories/architecture/atom.xml | 33 +- blog/categories/architecture/index.html | 61 +- blog/categories/branding/atom.xml | 9 +- blog/categories/branding/index.html | 61 +- blog/categories/component/atom.xml | 80 +- blog/categories/component/index.html | 88 +- blog/categories/core/atom.xml | 27 +- blog/categories/core/index.html | 70 +- blog/categories/esp8266/atom.xml | 418 +- blog/categories/esp8266/index.html | 61 +- blog/categories/frontend/atom.xml | 39 +- blog/categories/frontend/index.html | 70 +- blog/categories/how-to/atom.xml | 1083 +++-- blog/categories/how-to/index.html | 88 +- blog/categories/mqtt/atom.xml | 741 ++-- blog/categories/mqtt/index.html | 70 +- blog/categories/release-notes/atom.xml | 482 +- blog/categories/release-notes/index.html | 182 +- blog/categories/user-stories/atom.xml | 354 +- blog/categories/user-stories/index.html | 70 +- blog/categories/website/atom.xml | 2 +- blog/categories/website/index.html | 61 +- blog/index.html | 684 +-- blog/posts/2/index.html | 805 ++-- blog/posts/3/index.html | 485 +- components/alarm_control_panel.html | 2004 +-------- components/alarm_control_panel.manual.html | 1678 +------ .../alarm_control_panel.manual/index.html | 224 + components/alarm_control_panel.mqtt.html | 1687 +------ .../alarm_control_panel.mqtt/index.html | 218 + .../alarm_control_panel/index.html | 126 +- components/arduino.html | 2340 +--------- components/arduino/index.html | 229 + components/automation.html | 2597 +---------- components/automation/index.html | 503 +++ components/browser.html | 2305 +--------- components/browser/index.html | 201 + components/camera.foscam.html | 1658 +------ components/camera.foscam/index.html | 198 + components/camera.generic.html | 1661 +------ components/camera.generic/index.html | 204 + components/configurator.html | 2296 +--------- components/configurator/index.html | 187 + components/conversation.html | 2292 +--------- components/conversation/index.html | 188 + components/device_sun_light_trigger.html | 2309 +--------- .../device_sun_light_trigger/index.html | 204 + components/device_tracker.actiontec.html | 1734 +------- .../device_tracker.actiontec/index.html | 239 + components/device_tracker.aruba.html | 1732 +------- components/device_tracker.aruba/index.html | 237 + components/device_tracker.asuswrt.html | 1727 +------- components/device_tracker.asuswrt/index.html | 232 + components/device_tracker.ddwrt.html | 1722 +------- components/device_tracker.ddwrt/index.html | 228 + components/device_tracker.geofancy.html | 1708 +------ components/device_tracker.geofancy/index.html | 215 + components/device_tracker.html | 2086 +-------- components/device_tracker.luci.html | 1727 +------- components/device_tracker.luci/index.html | 236 + components/device_tracker.mqtt.html | 1747 +------- components/device_tracker.mqtt/index.html | 242 + components/device_tracker.netgear.html | 1720 +------- components/device_tracker.netgear/index.html | 226 + components/device_tracker.nmap_scanner.html | 1717 +------- .../device_tracker.nmap_scanner/index.html | 220 + components/device_tracker.owntracks.html | 1715 +------- .../device_tracker.owntracks/index.html | 220 + components/device_tracker.snmp.html | 1731 +------- components/device_tracker.snmp/index.html | 237 + components/device_tracker.thomson.html | 1722 +------- components/device_tracker.thomson/index.html | 228 + components/device_tracker.tomato.html | 1720 +------- components/device_tracker.tomato/index.html | 227 + components/device_tracker.tplink.html | 1732 +------- components/device_tracker.tplink/index.html | 237 + components/device_tracker.ubus.html | 1745 +------- components/device_tracker.ubus/index.html | 257 ++ components/device_tracker/index.html | 225 + components/discovery.html | 2304 +--------- components/discovery/index.html | 198 + components/downloader.html | 2311 +--------- components/downloader/index.html | 206 + components/group.html | 2275 +--------- components/group/index.html | 180 + components/history.html | 2307 +--------- components/history/index.html | 212 + components/ifttt.html | 1735 +------- components/ifttt.manything.html | 1715 +------- components/ifttt.manything/index.html | 252 ++ components/ifttt/index.html | 261 ++ components/index.html | 776 +--- components/introduction.html | 2289 +--------- components/introduction/index.html | 185 + components/isy994.html | 2413 +--------- components/isy994/index.html | 293 ++ components/keyboard.html | 2308 +--------- components/keyboard/index.html | 206 + components/light.blinksticklight.html | 1676 +------ components/light.blinksticklight/index.html | 203 + components/light.html | 2124 +-------- components/light.hue.html | 1666 +------ components/light.hue/index.html | 194 + components/light.hyperion.html | 1665 +------ components/light.hyperion/index.html | 194 + components/light.limitlessled.html | 1677 +------ components/light.limitlessled/index.html | 205 + components/light.rfxtrx.html | 1700 +------ components/light.rfxtrx/index.html | 219 + components/light.tellstick.html | 1689 +------ components/light.tellstick/index.html | 209 + components/light.vera.html | 1712 +------- components/light.vera/index.html | 229 + components/light.wink.html | 1684 +------ components/light.wink/index.html | 200 + components/light/index.html | 270 ++ components/logbook.html | 2281 +--------- components/logbook/index.html | 189 + components/media_player.cast.html | 1680 +------ components/media_player.cast/index.html | 204 + components/media_player.denon.html | 1701 +------ components/media_player.denon/index.html | 222 + components/media_player.firetv.html | 1717 +------- components/media_player.firetv/index.html | 236 + components/media_player.html | 2109 +-------- components/media_player.itunes.html | 1685 +------ components/media_player.itunes/index.html | 209 + components/media_player.kodi.html | 1686 +------ components/media_player.kodi/index.html | 210 + components/media_player.mpd.html | 1688 +------ components/media_player.mpd/index.html | 213 + components/media_player.plex.html | 1689 +------ components/media_player.plex/index.html | 215 + components/media_player.sonos.html | 1672 +------ components/media_player.sonos/index.html | 198 + components/media_player.squeezebox.html | 1686 +------ components/media_player.squeezebox/index.html | 210 + components/media_player/index.html | 251 ++ components/modbus.html | 2373 +--------- components/modbus/index.html | 252 ++ components/mqtt.html | 2471 +---------- components/mqtt/index.html | 350 ++ components/notify.file.html | 1690 +------ components/notify.file/index.html | 212 + components/notify.html | 2066 +-------- components/notify.instapush.html | 1710 +------- components/notify.instapush/index.html | 233 + components/notify.nma.html | 1692 +------ components/notify.nma/index.html | 213 + components/notify.pushbullet.html | 1690 +------ components/notify.pushbullet/index.html | 211 + components/notify.pushover.html | 1698 +------ components/notify.pushover/index.html | 219 + components/notify.slack.html | 1694 +------ components/notify.slack/index.html | 216 + components/notify.smtp.html | 1711 +------- components/notify.smtp/index.html | 232 + components/notify.syslog.html | 1799 +------- components/notify.syslog/index.html | 320 ++ components/notify.telegram.html | 1711 +------- components/notify.telegram/index.html | 234 + components/notify.xmpp.html | 1694 +------ components/notify.xmpp/index.html | 215 + components/notify/index.html | 218 + components/rfxtrx.html | 2362 +--------- components/rfxtrx/index.html | 242 + components/scene.html | 2293 +--------- components/scene/index.html | 187 + components/script.html | 2307 +--------- components/script/index.html | 202 + components/sensor.arduino.html | 1688 +------ components/sensor.arduino/index.html | 216 + components/sensor.arest.html | 1870 +------- components/sensor.arest/index.html | 363 ++ components/sensor.bitcoin.html | 1802 +------- components/sensor.bitcoin/index.html | 292 ++ components/sensor.command_sensor.html | 1816 +------- components/sensor.command_sensor/index.html | 324 ++ components/sensor.cpuspeed.html | 1744 +------- components/sensor.cpuspeed/index.html | 235 + components/sensor.dht.html | 1677 +------ components/sensor.dht/index.html | 210 + components/sensor.efergy.html | 1761 +------- components/sensor.efergy/index.html | 251 ++ components/sensor.forecast.html | 1677 +------ components/sensor.forecast/index.html | 221 + components/sensor.glances.html | 1790 +------- components/sensor.glances/index.html | 283 ++ components/sensor.html | 2119 +-------- components/sensor.modbus.html | 1812 +------- components/sensor.modbus/index.html | 288 ++ components/sensor.mqtt.html | 1780 +------- components/sensor.mqtt/index.html | 259 ++ components/sensor.mysensors.html | 1755 +------- components/sensor.mysensors/index.html | 249 ++ components/sensor.openweathermap.html | 1668 +------ components/sensor.openweathermap/index.html | 212 + components/sensor.rest.html | 1829 +------- components/sensor.rest/index.html | 327 ++ components/sensor.rfxtrx.html | 1759 +------- components/sensor.rfxtrx/index.html | 242 + components/sensor.rpi_gpio.html | 1697 +------ components/sensor.rpi_gpio/index.html | 222 + components/sensor.sabnzbd.html | 1763 +------- components/sensor.sabnzbd/index.html | 253 ++ components/sensor.swiss_public_transport.html | 1752 +------- .../sensor.swiss_public_transport/index.html | 243 + components/sensor.systemmonitor.html | 1844 +------- components/sensor.systemmonitor/index.html | 334 ++ components/sensor.tellstick.html | 1776 +------- components/sensor.tellstick/index.html | 258 ++ components/sensor.temper.html | 1736 +------- components/sensor.temper/index.html | 228 + components/sensor.time_date.html | 1752 +------- components/sensor.time_date/index.html | 242 + components/sensor.transmission.html | 1793 +------- components/sensor.transmission/index.html | 274 ++ components/sensor.vera.html | 1782 +------- components/sensor.vera/index.html | 262 ++ components/sensor.wink.html | 1756 +------- components/sensor.wink/index.html | 236 + components/sensor.worldclock.html | 1751 +------- components/sensor.worldclock/index.html | 245 ++ components/sensor/index.html | 234 + components/shell_command.html | 2295 +--------- components/shell_command/index.html | 189 + components/simple_alarm.html | 2280 +--------- components/simple_alarm/index.html | 185 + components/sun.html | 2340 +--------- components/sun/index.html | 243 + components/switch.arduino.html | 1694 +------ components/switch.arduino/index.html | 220 + components/switch.arest.html | 1729 +------- components/switch.arest/index.html | 242 + components/switch.command_switch.html | 1744 +------- components/switch.command_switch/index.html | 264 ++ components/switch.edimax.html | 1704 +------ components/switch.edimax/index.html | 220 + components/switch.hikvision.html | 1661 +------ components/switch.hikvision/index.html | 199 + components/switch.html | 2075 +-------- components/switch.modbus.html | 1760 +------- components/switch.modbus/index.html | 261 ++ components/switch.mqtt.html | 1747 +------- components/switch.mqtt/index.html | 248 ++ components/switch.rest.html | 1722 +------- components/switch.rest/index.html | 231 + components/switch.rfxtrx.html | 1724 +------- components/switch.rfxtrx/index.html | 232 + components/switch.rpi_gpio.html | 1691 +------ components/switch.rpi_gpio/index.html | 217 + components/switch.tellstick.html | 1721 +------- components/switch.tellstick/index.html | 228 + components/switch.transmission.html | 1719 +------- components/switch.transmission/index.html | 230 + components/switch.vera.html | 1734 +------- components/switch.vera/index.html | 239 + components/switch.wemo.html | 1690 +------ components/switch.wemo/index.html | 206 + components/switch.wink.html | 1708 +------ components/switch.wink/index.html | 213 + components/switch/index.html | 210 + components/tellstick.html | 2338 +--------- components/tellstick/index.html | 215 + components/thermostat.heat_control.html | 1644 +------ components/thermostat.heat_control/index.html | 187 + components/thermostat.html | 2015 +-------- components/thermostat.nest.html | 1650 +------ components/thermostat.nest/index.html | 191 + components/thermostat.radiotherm.html | 1655 +------ components/thermostat.radiotherm/index.html | 198 + .../thermostat/index.html | 126 +- components/vera.html | 2332 +--------- components/vera/index.html | 205 + components/verisure.html | 2333 +--------- components/verisure/index.html | 218 + components/wink.html | 2354 +--------- components/wink/index.html | 228 + components/zone.html | 2307 +--------- components/zone/index.html | 204 + components/zwave.html | 2327 +--------- components/zwave/index.html | 220 + cookbook/automation_for_rainy_days/index.html | 192 + cookbook/automation_sun/index.html | 178 + .../index.html | 174 + cookbook/dim_lights_when_playing_media.html | 225 - .../dim_lights_when_playing_media/index.html | 216 + cookbook/index.html | 65 +- .../index.html | 183 + demo/frontend.html | 2 +- developers/add_new_platform.html | 266 +- developers/add_new_platform/index.html | 227 + developers/api.html | 164 +- .../api/index.html | 87 +- developers/architecture.html | 301 +- developers/architecture/index.html | 265 ++ developers/creating_components.html | 272 +- developers/creating_components/index.html | 238 + developers/credits.html | 224 +- developers/credits/index.html | 207 + developers/frontend.html | 288 +- developers/frontend/index.html | 251 ++ developers/index.html | 99 +- developers/python_api.html | 371 +- developers/python_api/index.html | 303 ++ developers/rest_api.html | 563 +-- developers/rest_api/index.html | 437 ++ developers/website.html | 206 +- developers/website/index.html | 189 + getting-started/android.html | 171 +- .../android/index.html | 92 +- getting-started/automation.html | 408 +- getting-started/automation/index.html | 306 ++ getting-started/autostart.html | 296 +- getting-started/autostart/index.html | 276 ++ getting-started/configuration.html | 243 +- getting-started/configuration/index.html | 200 + getting-started/devices.html | 224 +- getting-started/devices/index.html | 188 + getting-started/index.html | 190 +- getting-started/presence-detection.html | 207 +- getting-started/presence-detection/index.html | 177 + .../troubleshooting-configuration.html | 281 +- .../troubleshooting-configuration/index.html | 218 + getting-started/troubleshooting.html | 224 +- getting-started/troubleshooting/index.html | 214 + help/index.html | 51 +- index.html | 83 +- sitemap.xml | 807 +++- stylesheets/screen.css | 2 +- 362 files changed, 42053 insertions(+), 256343 deletions(-) create mode 100644 .jekyll-metadata create mode 100644 components/alarm_control_panel.manual/index.html create mode 100644 components/alarm_control_panel.mqtt/index.html rename cookbook/automation_for_rainy_days.html => components/alarm_control_panel/index.html (54%) create mode 100644 components/arduino/index.html create mode 100644 components/automation/index.html create mode 100644 components/browser/index.html create mode 100644 components/camera.foscam/index.html create mode 100644 components/camera.generic/index.html create mode 100644 components/configurator/index.html create mode 100644 components/conversation/index.html create mode 100644 components/device_sun_light_trigger/index.html create mode 100644 components/device_tracker.actiontec/index.html create mode 100644 components/device_tracker.aruba/index.html create mode 100644 components/device_tracker.asuswrt/index.html create mode 100644 components/device_tracker.ddwrt/index.html create mode 100644 components/device_tracker.geofancy/index.html create mode 100644 components/device_tracker.luci/index.html create mode 100644 components/device_tracker.mqtt/index.html create mode 100644 components/device_tracker.netgear/index.html create mode 100644 components/device_tracker.nmap_scanner/index.html create mode 100644 components/device_tracker.owntracks/index.html create mode 100644 components/device_tracker.snmp/index.html create mode 100644 components/device_tracker.thomson/index.html create mode 100644 components/device_tracker.tomato/index.html create mode 100644 components/device_tracker.tplink/index.html create mode 100644 components/device_tracker.ubus/index.html create mode 100644 components/device_tracker/index.html create mode 100644 components/discovery/index.html create mode 100644 components/downloader/index.html create mode 100644 components/group/index.html create mode 100644 components/history/index.html create mode 100644 components/ifttt.manything/index.html create mode 100644 components/ifttt/index.html create mode 100644 components/introduction/index.html create mode 100644 components/isy994/index.html create mode 100644 components/keyboard/index.html create mode 100644 components/light.blinksticklight/index.html create mode 100644 components/light.hue/index.html create mode 100644 components/light.hyperion/index.html create mode 100644 components/light.limitlessled/index.html create mode 100644 components/light.rfxtrx/index.html create mode 100644 components/light.tellstick/index.html create mode 100644 components/light.vera/index.html create mode 100644 components/light.wink/index.html create mode 100644 components/light/index.html create mode 100644 components/logbook/index.html create mode 100644 components/media_player.cast/index.html create mode 100644 components/media_player.denon/index.html create mode 100644 components/media_player.firetv/index.html create mode 100644 components/media_player.itunes/index.html create mode 100644 components/media_player.kodi/index.html create mode 100644 components/media_player.mpd/index.html create mode 100644 components/media_player.plex/index.html create mode 100644 components/media_player.sonos/index.html create mode 100644 components/media_player.squeezebox/index.html create mode 100644 components/media_player/index.html create mode 100644 components/modbus/index.html create mode 100644 components/mqtt/index.html create mode 100644 components/notify.file/index.html create mode 100644 components/notify.instapush/index.html create mode 100644 components/notify.nma/index.html create mode 100644 components/notify.pushbullet/index.html create mode 100644 components/notify.pushover/index.html create mode 100644 components/notify.slack/index.html create mode 100644 components/notify.smtp/index.html create mode 100644 components/notify.syslog/index.html create mode 100644 components/notify.telegram/index.html create mode 100644 components/notify.xmpp/index.html create mode 100644 components/notify/index.html create mode 100644 components/rfxtrx/index.html create mode 100644 components/scene/index.html create mode 100644 components/script/index.html create mode 100644 components/sensor.arduino/index.html create mode 100644 components/sensor.arest/index.html create mode 100644 components/sensor.bitcoin/index.html create mode 100644 components/sensor.command_sensor/index.html create mode 100644 components/sensor.cpuspeed/index.html create mode 100644 components/sensor.dht/index.html create mode 100644 components/sensor.efergy/index.html create mode 100644 components/sensor.forecast/index.html create mode 100644 components/sensor.glances/index.html create mode 100644 components/sensor.modbus/index.html create mode 100644 components/sensor.mqtt/index.html create mode 100644 components/sensor.mysensors/index.html create mode 100644 components/sensor.openweathermap/index.html create mode 100644 components/sensor.rest/index.html create mode 100644 components/sensor.rfxtrx/index.html create mode 100644 components/sensor.rpi_gpio/index.html create mode 100644 components/sensor.sabnzbd/index.html create mode 100644 components/sensor.swiss_public_transport/index.html create mode 100644 components/sensor.systemmonitor/index.html create mode 100644 components/sensor.tellstick/index.html create mode 100644 components/sensor.temper/index.html create mode 100644 components/sensor.time_date/index.html create mode 100644 components/sensor.transmission/index.html create mode 100644 components/sensor.vera/index.html create mode 100644 components/sensor.wink/index.html create mode 100644 components/sensor.worldclock/index.html create mode 100644 components/sensor/index.html create mode 100644 components/shell_command/index.html create mode 100644 components/simple_alarm/index.html create mode 100644 components/sun/index.html create mode 100644 components/switch.arduino/index.html create mode 100644 components/switch.arest/index.html create mode 100644 components/switch.command_switch/index.html create mode 100644 components/switch.edimax/index.html create mode 100644 components/switch.hikvision/index.html create mode 100644 components/switch.modbus/index.html create mode 100644 components/switch.mqtt/index.html create mode 100644 components/switch.rest/index.html create mode 100644 components/switch.rfxtrx/index.html create mode 100644 components/switch.rpi_gpio/index.html create mode 100644 components/switch.tellstick/index.html create mode 100644 components/switch.transmission/index.html create mode 100644 components/switch.vera/index.html create mode 100644 components/switch.wemo/index.html create mode 100644 components/switch.wink/index.html create mode 100644 components/switch/index.html create mode 100644 components/tellstick/index.html create mode 100644 components/thermostat.heat_control/index.html create mode 100644 components/thermostat.nest/index.html create mode 100644 components/thermostat.radiotherm/index.html rename cookbook/turn_on_light_for_10_minutes_when_motion_detected.html => components/thermostat/index.html (55%) create mode 100644 components/vera/index.html create mode 100644 components/verisure/index.html create mode 100644 components/wink/index.html create mode 100644 components/zone/index.html create mode 100644 components/zwave/index.html create mode 100644 cookbook/automation_for_rainy_days/index.html create mode 100644 cookbook/automation_sun/index.html create mode 100644 cookbook/basic_example_use_trigger_values/index.html delete mode 100644 cookbook/dim_lights_when_playing_media.html create mode 100644 cookbook/dim_lights_when_playing_media/index.html create mode 100644 cookbook/turn_on_light_for_10_minutes_when_motion_detected/index.html create mode 100644 developers/add_new_platform/index.html rename cookbook/basic_example_use_trigger_values.html => developers/api/index.html (58%) create mode 100644 developers/architecture/index.html create mode 100644 developers/creating_components/index.html create mode 100644 developers/credits/index.html create mode 100644 developers/frontend/index.html create mode 100644 developers/python_api/index.html create mode 100644 developers/rest_api/index.html create mode 100644 developers/website/index.html rename cookbook/automation_sun.html => getting-started/android/index.html (59%) create mode 100644 getting-started/automation/index.html create mode 100644 getting-started/autostart/index.html create mode 100644 getting-started/configuration/index.html create mode 100644 getting-started/devices/index.html create mode 100644 getting-started/presence-detection/index.html create mode 100644 getting-started/troubleshooting-configuration/index.html create mode 100644 getting-started/troubleshooting/index.html diff --git a/.jekyll-metadata b/.jekyll-metadata new file mode 100644 index 0000000000000000000000000000000000000000..beefda1ae32c2cef8eb53a4f3c8407a532a22b51 GIT binary patch literal 4 LcmZSKsAd2F0U`j1 literal 0 HcmV?d00001 diff --git a/atom.xml b/atom.xml index f3e5c58ee2..6c278ae91a 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2015-10-27T12:45:27-07:00 + 2015-10-29T00:08:34-07:00 https://home-assistant.io/ @@ -18,58 +18,47 @@ 2015-10-26T18:10:00-07:00 https://home-assistant.io/blog/2015/10/26/firetv-and-radiotherm-now-supported - After two weeks of hard work I’m proud to announce the release of Home Assistant v0.7.6. For this release the main -focus was bugs, test coverage and documentation. And we exceeded expectations on all three fronts. Bugs have been -squashed, test coverage increased to 85% and thanks to the hard work by -@fabaff and myself the component section on the website has gotten a -complete revamp.

+ After two weeks of hard work I’m proud to announce the release of Home Assistant v0.7.6. For this release the main focus was bugs, test coverage and documentation. And we exceeded expectations on all three fronts. Bugs have been squashed, test coverage increased to 85% and thanks to the hard work by @fabaff and myself the component section on the website has gotten a complete revamp.

Changes

-

- -

+

- -

Breaking changes

As part of this release we did some cleanup which introduced backwards incompatible changes:

-

Heat Control thermostat no longer includes scheduling features.
-This feature has been removed completely. Use the automation component -instead to control target temperature.

+

Heat Control thermostat no longer includes scheduling features.
+This feature has been removed completely. Use the automation component instead to control target temperature.

-

Config changed for calling a service from a script.
-execute_service: has been replaced with service:. See component page -for example. The old method will continue working for some time.

+

Config changed for calling a service from a script.
+execute_service: has been replaced with service:. See component page for example. The old method will continue working for some time.

-

Scenes can no longer be turned off.
-It is no longer possible to turn a scene off after it has been activated. The way it worked was unpredictable -and causes a lot of confusion.

+

Scenes can no longer be turned off.
+It is no longer possible to turn a scene off after it has been activated. The way it worked was unpredictable and causes a lot of confusion.

-

Downloader treats relative paths now relative to the config dir instead of the current working dir.
+

Downloader treats relative paths now relative to the config dir instead of the current working dir.
This makes more sense as most people run Home Assistant as a daemon

]]> @@ -79,379 +68,364 @@ This makes more sense as most people run Home Assistant as a daemon

2015-10-11T12:10:00-07:00 https://home-assistant.io/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt - I recently learned about the ESP8266, a $5 chip that includes WiFi and is Arduino compatible. This means -that all your DIY projects can now be done for a fraction of the price.

+ I recently learned about the ESP8266, a $5 chip that includes WiFi and is Arduino compatible. This means that all your DIY projects can now be done for a fraction of the price.

-

For this tutorial, I’ll walk through how to get going with ESP8266, get the temperature and humidity and -report it to MQTT where Home Asssistant can pick it up.

+

For this tutorial, I’ll walk through how to get going with ESP8266, get the temperature and humidity and report it to MQTT where Home Asssistant can pick it up.

-

- +

+ Picture of the final setup (+ 2 LED for decoration)

- - - -

- +

+ Home Assistant will keep track of historical values and allow you to integrate it into automation.

- - - -

Components

-

I’ve been using Adafruit for my shopping:

+

I’ve been using Adafruit for my shopping:

- -

Besides this, you will need the usual hardware prototype equipment: a breadboard, some wires, -soldering iron + wire, Serial USB cable.

+

Besides this, you will need the usual hardware prototype equipment: a breadboard, some wires, soldering iron + wire, Serial USB cable.

Connections

On your breadboard, make the following connections from your ESP8266 to the HDC1008:

- - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + +
ESP8266 HDC1008
GND GND
3V Vin
14 SCL
#2 SDA
ESP8266HDC1008
GNDGND
3VVin
14SCL
#2SDA
-

I picked #2 and 14 myself, you can configure them in the sketch.

Preparing your IDE

-

Follow these instructions on how -to install and prepare the Arduino IDE for ESP8266 development.

+

Follow these instructions on how to install and prepare the Arduino IDE for ESP8266 development.

-

After you’re done installing, open the Arduino IDE, in the menu click on sketch -> include library -> -manage libraries and install the following libraries:

+

After you’re done installing, open the Arduino IDE, in the menu click on sketch -> include library -> manage libraries and install the following libraries:

    -
  • PubSubClient by Nick ‘O Leary
    • -
  • Adafruit HDC1000
    • +
  • PubSubClient by Nick ‘O Leary
    • +
  • Adafruit HDC1000
-

Sketch

-

If you have followed the previous steps, you’re all set.

+

If you have followed the previous steps, you’re all set.

    -
  • Open Arduino IDE and create a new sketch (File -> New)
    • -
  • Copy and paste the below sketch to the Arduino IDE
    • -
  • Adjust the values line 6 - 14 to match your setup
    • -
  • Optional: If you want to connect to an MQTT server without a username or password, adjust line 63.
    • -
  • To have the ESP8266 accept our new sketch, we have to put it in upload mode. On the ESP8266 device -keep the GPIO0 button pressed while pressing the reset button. The red led will glow half bright to -indicate it is in upload mode.
    • -
  • Press the upload button in Arduino IDE
    • -
  • Open the serial monitor (Tools -> Serial Monitor) to see the output from your device
    • +
  • Open Arduino IDE and create a new sketch (File -> New)
    • +
  • Copy and paste the below sketch to the Arduino IDE
    • +
  • Adjust the values line 6 - 14 to match your setup
    • +
  • Optional: If you want to connect to an MQTT server without a username or password, adjust line 63.
    • +
  • To have the ESP8266 accept our new sketch, we have to put it in upload mode. On the ESP8266 device keep the GPIO0 button pressed while pressing the reset button. The red led will glow half bright to indicate it is in upload mode.
    • +
  • Press the upload button in Arduino IDE
    • +
  • Open the serial monitor (Tools -> Serial Monitor) to see the output from your device
+

This sketch will connect to your WiFi network and MQTT broker. It will read the temperature and humidity from the sensor every second. It will report it to the MQTT server if the difference is > 1 since last reported value. Reports to the MQTT broker are sent with retain set to True. This means that anyone connecting to the MQTT topic will automatically be notified of the last reported value.

-

This sketch will connect to your WiFi network and MQTT broker. It will read the temperature and humidity -from the sensor every second. It will report it to the MQTT server if the difference is > 1 since last -reported value. Reports to the MQTT broker are sent with retain set to True. This means that anyone -connecting to the MQTT topic will automatically be notified of the last reported value.

+
+ + +
1
+2
+3
+4
+5
+6
+7
+8
+9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
+32
+33
+34
+35
+36
+37
+38
+39
+40
+41
+42
+43
+44
+45
+46
+47
+48
+49
+50
+51
+52
+53
+54
+55
+56
+57
+58
+59
+60
+61
+62
+63
+64
+65
+66
+67
+68
+69
+70
+71
+72
+73
+74
+75
+76
+77
+78
+79
+80
+81
+82
+83
+84
+85
+86
+87
+88
+89
+90
+91
+92
+93
+94
+95
+96
+97
+98
+99
+100
+101
+102
+103
+104
+105
+106
+107
+108
+109
+
#include <ESP8266WiFi.h>
+#include <Wire.h>
+#include <PubSubClient.h>
+#include <Adafruit_HDC1000.h>
 
-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-18
-19
-20
-21
-22
-23
-24
-25
-26
-27
-28
-29
-30
-31
-32
-33
-34
-35
-36
-37
-38
-39
-40
-41
-42
-43
-44
-45
-46
-47
-48
-49
-50
-51
-52
-53
-54
-55
-56
-57
-58
-59
-60
-61
-62
-63
-64
-65
-66
-67
-68
-69
-70
-71
-72
-73
-74
-75
-76
-77
-78
-79
-80
-81
-82
-83
-84
-85
-86
-87
-88
-89
-90
-91
-92
-93
-94
-95
-96
-97
-98
-99
-100
-101
-102
-103
-104
-105
-106
-107
-108
-109
-
#include <ESP8266WiFi.h>
-#include <Wire.h>
-#include <PubSubClient.h>
-#include <Adafruit_HDC1000.h>
-
-#define wifi_ssid "YOUR WIFI SSID"
-#define wifi_password "WIFI PASSWORD"
-
-#define mqtt_server "YOUR_MQTT_SERVER_HOST"
-#define mqtt_user "your_username"
-#define mqtt_password "your_password"
-
-#define humidity_topic "sensor/humidity"
-#define temperature_topic "sensor/temperature"
-
-WiFiClient espClient;
-PubSubClient client(espClient);
-Adafruit_HDC1000 hdc = Adafruit_HDC1000();
-
-void setup() {
-  Serial.begin(115200);
-  setup_wifi();
-  client.setServer(mqtt_server, 1883);
-
-  // Set SDA and SDL ports
-  Wire.begin(2, 14);
-
-  // Start sensor
-  if (!hdc.begin()) {
-    Serial.println("Couldn't find sensor!");
-    while (1);
-  }}
-
-void setup_wifi() {
-  delay(10);
-  // We start by connecting to a WiFi network
-  Serial.println();
-  Serial.print("Connecting to ");
-  Serial.println(wifi_ssid);
-
-  WiFi.begin(wifi_ssid, wifi_password);
-
-  while (WiFi.status() != WL_CONNECTED) {
-    delay(500);
-    Serial.print(".");
-  }
-
-  Serial.println("");
-  Serial.println("WiFi connected");
-  Serial.println("IP address: ");
-  Serial.println(WiFi.localIP());
-}
-
-void reconnect() {
-  // Loop until we're reconnected
-  while (!client.connected()) {
-    Serial.print("Attempting MQTT connection...");
-    // Attempt to connect
-    // If you do not want to use a username and password, change next line to
-    // if (client.connect("ESP8266Client")) {
-    if (client.connect("ESP8266Client", mqtt_user, mqtt_password)) {
-      Serial.println("connected");
-    } else {
-      Serial.print("failed, rc=");
-      Serial.print(client.state());
-      Serial.println(" try again in 5 seconds");
-      // Wait 5 seconds before retrying
-      delay(5000);
-    }
-  }
-}
-
-bool checkBound(float newValue, float prevValue, float maxDiff) {
-  return newValue < prevValue - maxDiff || newValue > prevValue + maxDiff;
-}
-
-long lastMsg = 0;
-float temp = 0.0;
-float hum = 0.0;
-float diff = 1.0;
-
-void loop() {
-  if (!client.connected()) {
-    reconnect();
-  }
-  client.loop();
-
-  long now = millis();
-  if (now - lastMsg > 1000) {
-    lastMsg = now;
-
-    float newTemp = hdc.readTemperature();
-    float newHum = hdc.readHumidity();
-
-    if (checkBound(newTemp, temp, diff)) {
-      temp = newTemp;
-      Serial.print("New temperature:");
-      Serial.println(String(temp).c_str());
-      client.publish(temperature_topic, String(temp).c_str(), true);
-    }
-
-    if (checkBound(newHum, hum, diff)) {
-      hum = newHum;
-      Serial.print("New humidity:");
-      Serial.println(String(hum).c_str());
-      client.publish(humidity_topic, String(hum).c_str(), true);
-    }
-  }
-}
-

+#define wifi_ssid "YOUR WIFI SSID"
+#define wifi_password "WIFI PASSWORD"
 
+#define mqtt_server "YOUR_MQTT_SERVER_HOST"
+#define mqtt_user "your_username"
+#define mqtt_password "your_password"
+
+#define humidity_topic "sensor/humidity"
+#define temperature_topic "sensor/temperature"
+
+WiFiClient espClient;
+PubSubClient client(espClient);
+Adafruit_HDC1000 hdc = Adafruit_HDC1000();
+
+void setup() {
+  Serial.begin(115200);
+  setup_wifi();
+  client.setServer(mqtt_server, 1883);
+
+  // Set SDA and SDL ports
+  Wire.begin(2, 14);
+
+  // Start sensor
+  if (!hdc.begin()) {
+    Serial.println("Couldn't find sensor!");
+    while (1);
+  }}
+
+void setup_wifi() {
+  delay(10);
+  // We start by connecting to a WiFi network
+  Serial.println();
+  Serial.print("Connecting to ");
+  Serial.println(wifi_ssid);
+
+  WiFi.begin(wifi_ssid, wifi_password);
+
+  while (WiFi.status() != WL_CONNECTED) {
+    delay(500);
+    Serial.print(".");
+  }
+
+  Serial.println("");
+  Serial.println("WiFi connected");
+  Serial.println("IP address: ");
+  Serial.println(WiFi.localIP());
+}
+
+void reconnect() {
+  // Loop until we're reconnected
+  while (!client.connected()) {
+    Serial.print("Attempting MQTT connection...");
+    // Attempt to connect
+    // If you do not want to use a username and password, change next line to
+    // if (client.connect("ESP8266Client")) {
+    if (client.connect("ESP8266Client", mqtt_user, mqtt_password)) {
+      Serial.println("connected");
+    } else {
+      Serial.print("failed, rc=");
+      Serial.print(client.state());
+      Serial.println(" try again in 5 seconds");
+      // Wait 5 seconds before retrying
+      delay(5000);
+    }
+  }
+}
+
+bool checkBound(float newValue, float prevValue, float maxDiff) {
+  return newValue < prevValue - maxDiff || newValue > prevValue + maxDiff;
+}
+
+long lastMsg = 0;
+float temp = 0.0;
+float hum = 0.0;
+float diff = 1.0;
+
+void loop() {
+  if (!client.connected()) {
+    reconnect();
+  }
+  client.loop();
+
+  long now = millis();
+  if (now - lastMsg > 1000) {
+    lastMsg = now;
+
+    float newTemp = hdc.readTemperature();
+    float newHum = hdc.readHumidity();
+
+    if (checkBound(newTemp, temp, diff)) {
+      temp = newTemp;
+      Serial.print("New temperature:");
+      Serial.println(String(temp).c_str());
+      client.publish(temperature_topic, String(temp).c_str(), true);
+    }
+
+    if (checkBound(newHum, hum, diff)) {
+      hum = newHum;
+      Serial.print("New humidity:");
+      Serial.println(String(hum).c_str());
+      client.publish(humidity_topic, String(hum).c_str(), true);
+    }
+  }
+}
+
+

Configuring Home Assistant

-

The last step is to integrate the sensor values into Home Assistant. This can be done by setting up -Home Assistant to connect to the MQTT broker and subscribe to the sensor topics.

+

The last step is to integrate the sensor values into Home Assistant. This can be done by setting up Home Assistant to connect to the MQTT broker and subscribe to the sensor topics.

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-18
-
mqtt:
-  broker: YOUR_MQTT_SERVER_HOST
-  username: your_username
-  password: your_password
-
-sensor:
-  platform: mqtt
-  name: "Temperature"
-  state_topic: "sensor/temperature"
-  qos: 0
-  unit_of_measurement: "ºC"
-
-sensor 2:
-  platform: mqtt
-  name: "Humidity"
-  state_topic: "sensor/humidity"
-  qos: 0
-  unit_of_measurement: "%"
-
+
+ + +
1
+2
+3
+4
+5
+6
+7
+8
+9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+
mqtt:
+  broker: YOUR_MQTT_SERVER_HOST
+  username: your_username
+  password: your_password
 
+sensor:
+  platform: mqtt
+  name: "Temperature"
+  state_topic: "sensor/temperature"
+  qos: 0
+  unit_of_measurement: "ºC"
+
+sensor 2:
+  platform: mqtt
+  name: "Humidity"
+  state_topic: "sensor/humidity"
+  qos: 0
+  unit_of_measurement: "%"
+
+
]]> @@ -463,28 +437,23 @@ Home Assistant to connect to the MQTT broker and subscribe to the sensor topics. We discovered two issues annoying enough to warrent the release of 0.7.5:

    -
  • Home Assistant package did not include the CloudMQTT certificate.
    • -
  • A bug in the core caused issues when some platforms are loaded twice.
    • +
  • Home Assistant package did not include the CloudMQTT certificate.
    • +
  • A bug in the core caused issues when some platforms are loaded twice.
-

This release also includes some new platforms (because they keep coming!):

-

- -

+

- -

Also, the media player was extended by @maddox to support the play media command. -This has been implemented for the iTunes platform.

+

Also, the media player was extended by @maddox to support the play media command. This has been implemented for the iTunes platform.

]]> @@ -493,43 +462,37 @@ This has been implemented for the 2015-10-05T21:49:00-07:00 https://home-assistant.io/blog/2015/10/05/home-assistant-goes-geo-with-owntracks - A few weeks have past and it is time again for another release: version 0.7.4. This time we’re very -glad to be able to introduce brand new integration with OwnTracks to allow tracking of people on a map. -The geo support consists of three different parts:

+ A few weeks have past and it is time again for another release: version 0.7.4. This time we’re very glad to be able to introduce brand new integration with OwnTracks to allow tracking of people on a map. The geo support consists of three different parts:

 +

We have added a new getting started section to get up and running.

-

We have added a new getting started section to get up and running.

- -

- +

+ Map in Home Assistant showing two people and three zones (home, school, work)

+

Ofcourse more things happened in the last three weeks. I’m moving away from my usual long post to a short summary of highlights:

-

Ofcourse more things happened in the last three weeks. I’m moving away from my usual long post to a -short summary of highlights:

- -

- +

+

- ]]> @@ -538,97 +501,61 @@ short summary of highlights:

2015-09-19T21:47:00-07:00 https://home-assistant.io/blog/2015/09/19/alarm-sonos-and-itunes-support - It’s like someone opened a can of rock solid developers and emptied it above our -chat channel because it exploded with -great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.

+ It’s like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.

See GitHub for more detailed release notes.

Migration note: the scheduler component has been removed in favor of the automation component.

-

Sonos
- -Sonos support has been added by @rhooper and @SEJeff. Home Assistant is now able to automatically -detect Sonos devices in your network and set them up for you. It will allow you to control music -playing on your Sonos and change the volume.

- -

iTunes and airplay speakers
- -@maddox has contributed support for controlling iTunes and airplay speakers. For this to work you will -have to run itunes-api on your Mac as middleware.

- -
1
-2
-3
-4
-5
-6
-
# Example configuration.yaml entry
-media_player:
-  platform: itunes
-  name: iTunes
-  host: http://192.168.1.50
-  port: 8181
-
- +

Sonos
+ Sonos support has been added by @rhooper and @SEJeff. Home Assistant is now able to automatically detect Sonos devices in your network and set them up for you. It will allow you to control music playing on your Sonos and change the volume.

+

iTunes and airplay speakers
+ @maddox has contributed support for controlling iTunes and airplay speakers. For this to work you will have to run itunes-api on your Mac as middleware.

+
+ 
# Example configuration.yaml entry
+media_player:
+  platform: itunes
+  name: iTunes
+  host: http://192.168.1.50
+  port: 8181
+
+
+
+

Automation
+Automation has gotten a lot of love. It now supports conditions, multiple triggers and new types of triggers. The best to get started with it is to head over to the new getting started with automation page.

-

Automation
-Automation has gotten a lot of love. It now supports conditions, multiple triggers and new types of -triggers. The best to get started with it is to head over to the new -getting started with automation page.

+
+ 
# Example of entry in configuration.yaml
+automation:
+  alias: Light on in the evening
+  trigger:
+    - platform: sun
+      event: sunset
+      offset: "-01:00:00"
+    - platform: state
+      entity_id: group.all_devices
+      state: home
+  condition:
+    - platform: state
+      entity_id: group.all_devices
+      state: home
+    - platform: time
+      after: "16:00:00"
+      before: "23:00:00"
+  action:
+    service: homeassistant.turn_on
+    entity_id: group.living_room
+
+
+
-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-18
-19
-20
-
# Example of entry in configuration.yaml
-automation:
-  alias: Light on in the evening
-  trigger:
-    - platform: sun
-      event: sunset
-      offset: "-01:00:00"
-    - platform: state
-      entity_id: group.all_devices
-      state: home
-  condition:
-    - platform: state
-      entity_id: group.all_devices
-      state: home
-    - platform: time
-      after: "16:00:00"
-      before: "23:00:00"
-  action:
-    service: homeassistant.turn_on
-    entity_id: group.living_room
-
- - -

Verisure Alarms
- -We now support arming and disarming your verisure alarm from within Home Assistant thanks to added -support by @persandstrom.

+

Verisure Alarms
+ We now support arming and disarming your verisure alarm from within Home Assistant thanks to added support by @persandstrom.

]]> @@ -637,88 +564,81 @@ support by @persandstrom.

2015-09-18T02:00:00-07:00 https://home-assistant.io/blog/2015/09/18/monitoring-with-glances-and-home-assistant - -Inspried by a feature requests I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the systemmonitor sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.

+
+Inspried by a feature requests I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the systemmonitor sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.

-

The basic problem is to get the data from the remote host. Starting with psutil that is used by the systemmonitor sensor, a possible solution is only a click away and named Glances. Glances has a nice curses-based interface and a RESTful API.

-

The Glances sensor sensor uses that API to get all needed data.

+

The Glances sensor sensor uses that API to get all needed data.

-

In this post a default Fedora 22 Workstation installation is used on the host that should be monitored. In fact, it doesn’t matter if the system is the local one or a remote one as long as Glances is available. With some adjustments it should work on your own systems too. The difference will be the package and the firewall management tools.

+

In this post a default Fedora 22 Workstation installation is used on the host that should be monitored. In fact, it doesn’t matter if the system is the local one or a remote one as long as Glances is available. With some adjustments it should work on your own systems too. The difference will be the package and the firewall management tools.

First some extra packages are needed beside Glances, especially the bottle webserver. I guess that Glances is available for your distribution as well. Otherwise follow those instructions.

-
1
-
sudo dnf -y install glances python-bottle
+
+ 
$ sudo dnf -y install glances python-bottle
+
+
+
+

On Fedora the Firewall settings are strict. Let’s open port 61208 to allow other hosts to connect to that port. This is not needed if you just want to observe your local machine.

-

On Fedora the Firewall settings are strict. Let’s open port 61208 to allow other hosts to connect to that port. This is not needed if you just want to observe your local machine.

- -
1
-2
-
sudo firewall-cmd --permanent --add-port=61208/tcp
-sudo firewall-cmd --reload
-
- +
+ 
$ sudo firewall-cmd --permanent --add-port=61208/tcp
+$ sudo firewall-cmd --reload
+
+
+

Launch glances and keep an eye on the output.

-
1
-2
-
glances -w
-Glances web server started on http://0.0.0.0:61208/
-
+
+ 
$ glances -w
+Glances web server started on http://0.0.0.0:61208/
+
+
+
+

Now browse to http://IP_ADRRESS:61208/. You should see the webified view of Glances.

-

Now browse to http://IP_ADRRESS:61208/. You should see the webified view of Glances.

- -

- +

+ Glances web interface

+

Another check is to access the API located at http://IP_ADRRESS:61208/api/2/mem/used and to confirm that a detail about your memory usage is provided as a JSON response. If so, you are good to proceed.

-

Another check is to access the API located at http://IP_ADRRESS:61208/api/2/mem/used and to confirm that a detail about your memory usage is provided as a JSON response. If so, you are good to proceed.

+
+ 
$ curl -X GET http://IP_ADDRESS:61208/api/2/mem/used
+{"used": 203943936}
+
+
+
-
1
-2
-
curl -X GET http://IP_ADDRESS:61208/api/2/mem/used
-{"used": 203943936}
-
- - -

Add the glances sensor entry to your configuration.yaml file and restart Home Assistant then.

- -
1
-2
-3
-4
-5
-6
-7
-8
-
# Example configuration.yaml entry
-  - platform: glances
-    name: NAS
-    host: IP_ADDRESS
-    resources:
-      - 'disk_use_percent'
-      - 'disk_use'
-      - 'disk_free'
-
+

Add the glances sensor entry to your configuration.yaml file and restart Home Assistant then.

+
+ 
# Example configuration.yaml entry
+  - platform: glances
+    name: NAS
+    host: IP_ADDRESS
+    resources:
+      - 'disk_use_percent'
+      - 'disk_use'
+      - 'disk_free'
+
+
+

If there are no error in the log file then you should see your new sensors.

-

- +

+ The Glances sensors

-

Glances has a couple of optional dependencies which are extenting the range of provided information. This means that it would be possible to get details about the RAID system, HDD temperature, IP addresses, sensors, etc., please create a Pull request with your additions or a Feature request if you want see more details in your Home Assistant frontend.

]]> @@ -728,207 +648,179 @@ Inspried by a fea 2015-09-13T09:28:00-07:00 https://home-assistant.io/blog/2015/09/13/home-assistant-meets-ifttt - Today we announce the release of Home Assistant v0.7.2 which includes brand new support by -@sfam to integrate with IFTTT. IFTTT stands for If This, Then That and is a -webservice that integrates with almost every possible webservice out there. Adding Home -Assistant to this mix means Home Assistant can connect with all via IFTTT.

+ Today we announce the release of Home Assistant v0.7.2 which includes brand new support by @sfam to integrate with IFTTT. IFTTT stands for If This, Then That and is a webservice that integrates with almost every possible webservice out there. Adding Home Assistant to this mix means Home Assistant can connect with all via IFTTT.

-

It is now possible to disable your irregation system if it is going to be cloudy tomorrow or tweet -if your smoke alarm goes off.

+

It is now possible to disable your irregation system if it is going to be cloudy tomorrow or tweet if your smoke alarm goes off.

-

- +

+

- -

Head over to the setup instructions to get started with IFTTT. Click the -read more button for some example recipes.

+

Head over to the setup instructions to get started with IFTTT. Click the read more button for some example recipes.

+

In each of the following examples, make sure to replace the XXX in the url with your correct host address and api password.

-

In each of the following examples, make sure to replace the XXX in the url with your correct -host address and api password.

+

Turn off irregation system when not needed

-

Turn off irregation system when not needed

- -

- +

+

-

Maker channel setup:

- - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + +
Field Value
URL http://xxx.xxx.xxx.xxx:8123/api/services/switch/turn_off?api_password=xxxxxxxx
METHOD POST
CONTENT TYPE application/json
BODY { “entity_id”: “switch.irrigation” }
FieldValue
URLhttp://xxx.xxx.xxx.xxx:8123/api/services/switch/turn_off?api_password=xxxxxxxx
METHODPOST
CONTENT TYPEapplication/json
BODY{ “entity_id”: “switch.irrigation” }
+

Tweet when important events happen

-

Tweet when important events happen

- -

- +

+

+

This will tweet a message when an MQTT message is received that the smoke alarm has been triggered. Setup Maker channel with event name HA_FIRE_ALARM and Twitter channel to tweet the message in value1.

-

This will tweet a message when an MQTT message is received that the smoke alarm has been triggered. -Setup Maker channel with event name HA_FIRE_ALARM and Twitter channel to tweet the message in -value1.

+
+ 
# Configuration.yaml entry
+automation:
+- alias: Post a tweet when fire alarm is triggered
+  trigger:
+    platform: mqtt
+    mqtt_topic: home/alarm/fire
+    mqtt_payload: 'on'
 
-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-
# Configuration.yaml entry
-automation:
-- alias: Post a tweet when fire alarm is triggered
-  trigger:
-    platform: mqtt
-    mqtt_topic: home/alarm/fire
-    mqtt_payload: 'on'
-
-  action:
-    service: ifttt.trigger
-    data: {"event":"HA_FIRE_ALARM", "value1":"The fire alarm just triggered!"}
-

+  action:
+    service: ifttt.trigger
+    data: {"event":"HA_FIRE_ALARM", "value1":"The fire alarm just triggered!"}
+
+
+
+

Turn on lights when I get home

-

Turn on lights when I get home

- -

- +

+

-

Maker channel setup:

- - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + +
Field Value
URL http://xxx.xxx.xxx.xxx:8123/api/services/light/turn_on?api_password=xxxxxxxx
METHOD POST
CONTENT TYPE application/json
BODY { “entity_id”: “light.kitchen” }
FieldValue
URLhttp://xxx.xxx.xxx.xxx:8123/api/services/light/turn_on?api_password=xxxxxxxx
METHODPOST
CONTENT TYPEapplication/json
BODY{ “entity_id”: “light.kitchen” }
+

Flash lights when a new PR comes in for Home Assistant

-

Flash lights when a new PR comes in for Home Assistant

- -

- +

+

-

Maker channel setup:

- - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + +
Field Value
URL http://xxx.xxx.xxx.xxx:8123/api/services/light/turn_on?api_password=xxxxxxxx
METHOD POST
CONTENT TYPE application/json
BODY { “entity_id”: “group.all_lights”, “flash”:“yes” }
FieldValue
URLhttp://xxx.xxx.xxx.xxx:8123/api/services/light/turn_on?api_password=xxxxxxxx
METHODPOST
CONTENT TYPEapplication/json
BODY{ “entity_id”: “group.all_lights”, “flash”:”yes” }
+

Fire events when pressing the DO button

-

Fire events when pressing the DO button

- -

- +

+

-

Maker channel setup:

- - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + +
Field Value
URL http://xxx.xxx.xxx.xxx:8123/api/events/do_button_pressed?api_password=xxxxxxxx
METHOD POST
CONTENT TYPE application/json
FieldValue
URLhttp://xxx.xxx.xxx.xxx:8123/api/events/do_button_pressed?api_password=xxxxxxxx
METHODPOST
CONTENT TYPEapplication/json
- ]]> @@ -937,8 +829,8 @@ Setup Maker channel with event name HA_FIRE_ALARM and Twitter chann 2015-09-11T02:19:38-07:00 https://home-assistant.io/blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant - -The MQTT support was added to Home Assistant recently. The MQTT component will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn’t care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn’t matter if the data is coming from a human, a web service, or a device.

+ MQTT support was added to Home Assistant recently. The MQTT component will enable you to do all sort of things. Most likely you will use it to communicate with your devices. But Home Assistant doesn’t care where the data is coming from or is limited to real hardware as long as there is MQTT support. This means that it doesn’t matter if the data is coming from a human, a web service, or a device.

A great example is shown in a Laundry Automation post in this blog.

@@ -946,299 +838,310 @@ The MQTT support was added to H +

Manual usage

-

Manual usage

+

The simplest but not the coolest way as a human to interact with a Home Assistant sensor is launching a command manually. Let’s create a “Mood” sensor. For simplicity Home Assistant and the MQTT broker are both running on the same host. The needed configuration snipplets to add to the configuration.yaml file consists of two parts: one for the broker and one for the sensor.

-

The simplest but not the coolest way as a human to interact with a Home Assistant sensor is launching a command manually. Let’s create a “Mood” sensor. For simplicity Home Assistant and the MQTT broker are both running on the same host. The needed configuration snipplets to add to the configuration.yaml file consists of two parts: one for the broker and one for the sensor.

+
+ + +
1
+2
+3
+4
+5
+6
+7
+
mqtt:
+  broker: 127.0.0.1
 
-
1
-2
-3
-4
-5
-6
-7
-
mqtt:
-  broker: 127.0.0.1
-
-sensor:
-  - platform: mqtt
-    name: "Fabian's Mood"
-    state_topic: "home-assistant/fabian/mood"
-

+sensor:
+  - platform: mqtt
+    name: "Fabian's Mood"
+    state_topic: "home-assistant/fabian/mood"
+
+
- -

After a restart of Home Assistant the “Mood” sensor will show up in the frontend. For more details about the configuration of MQTT itself and the sensor, please refer to the MQTT component or the MQTT sensor documentation.

+

After a restart of Home Assistant the “Mood” sensor will show up in the frontend. For more details about the configuration of MQTT itself and the sensor, please refer to the MQTT component or the MQTT sensor documentation.

Now we can set the mood. The commandline tool (mosquitto_pub) which is shipped with mosquitto is used to send an MQTT message.

-
1
-
mosquitto_pub  -h 127.0.0.1 -t "home-assistant/fabian/mood" -m "bad"
-
+
+ + +
1
+
$ mosquitto_pub  -h 127.0.0.1 -t "home-assistant/fabian/mood" -m "bad"
+
+
- - - -

- +

+ The Mood sensor

+

This is a really bad example. Don’t do this in the real world because you won’t be able to create diagrams of historical data. Better use a numerical value.

-

This is a really bad example. Don’t do this in the real world because you won’t be able to create diagrams of historical data. Better use a numerical value.

- -

Python MQTT bindings

+

Python MQTT bindings

The last section was pretty boring, I know. Nobody wants to send MQTT messages by hand if there is a computer on the desk. If you are playing the lottery this section is for you. If not, read it anyway because the lottery is just an example :-).

This example is using the Paho MQTT Python binding because those binding should be available on the host where Home Assistant is running. If you want to use this example on another machine, please make sure that the bindings are installed (pip3 install paho-mqtt).

-

The first step is to add an additional MQTT sensor to the configuration.yaml file. The sensor will be called “Lottery” and the unit of measurement will be “No.”.

+

The first step is to add an additional MQTT sensor to the configuration.yaml file. The sensor will be called “Lottery” and the unit of measurement will be “No.”.

-
1
-2
-3
-4
-
  - platform: mqtt
-    name: "Lottery"
-    state_topic: "home-assistant/lottery/number"
-    unit_of_measurement: "No."
-
+
+ + +
1
+2
+3
+4
+
  - platform: mqtt
+    name: "Lottery"
+    state_topic: "home-assistant/lottery/number"
+    unit_of_measurement: "No."
+
+
- -

Don’t forget to restart Home Assistant to make the configuration active.

+

Don’t forget to restart Home Assistant to make the configuration active.

To play, we need numbers from 1 to 49 which can be marked on the ticket. Those numbers should be random and displayed in the Home Assistant frontend. The Python script below is another simple example on how to send MQTT messages from the commandline; this time in a loop. For further information and examples please check the Paho MQTT documentation.

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-18
-19
-20
-21
-22
-
#!/usr/bin/python3
-#
-import time
-import random
-import paho.mqtt.client as mqtt
-import paho.mqtt.publish as publish
-
-broker = '127.0.0.1'
-state_topic = 'home-assistant/lottery/number'
-delay = 5
-
-# Send a single message to set the mood
-publish.single('home-assistant/fabian/mood', 'good', hostname=broker)
-
-# Send messages in a loop
-client = mqtt.Client("ha-client")
-client.connect(broker)
-client.loop_start()
-
-while True:
-    client.publish(state_topic, random.randrange(0, 50, 1))
-    time.sleep(delay)
-
+
+ + +
1
+2
+3
+4
+5
+6
+7
+8
+9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+
#!/usr/bin/python3
+#
+import time
+import random
+import paho.mqtt.client as mqtt
+import paho.mqtt.publish as publish
 
+broker = '127.0.0.1'
+state_topic = 'home-assistant/lottery/number'
+delay = 5
+
+# Send a single message to set the mood
+publish.single('home-assistant/fabian/mood', 'good', hostname=broker)
+
+# Send messages in a loop
+client = mqtt.Client("ha-client")
+client.connect(broker)
+client.loop_start()
+
+while True:
+    client.publish(state_topic, random.randrange(0, 50, 1))
+    time.sleep(delay)
+
+

Every 5 seconds a message with a new number is sent to the broker and picked up by Home Assistant. By the way, my mood is much better now.

-

- +

+ The Lottery sensor

+

With only a few lines of Python and an MQTT broker you can create your own “smartdevice” or send information to Home Assistant which you haven’t think of. Of course this is not limited to Python. If there is an MQTT library available, the device can be used with Home Assistant now.

-

With only a few lines of Python and an MQTT broker you can create your own “smartdevice” or send information to Home Assistant which you haven’t think of. Of course this is not limited to Python. If there is an MQTT library available, the device can be used with Home Assistant now.

- -

Arduino

+

Arduino

To get started with real hardware that is capable to send MQTT messages, the Arduino platform is an inexpensive way to do it. In this section an Arduino UNO with an Ethernet shield and a photo resistor is used. The photo resistor is connected to analog pin 0 (A0) and has an output from 0 to 1024.

-

- +

+ The Arduino UNO with Ethernet shield and photo resistor

-

The MQTT client for the Arduino needs to be available in your Arduino IDE. Below you will find a sketch which could act as a starting point. Please modify the IP addresses, the MAC address, and the pin as needed and upload the sketch to your Arduino.

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-18
-19
-20
-21
-22
-23
-24
-25
-26
-27
-28
-29
-30
-31
-32
-33
-34
-35
-36
-37
-38
-39
-40
-41
-42
-43
-44
-45
-46
-47
-48
-49
-50
-51
-52
-53
-54
-55
-56
-57
-58
-59
-60
-61
-62
-63
-64
-65
-66
-67
-68
-
/*
-  This sketch is based on the basic MQTT example by
-  http://knolleary.github.io/pubsubclient/
-*/
-
-#include <SPI.h>
-#include <Ethernet.h>
-#include <PubSubClient.h>
-
-#define DEBUG 1 // Debug output to serial console
-
-// Device settings
-IPAddress deviceIp(192, 168, 0, 43);
-byte deviceMac[] = { 0xAB, 0xCD, 0xFE, 0xFE, 0xFE, 0xFE };
-char* deviceId  = "sensor01"; // Name of the sensor
-char* stateTopic = "home-assistant/sensor01/brightness"; // MQTT topic where values are published
-int sensorPin = A0; // Pin to which the sensor is connected to
-char buf[4]; // Buffer to store the sensor value
-int updateInterval = 1000; // Interval in miliseconds
-
-// MQTT server settings
-IPAddress mqttServer(192, 168, 0, 12);
-int mqttPort = 1883;
-
-EthernetClient ethClient;
-PubSubClient client(ethClient);
-
-void reconnect() {
-  while (!client.connected()) {
-#if DEBUG
-    Serial.print("Attempting MQTT connection...");
-#endif
-    if (client.connect(deviceId)) {
-#if DEBUG
-      Serial.println("connected");
-#endif
-    } else {
-#if DEBUG
-      Serial.print("failed, rc=");
-      Serial.print(client.state());
-      Serial.println(" try again in 5 seconds");
-#endif
-      delay(5000);
-    }
-  }
-}
-
-void setup() {
-  Serial.begin(57600);
-  client.setServer(mqttServer, mqttPort);
-  Ethernet.begin(deviceMac, deviceIp);
-  delay(1500);
-}
-
-void loop() {
-  if (!client.connected()) {
-    reconnect();
-  }
-  client.loop();
-
-  int sensorValue = analogRead(sensorPin);
-#if DEBUG
-  Serial.print("Sensor value: ");
-  Serial.println(sensorValue);
-#endif
-  client.publish(stateTopic, itoa(sensorValue, buf, 10));
-  delay(updateInterval);
-}
-
+
+ + +
1
+2
+3
+4
+5
+6
+7
+8
+9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
+32
+33
+34
+35
+36
+37
+38
+39
+40
+41
+42
+43
+44
+45
+46
+47
+48
+49
+50
+51
+52
+53
+54
+55
+56
+57
+58
+59
+60
+61
+62
+63
+64
+65
+66
+67
+68
+
/*
+  This sketch is based on the basic MQTT example by
+  http://knolleary.github.io/pubsubclient/
+*/
 
+#include <SPI.h>
+#include <Ethernet.h>
+#include <PubSubClient.h>
+
+#define DEBUG 1 // Debug output to serial console
+
+// Device settings
+IPAddress deviceIp(192, 168, 0, 43);
+byte deviceMac[] = { 0xAB, 0xCD, 0xFE, 0xFE, 0xFE, 0xFE };
+char* deviceId  = "sensor01"; // Name of the sensor
+char* stateTopic = "home-assistant/sensor01/brightness"; // MQTT topic where values are published
+int sensorPin = A0; // Pin to which the sensor is connected to
+char buf[4]; // Buffer to store the sensor value
+int updateInterval = 1000; // Interval in miliseconds
+
+// MQTT server settings
+IPAddress mqttServer(192, 168, 0, 12);
+int mqttPort = 1883;
+
+EthernetClient ethClient;
+PubSubClient client(ethClient);
+
+void reconnect() {
+  while (!client.connected()) {
+#if DEBUG
+    Serial.print("Attempting MQTT connection...");
+#endif
+    if (client.connect(deviceId)) {
+#if DEBUG
+      Serial.println("connected");
+#endif
+    } else {
+#if DEBUG
+      Serial.print("failed, rc=");
+      Serial.print(client.state());
+      Serial.println(" try again in 5 seconds");
+#endif
+      delay(5000);
+    }
+  }
+}
+
+void setup() {
+  Serial.begin(57600);
+  client.setServer(mqttServer, mqttPort);
+  Ethernet.begin(deviceMac, deviceIp);
+  delay(1500);
+}
+
+void loop() {
+  if (!client.connected()) {
+    reconnect();
+  }
+  client.loop();
+
+  int sensorValue = analogRead(sensorPin);
+#if DEBUG
+  Serial.print("Sensor value: ");
+  Serial.println(sensorValue);
+#endif
+  client.publish(stateTopic, itoa(sensorValue, buf, 10));
+  delay(updateInterval);
+}
+
+

The Arduino will send the value of the sensor every second. To use the data in Home Assistant, add an additional MQTT sensor to the configuration.yaml file.

-
1
-2
-3
-4
-
  - platform: mqtt
-    name: "Brightness"
-    state_topic: "home-assistant/sensor01/brightness"
-    unit_of_measurement: "cd"
-
- +
+ + +
1
+2
+3
+4
+
  - platform: mqtt
+    name: "Brightness"
+    state_topic: "home-assistant/sensor01/brightness"
+    unit_of_measurement: "cd"
+
+

After a restart of Home Assistant the values of your Arduino will be available.

-

- +

+ The Brightness sensor

-

I hope that this post could give you some ideas about the usage Home Assistant and MQTT. If you are working on a cool project that includes Home Assistant, please let us now.

]]> @@ -1248,170 +1151,119 @@ The MQTT support was added to H 2015-08-31T14:12:00-07:00 https://home-assistant.io/blog/2015/08/31/version-7-revamped-ui-and-improved-distribution - As Home Assistant is gaining more and more users we started to feel the pain from not having a -proper release mechanism. We had no version numbering and required users to checkout the source -using Git to get started. On top of that, as the number of devices that we support keeps raising, so -did the number of dependencies that are used. That’s why we decided to change the way we roll. From -now on:

+ As Home Assistant is gaining more and more users we started to feel the pain from not having a proper release mechanism. We had no version numbering and required users to checkout the source using Git to get started. On top of that, as the number of devices that we support keeps raising, so did the number of dependencies that are used. That’s why we decided to change the way we roll. From now on:

    -
  • Each release will have a version number, starting with version 0.7. This was chosen because it -shows that we have been around for some time but are not considering ourselves to be fully -stable.
    • -
  • Each release will be pushed to PyPi. This will be the only supported method of distribution.
    • -
  • Home Assistant is available after installation as a command-line utility hass.
    • -
  • The default configuration location has been moved from config in the current working directory -to ~/.homeassistant (%APPDATA%/.homeassistant on Windows).
    • -
  • Requirements for components and platforms are no longer installed into the current Python -environment (being virtual or not) but will be installed in <config-dir>/lib.
    • +
  • Each release will have a version number, starting with version 0.7. This was chosen because it shows that we have been around for some time but are not considering ourselves to be fully stable.
    • +
  • Each release will be pushed to PyPi. This will be the only supported method of distribution.
    • +
  • Home Assistant is available after installation as a command-line utility hass.
    • +
  • The default configuration location has been moved from config in the current working directory to ~/.homeassistant (%APPDATA%/.homeassistant on Windows).
    • +
  • Requirements for components and platforms are no longer installed into the current Python environment (being virtual or not) but will be installed in <config-dir>/lib.
+

A huge shout out to Ryan Kraus for making this all possible. Please make sure you read the full blog post for details on how to migrate your existing setup.

-

A huge shout out to Ryan Kraus for making this all possible. Please -make sure you read the full blog post for details on how to migrate your existing setup.

+

And while Ryan was fixing distribution, I have been hard at work in giving Home Assistant a face lift. We already looked pretty good but lacked proper form of organization for users with many devices. The new UI moves away from a card per entity and has cards per group and domain instead. The demo has been updated so give it a spin.

-

And while Ryan was fixing distribution, I have been hard at work in giving Home Assistant a face -lift. We already looked pretty good but lacked proper form of organization for users with many -devices. The new UI moves away from a card per entity and has cards per group and domain instead. -The demo has been updated so give it a spin.

- -

- - +

+ + Screenshots of the new UI

- - - +

Migration to version 0.7

-

Migration to version 0.7

- -

For this example, let’s say we have an old Home Assistant installation in -/home/paulus/home-assistant.

+

For this example, let’s say we have an old Home Assistant installation in /home/paulus/home-assistant.

If you want to migrate your existing configuration to be used as the default configuration:

-
1
-
cp -r /home/paulus/home-assistant ~/.homeassistant
-
+
+ 
$ cp -r /home/paulus/home-assistant ~/.homeassistant
+
+
+
+

It If you want to have the configuration in a different location, for example /home/paulus/home-assistant-config, you will have to point Home Assistant at this configuration folder when launching:

-

It If you want to have the configuration in a different location, for example -/home/paulus/home-assistant-config, you will have to point Home Assistant at this configuration -folder when launching:

+
+ 
$ hass --config /home/paulus/home-assistant-config
+
+
+
-
1
-
hass --config /home/paulus/home-assistant-config
-
- - -

New platforms

+

New platforms

And last, but not least: new platforms!

-

MQTT Sensors and Switches
- -@sfam has blessed us with two more MQTT platforms to extend our -integration with MQTTT: sensor and switch. Both platforms require the -MQTT component to be connected to a broker.

+

MQTT Sensors and Switches
+ @sfam has blessed us with two more MQTT platforms to extend our integration with MQTTT: sensor and switch. Both platforms require the MQTT component to be connected to a broker.

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-
# Example configuration.yml entr
-sensor:
-  platform: mqtt
-  name: "MQTT Sensor"
-  state_topic: "home/bedroom/temperature"
-  unit_of_measurement: "ºC"
-
-switch:
-  platform: mqtt
-  name: "Bedroom Switch"
-  state_topic: "home/bedroom/switch1"
-  command_topic: "home/bedroom/switch1/set"
-  payload_on: "ON"
-  payload_off: "OFF"
-  optimistic: false
-
+
+ 
# Example configuration.yml entr
+sensor:
+  platform: mqtt
+  name: "MQTT Sensor"
+  state_topic: "home/bedroom/temperature"
+  unit_of_measurement: "ºC"
 
+switch:
+  platform: mqtt
+  name: "Bedroom Switch"
+  state_topic: "home/bedroom/switch1"
+  command_topic: "home/bedroom/switch1/set"
+  payload_on: "ON"
+  payload_off: "OFF"
+  optimistic: false
+
+
+
-

Actiontec MI424WR Verizon FIOS Wireless router
- -Nolan has contributed support for Actiontec wireless routers.

+

Actiontec MI424WR Verizon FIOS Wireless router
+ Nolan has contributed support for Actiontec wireless routers.

-
1
-2
-3
-4
-5
-6
-
# Example configuration.yaml entry
-device_tracker:
-  platform: actiontec
-  host: YOUR_ROUTER_IP
-  username: YOUR_ADMIN_USERNAME
-  password: YOUR_ADMIN_PASSWORD
-
+
+ 
# Example configuration.yaml entry
+device_tracker:
+  platform: actiontec
+  host: YOUR_ROUTER_IP
+  username: YOUR_ADMIN_USERNAME
+  password: YOUR_ADMIN_PASSWORD
+
+
+
+

DHT temperature and humidty sensors
+@MakeMeASandwich has contributed support for DHT temperature and humidity sensors. It allows you to get the current temperature and humidity from a DHT11, DHT22, or AM2302 device.

-

DHT temperature and humidty sensors
-@MakeMeASandwich has contributed support for DHT temperature -and humidity sensors. It allows you to get the current temperature and humidity from a DHT11, DHT22, -or AM2302 device.

+
+ 
# Example configuration.yaml entry
+sensor:
+  platform: dht
+  sensor: DHT22
+  pin: 23
+  monitored_conditions:
+    - temperature
+    - humidity
+
+
+
-
1
-2
-3
-4
-5
-6
-7
-8
-
# Example configuration.yaml entry
-sensor:
-  platform: dht
-  sensor: DHT22
-  pin: 23
-  monitored_conditions:
-    - temperature
-    - humidity
-
- - -

Aruba device tracker
+

Aruba device tracker
Michael Arnauts has contributed support for Aruba wireless routers for presence detection.

-
1
-2
-3
-4
-5
-6
-
# Example configuration.yaml entry
-device_tracker:
-  platform: aruba
-  host: YOUR_ACCESS_POINT_IP
-  username: YOUR_ADMIN_USERNAME
-  password: YOUR_ADMIN_PASSWORD
-
- +
+ 
# Example configuration.yaml entry
+device_tracker:
+  platform: aruba
+  host: YOUR_ACCESS_POINT_IP
+  username: YOUR_ADMIN_USERNAME
+  password: YOUR_ADMIN_PASSWORD
+
+
+
]]> @@ -1424,218 +1276,136 @@ or AM2302 device.

In our house, laundry has been a struggle for quite some time. Our washer and dryer both lack a buzzer which leads to forgotten laundry, and stinky mess that needs to be rewashed. I decided to create a solution by monitoring the washer and dryer myself with some cheap electronics.

-

As an avid user of Home Assistant, I decided it would be the perfect application to manage the UI and notification system. Now all I needed was a way to monitor the washer and dryer. I tried using sound sensors but found them unreliable. I ended up opting for an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect if the doors are open or closed. I connected the accelerometers and reed switches to a Moteino, an arduino clone with an RF transceiver. The Moteino can perform the logic to figure out which state the appliances are in and wirelessly communicate that data with another Moteino that is connected via serial to my Raspberry Pi. The Raspberry Pi reads the serial data and repeats it over MQTT for Home Assistant to use. This is great because I don’t have to run Home Assistant on the Raspberry Pi. I can run it on a faster machine and point the MQTT component to my Raspberry Pi.

+

As an avid user of Home Assistant, I decided it would be the perfect application to manage the UI and notification system. Now all I needed was a way to monitor the washer and dryer. I tried using sound sensors but found them unreliable. I ended up opting for an accelerometer attached to the back of each appliance. I also added magnetic reed switches on the doors of the washer and dryer to detect if the doors are open or closed. I connected the accelerometers and reed switches to a Moteino, an arduino clone with an RF transceiver. The Moteino can perform the logic to figure out which state the appliances are in and wirelessly communicate that data with another Moteino that is connected via serial to my Raspberry Pi. The Raspberry Pi reads the serial data and repeats it over MQTT for Home Assistant to use. This is great because I don’t have to run Home Assistant on the Raspberry Pi. I can run it on a faster machine and point the MQTT component to my Raspberry Pi.

-

After taking some sample data from the accelerometers while each appliance was in operation, I decided to plot the data to help determine the proper thresholds of when the devices were running or off. I had to do this in order to get precise ranges so the dryer sensor wouldn’t get tripped by the washer or vice versa. In the plot below you can see the acceleration in the x direction for the accelerometer connected to the washing machine. It’s easy to see when the washing machine is in operation here. I used the same technique for the dryer’s accelerometer.

+

After taking some sample data from the accelerometers while each appliance was in operation, I decided to plot the data to help determine the proper thresholds of when the devices were running or off. I had to do this in order to get precise ranges so the dryer sensor wouldn’t get tripped by the washer or vice versa. In the plot below you can see the acceleration in the x direction for the accelerometer connected to the washing machine. It’s easy to see when the washing machine is in operation here. I used the same technique for the dryer’s accelerometer.

-

- - +

+ + Graph showing the accelerometer data

- - - +

Next it was just a matter of integrating everything with Home Assistant. I was able to use the MQTT component to read the washer and dryer states from the Moteino and display it in Home Assistant.

-

Next it was just a matter of integrating everything with Home Assistant. I was able to use the MQTT component to read the washer and dryer states from the Moteino and display it in Home Assistant.

- -

- +

+ Status of the dryer and washer in Home Assistant

+

Next I wrote scripts that are run whenever the washer or dryer completes a load. This is triggered by the automation component. When the laundry is complete I have the lights in the house turn red and notify me via PushBullet. Once the laundry is taken care of another script runs that sets the lights back to normal. So far it has been very helpful and very reliable.

-

Next I wrote scripts that are run whenever the washer or dryer completes a load. This is triggered by the automation component. When the laundry is complete I have the lights in the house turn red and notify me via PushBullet. Once the laundry is taken care of another script runs that sets the lights back to normal. So far it has been very helpful and very reliable.

- -

- - +

+ + Top left: reed switch. Bottom left: moteino. Right: Accelerometer.

-

Materials used:

-

Sketch for the Moteino is available here.

Home Assistant Configuration:

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-18
-19
-20
-21
-22
-23
-24
-25
-26
-27
-28
-29
-30
-31
-32
-33
-34
-35
-36
-37
-38
-39
-40
-41
-42
-43
-44
-45
-46
-47
-48
-49
-50
-51
-52
-53
-54
-55
-56
-57
-58
-59
-60
-61
-62
-63
-64
-65
-66
-67
-68
-69
-70
-71
-72
-73
-74
-75
-76
-77
-78
-
mqtt:
-  broker: 192.168.1.100
-  port: 1883
-  keepalive: 60
-  qos: 0
-
-sensor:
-  platform: mqtt
-  name: "Dryer Status"
-  state_topic: "sensor/dryer"
-  unit_of_measurement: ""
-
-sensor 2:
-  platform: mqtt
-  name: "Washer Status"
-  state_topic: "sensor/washer"
-  unit_of_measurement: ""
-
-automation:
-  alias: Dryer complete
-
-  platform: state
-  state_entity_id: sensor.dryer_status
-  state_from: 'Running'
-  state_to: 'Complete'
-
-  execute_service: script.turn_on
-  service_entity_id: script.dryer_complete
-
-automation 2:
-  alias: Dryer emptied
-
-  platform: state
-  state_entity_id: sensor.dryer_status
-  state_from: 'Complete'
-  state_to: 'Empty'
-
-  execute_service: script.turn_on
-  service_entity_id: script.dryer_cleared
-
-script:
-  dryer_complete:
-    alias: Dryer Complete Script
-    sequence:
-      - alias: Pushbullet Notification
-        execute_service: notify.notify
-        service_data:
-          message: "The dryer has finished its cycle, please empty it!"
-      - alias: Living Room Lights Red
-        execute_service: scene.turn_on
-        service_data:
-          entity_id: scene.red
-      - delay:
-          seconds: 1
-      - alias: Living Room Lights Off
-        execute_service: light.turn_off
-        service_data:
-          entity_id: group.living_room
-      - delay:
-          seconds: 1
-      - alias: Living Room Lights Red
-        execute_service: scene.turn_on
-        service_data:
-          entity_id: scene.red
-
-  dryer_cleared:
-    alias: Dryer Cleared Script
-    sequence:
-      - alias: Living Room Lights Off
-        execute_service: light.turn_off
-        service_data:
-          entity_id: group.living_room
-      - delay:
-          seconds: 1
-      - alias: Living Room Lights Normal
-        execute_service: scene.turn_on
-        service_data:
-          entity_id: scene.normal
+
+ 
mqtt:
+  broker: 192.168.1.100
+  port: 1883
+  keepalive: 60
+  qos: 0
 
+sensor:
+  platform: mqtt
+  name: "Dryer Status"
+  state_topic: "sensor/dryer"
+  unit_of_measurement: ""
+
+sensor 2:
+  platform: mqtt
+  name: "Washer Status"
+  state_topic: "sensor/washer"
+  unit_of_measurement: ""
+
+automation:
+  alias: Dryer complete
+
+  platform: state
+  state_entity_id: sensor.dryer_status
+  state_from: 'Running'
+  state_to: 'Complete'
+
+  execute_service: script.turn_on
+  service_entity_id: script.dryer_complete
+
+automation 2:
+  alias: Dryer emptied
+
+  platform: state
+  state_entity_id: sensor.dryer_status
+  state_from: 'Complete'
+  state_to: 'Empty'
+
+  execute_service: script.turn_on
+  service_entity_id: script.dryer_cleared
+
+script:
+  dryer_complete:
+    alias: Dryer Complete Script
+    sequence:
+      - alias: Pushbullet Notification
+        execute_service: notify.notify
+        service_data:
+          message: "The dryer has finished its cycle, please empty it!"
+      - alias: Living Room Lights Red
+        execute_service: scene.turn_on
+        service_data:
+          entity_id: scene.red
+      - delay:
+          seconds: 1
+      - alias: Living Room Lights Off
+        execute_service: light.turn_off
+        service_data:
+          entity_id: group.living_room
+      - delay:
+          seconds: 1
+      - alias: Living Room Lights Red
+        execute_service: scene.turn_on
+        service_data:
+          entity_id: scene.red
+
+  dryer_cleared:
+    alias: Dryer Cleared Script
+    sequence:
+      - alias: Living Room Lights Off
+        execute_service: light.turn_off
+        service_data:
+          entity_id: group.living_room
+      - delay:
+          seconds: 1
+      - alias: Living Room Lights Normal
+        execute_service: scene.turn_on
+        service_data:
+          entity_id: scene.normal
+
+
+

Resources used:

]]> @@ -1648,38 +1418,30 @@ or AM2302 device.

https://home-assistant.io/blog/2015/08/17/verisure-and-modern-tp-link-router-support A minor bug fix release to fix some issues that have come up since the last release. Please upgrade as soon as possible by running git pull from the Home Assistant directory.

-

This release is a major milestone in our test coverage as we’ve crossed into the 80s! It has to be noted that this covers mainly the core and automation components. Platforms that communicate with IoT devices have been excluded.

+

This release is a major milestone in our test coverage as we’ve crossed into the 80s! It has to be noted that this covers mainly the core and automation components. Platforms that communicate with IoT devices have been excluded.

-

As we didn’t want to just push out bug fixes, this release includes a few additions:

+

As we didn’t want to just push out bug fixes, this release includes a few additions:

    -
  • Support for modern TP-Link routers like the ArcherC9 line has been contributed by @chrisvis.
    • -
  • Improved support for MQTT topic subscriptions has been contributed by @qrtn
    • +
  • Support for modern TP-Link routers like the ArcherC9 line has been contributed by @chrisvis.
    • +
  • Improved support for MQTT topic subscriptions has been contributed by @qrtn
+

Verisure Support
+ Home Assistant support to integrate your Verisure alarms, hygrometers, sensors and thermometers has been contributed by @persandstrom.

-

Verisure Support
- -Home Assistant support to integrate your Verisure alarms, hygrometers, sensors and thermometers has been contributed by @persandstrom.

- -
1
-2
-3
-4
-5
-6
-7
-8
-
# Example configuration.yaml entry
-verisure:
-  username: user@example.com
-  password: password
-  alarm: 1
-  hygrometers: 0
-  smartplugs: 1
-  thermometers: 0
-
- +
+ 
# Example configuration.yaml entry
+verisure:
+  username: user@example.com
+  password: password
+  alarm: 1
+  hygrometers: 0
+  smartplugs: 1
+  thermometers: 0
+
+
+
]]> @@ -1688,162 +1450,122 @@ Home Assistant support to integrate your Ver 2015-08-09T18:01:00-07:00 https://home-assistant.io/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support - It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to @balloob. If you’re a developer, make sure you read up on the deprecation notices. @fabaff did another great round of documentating all the various components.

- -

MQTT Support
- -The big new addition in this release is the support for the MQTT protocol by @fabaff with some help from @balloob. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (see the example) and also support for the automation component has been added. For more information, see the MQTT component page.

- -
1
-2
-3
-4
-5
-6
-7
-8
-9
-
# Example configuration.yaml entry
-mqtt:
-  broker: IP_ADDRESS_BROKER
-  # All the other options are optional:
-  port: 1883
-  keepalive: 60
-  qos: 0
-  username: your_username
-  password: your_secret_password
-
- + It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to @balloob. If you’re a developer, make sure you read up on the deprecation notices. @fabaff did another great round of documentating all the various components.

+

MQTT Support
+ The big new addition in this release is the support for the MQTT protocol by @fabaff with some help from @balloob. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (see the example) and also support for the automation component has been added. For more information, see the MQTT component page.

+
+ 
# Example configuration.yaml entry
+mqtt:
+  broker: IP_ADDRESS_BROKER
+  # All the other options are optional:
+  port: 1883
+  keepalive: 60
+  qos: 0
+  username: your_username
+  password: your_secret_password
+
+
+
+

Raspberry PI GPIO Support
+ @gbarba has contributed support to use the general purpose input and output pins on a Raspberry PI as switches inside Home Assistant.

-

Raspberry PI GPIO Support
- -@gbarba has contributed support to use the general purpose input and output pins on a Raspberry PI as switches inside Home Assistant.

+
+ 
# Example configuration.yaml entry
+switch:
+  platform: rpi_gpio
+  ports:
+    11: Fan Office
+    12: Light Desk
+
+
+
-
1
-2
-3
-4
-5
-6
-
# Example configuration.yaml entry
-switch:
-  platform: rpi_gpio
-  ports:
-    11: Fan Office
-    12: Light Desk
-
+

ASUSWRT based routers
+ @persandstrom has contributed support to do prescence detection using ASUSWRT based routers.

+
+ 
# Example configuration.yaml entry
+device_tracker:
+  platform: asuswrt
+  host: YOUR_ROUTER_IP
+  username: YOUR_ADMIN_USERNAME
+  password: YOUR_ADMIN_PASSWORD
+
+
+
-

ASUSWRT based routers
- -@persandstrom has contributed support to do prescence detection using ASUSWRT based routers.

+

Logitech Squeezebox media player support
+ @persandstrom also contributed support for the Logitech Squeezebox media player. This allows you to control your Logitech Squeezebox from Home Assistant.

-
1
-2
-3
-4
-5
-6
-
# Example configuration.yaml entry
-device_tracker:
-  platform: asuswrt
-  host: YOUR_ROUTER_IP
-  username: YOUR_ADMIN_USERNAME
-  password: YOUR_ADMIN_PASSWORD
-
+
+ 
# Example configuration.yaml entry
+media_player:
+  platform: squeezebox
+  host: 192.168.1.21
+  port: 9090
+  username: user
+  password: password
+
+
+
+

Slack notification support
+ @jamespcole has contributed a Slack platform for the notification platform. This allows you to deliver messages to any channel.

-

Logitech Squeezebox media player support
- -@persandstrom also contributed support for the Logitech Squeezebox media player. This allows you to control your Logitech Squeezebox from Home Assistant.

+
+ 
# Example configuration.yaml entry
+notify:
+  platform: slack
+  api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
+  default_channel: '#general'
+
+
+
-
1
-2
-3
-4
-5
-6
-7
-
# Example configuration.yaml entry
-media_player:
-  platform: squeezebox
-  host: 192.168.1.21
-  port: 9090
-  username: user
-  password: password
-
+

Edimax Smart Switches support
+ @rkabadi has contributed support for integrating Edimax Smart Switches into Home Assistant.

+
+ 
# Example configuration.yaml entry
+switch:
+  platform: edimax
+  host: 192.168.1.32
+  username: YOUR_USERNAME
+  password: YOUR_PASSWORD
+  name: Edimax Smart Plug
+
+
+
-

Slack notification support
- -@jamespcole has contributed a Slack platform for the notification platform. This allows you to deliver messages to any channel.

- -
1
-2
-3
-4
-5
-
# Example configuration.yaml entry
-notify:
-  platform: slack
-  api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
-  default_channel: '#general'
-
- - -

Edimax Smart Switches support
- -@rkabadi has contributed support for integrating Edimax Smart Switches into Home Assistant.

- -
1
-2
-3
-4
-5
-6
-7
-
# Example configuration.yaml entry
-switch:
-  platform: edimax
-  host: 192.168.1.32
-  username: YOUR_USERNAME
-  password: YOUR_PASSWORD
-  name: Edimax Smart Plug
-
- - -

RFXtrx sensor support
+

RFXtrx sensor support
@danielhiversen has contributed support for RFXtrx sensors. It supports sensors that communicate in the frequency range of 433.92 MHz.

-
1
-2
-3
-4
-
# Example configuration.yaml entry
-sensor:
-  - platform: rfxtrx
-    device: PATH_TO_DEVICE
-
- +
+ 
# Example configuration.yaml entry
+sensor:
+  - platform: rfxtrx
+    device: PATH_TO_DEVICE
+
+
+

The path to your device, e.g. /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0

-

TEMPer temperature sensor support
+

TEMPer temperature sensor support
Support for Temper temperature sensors has been contributed by @rkabadi.

-
1
-2
-3
-
# Example configuration.yaml entry
-sensor:
-  platform: temper
-
- +
+ 
# Example configuration.yaml entry
+sensor:
+  platform: temper
+
+
+
]]> @@ -1856,195 +1578,129 @@ Support for Temper temperature sensors has been contributed by NuclearJS JavaScript backend. This has greatly helped to organize and optimize the frontend code. Another change is that Home Assistant will now install dependencies on-demand instead of installing dependencies for all supported devices.

-

IP Camera Support
+

IP Camera Support
James has worked very hard to add support for IP cameras to Home Assistant which is included in this release. The initial release focusses on providing generic IP camera support. This means that any webcam that can exposes a JPEG image via a url can be integrated.

-

Home Assistant will route the requests to your camera via the server allowing you to expose IP camera’s inside your network via the Home Assistant app.

+

Home Assistant will route the requests to your camera via the server allowing you to expose IP camera’s inside your network via the Home Assistant app.

-
1
-2
-3
-4
-5
-6
-7
-
# Example configuration.yaml entry
-camera:
-  platform: generic
-  name: my sample camera
-  username: MY_USERNAME
-  password: MY_PASSWORD
-  still_image_url: http://194.218.96.92/jpg/image.jpg
-
+
+ 
# Example configuration.yaml entry
+camera:
+  platform: generic
+  name: my sample camera
+  username: MY_USERNAME
+  password: MY_PASSWORD
+  still_image_url: http://194.218.96.92/jpg/image.jpg
+
+
+
- - - -

-To update to the latest version, run scripts/update. Please report any issues on GitHub. +

+To update to the latest version, run scripts/update. Please report any issues on GitHub.

- - - +

Arduino
+ Fabian has contributed support for interfacing with Arduinos. This makes it possible to connect your Arduino via USB and expose pins as sensor data and write to pins via switches. Have a look at the docs for an extensive guide to get started.

-

Arduino
- -Fabian has contributed support for interfacing with Arduinos. This makes it possible to connect your Arduino via USB and expose pins as sensor data and write to pins via switches. Have a look at the docs for an extensive guide to get started.

+
+ 
# Example configuration.yaml entry
+switch:
+  platform: arduino
+  pins:
+    11:
+      name: Fan Office
+      type: digital
+    12:
+      name: Light Desk
+      type: digital
 
-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-18
-19
-20
-
# Example configuration.yaml entry
-switch:
-  platform: arduino
-  pins:
-    11:
-      name: Fan Office
-      type: digital
-    12:
-      name: Light Desk
-      type: digital
-
-sensor:
-  platform: arduino
-  pins:
-    1:
-      name: Door switch
-      type: analog
-    0:
-      name: Brightness
-      type: analog
-

+sensor:
+  platform: arduino
+  pins:
+    1:
+      name: Door switch
+      type: analog
+    0:
+      name: Brightness
+      type: analog
+
+
+
+

Kodi (XBMC)
+ Ettisan has contributed a Kodi (XBMC) platform for the media player component. This allows you to track all the media that you are playing and allow you to control it.

-

Kodi (XBMC)
- -Ettisan has contributed a Kodi (XBMC) platform for the media player component. This allows you to track all the media that you are playing and allow you to control it.

+
+ 
# Example configuration.yaml entry
+media_player:
+  platform: kodi
+  name: Kodi
+  url: http://192.168.0.123/jsonrpc
+  user: kodi
+  password: my_secure_password
+
+
+
-
1
-2
-3
-4
-5
-6
-7
-
# Example configuration.yaml entry
-media_player:
-  platform: kodi
-  name: Kodi
-  url: http://192.168.0.123/jsonrpc
-  user: kodi
-  password: my_secure_password
-
+

TP-Link
+ Michael has added TP-Link support to the device tracker. This allows you to now detect presence if you have a TP-Link router.

+
+ 
# Example configuration.yaml entry
+device_tracker:
+  platform: tplink
+  host: YOUR_ROUTER_IP
+  username: YOUR_ADMIN_USERNAME
+  password: YOUR_ADMIN_PASSWORD
+
+
+
-

TP-Link
- -Michael has added TP-Link support to the device tracker. This allows you to now detect presence if you have a TP-Link router.

+

Efergy energy monitor
+ Miniconfig has contributed support for the Efergy energy meters. To get an app token, log in to your efergy account, go to the Settings page, click on App tokens, and click “Add token”.

-
1
-2
-3
-4
-5
-6
-
# Example configuration.yaml entry
-device_tracker:
-  platform: tplink
-  host: YOUR_ROUTER_IP
-  username: YOUR_ADMIN_USERNAME
-  password: YOUR_ADMIN_PASSWORD
-
+
+ 
# Example configuration.yaml entry
+sensor:
+  platform: efergy
+  app_token: APP_TOKEN
+  utc_offset: UTC_OFFSET
+  monitored_variables:
+    - type: instant_readings
+    - type: budget
+    - type: cost
+      period: day
+      currency: $
+
+
+
- -

Efergy energy monitor
- -Miniconfig has contributed support for the Efergy energy meters. To get an app token, log in to your efergy account, go to the Settings page, click on App tokens, and click “Add token”.

- -
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-
# Example configuration.yaml entry
-sensor:
-  platform: efergy
-  app_token: APP_TOKEN
-  utc_offset: UTC_OFFSET
-  monitored_variables:
-    - type: instant_readings
-    - type: budget
-    - type: cost
-      period: day
-      currency: $
-
- - -

Forecast.io
+

Forecast.io
Fabian has added support for Forecast.io to get weather forecasts for Home Assistant. You need an API key which is free but requires a registration. To add Forecast.io to your installation, add the following to your configuration.yaml file:

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-
# Example configuration.yaml entry
-sensor:
-  platform: forecast
-  api_key: YOUR_APP_KEY
-  monitored_conditions:
-    - summary
-    - precip_type
-    - precip_intensity
-    - temperature
-    - dew_point
-    - wind_speed
-    - wind_bearing
-    - cloud_cover
-    - humidity
-    - pressure
-    - visibility
-    - ozone
-
- +
+ 
# Example configuration.yaml entry
+sensor:
+  platform: forecast
+  api_key: YOUR_APP_KEY
+  monitored_conditions:
+    - summary
+    - precip_type
+    - precip_intensity
+    - temperature
+    - dew_point
+    - wind_speed
+    - wind_bearing
+    - cloud_cover
+    - humidity
+    - pressure
+    - visibility
+    - ozone
+
+
+
]]> @@ -2053,255 +1709,181 @@ Fabian has added support for Forecast.io to g 2015-06-10T18:54:00-07:00 https://home-assistant.io/blog/2015/06/10/release-notes - Wow, almost a month has gone by since the last release and this release is packed. The biggest part of this release is probably one that you won’t notice: the frontend has been upgraded from Polymer 0.5 to the brand new released Polymer 1.0. Polymer has been declared stable by the Google overlords which will allow us to expand functionality that was waiting for this moment to arrive.

+ Wow, almost a month has gone by since the last release and this release is packed. The biggest part of this release is probably one that you won’t notice: the frontend has been upgraded from Polymer 0.5 to the brand new released Polymer 1.0. Polymer has been declared stable by the Google overlords which will allow us to expand functionality that was waiting for this moment to arrive.

This release sets a record for the amount of people involved: 8! Andythigpen, Jamespcole, Azelphur, Fabaff, Dutchy-, Fbradyirl, wind-rider and ettisan, thanks a lot for your contributions!

A big improvement has been brought this release by wind-rider. He took the time to revive the Chromecast support and started improving the media player integration. This triggered other people to join in resulting in a revamped media player experience and support for the Music Player Daemon.

-

- - Example of the new media player cards +

+ Example of the new media player cards

- - - -

-To update to the latest version, run scripts/update. Please report any issues on GitHub. +

+To update to the latest version, run scripts/update. Please report any issues on GitHub.

- - - -

Before jumping into the newly supported platforms, here are the other improvements that are landing this release:

    -
  • Fronted upgraded to Polymer 1.0 by @balloob
    • -
  • Include other YAML files using the !include keyword by @andythigpen
    • -
  • Switch support and bug fixes for Vera platform by @jamespcole
    • -
  • HTTP session support for the HTTP component by @jamespcole
    • -
  • Device tracker bugfixes by @Dutchy-
    • -
  • Bugfix for device tracker platform by @fbradyirl
    • -
  • Fixing Chromecast support by @wind-rider
    • -
  • Media player improvements by @balloob and @wind-rider
    • -
  • Nest thermostat bugfixes by @balloob
    • -
  • Fix the device tracker getting in a deadlock by @balloob
    • -
  • Update documentation by @fabaff
    • +
  • Fronted upgraded to Polymer 1.0 by @balloob
    • +
  • Include other YAML files using the !include keyword by @andythigpen
    • +
  • Switch support and bug fixes for Vera platform by @jamespcole
    • +
  • HTTP session support for the HTTP component by @jamespcole
    • +
  • Device tracker bugfixes by @Dutchy-
    • +
  • Bugfix for device tracker platform by @fbradyirl
    • +
  • Fixing Chromecast support by @wind-rider
    • +
  • Media player improvements by @balloob and @wind-rider
    • +
  • Nest thermostat bugfixes by @balloob
    • +
  • Fix the device tracker getting in a deadlock by @balloob
    • +
  • Update documentation by @fabaff
+

Music Player Daemon
+ Fabaff has contributed MusicPlayerDaemon support. The mpd platform allows you to control a Music Player Daemon from Home Assistant. Right now, only playback is supported and not playlist manipulation.

-

Music Player Daemon
- -Fabaff has contributed MusicPlayerDaemon support. The mpd platform allows you to control a Music Player Daemon from Home Assistant. Right now, only playback is supported and not playlist manipulation.

+
+ 
# Example configuration.yaml entry
+media_player:
+  platform: mpd
+  server: 127.0.0.1
+  port: 6600
+  location: bedroom
+
+
+
-
1
-2
-3
-4
-5
-6
-
# Example configuration.yaml entry
-media_player:
-  platform: mpd
-  server: 127.0.0.1
-  port: 6600
-  location: bedroom
-
- - -

Command line switch
+

Command line switch
A switch platform that issues specific commands when it is turned on and off. This might very well become our most popular platform as it allows anyone to integrate any type of switch into Home Assistant that can be controlled from the command line, including calling other scripts!

-
1
-2
-3
-4
-5
-6
-7
-
# Example configuration.yaml entry
-switch:
-  platform: command_switch
-  switches:
-    - kitchen_light:
-        oncmd: switch_command on kitchen
-        offcmd: switch_command off kitchen
-
+
+ 
# Example configuration.yaml entry
+switch:
+  platform: command_switch
+  switches:
+    - kitchen_light:
+        oncmd: switch_command on kitchen
+        offcmd: switch_command off kitchen
+
+
+
- -

LimitlessLED
+

LimitlessLED
This new platform can control your LimitlessLED lights from within Home Assistant. The lights are also known as EasyBulb, AppLight, AppLamp, MiLight, LEDme, dekolight or iLight.

-
1
-2
-3
-4
-5
-6
-7
-8
-
# Example configuration.yaml entry
-light:
-  platform: limitlessled
-  host: 192.168.1.10
-  group_1_name: Living Room
-  group_2_name: Bedroom
-  group_3_name: Office
-  group_4_name: Kitchen
-
+
+ 
# Example configuration.yaml entry
+light:
+  platform: limitlessled
+  host: 192.168.1.10
+  group_1_name: Living Room
+  group_2_name: Bedroom
+  group_3_name: Office
+  group_4_name: Kitchen
+
+
+
+

Bitcoin sensor
+ The bitcoin platform displays various details about the Bitcoin network. If you have an online wallet from Blockchain.info the sensor is capable to show your current balance.

-

Bitcoin sensor
- -The bitcoin platform displays various details about the Bitcoin network. If you have an online wallet from Blockchain.info the sensor is capable to show your current balance.

+
+ 
# Example configuration.yaml entry
+sensor:
+  platform: bitcoin
+  wallet: 'YOUR WALLET_ID'
+  password: YOUR_ACCOUNT_PASSWORD
+  currency: YOUR CURRENCY
+  display_options:
+    - exchangerate
+    - trade_volume_btc
+    - miners_revenue_usd
+    - btc_mined
+    - trade_volume_usd
+    - difficulty
+    - minutes_between_blocks
+    - number_of_transactions
+    - hash_rate
+    - timestamp
+    - mined_blocks
+    - blocks_size
+    - total_fees_btc
+    - total_btc_sent
+    - estimated_btc_sent
+    - total_btc
+    - total_blocks
+    - next_retarget
+    - estimated_transaction_volume_usd
+    - miners_revenue_btc
+    - market_price_usd
+
+
+
-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-18
-19
-20
-21
-22
-23
-24
-25
-26
-27
-28
-
# Example configuration.yaml entry
-sensor:
-  platform: bitcoin
-  wallet: 'YOUR WALLET_ID'
-  password: YOUR_ACCOUNT_PASSWORD
-  currency: YOUR CURRENCY
-  display_options:
-    - exchangerate
-    - trade_volume_btc
-    - miners_revenue_usd
-    - btc_mined
-    - trade_volume_usd
-    - difficulty
-    - minutes_between_blocks
-    - number_of_transactions
-    - hash_rate
-    - timestamp
-    - mined_blocks
-    - blocks_size
-    - total_fees_btc
-    - total_btc_sent
-    - estimated_btc_sent
-    - total_btc
-    - total_blocks
-    - next_retarget
-    - estimated_transaction_volume_usd
-    - miners_revenue_btc
-    - market_price_usd
-
+

SMTP notificatoin platform
+ The smtp platform allows you to deliver notifications from Home Assistant to an e-mail recipient.

+
+ 
# Example configuration.yaml entry
+notify:
+  platform: mail
+  server: MAIL_SERVER
+  port: YOUR_SMTP_PORT
+  sender: SENDER_EMAIL_ADDRESS
+  starttls: 1 or 0
+  username: YOUR_SMTP_USERNAME
+  password: YOUR_SMTP_PASSWORD
+  recipient: YOUR_RECIPIENT
+
+
+
-

SMTP notificatoin platform
- -The smtp platform allows you to deliver notifications from Home Assistant to an e-mail recipient.

- -
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-
# Example configuration.yaml entry
-notify:
-  platform: mail
-  server: MAIL_SERVER
-  port: YOUR_SMTP_PORT
-  sender: SENDER_EMAIL_ADDRESS
-  starttls: 1 or 0
-  username: YOUR_SMTP_USERNAME
-  password: YOUR_SMTP_PASSWORD
-  recipient: YOUR_RECIPIENT
-
- - -

Syslog notification platform
+

Syslog notification platform
The syslog platform allows you to deliver notifications from Home Assistant to the local syslog.

-
1
-2
-3
-
# Example configuration.yaml entry
-notify:
-  platform: syslog
-
+
+ 
# Example configuration.yaml entry
+notify:
+  platform: syslog
+
+
+
+

Swiss Public transport sensor
+The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. See the component page for more information how to set it up.

-

Swiss Public transport sensor
-The swiss public transport sensor will give you the next two departure times from a given location to another one in Switzerland. See the component page for more information how to set it up.

+

Transmission turtle mode switch
+ The transmission platform allows you to control your Transmission client from within Home Assistant. The platform enables you switch to your ‘Alternative Speed Limits’ (aka ‘Turtle mode’) setting.

-

Transmission turtle mode switch
- -The transmission platform allows you to control your Transmission client from within Home Assistant. The platform enables you switch to your ‘Alternative Speed Limits’ (aka ‘Turtle mode’) setting.

+
+ 
# Example configuration.yaml entry
+switch:
+  platform: transmission
+  name: Transmission
+  host: 192.168.1.26
+  port: 9091
+  username: YOUR_USERNAME
+  password: YOUR_PASSWORD
+
+
+
-
1
-2
-3
-4
-5
-6
-7
-8
-
# Example configuration.yaml entry
-switch:
-  platform: transmission
-  name: Transmission
-  host: 192.168.1.26
-  port: 9091
-  username: YOUR_USERNAME
-  password: YOUR_PASSWORD
-
- - -

Hikvision camera motion detection support
+

Hikvision camera motion detection support
This switch platform allows you to control your motion detection setting on your Hikvision camera.

-
1
-2
-3
-4
-5
-6
-7
-
# Example configuration.yaml entry
-switch:
-    platform: hikvisioncam
-    name: Hikvision Cam 1 Motion Detection
-    host: 192.168.1.26
-    username: YOUR_USERNAME
-    password: YOUR_PASSWORD
-
- +
+ 
# Example configuration.yaml entry
+switch:
+    platform: hikvisioncam
+    name: Hikvision Cam 1 Motion Detection
+    host: 192.168.1.26
+    username: YOUR_USERNAME
+    password: YOUR_PASSWORD
+
+
+
]]> @@ -2310,176 +1892,128 @@ This switch platform allows you to control your motion detection setting on your 2015-05-14T22:25:00-07:00 https://home-assistant.io/blog/2015/05/14/release-notes - Almost three busy weeks have past since the last release. We used this time to finally make the overhaul to use UTC as the internal date time format. We added a bunch of test coverage in the process to make sure the transition went smoothly. Pleas see the blog post about the UTC refactor for backwards incompatible changes.

+ Almost three busy weeks have past since the last release. We used this time to finally make the overhaul to use UTC as the internal date time format. We added a bunch of test coverage in the process to make sure the transition went smoothly. Pleas see the blog post about the UTC refactor for backwards incompatible changes.

This release includes a significant startup boost for the frontend and a fix for Wemo discovery after their latest firmware upgrade.

I would like to give a big shout out to our newest contributor fabaff for taking the time to improve the documentation.

-

-To update to the latest version, run scripts/update. Please report any issues on GitHub. +

+To update to the latest version, run scripts/update. Please report any issues on GitHub.

- - - - -

Overwriting Entity Attributes
+

Overwriting Entity Attributes
Before diving into the newly supported devices and services, I want to highlight an awesome configuration enhancement by rmkraus: overwriting entity attributes.

These new configuration settings allow you to overwrite entity state attributes. The main usage for this is being able to overwrite attributes that influence how an entity is shown in the interface.

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-
# Example configuration.yaml entry
-homeassistant:
-  customize:
-    light.bowl:
-      # hides this entity from the interface
-      hidden: true
-    light.ceiling:
-      # Replaces the state badge with given picture
-      entity_picture: http://graph.facebook.com/schoutsen/picture
-
+
+ 
# Example configuration.yaml entry
+homeassistant:
+  customize:
+    light.bowl:
+      # hides this entity from the interface
+      hidden: true
+    light.ceiling:
+      # Replaces the state badge with given picture
+      entity_picture: http://graph.facebook.com/schoutsen/picture
+
+
+
+

MySensors
+ Andythigpen and Theolind have added support for the MySensors platform to Home Assistant.

-

MySensors
- -Andythigpen and Theolind have added support for the MySensors platform to Home Assistant.

+
+ 
# Example configuration.yaml entry
+sensor:
+  platform: mysensors
+  port: /dev/ttyACM0
+
+
+
-
1
-2
-3
-4
-
# Example configuration.yaml entry
-sensor:
-  platform: mysensors
-  port: /dev/ttyACM0
-
+

OpenWeatherMap
+ Fabaff has contributed support for OpenWeatherMap. This will allow you to integrate local meteorological data into Home Assistant.

+
+ 
# Example configuration.yaml entry
+sensor:
+  platform: openweathermap
+  api_key: YOUR_API_KEY
+  monitored_variables:
+    - type: 'weather'
+    - type: 'temperature'
+    - type: 'wind_speed'
+    - type: 'humidity'
+    - type: 'pressure'
+    - type: 'clouds'
+    - type: 'rain'
+    - type: 'snow'
+
+
+
-

OpenWeatherMap
- -Fabaff has contributed support for OpenWeatherMap. This will allow you to integrate local meteorological data into Home Assistant.

+

InstaPush
+ Fabaff has contributed support for InstaPush. This will allow you send messages from Home Assistant to your iOS and Android devices.

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-
# Example configuration.yaml entry
-sensor:
-  platform: openweathermap
-  api_key: YOUR_API_KEY
-  monitored_variables:
-    - type: 'weather'
-    - type: 'temperature'
-    - type: 'wind_speed'
-    - type: 'humidity'
-    - type: 'pressure'
-    - type: 'clouds'
-    - type: 'rain'
-    - type: 'snow'
-
+
+ 
# Example configuration.yaml entry
+notify:
+    platform: instapush
+    # Get those by creating a new application, event, and tracker on https://instapush.im
+    api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
+    app_secret: ABCDEFGHJKLMNOPQRSTUVXYZ
+    event: ABCDEFGHJKLMNOPQRSTUVXYZ
+    tracker: ABCDEFGHJKLMNOPQRSTUVXYZ
+
+
+
+

XMPP
+ Fabaff has contributed support for Jabber/XMPP. This will allow you send messages from Home Assistant to anyone on Jabber/XMPP.

-

InstaPush
- -Fabaff has contributed support for InstaPush. This will allow you send messages from Home Assistant to your iOS and Android devices.

+
+ 
# Example configuration.yaml entry
+notify:
+    platform: xmpp
+    sender: YOUR_JID
+    password: YOUR_JABBER_ACCOUNT_PASSWORD
+    recipient: YOUR_RECIPIENT
+
+
+
-
1
-2
-3
-4
-5
-6
-7
-8
-
# Example configuration.yaml entry
-notify:
-    platform: instapush
-    # Get those by creating a new application, event, and tracker on https://instapush.im
-    api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
-    app_secret: ABCDEFGHJKLMNOPQRSTUVXYZ
-    event: ABCDEFGHJKLMNOPQRSTUVXYZ
-    tracker: ABCDEFGHJKLMNOPQRSTUVXYZ
-
+

Notify My Android
+ Fabaff has contributed support for Notify My Android. This will allow you to send messages from Home Assistant to your Android device.

+
+ 
# Example configuration.yaml entry
+notify:
+    platform: nma
+    # Get this by registering a new application on http://www.notifymyandroid.com/
+    api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
+
+
+
-

XMPP
- -Fabaff has contributed support for Jabber/XMPP. This will allow you send messages from Home Assistant to anyone on Jabber/XMPP.

- -
1
-2
-3
-4
-5
-6
-
# Example configuration.yaml entry
-notify:
-    platform: xmpp
-    sender: YOUR_JID
-    password: YOUR_JABBER_ACCOUNT_PASSWORD
-    recipient: YOUR_RECIPIENT
-
- - -

Notify My Android
- -Fabaff has contributed support for Notify My Android. This will allow you to send messages from Home Assistant to your Android device.

- -
1
-2
-3
-4
-5
-
# Example configuration.yaml entry
-notify:
-    platform: nma
-    # Get this by registering a new application on http://www.notifymyandroid.com/
-    api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
-
- - -

Time & Date sensor
+

Time & Date sensor
Fabaff has contributed a time & date sensor. This will allow you to show the current time/date on the dashboard.

-
1
-2
-3
-4
-5
-6
-7
-8
-
# Example configuration.yaml entry
-sensor:
-  platform: time_date
-  monitored_variables:
-    - type: 'time'
-    - type: 'date'
-    - type: 'date_time'
-    - type: 'time_date'
-
- +
+ 
# Example configuration.yaml entry
+sensor:
+  platform: time_date
+  monitored_variables:
+    - type: 'time'
+    - type: 'date'
+    - type: 'date_time'
+    - type: 'time_date'
+
+
+
]]> @@ -2488,39 +2022,36 @@ Before diving into the newly supported devices and services, I want to highlight 2015-05-09T23:08:00-07:00 https://home-assistant.io/blog/2015/05/09/utc-time-zone-awareness - I have recently merged code to refactor Home Assistant to use only UTC times internally. A much needed refactor. I’ve added some extra test coverage to time sensitive parts to ensure stability. The code has been live in the dev branch for the last 9 days and will be soon released to the master branch.

+ I have recently merged code to refactor Home Assistant to use only UTC times internally. A much needed refactor. I’ve added some extra test coverage to time sensitive parts to ensure stability. The code has been live in the dev branch for the last 9 days and will be soon released to the master branch.

From now on all internal communication will be done in UTC: time changed events, datetime attributes of states, etc. To get the current time in UTC you can call homeassistant.util.dt.utcnow(). This is a timezone aware UTC datetime object. homeassistant.util.dt is a new util package with date helpers.

There is also such a thing as local time. Local time is based on the time zone that you have setup in your configuration.yaml. Local times should only be used for user facing information: logs, frontend and automation settings in configuration.yaml.

Setting up your time zone

-

Setting up a time zone happens in configuration.yaml. If you have no time zone setup, it will be auto detected using the existing detection code using freegeoip.net. You can find a list of compatible time zones on Wikipedia.

-
1
-2
-
homeassistant:
-  time_zone: America/Los_Angeles
-
- +
+ 
homeassistant:
+  time_zone: America/Los_Angeles
+
+
+

Compatibility

-

The changes to the code are mostly backwards compatible. The old hass.track_time_change and hass.track_point_in_time use now internally two new methods: hass.track_utc_time_change and hass.track_point_in_utc_time. The usage of the old methods have not changed and should be backwards compatible.

This refactor adds a new migration for the database adding a utc_offset column to events and states. This information is currently not used but can prove useful in the future when we start analyzing the historical data.

-

Backwards incompatible stuff

+

Backwards incompatible stuff

All built-in components have been upgraded. The following list is only for people that run custom components:

    -
  • hass.track_time_change and hass.track_point_in_time will now return a time zone aware datetime object. Python does not allow comparing a naive with an aware datetime object.
    • -
  • the sun attributes for rising and setting are now in UTC. The methods sun.next_rising(hass) and sun.next_setting(hass) are backwards compatible, just be careful if you used to read the raw attributes.
    • -
  • the API sends all times in UTC. If you use anything else besides the frontend to talk to HA, make sure it handles it differently.
    • +
  • hass.track_time_change and hass.track_point_in_time will now return a time zone aware datetime object. Python does not allow comparing a naive with an aware datetime object.
    • +
  • the sun attributes for rising and setting are now in UTC. The methods sun.next_rising(hass) and sun.next_setting(hass) are backwards compatible, just be careful if you used to read the raw attributes.
    • +
  • the API sends all times in UTC. If you use anything else besides the frontend to talk to HA, make sure it handles it differently.
- ]]> @@ -2529,349 +2060,248 @@ Before diving into the newly supported devices and services, I want to highlight 2015-04-25T06:57:00-07:00 https://home-assistant.io/blog/2015/04/25/release-notes - It’s been a month since the latest update and a lot has happened again. Here a quick overview of the new things.

+ It’s been a month since the latest update and a lot has happened again. Here a quick overview of the new things.

-

Line Charts
+

Line Charts
James has upgraded the history in the frontend to support line graphs. Line graphs will be shown for any entity that has a unit of measurement. The line graphs will also be shown in the more info card of an entity. See the demo for a live example.

-

- +

+

+

ISY994 hub support
+ Ryan has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.

-

ISY994 hub support
- -Ryan has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.

- -

He has created an extensive getting started guide which can be found on the ISY994 component page.

- -
1
-2
-
# Example configuration.yaml entry
-isy994:
-
- - -

Logbook
- -I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. See the demo for a live example. -

- -
1
-2
-
# Example configuration.yaml entry
-logbook:
-
+

He has created an extensive getting started guide which can be found on the ISY994 component page.

+
+ 
# Example configuration.yaml entry
+isy994:
+
+
+
+

Logbook
+ I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. See the demo for a live example.
+

+
+ 
# Example configuration.yaml entry
+logbook:
+
+
+
+

Transmission support
+ James has also contributed support for integrating Transmission into Home Assistant.

-

Transmission support
- -James has also contributed support for integrating Transmission into Home Assistant.

+
+ 
# Example configuration.yaml entry
+sensor:
+  platform: transmission
+  name: Transmission
+  host: 192.168.1.26
+  port: 9091
+  username: YOUR_USERNAME
+  password: YOUR_PASSWORD
+  monitored_variables:
+    - type: 'current_status'
+    - type: 'download_speed'
+    - type: 'upload_speed'
+
+
+
-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-
# Example configuration.yaml entry
-sensor:
-  platform: transmission
-  name: Transmission
-  host: 192.168.1.26
-  port: 9091
-  username: YOUR_USERNAME
-  password: YOUR_PASSWORD
-  monitored_variables:
-    - type: 'current_status'
-    - type: 'download_speed'
-    - type: 'upload_speed'
-
- - -

Modbus support
+

Modbus support
Kixam has contributed support for modbus, a serial communication protocol to control PLCs. It currently supports sensors and switches which can be controlled over serial, TCP and UDP connections.

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-18
-19
-20
-21
-22
-23
-24
-25
-26
-27
-28
-29
-30
-31
-32
-33
-34
-
# Example configuration.yaml entry
-modbus:
-  type: serial
-  method: rtu
-  port: /dev/ttyUSB0
-  baudrate: 9600
-  stopbits: 1
-  bytesize: 8
-  parity: N
-
-sensor:
-  platform: modbus
-  slave: 1
-  registers:
-    16:
-      name: My integer sensor
-        unit: C
-    24:
-      bits:
-        0:
-          name: My boolean sensor
-        2:
-          name: My other boolean sensor
-
-switch:
-  platform: modbus
-  slave: 1
-  registers:
-    24:
-      bits:
-        0:
-          name: My switch
-        2:
-          name: My other switch
-
+
+ 
# Example configuration.yaml entry
+modbus:
+  type: serial
+  method: rtu
+  port: /dev/ttyUSB0
+  baudrate: 9600
+  stopbits: 1
+  bytesize: 8
+  parity: N
 
+sensor:
+  platform: modbus
+  slave: 1
+  registers:
+    16:
+      name: My integer sensor
+        unit: C
+    24:
+      bits:
+        0:
+          name: My boolean sensor
+        2:
+          name: My other boolean sensor
+
+switch:
+  platform: modbus
+  slave: 1
+  registers:
+    24:
+      bits:
+        0:
+          name: My switch
+        2:
+          name: My other switch
+
+
+
]]> <![CDATA[Release notes for March 22, 2015]]> - 2015-03-22T00:21:00-08:00 + 2015-03-22T01:21:00-07:00 https://home-assistant.io/blog/2015/03/22/release-notes A new version of Home Assistant has just been pushed out. It contains bugfixes contributed by jamespcole, andythigpen, trainman419 and me. It also adds a bunch of great new features:

-

Script
+

Script
Andythigpen has contributed a script component. This allows users to create a sequence of service calls and delays. Scripts can be started using the service script/turn_on and interrupted using the service script/turn_off. A separate page has been added to the frontend to see the status of your scripts.

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-15
-16
-17
-
# Example configuration.yaml entry
-script:
-  # Turns on the bedroom lights and then the living room lights 1 minute later
-  wakeup:
-    alias: Wake Up
-    sequence:
-      - alias: Bedroom lights on
-        execute_service: light.turn_on
-        service_data:
-          entity_id: group.bedroom
-      - delay:
-          # supports seconds, milliseconds, minutes, hours, etc.
-          minutes: 1
-      - alias: Living room lights on
-        execute_service: light.turn_on
-        service_data:
-          entity_id: group.living_room
-
- - - +
+ 
# Example configuration.yaml entry
+script:
+  # Turns on the bedroom lights and then the living room lights 1 minute later
+  wakeup:
+    alias: Wake Up
+    sequence:
+      - alias: Bedroom lights on
+        execute_service: light.turn_on
+        service_data:
+          entity_id: group.bedroom
+      - delay:
+          # supports seconds, milliseconds, minutes, hours, etc.
+          minutes: 1
+      - alias: Living room lights on
+        execute_service: light.turn_on
+        service_data:
+          entity_id: group.living_room
+
+
+
- -

Scene
+

Scene
I (Paulus) have contributed a scene component. A user can create scenes that capture the states you want certain entities to be. For example a scene can contain that light A should be turned on and light B should be bright red. Deactivating a scene will restore the previous state from before the scene was activated. Just like scripts, scenes have their own separate page to see which scenes are on.

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-
# Example configuration.yaml entry
-scene:
-  - name: Romantic
-    entities:
-      light.tv_back_light: on
-      light.ceiling:
-        state: on
-        color: [0.33, 0.66]
-        brightness: 200
-
+
+ 
# Example configuration.yaml entry
+scene:
+  - name: Romantic
+    entities:
+      light.tv_back_light: on
+      light.ceiling:
+        state: on
+        color: [0.33, 0.66]
+        brightness: 200
+
+
+
+


+SABnzbd
+ James Cole has contributed support to integrate SABnzbd. This will allow you to monitor your downloads from within Home Assistant and setup automation based on the information.

-

-SABnzbd
- -James Cole has contributed support to integrate SABnzbd. This will allow you to monitor your downloads from within Home Assistant and setup automation based on the information.

+
+ 
# Example configuration.yaml entry
+sensor:
+  - platform: sabnzbd
+    name: SAB
+    api_key: YOUR_API_KEY
+    # Example: http://192.168.1.32:8124/
+    base_url: YOUR_SABNZBD_BASE_URL
+    monitored_variables:
+        - type: 'current_status'
+        - type: 'speed'
+        - type: 'queue_size'
+        - type: 'queue_remaining'
+        - type: 'disk_size'
+        - type: 'disk_free'
+
+
+
-
1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
-12
-13
-14
-
# Example configuration.yaml entry
-sensor:
-  - platform: sabnzbd
-    name: SAB
-    api_key: YOUR_API_KEY
-    # Example: http://192.168.1.32:8124/
-    base_url: YOUR_SABNZBD_BASE_URL
-    monitored_variables:
-        - type: 'current_status'
-        - type: 'speed'
-        - type: 'queue_size'
-        - type: 'queue_remaining'
-        - type: 'disk_size'
-        - type: 'disk_free'
-
- - -

-PushOver
- -James Cole has also contributed support for the PushOver service as a platform for the notify component. This allows components to send messages to the user using PushOver.

- -
1
-2
-3
-4
-5
-6
-7
-
# Example configuration.yaml entry
-notify:
-    platform: pushover
-    # Get this by registering a new application on https://pushover.net
-    api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
-    # Get this by logging into your account on https://pushover.net
-    user_key: ABCDEFGHJKLMNOPQRSTUVXYZ
-
+


+PushOver
+ James Cole has also contributed support for the PushOver service as a platform for the notify component. This allows components to send messages to the user using PushOver.

+
+ 
# Example configuration.yaml entry
+notify:
+    platform: pushover
+    # Get this by registering a new application on https://pushover.net
+    api_key: ABCDEFGHJKLMNOPQRSTUVXYZ
+    # Get this by logging into your account on https://pushover.net
+    user_key: ABCDEFGHJKLMNOPQRSTUVXYZ
+
+
+
]]> <![CDATA[Release notes for March 11, 2015]]> - 2015-03-11T18:36:00-08:00 + 2015-03-11T19:36:00-07:00 https://home-assistant.io/blog/2015/03/11/release-notes It has only been a little over a week since Theodor introduced YAML support for Home Assistant but so much has already happened that it is time for a summary of recent changes. Before mentioning the highlights I want to thank andythigpen, jamespcole and theolind for numerous bug fixes, enhancements and new contributions. Thanks!

-

Monitor local resources.
+

Monitor local resources.

Theodor has contributed a new sensor platform to allow you to monitor disk usage, memory usage, CPU usage and running processes. This platform has superseded the process component which is now considered deprecated.

-
1
-2
-3
-4
-5
-6
-7
-8
-9
-
# Example configuration.yaml entry
-sensor:
-  - platform: systemmonitor
-    resources:
-      - type: disk_use_percent
-        arg: /home
-      - type: memory_free
-      - type: process
-        arg: kodi
-
+
+ 
# Example configuration.yaml entry
+sensor:
+  - platform: systemmonitor
+    resources:
+      - type: disk_use_percent
+        arg: /home
+      - type: memory_free
+      - type: process
+        arg: kodi
+
+
+
- -

Experimental Z-Wave support
+

Experimental Z-Wave support

There is now experimental support for connecting Z-Wave networks using a Z-Wave USB stick. Right now it only integrates Z-Wave sensors into Home Assistant. Our goal is to get this tested by more people before adding support for other Z-Wave devices.

-

The new component is built on top of python-openzwave. This package is currently not distributed on PyPi so we’ve added a script scripts/build_python_openzwave to install it on your machine. Alternatively you can use the Docker image which is ready to go.

+

The new component is built on top of python-openzwave. This package is currently not distributed on PyPi so we’ve added a script scripts/build_python_openzwave to install it on your machine. Alternatively you can use the Docker image which is ready to go.

The development was done using an AEON Z-Wave USB stick and an AEON Z-Wave MultiSensor.

-
1
-2
-3
-
# Example configuration.yaml entry
-zwave:
-  usb_path: /dev/ttyUSB0
-
+
+ 
# Example configuration.yaml entry
+zwave:
+  usb_path: /dev/ttyUSB0
+
+
+
- -

Voice control
+

Voice control

An initial version of voice control for Home Assistant has landed. The current implementation consists of two parts.

The first part is a component called conversation that exposes the service conversation/process. This service is capable of processing text and translating them into commands for devices. For now it will only support commands in the format of Turn <Friendly Name> <on/off>.

-

The second part is an upgrade to the frontend to use the speech-to-text in Chrome to allow users to speak commands. If you’re using Chrome, you can test this out in the demo.

- -
1
-2
-
# Example configuration.yaml entry
-conversation:
-
+

The second part is an upgrade to the frontend to use the speech-to-text in Chrome to allow users to speak commands. If you’re using Chrome, you can test this out in the demo.

+
+ 
# Example configuration.yaml entry
+conversation:
+
+
+
]]> @@ -2880,15 +2310,14 @@ An initial version of voice control for Home Assistant has landed. The current i 2015-03-08T23:16:10-07:00 https://home-assistant.io/blog/2015/03/08/new-logo - It is well known that you are either a good programmer or a good designer. It’s rare you’ll meet someone that is both. That’s why it wasn’t surprising to anyone that the logo that I made was mediocre — at best. Luckily, Jeremy Geltman has come to the rescue and contributed a brand new logo for Home Assistant.

+ It is well known that you are either a good programmer or a good designer. It’s rare you’ll meet someone that is both. That’s why it wasn’t surprising to anyone that the logo that I made was mediocre — at best. Luckily, Jeremy Geltman has come to the rescue and contributed a brand new logo for Home Assistant.

The new logo follows Googles material design spec. It uses the blue color that Home Assistant uses in the interface and it comes in two versions: a high detailed version (for homescreen icon etc) and a simple version (for favicon etc).

-

- +

+ The old logo, the new detailed logo and the new simple logo.

- ]]> diff --git a/blog/2014/12/18/website-launched/index.html b/blog/2014/12/18/website-launched/index.html index de3067575c..e78f2e4c27 100644 --- a/blog/2014/12/18/website-launched/index.html +++ b/blog/2014/12/18/website-launched/index.html @@ -5,8 +5,6 @@ - - @@ -32,7 +30,6 @@ -
@@ -54,10 +51,10 @@ Getting started @@ -65,26 +62,24 @@
  • Developers
  • Blog
  • Need help?
    • - -
    @@ -98,6 +93,7 @@ - +

    Comments

    -
    -
    +
    @@ -170,7 +142,6 @@ -