+ Home Assistant Podcast #4
+ +We quickly cover off a few community items including the move to Discord and Carlo talks with Phil about his use of Floorplan.
+ +
+
+Last Wednesday we released Hass.io, an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
+ +The launch has been crazy successful. The 20 minute introduction video by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.
+ +Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
+ +Adding the power of voice to integrations
+ +Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
+ +But enough about Hass.io, let’s not forget about Home Assistant. This release has completely revamped the way how we deal with voice integrations. We turned Home Assistant into a platform to write voice apps, no matter where the processing of the voice happens. This can be done by Alexa, Google Assistant or in the Home Assistant user interface.
+ +We are super excited about the new functionality and hope that it will trigger a new type of applications and systems to be built on top of Home Assistant. This release includes a shopping list to show the new functionality. As a user you can add any item to the shopping list with your voice and also ask what is on your shopping list.
+ +# Example configuration.yaml entry
+shopping_list:
+To make testing these applications easier, we’ve updated the conversation component. The component will now allow sentences to be configured that hook directly into the new voice functionality. Combined with the new interface it will allow for some great interactions!
+ + + +History improvements
+ +@OverloadUT has been recently spending a lot of time on optimizing the history database queries. This release includes PR #8632, the first in a list of improvements that he is working on. This PR greatly improves requests for single entities by using an optimized query for this use case.
+ +The performance change in some of his tests shows this change to be about 300x faster (30 seconds to 0.1 seconds!) (There is no theoretical upper limit due to the issue with multi-entity queries getting worse the longer the current recorder run has been going.)
+ +Xiaomi integration
+ +Yes, it has happened! After being in beta for a while, the Xiaomi support is now available to all. @danielhiversen did an amazing job and we now support sensors, switches, lights and covers.
+ +Velbus integration
+ +Another awesome integration is that of the Velbus home automation system which has been contributed by @thomasdelaet. It integrates their sensors, covers, fans, lights and switches.
+ +Manual alarm with MQTT control
+ +A new version of the manual alarm component is now available with full MQTT control thanks to @colinodell. Using this you can build your own control panel to remotely arm/disarm the alarm. For example, using a Raspberry Pi to create an alarm.
+ +New Platforms
+ +-
+
- Initial support for Google Wifi/OnHub (@fronzbot - #8485) (sensor.google_wifi docs) (new-platform) +
- Xiaomi gw support (@danielhiversen - #8555) (xiaomi docs) (binary_sensor.xiaomi docs) (cover.xiaomi docs) (light.xiaomi docs) (sensor.xiaomi docs) (switch.xiaomi docs) (new-platform) +
- Add Intent component (@balloob - #8434) (alexa docs) (intent docs) (intent_script docs) (shopping_list docs) (snips docs) (breaking change) (new-platform) +
- Manual alarm with MQTT control (@colinodell - #8257) (alarm_control_panel.manual_mqtt docs) (new-platform) +
- Add component Light TPLink (@gollo - #8643) (light.tplink docs) (new-platform) +
- Velbus (@thomasdelaet - #8076) (velbus docs) (binary_sensor.velbus docs) (light.velbus docs) (new-platform) +
- Add uk_transport component. (@robmarkcole - #8600) (sensor.uk_transport docs) (new-platform) +
If you need help…
+…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+ +Reporting Issues
+Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
+ + +Breaking Changes
+ +-
+
- Automations: The state trigger keyword
stateand the time trigger keywordafterwere deprecated in 0.46. They have now been removed. (@amelchio - #8510) (automation.state docs) (automation.time docs) (breaking change)
+ - Wink: the component is no longer supporting the
access_tokenin the config. Use the new OAuth authentication or add your username and password to the config. (@w1ll1am23 - #8208) (wink docs) (breaking change)
+ - Alexa/API.AI/Snips.ai/Conversation: configuring responses to intents/sentences has been moved to a new component called
intent_script. Conversation now allows configuring sentences to map to intents. (@balloob - #8434) (alexa docs) (intent docs) (intent_script docs) + (shopping_list docs) (snips docs) (breaking change) (new-platform)
+
alexa:
+snips:
+apiai:
+
+intent_script:
+ LightKitchen:
+ speech:
+ type: plain
+ text: I did the work, yay.
+ card:
+ type: simple
+ title: Lights Card
+ content: I have turned on the lights.
+ action:
+ service: light.turn_on
+ data:
+ entity_id: light.kitchen
+
+conversation:
+ intents:
+ LightKitchen:
+ - The kitchen is magic
+-
+
- Switch fritzdect: attributes have been renamed to use underscores and no capital letters (@thomasklingbeil - #8436) (switch.fritzdect docs) (breaking change) +
- Yahoo Weather: no longer allow configuring forecasts but include all instead. (@fanthos - #8626) (weather.yweather docs) (breaking change) +
- The Home Assistant Z-Wave Cover implementation has been updated to support the latest development version of OpenZWave. If you are currently applying a workaround to your OpenZWave installation to support the barrier command class, you’ll need to make sure you update your workaround to the latest development version of OpenZWave. (@firstof9 - #8574) (cover docs) (cover.zwave docs) (breaking change) +
All changes
+ +-
+
- Make deps directory persistent over upgrades (@MartinHjelmare - #7801) +
- Fix check for running inside venv (@MartinHjelmare - #8481) +
- Bump to KNXIP 0.5 (@open-homeautomation - #8492) (knx docs) +
- Expose all components on hass [Concept] (@balloob - #8490) (light docs) +
- Add bind_hass to components (@balloob - #8502) +
- Persistent notification import (@balloob - #8507) +
- Added additional attributes to OwnTracks device_tracker (@binarybucks - #8503) (device_tracker.owntracks docs) +
- Added sensor state rounding (@fronzbot - #8499) (sensor.pi_hole docs) +
- fix for a bug introduced with media support in #8282 (@MikeChristianson - #8513) (notify.twitter docs) +
- handle timeout errors without logging.exception when updating hue lights; double quotes in log msgs (@azogue - #8524) (light.hue docs) +
- Remove deprecated automation keywords (@amelchio - #8510) (automation.state docs) (automation.time docs) (breaking change) +
- Citybikes: Allow None as result for empty slots (@janLo - #8528) (sensor.citybikes docs) +
- Return a 0 temperature value when none is found (@phil-lavin - #8518) (climate.maxcube docs) +
- Fix #6469 and #6828 (@titilambert - #8537) (sensor.hydroquebec docs) +
- Update docstrings (@fabaff - #8536) +
- Upgrade TwitterAPI to 2.4.6 (@fabaff - #8535) (notify.twitter docs) +
- Decora: Fix set brightness and improve reconnection (@titilambert - #8522) (light.decora docs) +
- Initial support for Google Wifi/OnHub (@fronzbot - #8485) (sensor.google_wifi docs) (new-platform) +
- Fix exception dlib_face_identify when image is not recognized by face_recognition module (@tchellomello - #8552) (image_processing.dlib_face_identify docs) +
- [media_extractor] Add support for custom stream queries for media_extractor (@minchik - #8538) (media_extractor docs) +
- Report Harmony remote off if state is unknown (@jawilson - #8547) (remote.harmony docs) +
- Upgrade the alarmdecoder dependency library from 0.12.1 to 0.12.3. (@viswa-swami - #8542) (alarmdecoder docs) +
- turn_on_action and turn_off_action with script syntax (@azogue - #8558) (media_player.kodi docs) +
- Extends Pi-hole sensor to support the new sensors: (@tchellomello - #8549) (sensor.pi_hole docs) +
- Support for Wink Switch and Light groups also fix fan speed selection (@w1ll1am23 - #8501) (wink docs) (fan.wink docs) (light.wink docs) (switch.wink docs) +
- Added a service to write to KNX group addressed including documentation (@open-homeautomation - #8491) (knx docs) +
- Handle manual edits to emulated_hue_ids.json (@jawilson - #8560) (emulated_hue docs) +
- Enhance python_script to support “getitem” (@sdague - #8541) (python_script docs) +
- Update persistent deps dir version in config.py (@balloob - #8479) +
- Xiaomi gw support (@danielhiversen - #8555) (xiaomi docs) (binary_sensor.xiaomi docs) (cover.xiaomi docs) (light.xiaomi docs) (sensor.xiaomi docs) (switch.xiaomi docs) (new-platform) +
- fix #8263 corrected Adafruit DHT library version from 1.3.0 to 1.3.2 (@namadori - #8562) (sensor.dht docs) +
- xiaomi bug fix (@danielhiversen - #8576) (binary_sensor.xiaomi docs) +
- Bumped python-simplisafe version (@bachya - #8578) (alarm_control_panel.simplisafe docs) +
- Added Time Remaining and Time Elapsed sensors for octoprint (@w1ll1am23 - #8581) (sensor.octoprint docs) +
- upgade xiaomi lib to 0.2 (@danielhiversen - #8584) (xiaomi docs) +
- Device support for different new sensors of the xiaomi aqara gateway (@syssi - #8577) (xiaomi docs) (binary_sensor.xiaomi docs) (sensor.xiaomi docs) (switch.xiaomi docs) +
- Extends Fitbit sensors to track the device battery level (@tchellomello - #8583) (sensor.fitbit docs) +
- xiaomi binary sensor bug fix (@danielhiversen - #8586) (binary_sensor.xiaomi docs) +
- upgrade pywebpush and PyJWT (@perosb - #8588) (notify.html5 docs) +
- Support for Wink oauth application authorization (@w1ll1am23 - #8208) (wink docs) (breaking change) +
- Add Intent component (@balloob - #8434) (alexa docs) (intent docs) (intent_script docs) (shopping_list docs) (snips docs) (breaking change) (new-platform) +
- Remove code in wink.py overwriting hass.data configurator (@w1ll1am23 - #8595) (wink docs) +
- bump python-mirobo version for more robust protocol handling, make the platform to update on startup (@rytilahti - #8602) (switch.xiaomi_vacuum docs) +
- Binary sensor ping fixed for hassio (@gollo - #8573) (binary_sensor.ping docs) +
- Simplified percent conversion, better logging (@open-homeautomation - #8568) (sensor.knx docs) +
- make attributes in the fritzdect module easier to process (@thomasklingbeil - #8436) (switch.fritzdect docs) (breaking change) +
- Allow set_cover_position in scenes (@peckham - #8613) +
- better but still not great (@cribbstechnologies - #8618) +
- Upgrade youtube_dl to 2017.7.23 (@fabaff - #8617) (media_extractor docs) +
- Upgrade mypy to 0.520 (@fabaff - #8616) +
- REST binary sensor value_template optional (@philhawthorne - #8596) (binary_sensor.rest docs) +
- added onvif camera fix for non-virtual env installations (@matt2005 - #8592) (camera.onvif docs) +
- Cleanup old device_tracker stuff (@pvizeli - #8627) +
- Add support for using credstash as a secret store (@justin8 - #8494) +
- Added support for default value when environment variable is missing (@devspacenine - #8484) +
- Manual alarm with MQTT control (@colinodell - #8257) (alarm_control_panel.manual_mqtt docs) (new-platform) +
- Catch and log Lyft API errors (@armills - #8635) (sensor.lyft docs) +
- Tweak conversation/intent/shopping list (@balloob - #8636) (conversation docs) (shopping_list docs) +
- Update dependencies cast + discovery (@balloob - #8646) (media_player.cast docs) +
- Add component Light TPLink (@gollo - #8643) (light.tplink docs) (new-platform) +
- Fixes Fitbit sensor to report battery level with the expected device (@tchellomello - #8647) (sensor.fitbit docs) +
- Upgrade aiolifx (@amelchio - #8648) (light.lifx docs) +
- Velbus (@thomasdelaet - #8076) (velbus docs) (binary_sensor.velbus docs) (light.velbus docs) (new-platform) +
- Yahoo Weather update, supports forecast for more days (@fanthos - #8626) (weather.yweather docs) (breaking change) +
- History performance improvements for single-entity requests (@OverloadUT - #8632) (history docs) +
- Add transition support to light.zha (@jawilson - #8548) (light.zha docs) +
- Add uk_transport component. (@robmarkcole - #8600) (sensor.uk_transport docs) (new-platform) +
- Added support for SerenaHoneycombShades to Lutron Caseta (@809694+kfcook - #8662) (cover.lutron_caseta docs) +
- MQTT Switch: add availability_topic for online/offline status (@abmantis - #8593) (mqtt docs) (switch.mqtt docs) +
- Adding support for mapping keys to value in statsd (@Khabi - #8665) (statsd docs) +
- Upgrade fuzzywuzzy to 0.15.1 (@fabaff - #8671) (conversation docs) +
- Upgrade libnacl to 1.5.2 (@fabaff - #8670) (device_tracker.owntracks docs) +
- Upgrade sqlalchemy to 1.1.12 (@fabaff - #8669) (recorder docs) +
- Upgrade pyhomematic to 0.1.30 (@danielperna84 - #8673) (homematic docs) +
- Hass.io: logo support / timeout handling (@pvizeli - #8668) (hassio docs) +
- Updated pysnmp to 4.3.9 (@bgehrich - #8675) (device_tracker.snmp docs) (sensor.snmp docs) +
- Fix COMMAND_CLASS_BARRIER_OPERATOR for dev branch of OpenZwave (@firstof9 - #8574) (cover docs) (cover.zwave docs) (breaking change) +
- Shopping List: edit name / complete status (@balloob - #8666) (shopping_list docs) +
- Support for Wink local control (@w1ll1am23 - #8607) (wink docs) +
- Persist shopping list + clear completed (@balloob - #8697) (shopping_list docs) +
We use Pivotal Tracker to track things that are in progress and what we might work on.
+]]> +
-
-
-Saw the announcement yesterday for HASSbian 1.21 and got super excited?
- -Today we’ll flash the latest HASSbian to a Raspbery Pi Zero W. -With an added bonus that besides for an USB cable for power, there’s no need for any cables!
- -What you’ll need:
--
-
- a Raspberry Pi Zero W (an amazing tiny computer with built-in wifi) -
- a microSD card -
- some source of USB power -
- Wifi -
- a desktop or laptop -
Let’s get to it!
- -First, download the HASSbian 1.21 image from here.
- -Unzip it.
- -Flash it to the microSD card. If you need a flash tool, try Etcher
- -When the flashing finishes, remove it and plug it back in. You should see a drive called “boot”.
- -Right in there, not in any folders, create a file called wpa_supplicant.conf.
The contents of the configuration file should be something like this: -(You may have to adjust for your configuration, hints here )
- -network={
- ssid="YOUR_WIFI_NETWORK_NAME_HERE"
- psk="YOUR_WIFI_PASSWORD_HERE"
- key_mgmt=WPA-PSK
-}
-Next stick your SD card into the Raspberry Pi Zero W, and plug it in.
- -After about a minute, use your SSH client to connect to HASSbian (or hassbian.local from a Mac), with the username pi. The default password is raspberry.
It’s a good idea to change the password. To do so, use the passwd command.
Next, type the following two commands into the SSH console:
- -$ sudo systemctl enable install_homeassistant.service
-$ sudo systemctl start install_homeassistant.service
-Wait about 15-20 minutes and voilà you have your Home Assistant on your Raspberry Pi Zero W in 30 minutes.
- -To try it out, go to http://hassbian:8123 or http://hassbian.local:8123 if you’re using Mac.
- -For further details about HASSbian, take a look at the documentation.
- -]]>Since I, the developer of HASSbian, have been moving, started a new job and so on I’ve had few moments over for HASSbian development. The 1.2 release has been in pre-release for a few months now and just not communicated out that well. Hopefully this release changes that and I’ll do my best to release more often. There’s no simple way to update from 1.1 to 1.21 but 95% of the changes can be done by installing the hassbian-config package. For more information have a look at the hassbian-config page.
- -Hassbian 1.22 - Sins of last night
-Development is sometimes fast and joyful but mistakes are made at times.
- -With the release of 1.21 a small problem with the OpenZWave build script wasn’t corrected even tough it was a known bug. Problem is simple as it’s only a problem with the symlink created for to the configuration folder for OpenZWave. This has been fixed and we bring some new things since they where ready anyway. The list below has been augmented with the updated information.
- -Hassbian-config
- -To allow you to customize your installation further, we have included a tool called hassbian-config. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the hassbian-scripts functionality from 1.1.
-
-
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai. -
- Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support. -
- Install Libcec. Adds local HDMI CEC support. -
- Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed. -
- Install Open Z-Wave. Installs Python Open Z-Wave and OZWCP from git. -
- Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and it’s usage is not recommended if you share your network with others. -
- Install Tellstick. Installs the Tellstick package for controlling and using a connected Tellstick. -
- Install Tradfri. Installs dependencies for using IKEA Trådfri. -
Spring cleaning
- -With this image there also quite a bit of cleaning of the base system and the script that generates our Raspberry Pi image.
- --
-
- Replaced the
hassbian-scriptsfolder withhassbian-config.
- - Update
pi-gen. Our build script has been upgraded to follow the Raspbian image closer once again. Now you could build this image with Docker if your so inclined.
- - Added libtool and autoconf package. Dependencies for some of the pip packages. -
- Pi ZeroW should now work with the image. -
To follow discussions about the development of the HASSbian image or to contribute join our Discord chat server.
- -To get started with the new image, check out the installation instructions in the getting started section.
- ]]>Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
--open-ui and
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
-
+
- + 0.50: Voice control, History improvements, and Xiaomi +
- Talk Python interview with Paulus Schoutsen
- Introducing Hass.io +
- + Home Assistant Podcast #4 +
- 0.49: Themes 🎨, kiosk mode and Prometheus.io -
- - Home Assistant Podcast #3 - -
- - Home Assistant is moving to Discord -
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
-
+
- + 0.50: Voice control, History improvements, and Xiaomi +
- Talk Python interview with Paulus Schoutsen
- Introducing Hass.io +
- + Home Assistant Podcast #4 +
- 0.49: Themes 🎨, kiosk mode and Prometheus.io -
- - Home Assistant Podcast #3 - -
- - Home Assistant is moving to Discord -
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
-
+
- + 0.50: Voice control, History improvements, and Xiaomi +
- Talk Python interview with Paulus Schoutsen
- Introducing Hass.io +
- + Home Assistant Podcast #4 +
- 0.49: Themes 🎨, kiosk mode and Prometheus.io -
- - Home Assistant Podcast #3 - -
- - Home Assistant is moving to Discord -
Recent Posts
Recent Posts
Recent Posts
Recent Posts
-
+
- + 0.50: Voice control, History improvements, and Xiaomi +
- Talk Python interview with Paulus Schoutsen
- Introducing Hass.io +
- + Home Assistant Podcast #4 +
- 0.49: Themes 🎨, kiosk mode and Prometheus.io -
- - Home Assistant Podcast #3 - -
- - Home Assistant is moving to Discord -
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
+ -
+ 0.50: Voice control, History improvements, and Xiaomi
+
-
Talk Python interview with Paulus Schoutsen
-
Introducing Hass.io
+ -
+ Home Assistant Podcast #4
+
-
0.49: Themes 🎨, kiosk mode and Prometheus.io
- -
- Home Assistant Podcast #3
-
- -
- Home Assistant is moving to Discord
-
diff --git a/blog/2017/02/04/hassbian-toybox/index.html b/blog/2017/02/04/hassbian-toybox/index.html
index fa32867e44..2195e2f82a 100644
--- a/blog/2017/02/04/hassbian-toybox/index.html
+++ b/blog/2017/02/04/hassbian-toybox/index.html
@@ -166,21 +166,21 @@ On the close horizon from @Landrash th
Recent Posts
diff --git a/blog/2017/02/11/alert-appletv-mqtt-yeelight/index.html b/blog/2017/02/11/alert-appletv-mqtt-yeelight/index.html
index 0ac7aa0b77..96277b2d02 100644
--- a/blog/2017/02/11/alert-appletv-mqtt-yeelight/index.html
+++ b/blog/2017/02/11/alert-appletv-mqtt-yeelight/index.html
@@ -253,21 +253,21 @@
Recent Posts
diff --git a/blog/2017/02/14/clt-workshop/index.html b/blog/2017/02/14/clt-workshop/index.html
index cdb81e43bd..fc1c437905 100644
--- a/blog/2017/02/14/clt-workshop/index.html
+++ b/blog/2017/02/14/clt-workshop/index.html
@@ -136,21 +136,21 @@
Recent Posts
diff --git a/blog/2017/02/22/home-assistant-tshirts-have-arrived/index.html b/blog/2017/02/22/home-assistant-tshirts-have-arrived/index.html
index 2746cb7b98..fb34d3bd9a 100644
--- a/blog/2017/02/22/home-assistant-tshirts-have-arrived/index.html
+++ b/blog/2017/02/22/home-assistant-tshirts-have-arrived/index.html
@@ -170,21 +170,21 @@
Recent Posts
diff --git a/blog/2017/02/25/config-panel-and-state-restoration/index.html b/blog/2017/02/25/config-panel-and-state-restoration/index.html
index 15a2d0938b..a0cd939537 100644
--- a/blog/2017/02/25/config-panel-and-state-restoration/index.html
+++ b/blog/2017/02/25/config-panel-and-state-restoration/index.html
@@ -308,21 +308,21 @@
Recent Posts
diff --git a/blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/index.html b/blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/index.html
index 64c7c983fa..7ecdb994e4 100644
--- a/blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/index.html
+++ b/blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/index.html
@@ -341,21 +341,21 @@ Screenshot of all the different functionality the IP webcam integration offers.
Recent Posts
diff --git a/blog/2017/03/22/broken-dependencies/index.html b/blog/2017/03/22/broken-dependencies/index.html
index fec80d3007..6d1b6ed587 100644
--- a/blog/2017/03/22/broken-dependencies/index.html
+++ b/blog/2017/03/22/broken-dependencies/index.html
@@ -138,21 +138,21 @@
Recent Posts
diff --git a/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/index.html b/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/index.html
index a0bfb8be4b..8fdbeca163 100644
--- a/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/index.html
+++ b/blog/2017/03/23/opensourcecraft-interview-with-founder-paulus-schoutsen/index.html
@@ -131,21 +131,21 @@
Recent Posts
diff --git a/blog/2017/03/25/todo-volumio-workday/index.html b/blog/2017/03/25/todo-volumio-workday/index.html
index 00165ff075..542552ee3a 100644
--- a/blog/2017/03/25/todo-volumio-workday/index.html
+++ b/blog/2017/03/25/todo-volumio-workday/index.html
@@ -286,21 +286,21 @@
Recent Posts
diff --git a/blog/2017/03/28/http-to-mqtt-bridge/index.html b/blog/2017/03/28/http-to-mqtt-bridge/index.html
index 312306b341..2d1af95d49 100644
--- a/blog/2017/03/28/http-to-mqtt-bridge/index.html
+++ b/blog/2017/03/28/http-to-mqtt-bridge/index.html
@@ -179,21 +179,21 @@
Recent Posts
diff --git a/blog/2017/04/01/thomas-krenn-award/index.html b/blog/2017/04/01/thomas-krenn-award/index.html
index 39b79fa984..5b2a116976 100644
--- a/blog/2017/04/01/thomas-krenn-award/index.html
+++ b/blog/2017/04/01/thomas-krenn-award/index.html
@@ -140,21 +140,21 @@
Recent Posts
diff --git a/blog/2017/04/08/eddystone-beacons-lockitron-locks-total-connect/index.html b/blog/2017/04/08/eddystone-beacons-lockitron-locks-total-connect/index.html
index 5b95d955e5..0aa414e676 100644
--- a/blog/2017/04/08/eddystone-beacons-lockitron-locks-total-connect/index.html
+++ b/blog/2017/04/08/eddystone-beacons-lockitron-locks-total-connect/index.html
@@ -339,21 +339,21 @@
Recent Posts
diff --git a/blog/2017/04/15/ios/index.html b/blog/2017/04/15/ios/index.html
index e6512e8f32..d03136b1c2 100644
--- a/blog/2017/04/15/ios/index.html
+++ b/blog/2017/04/15/ios/index.html
@@ -143,21 +143,21 @@
Recent Posts
diff --git a/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html b/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html
index ccfdfee9b4..91d2fe7be4 100644
--- a/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html
+++ b/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html
@@ -196,21 +196,21 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
Recent Posts
diff --git a/blog/2017/04/22/ikea-tradfri-spotify/index.html b/blog/2017/04/22/ikea-tradfri-spotify/index.html
index a62f66eb4d..78d2473b48 100644
--- a/blog/2017/04/22/ikea-tradfri-spotify/index.html
+++ b/blog/2017/04/22/ikea-tradfri-spotify/index.html
@@ -341,21 +341,21 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
Recent Posts
diff --git a/blog/2017/04/24/hardware-contest-2017/index.html b/blog/2017/04/24/hardware-contest-2017/index.html
index 5d89faa584..c76609e1f4 100644
--- a/blog/2017/04/24/hardware-contest-2017/index.html
+++ b/blog/2017/04/24/hardware-contest-2017/index.html
@@ -136,21 +136,21 @@
Recent Posts
diff --git a/blog/2017/04/25/influxdb-grafana-docker/index.html b/blog/2017/04/25/influxdb-grafana-docker/index.html
index 6d643097f8..51e3a8fdc8 100644
--- a/blog/2017/04/25/influxdb-grafana-docker/index.html
+++ b/blog/2017/04/25/influxdb-grafana-docker/index.html
@@ -178,21 +178,21 @@
Recent Posts
diff --git a/blog/2017/04/30/hassbian-1.21-its-about-time/index.html b/blog/2017/04/30/hassbian-1.21-its-about-time/index.html
index cf6fdfbfcb..38230ba2a8 100644
--- a/blog/2017/04/30/hassbian-1.21-its-about-time/index.html
+++ b/blog/2017/04/30/hassbian-1.21-its-about-time/index.html
@@ -153,21 +153,21 @@
Recent Posts
diff --git a/blog/2017/05/01/home-assistant-on-raspberry-pi-zero-in-30-minutes/index.html b/blog/2017/05/01/home-assistant-on-raspberry-pi-zero-in-30-minutes/index.html
index b0e65dc67d..d03ee0630a 100644
--- a/blog/2017/05/01/home-assistant-on-raspberry-pi-zero-in-30-minutes/index.html
+++ b/blog/2017/05/01/home-assistant-on-raspberry-pi-zero-in-30-minutes/index.html
@@ -167,21 +167,21 @@ $ sudo systemctl start install_homeassistant.service
Recent Posts
diff --git a/blog/2017/05/05/podcast-init-interview/index.html b/blog/2017/05/05/podcast-init-interview/index.html
index f5be6f912f..0e56400083 100644
--- a/blog/2017/05/05/podcast-init-interview/index.html
+++ b/blog/2017/05/05/podcast-init-interview/index.html
@@ -132,21 +132,21 @@
Recent Posts
diff --git a/blog/2017/05/06/zigbee-opencv-dlib/index.html b/blog/2017/05/06/zigbee-opencv-dlib/index.html
index 2069a1d988..435a1bc5b9 100644
--- a/blog/2017/05/06/zigbee-opencv-dlib/index.html
+++ b/blog/2017/05/06/zigbee-opencv-dlib/index.html
@@ -330,21 +330,21 @@
Recent Posts
diff --git a/blog/2017/05/07/grazer-linuxtage-2017-talk-python-everywhere/index.html b/blog/2017/05/07/grazer-linuxtage-2017-talk-python-everywhere/index.html
index db5c07554c..bf9c6f101c 100644
--- a/blog/2017/05/07/grazer-linuxtage-2017-talk-python-everywhere/index.html
+++ b/blog/2017/05/07/grazer-linuxtage-2017-talk-python-everywhere/index.html
@@ -133,21 +133,21 @@
Recent Posts
diff --git a/blog/2017/05/13/home-assistant-on-orange-pi-zero/index.html b/blog/2017/05/13/home-assistant-on-orange-pi-zero/index.html
index 785e680b4a..80b200e50b 100644
--- a/blog/2017/05/13/home-assistant-on-orange-pi-zero/index.html
+++ b/blog/2017/05/13/home-assistant-on-orange-pi-zero/index.html
@@ -236,21 +236,21 @@ Reading package lists... Done
Recent Posts
diff --git a/blog/2017/05/19/home-assistant-at-pycon-us-2017/index.html b/blog/2017/05/19/home-assistant-at-pycon-us-2017/index.html
index 5ecc0338fc..62d5fe10ca 100644
--- a/blog/2017/05/19/home-assistant-at-pycon-us-2017/index.html
+++ b/blog/2017/05/19/home-assistant-at-pycon-us-2017/index.html
@@ -131,21 +131,21 @@
Recent Posts
diff --git a/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html b/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
index c43323e081..321b97a248 100644
--- a/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
+++ b/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
@@ -289,21 +289,21 @@ If you have a security key set in your Open Z-Wave
Recent Posts
+ -
+ 0.50: Voice control, History improvements, and Xiaomi
+
-
Talk Python interview with Paulus Schoutsen
-
Introducing Hass.io
+ -
+ Home Assistant Podcast #4
+
-
0.49: Themes 🎨, kiosk mode and Prometheus.io
- -
- Home Assistant Podcast #3
-
- -
- Home Assistant is moving to Discord
-
diff --git a/blog/2017/06/02/home-assistant-podcast-1/index.html b/blog/2017/06/02/home-assistant-podcast-1/index.html
index f464b1014a..3d75cfd613 100644
--- a/blog/2017/06/02/home-assistant-podcast-1/index.html
+++ b/blog/2017/06/02/home-assistant-podcast-1/index.html
@@ -132,21 +132,21 @@
Recent Posts
diff --git a/blog/2017/06/04/release-46/index.html b/blog/2017/06/04/release-46/index.html
index 2698ada496..14a5578b57 100644
--- a/blog/2017/06/04/release-46/index.html
+++ b/blog/2017/06/04/release-46/index.html
@@ -275,21 +275,21 @@
Recent Posts
diff --git a/blog/2017/06/10/interview-with-jupiter-broadcasting/index.html b/blog/2017/06/10/interview-with-jupiter-broadcasting/index.html
index 8310eea122..375303abc6 100644
--- a/blog/2017/06/10/interview-with-jupiter-broadcasting/index.html
+++ b/blog/2017/06/10/interview-with-jupiter-broadcasting/index.html
@@ -131,21 +131,21 @@
Recent Posts
diff --git a/blog/2017/06/15/zwave-entity-ids/index.html b/blog/2017/06/15/zwave-entity-ids/index.html
index 4136740b43..05aee7ef60 100644
--- a/blog/2017/06/15/zwave-entity-ids/index.html
+++ b/blog/2017/06/15/zwave-entity-ids/index.html
@@ -131,21 +131,21 @@
Recent Posts
diff --git a/blog/2017/06/17/release-47/index.html b/blog/2017/06/17/release-47/index.html
index e281f884ae..3ead8df6a2 100644
--- a/blog/2017/06/17/release-47/index.html
+++ b/blog/2017/06/17/release-47/index.html
@@ -372,21 +372,21 @@ trigger:
Recent Posts
diff --git a/blog/2017/06/20/things-you-should-know-about-senic-covi/index.html b/blog/2017/06/20/things-you-should-know-about-senic-covi/index.html
index 47dd90dc77..a26e08d003 100644
--- a/blog/2017/06/20/things-you-should-know-about-senic-covi/index.html
+++ b/blog/2017/06/20/things-you-should-know-about-senic-covi/index.html
@@ -155,21 +155,21 @@ Core Developer, Home Assistant
Recent Posts
diff --git a/blog/2017/07/02/release-48/index.html b/blog/2017/07/02/release-48/index.html
index a2281a10d5..2140b3e155 100644
--- a/blog/2017/07/02/release-48/index.html
+++ b/blog/2017/07/02/release-48/index.html
@@ -342,21 +342,21 @@
Recent Posts
diff --git a/blog/2017/07/03/home-assistant-is-moving-to-discord/index.html b/blog/2017/07/03/home-assistant-is-moving-to-discord/index.html
index 207c1a8b17..ef45a7129e 100644
--- a/blog/2017/07/03/home-assistant-is-moving-to-discord/index.html
+++ b/blog/2017/07/03/home-assistant-is-moving-to-discord/index.html
@@ -178,6 +178,9 @@ Community Leader, Home Assistant
Recent Posts
+ -
+ 0.50: Voice control, History improvements, and Xiaomi
+
-
Talk Python interview with Paulus Schoutsen
@@ -185,10 +188,10 @@ Community Leader, Home Assistant
Introducing Hass.io
-
- 0.49: Themes 🎨, kiosk mode and Prometheus.io
+ Home Assistant Podcast #4
-
- Home Assistant Podcast #3
+ 0.49: Themes 🎨, kiosk mode and Prometheus.io
diff --git a/blog/2017/07/05/hasspodcast-ep-3/index.html b/blog/2017/07/05/hasspodcast-ep-3/index.html
index 3e04b2f06f..f2094227fa 100644
--- a/blog/2017/07/05/hasspodcast-ep-3/index.html
+++ b/blog/2017/07/05/hasspodcast-ep-3/index.html
@@ -129,6 +129,9 @@
Recent Posts
+ -
+ 0.50: Voice control, History improvements, and Xiaomi
+
-
Talk Python interview with Paulus Schoutsen
@@ -136,10 +139,10 @@
Introducing Hass.io
-
- 0.49: Themes 🎨, kiosk mode and Prometheus.io
+ Home Assistant Podcast #4
-
- Home Assistant is moving to Discord
+ 0.49: Themes 🎨, kiosk mode and Prometheus.io
diff --git a/blog/2017/07/15/release-49/index.html b/blog/2017/07/15/release-49/index.html
index 19f8cf8634..6f9ac38437 100644
--- a/blog/2017/07/15/release-49/index.html
+++ b/blog/2017/07/15/release-49/index.html
@@ -328,6 +328,9 @@ Screenshot of a green dashboard
Recent Posts
+ -
+ 0.50: Voice control, History improvements, and Xiaomi
+
-
Talk Python interview with Paulus Schoutsen
@@ -335,10 +338,7 @@ Screenshot of a green dashboard
Introducing Hass.io
-
- Home Assistant Podcast #3
-
- -
- Home Assistant is moving to Discord
+ Home Assistant Podcast #4
diff --git a/blog/2017/07/17/hasspodcast-ep-4/index.html b/blog/2017/07/17/hasspodcast-ep-4/index.html
new file mode 100644
index 0000000000..5ac5aeb96d
--- /dev/null
+++ b/blog/2017/07/17/hasspodcast-ep-4/index.html
@@ -0,0 +1,209 @@
+
+
+
+
+
+
+
+
+ Home Assistant Podcast #4 - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Comments
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/blog/2017/07/25/introducing-hassio/index.html b/blog/2017/07/25/introducing-hassio/index.html
index f205b0f383..60d8503e31 100644
--- a/blog/2017/07/25/introducing-hassio/index.html
+++ b/blog/2017/07/25/introducing-hassio/index.html
@@ -163,18 +163,18 @@ Hass.io dashboard
Recent Posts
diff --git a/blog/2017/07/27/talk-python-podcast/index.html b/blog/2017/07/27/talk-python-podcast/index.html
index 43ecd96aa4..8e56ea3615 100644
--- a/blog/2017/07/27/talk-python-podcast/index.html
+++ b/blog/2017/07/27/talk-python-podcast/index.html
@@ -132,18 +132,18 @@
Recent Posts
diff --git a/blog/2017/07/29/release-50/index.html b/blog/2017/07/29/release-50/index.html
new file mode 100644
index 0000000000..91d7e1144b
--- /dev/null
+++ b/blog/2017/07/29/release-50/index.html
@@ -0,0 +1,364 @@
+
+
+
+
+
+
+
+
+ 0.50: Voice control, History improvements, and Xiaomi - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 0.50: Voice control, History improvements, and Xiaomi
+
+
+ 
+Last Wednesday we released Hass.io, an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
+The launch has been crazy successful. The 20 minute introduction video by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.
+Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
+ Adding the power of voice to integrations
+Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
+But enough about Hass.io, let’s not forget about Home Assistant. This release has completely revamped the way how we deal with voice integrations. We turned Home Assistant into a platform to write voice apps, no matter where the processing of the voice happens. This can be done by Alexa, Google Assistant or in the Home Assistant user interface.
+We are super excited about the new functionality and hope that it will trigger a new type of applications and systems to be built on top of Home Assistant. This release includes a shopping list to show the new functionality. As a user you can add any item to the shopping list with your voice and also ask what is on your shopping list.
+# Example configuration.yaml entry
+shopping_list:
+
+
+To make testing these applications easier, we’ve updated the conversation component. The component will now allow sentences to be configured that hook directly into the new voice functionality. Combined with the new interface it will allow for some great interactions!
+
+ History improvements
+@OverloadUT has been recently spending a lot of time on optimizing the history database queries. This release includes PR #8632, the first in a list of improvements that he is working on. This PR greatly improves requests for single entities by using an optimized query for this use case.
+The performance change in some of his tests shows this change to be about 300x faster (30 seconds to 0.1 seconds!) (There is no theoretical upper limit due to the issue with multi-entity queries getting worse the longer the current recorder run has been going.)
+ Xiaomi integration
+Yes, it has happened! After being in beta for a while, the Xiaomi support is now available to all. @danielhiversen did an amazing job and we now support sensors, switches, lights and covers.
+ Velbus integration
+Another awesome integration is that of the Velbus home automation system which has been contributed by @thomasdelaet. It integrates their sensors, covers, fans, lights and switches.
+ Manual alarm with MQTT control
+A new version of the manual alarm component is now available with full MQTT control thanks to @colinodell. Using this you can build your own control panel to remotely arm/disarm the alarm. For example, using a Raspberry Pi to create an alarm.
+ New Platforms
+
+ - Initial support for Google Wifi/OnHub (@fronzbot - #8485) (sensor.google_wifi docs) (new-platform)
+ - Xiaomi gw support (@danielhiversen - #8555) (xiaomi docs) (binary_sensor.xiaomi docs) (cover.xiaomi docs) (light.xiaomi docs) (sensor.xiaomi docs) (switch.xiaomi docs) (new-platform)
+ - Add Intent component (@balloob - #8434) (alexa docs) (intent docs) (intent_script docs) (shopping_list docs) (snips docs) (breaking change) (new-platform)
+ - Manual alarm with MQTT control (@colinodell - #8257) (alarm_control_panel.manual_mqtt docs) (new-platform)
+ - Add component Light TPLink (@gollo - #8643) (light.tplink docs) (new-platform)
+ - Velbus (@thomasdelaet - #8076) (velbus docs) (binary_sensor.velbus docs) (light.velbus docs) (new-platform)
+ - Add uk_transport component. (@robmarkcole - #8600) (sensor.uk_transport docs) (new-platform)
+
+ If you need help…
+…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+ Reporting Issues
+Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
+
+ Breaking Changes
+
+ - Automations: The state trigger keyword
state and the time trigger keyword after were deprecated in 0.46. They have now been removed. (@amelchio - #8510) (automation.state docs) (automation.time docs) (breaking change)
+ - Wink: the component is no longer supporting the
access_token in the config. Use the new OAuth authentication or add your username and password to the config. (@w1ll1am23 - #8208) (wink docs) (breaking change)
+ - Alexa/API.AI/Snips.ai/Conversation: configuring responses to intents/sentences has been moved to a new component called
intent_script. Conversation now allows configuring sentences to map to intents. (@balloob - #8434) (alexa docs) (intent docs) (intent_script docs)
+ (shopping_list docs) (snips docs) (breaking change) (new-platform)
+
+alexa:
+snips:
+apiai:
+
+intent_script:
+ LightKitchen:
+ speech:
+ type: plain
+ text: I did the work, yay.
+ card:
+ type: simple
+ title: Lights Card
+ content: I have turned on the lights.
+ action:
+ service: light.turn_on
+ data:
+ entity_id: light.kitchen
+
+conversation:
+ intents:
+ LightKitchen:
+ - The kitchen is magic
+
+
+
+ - Switch fritzdect: attributes have been renamed to use underscores and no capital letters (@thomasklingbeil - #8436) (switch.fritzdect docs) (breaking change)
+ - Yahoo Weather: no longer allow configuring forecasts but include all instead. (@fanthos - #8626) (weather.yweather docs) (breaking change)
+ - The Home Assistant Z-Wave Cover implementation has been updated to support the latest development version of OpenZWave. If you are currently applying a workaround to your OpenZWave installation to support the barrier command class, you’ll need to make sure you update your workaround to the latest development version of OpenZWave. (@firstof9 - #8574) (cover docs) (cover.zwave docs) (breaking change)
+
+ All changes
+
+ - Make deps directory persistent over upgrades (@MartinHjelmare - #7801)
+ - Fix check for running inside venv (@MartinHjelmare - #8481)
+ - Bump to KNXIP 0.5 (@open-homeautomation - #8492) (knx docs)
+ - Expose all components on hass [Concept] (@balloob - #8490) (light docs)
+ - Add bind_hass to components (@balloob - #8502)
+ - Persistent notification import (@balloob - #8507)
+ - Added additional attributes to OwnTracks device_tracker (@binarybucks - #8503) (device_tracker.owntracks docs)
+ - Added sensor state rounding (@fronzbot - #8499) (sensor.pi_hole docs)
+ - fix for a bug introduced with media support in #8282 (@MikeChristianson - #8513) (notify.twitter docs)
+ - handle timeout errors without logging.exception when updating hue lights; double quotes in log msgs (@azogue - #8524) (light.hue docs)
+ - Remove deprecated automation keywords (@amelchio - #8510) (automation.state docs) (automation.time docs) (breaking change)
+ - Citybikes: Allow None as result for empty slots (@janLo - #8528) (sensor.citybikes docs)
+ - Return a 0 temperature value when none is found (@phil-lavin - #8518) (climate.maxcube docs)
+ - Fix #6469 and #6828 (@titilambert - #8537) (sensor.hydroquebec docs)
+ - Update docstrings (@fabaff - #8536)
+ - Upgrade TwitterAPI to 2.4.6 (@fabaff - #8535) (notify.twitter docs)
+ - Decora: Fix set brightness and improve reconnection (@titilambert - #8522) (light.decora docs)
+ - Initial support for Google Wifi/OnHub (@fronzbot - #8485) (sensor.google_wifi docs) (new-platform)
+ - Fix exception dlib_face_identify when image is not recognized by face_recognition module (@tchellomello - #8552) (image_processing.dlib_face_identify docs)
+ - [media_extractor] Add support for custom stream queries for media_extractor (@minchik - #8538) (media_extractor docs)
+ - Report Harmony remote off if state is unknown (@jawilson - #8547) (remote.harmony docs)
+ - Upgrade the alarmdecoder dependency library from 0.12.1 to 0.12.3. (@viswa-swami - #8542) (alarmdecoder docs)
+ - turn_on_action and turn_off_action with script syntax (@azogue - #8558) (media_player.kodi docs)
+ - Extends Pi-hole sensor to support the new sensors: (@tchellomello - #8549) (sensor.pi_hole docs)
+ - Support for Wink Switch and Light groups also fix fan speed selection (@w1ll1am23 - #8501) (wink docs) (fan.wink docs) (light.wink docs) (switch.wink docs)
+ - Added a service to write to KNX group addressed including documentation (@open-homeautomation - #8491) (knx docs)
+ - Handle manual edits to emulated_hue_ids.json (@jawilson - #8560) (emulated_hue docs)
+ - Enhance python_script to support “getitem” (@sdague - #8541) (python_script docs)
+ - Update persistent deps dir version in config.py (@balloob - #8479)
+ - Xiaomi gw support (@danielhiversen - #8555) (xiaomi docs) (binary_sensor.xiaomi docs) (cover.xiaomi docs) (light.xiaomi docs) (sensor.xiaomi docs) (switch.xiaomi docs) (new-platform)
+ - fix #8263 corrected Adafruit DHT library version from 1.3.0 to 1.3.2 (@namadori - #8562) (sensor.dht docs)
+ - xiaomi bug fix (@danielhiversen - #8576) (binary_sensor.xiaomi docs)
+ - Bumped python-simplisafe version (@bachya - #8578) (alarm_control_panel.simplisafe docs)
+ - Added Time Remaining and Time Elapsed sensors for octoprint (@w1ll1am23 - #8581) (sensor.octoprint docs)
+ - upgade xiaomi lib to 0.2 (@danielhiversen - #8584) (xiaomi docs)
+ - Device support for different new sensors of the xiaomi aqara gateway (@syssi - #8577) (xiaomi docs) (binary_sensor.xiaomi docs) (sensor.xiaomi docs) (switch.xiaomi docs)
+ - Extends Fitbit sensors to track the device battery level (@tchellomello - #8583) (sensor.fitbit docs)
+ - xiaomi binary sensor bug fix (@danielhiversen - #8586) (binary_sensor.xiaomi docs)
+ - upgrade pywebpush and PyJWT (@perosb - #8588) (notify.html5 docs)
+ - Support for Wink oauth application authorization (@w1ll1am23 - #8208) (wink docs) (breaking change)
+ - Add Intent component (@balloob - #8434) (alexa docs) (intent docs) (intent_script docs) (shopping_list docs) (snips docs) (breaking change) (new-platform)
+ - Remove code in wink.py overwriting hass.data configurator (@w1ll1am23 - #8595) (wink docs)
+ - bump python-mirobo version for more robust protocol handling, make the platform to update on startup (@rytilahti - #8602) (switch.xiaomi_vacuum docs)
+ - Binary sensor ping fixed for hassio (@gollo - #8573) (binary_sensor.ping docs)
+ - Simplified percent conversion, better logging (@open-homeautomation - #8568) (sensor.knx docs)
+ - make attributes in the fritzdect module easier to process (@thomasklingbeil - #8436) (switch.fritzdect docs) (breaking change)
+ - Allow set_cover_position in scenes (@peckham - #8613)
+ - better but still not great (@cribbstechnologies - #8618)
+ - Upgrade youtube_dl to 2017.7.23 (@fabaff - #8617) (media_extractor docs)
+ - Upgrade mypy to 0.520 (@fabaff - #8616)
+ - REST binary sensor value_template optional (@philhawthorne - #8596) (binary_sensor.rest docs)
+ - added onvif camera fix for non-virtual env installations (@matt2005 - #8592) (camera.onvif docs)
+ - Cleanup old device_tracker stuff (@pvizeli - #8627)
+ - Add support for using credstash as a secret store (@justin8 - #8494)
+ - Added support for default value when environment variable is missing (@devspacenine - #8484)
+ - Manual alarm with MQTT control (@colinodell - #8257) (alarm_control_panel.manual_mqtt docs) (new-platform)
+ - Catch and log Lyft API errors (@armills - #8635) (sensor.lyft docs)
+ - Tweak conversation/intent/shopping list (@balloob - #8636) (conversation docs) (shopping_list docs)
+ - Update dependencies cast + discovery (@balloob - #8646) (media_player.cast docs)
+ - Add component Light TPLink (@gollo - #8643) (light.tplink docs) (new-platform)
+ - Fixes Fitbit sensor to report battery level with the expected device (@tchellomello - #8647) (sensor.fitbit docs)
+ - Upgrade aiolifx (@amelchio - #8648) (light.lifx docs)
+ - Velbus (@thomasdelaet - #8076) (velbus docs) (binary_sensor.velbus docs) (light.velbus docs) (new-platform)
+ - Yahoo Weather update, supports forecast for more days (@fanthos - #8626) (weather.yweather docs) (breaking change)
+ - History performance improvements for single-entity requests (@OverloadUT - #8632) (history docs)
+ - Add transition support to light.zha (@jawilson - #8548) (light.zha docs)
+ - Add uk_transport component. (@robmarkcole - #8600) (sensor.uk_transport docs) (new-platform)
+ - Added support for SerenaHoneycombShades to Lutron Caseta (@809694+kfcook - #8662) (cover.lutron_caseta docs)
+ - MQTT Switch: add availability_topic for online/offline status (@abmantis - #8593) (mqtt docs) (switch.mqtt docs)
+ - Adding support for mapping keys to value in statsd (@Khabi - #8665) (statsd docs)
+ - Upgrade fuzzywuzzy to 0.15.1 (@fabaff - #8671) (conversation docs)
+ - Upgrade libnacl to 1.5.2 (@fabaff - #8670) (device_tracker.owntracks docs)
+ - Upgrade sqlalchemy to 1.1.12 (@fabaff - #8669) (recorder docs)
+ - Upgrade pyhomematic to 0.1.30 (@danielperna84 - #8673) (homematic docs)
+ - Hass.io: logo support / timeout handling (@pvizeli - #8668) (hassio docs)
+ - Updated pysnmp to 4.3.9 (@bgehrich - #8675) (device_tracker.snmp docs) (sensor.snmp docs)
+ - Fix COMMAND_CLASS_BARRIER_OPERATOR for dev branch of OpenZwave (@firstof9 - #8574) (cover docs) (cover.zwave docs) (breaking change)
+ - Shopping List: edit name / complete status (@balloob - #8666) (shopping_list docs)
+ - Support for Wink local control (@w1ll1am23 - #8607) (wink docs)
+ - Persist shopping list + clear completed (@balloob - #8697) (shopping_list docs)
+
+
+
+ Comments
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/blog/archives/index.html b/blog/archives/index.html
index 1829a8a163..bea7d5c0dd 100644
--- a/blog/archives/index.html
+++ b/blog/archives/index.html
@@ -2935,6 +2935,27 @@
+
+
+
+
+
+
+
+
+ Home Assistant Podcast #4
+
+
+
@@ -2977,6 +2998,27 @@
+
+
+
+
+
+
+
+
@@ -3017,21 +3059,21 @@
Recent Posts
diff --git a/blog/categories/announcements/atom.xml b/blog/categories/announcements/atom.xml
index 13ff95ead7..7b8c220c6a 100644
--- a/blog/categories/announcements/atom.xml
+++ b/blog/categories/announcements/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Announcements | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml
index 1cb4a0f796..01a80cae37 100644
--- a/blog/categories/community/atom.xml
+++ b/blog/categories/community/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Community | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml
index 421eb8a1ae..472f4665e5 100644
--- a/blog/categories/device-tracking/atom.xml
+++ b/blog/categories/device-tracking/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Device-Tracking | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml
index d9b5746145..4c9970fd3a 100644
--- a/blog/categories/esp8266/atom.xml
+++ b/blog/categories/esp8266/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: ESP8266 | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml
index fe348ce7ab..b09907970b 100644
--- a/blog/categories/how-to/atom.xml
+++ b/blog/categories/how-to/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: How-To | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml
index 0c6504e3fd..ddbe6c3f53 100644
--- a/blog/categories/ibeacons/atom.xml
+++ b/blog/categories/ibeacons/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: iBeacons | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml
index 0d842216e0..779301ba39 100644
--- a/blog/categories/internet-of-things/atom.xml
+++ b/blog/categories/internet-of-things/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Internet-of-Things | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml
index cd118baaba..cc430885d0 100644
--- a/blog/categories/iot-data/atom.xml
+++ b/blog/categories/iot-data/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: IoT-Data | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/media/atom.xml b/blog/categories/media/atom.xml
index 4886b38933..52c13853b5 100644
--- a/blog/categories/media/atom.xml
+++ b/blog/categories/media/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Media | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
+ <![CDATA[Home Assistant Podcast #4]]>
+
+ 2017-07-17T00:01:00+00:00
+ https://home-assistant.io/blog/2017/07/17/hasspodcast-ep-4
+
+
<![CDATA[Home Assistant Podcast #3]]>
@@ -69,23 +82,6 @@ Join Michael Kennedy at the Talk Python podcast for an hour long interview with
- Listen online: [https://hasspodcast.io/ha001/](https://hasspodcast.io/ha001/)
- Download: [https://hasspodcast.io/podcast-download/13/ha001.mp3](https://hasspodcast.io/podcast-download/13/ha001.mp3)
-]]>
-
-
-
- <![CDATA[Podcast.__init__ interview with Paulus Schoutsen]]>
-
- 2017-05-05T02:00:00+00:00
- https://home-assistant.io/blog/2017/05/05/podcast-init-interview
-
-
-
-
-Earlier this year I was interviewed by Tobias Macey from [Podcast.\_\_init\_\_][pc-init] about Python and Home Assistant. Just realized that we never shared this on the blog, oops. Here it is, enjoy!
-
-
-
-[pc-init]: https://www.podcastinit.com/
]]>
diff --git a/blog/categories/media/index.html b/blog/categories/media/index.html
index a7804f7700..f5116b629d 100644
--- a/blog/categories/media/index.html
+++ b/blog/categories/media/index.html
@@ -96,6 +96,27 @@
+
+
+
+
+
+
+
+
+ Home Assistant Podcast #4
+
+
+
@@ -241,21 +262,21 @@
Recent Posts
diff --git a/blog/categories/merchandise/atom.xml b/blog/categories/merchandise/atom.xml
index a6e0dee49c..11064298fb 100644
--- a/blog/categories/merchandise/atom.xml
+++ b/blog/categories/merchandise/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Merchandise | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml
index 2983c02efe..95b9dba3bc 100644
--- a/blog/categories/micropython/atom.xml
+++ b/blog/categories/micropython/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Micropython | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml
index 37ea110420..cf1fda48c8 100644
--- a/blog/categories/mqtt/atom.xml
+++ b/blog/categories/mqtt/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: MQTT | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml
index dc6be392f7..8714326514 100644
--- a/blog/categories/organisation/atom.xml
+++ b/blog/categories/organisation/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Organisation | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml
index 9aed4839bf..95e66418b7 100644
--- a/blog/categories/owntracks/atom.xml
+++ b/blog/categories/owntracks/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: OwnTracks | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml
index 01c0e194c5..e63682b8e7 100644
--- a/blog/categories/presence-detection/atom.xml
+++ b/blog/categories/presence-detection/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Presence-Detection | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml
index cb79053f15..f575624a47 100644
--- a/blog/categories/public-service-announcement/atom.xml
+++ b/blog/categories/public-service-announcement/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Public-Service-Announcement | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Recent Posts
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index bbd6cf575d..d66204f369 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Release-Notes | Home Assistant]]>
- 2017-07-29T20:39:19+00:00
+ 2017-07-29T21:57:28+00:00
https://home-assistant.io/
Octopress
+
+ <![CDATA[0.50: Voice control, History improvements, and Xiaomi]]>
+
+ 2017-07-29T00:11:05+00:00
+ https://home-assistant.io/blog/2017/07/29/release-50
+
+
+Last Wednesday we released [Hass.io](https://home-assistant.io/hassio/), an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
+
+The launch has been crazy successful. The [20 minute introduction video][hassio-intro] by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.
+
+Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
+
+### Adding the power of voice to integrations
+
+Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
+
+But enough about Hass.io, let's not forget about Home Assistant. This release has completely revamped the way how we deal with voice integrations. We turned Home Assistant into a platform to write voice apps, no matter where the processing of the voice happens. This can be done by Alexa, Google Assistant or in the Home Assistant user interface.
+
+We are super excited about the new functionality and hope that it will trigger a new type of applications and systems to be built on top of Home Assistant. This release includes a shopping list to show the new functionality. As a user you can add any item to the shopping list with your voice and also ask what is on your shopping list.
+
+```yaml
+# Example configuration.yaml entry
+shopping_list:
+```
+
+To make testing these applications easier, we've updated the conversation component. The component will now allow sentences to be configured that hook directly into the new voice functionality. Combined with the new interface it will allow for some great interactions!
+
+
+
+### History improvements
+
+[@OverloadUT] has been recently spending a lot of time on optimizing the history database queries. This release includes PR [#8632], the first in a list of improvements that he is working on. This PR greatly improves requests for single entities by using an optimized query for this use case.
+
+The performance change in some of his tests shows this change to be about 300x faster (30 seconds to 0.1 seconds!) (There is no theoretical upper limit due to the issue with multi-entity queries getting worse the longer the current recorder run has been going.)
+
+[hassio-intro]: https://www.youtube.com/watch?v=XWPluWcYRMI&feature=youtu.be
+
+### Xiaomi integration
+
+Yes, it has happened! After being in beta for a while, the Xiaomi support is now available to all. [@danielhiversen] did an amazing job and we now support sensors, switches, lights and covers.
+
+### Velbus integration
+
+Another awesome integration is that of the Velbus home automation system which has been contributed by [@thomasdelaet]. It integrates their sensors, covers, fans, lights and switches.
+
+### Manual alarm with MQTT control
+
+A new version of the manual alarm component is now available with full MQTT control thanks to [@colinodell]. Using this you can build your own control panel to remotely arm/disarm the alarm. For example, using a [Raspberry Pi to create an alarm](https://www.hackster.io/colinodell/diy-alarm-control-panel-for-home-assistant-ac1813).
+
+## New Platforms
+
+- Initial support for Google Wifi/OnHub ([@fronzbot] - [#8485]) ([sensor.google_wifi docs]) (new-platform)
+- Xiaomi gw support ([@danielhiversen] - [#8555]) ([xiaomi docs]) ([binary_sensor.xiaomi docs]) ([cover.xiaomi docs]) ([light.xiaomi docs]) ([sensor.xiaomi docs]) ([switch.xiaomi docs]) (new-platform)
+- Add Intent component ([@balloob] - [#8434]) ([alexa docs]) ([intent docs]) ([intent_script docs]) ([shopping_list docs]) ([snips docs]) (breaking change) (new-platform)
+- Manual alarm with MQTT control ([@colinodell] - [#8257]) ([alarm_control_panel.manual_mqtt docs]) (new-platform)
+- Add component Light TPLink ([@gollo] - [#8643]) ([light.tplink docs]) (new-platform)
+- Velbus ([@thomasdelaet] - [#8076]) ([velbus docs]) ([binary_sensor.velbus docs]) ([light.velbus docs]) (new-platform)
+- Add uk_transport component. ([@robmarkcole] - [#8600]) ([sensor.uk_transport docs]) (new-platform)
+
+## If you need help...
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+## Reporting Issues
+Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
+
+
+## Breaking Changes
+
+- Automations: The state trigger keyword `state` and the time trigger keyword `after` were deprecated in 0.46. They have now been removed. ([@amelchio] - [#8510]) ([automation.state docs]) ([automation.time docs]) (breaking change)
+- Wink: the component is no longer supporting the `access_token` in the config. Use the new OAuth authentication or add your username and password to the config. ([@w1ll1am23] - [#8208]) ([wink docs]) (breaking change)
+- Alexa/API.AI/Snips.ai/Conversation: configuring responses to intents/sentences has been moved to a new component called `intent_script`. Conversation now allows configuring sentences to map to intents. ([@balloob] - [#8434]) ([alexa docs]) ([intent docs]) ([intent_script docs])
+ ([shopping_list docs]) ([snips docs]) (breaking change) (new-platform)
+
+```yaml
+alexa:
+snips:
+apiai:
+
+intent_script:
+ LightKitchen:
+ speech:
+ type: plain
+ text: I did the work, yay.
+ card:
+ type: simple
+ title: Lights Card
+ content: I have turned on the lights.
+ action:
+ service: light.turn_on
+ data:
+ entity_id: light.kitchen
+
+conversation:
+ intents:
+ LightKitchen:
+ - The kitchen is magic
+```
+
+- Switch fritzdect: attributes have been renamed to use underscores and no capital letters ([@thomasklingbeil] - [#8436]) ([switch.fritzdect docs]) (breaking change)
+- Yahoo Weather: no longer allow configuring forecasts but include all instead. ([@fanthos] - [#8626]) ([weather.yweather docs]) (breaking change)
+- The Home Assistant Z-Wave Cover implementation has been updated to support the latest development version of OpenZWave. If you are currently applying a workaround to your OpenZWave installation to support the barrier command class, you'll need to make sure you update your workaround to the latest development version of OpenZWave. ([@firstof9] - [#8574]) ([cover docs]) ([cover.zwave docs]) (breaking change)
+
+## All changes
+
+- Make deps directory persistent over upgrades ([@MartinHjelmare] - [#7801])
+- Fix check for running inside venv ([@MartinHjelmare] - [#8481])
+- Bump to KNXIP 0.5 ([@open-homeautomation] - [#8492]) ([knx docs])
+- Expose all components on hass [Concept] ([@balloob] - [#8490]) ([light docs])
+- Add bind_hass to components ([@balloob] - [#8502])
+- Persistent notification import ([@balloob] - [#8507])
+- Added additional attributes to OwnTracks device_tracker ([@binarybucks] - [#8503]) ([device_tracker.owntracks docs])
+- Added sensor state rounding ([@fronzbot] - [#8499]) ([sensor.pi_hole docs])
+- fix for a bug introduced with media support in #8282 ([@MikeChristianson] - [#8513]) ([notify.twitter docs])
+- handle timeout errors without logging.exception when updating hue lights; double quotes in log msgs ([@azogue] - [#8524]) ([light.hue docs])
+- Remove deprecated automation keywords ([@amelchio] - [#8510]) ([automation.state docs]) ([automation.time docs]) (breaking change)
+- Citybikes: Allow None as result for empty slots ([@janLo] - [#8528]) ([sensor.citybikes docs])
+- Return a 0 temperature value when none is found ([@phil-lavin] - [#8518]) ([climate.maxcube docs])
+- Fix #6469 and #6828 ([@titilambert] - [#8537]) ([sensor.hydroquebec docs])
+- Update docstrings ([@fabaff] - [#8536])
+- Upgrade TwitterAPI to 2.4.6 ([@fabaff] - [#8535]) ([notify.twitter docs])
+- Decora: Fix set brightness and improve reconnection ([@titilambert] - [#8522]) ([light.decora docs])
+- Initial support for Google Wifi/OnHub ([@fronzbot] - [#8485]) ([sensor.google_wifi docs]) (new-platform)
+- Fix exception dlib_face_identify when image is not recognized by face_recognition module ([@tchellomello] - [#8552]) ([image_processing.dlib_face_identify docs])
+- [media_extractor] Add support for custom stream queries for media_extractor ([@minchik] - [#8538]) ([media_extractor docs])
+- Report Harmony remote off if state is unknown ([@jawilson] - [#8547]) ([remote.harmony docs])
+- Upgrade the alarmdecoder dependency library from 0.12.1 to 0.12.3. ([@viswa-swami] - [#8542]) ([alarmdecoder docs])
+- turn_on_action and turn_off_action with script syntax ([@azogue] - [#8558]) ([media_player.kodi docs])
+- Extends Pi-hole sensor to support the new sensors: ([@tchellomello] - [#8549]) ([sensor.pi_hole docs])
+- Support for Wink Switch and Light groups also fix fan speed selection ([@w1ll1am23] - [#8501]) ([wink docs]) ([fan.wink docs]) ([light.wink docs]) ([switch.wink docs])
+- Added a service to write to KNX group addressed including documentation ([@open-homeautomation] - [#8491]) ([knx docs])
+- Handle manual edits to emulated_hue_ids.json ([@jawilson] - [#8560]) ([emulated_hue docs])
+- Enhance python_script to support "_getitem_" ([@sdague] - [#8541]) ([python_script docs])
+- Update persistent deps dir version in config.py ([@balloob] - [#8479])
+- Xiaomi gw support ([@danielhiversen] - [#8555]) ([xiaomi docs]) ([binary_sensor.xiaomi docs]) ([cover.xiaomi docs]) ([light.xiaomi docs]) ([sensor.xiaomi docs]) ([switch.xiaomi docs]) (new-platform)
+- fix #8263 corrected Adafruit DHT library version from 1.3.0 to 1.3.2 ([@namadori] - [#8562]) ([sensor.dht docs])
+- xiaomi bug fix ([@danielhiversen] - [#8576]) ([binary_sensor.xiaomi docs])
+- Bumped python-simplisafe version ([@bachya] - [#8578]) ([alarm_control_panel.simplisafe docs])
+- Added Time Remaining and Time Elapsed sensors for octoprint ([@w1ll1am23] - [#8581]) ([sensor.octoprint docs])
+- upgade xiaomi lib to 0.2 ([@danielhiversen] - [#8584]) ([xiaomi docs])
+- Device support for different new sensors of the xiaomi aqara gateway ([@syssi] - [#8577]) ([xiaomi docs]) ([binary_sensor.xiaomi docs]) ([sensor.xiaomi docs]) ([switch.xiaomi docs])
+- Extends Fitbit sensors to track the device battery level ([@tchellomello] - [#8583]) ([sensor.fitbit docs])
+- xiaomi binary sensor bug fix ([@danielhiversen] - [#8586]) ([binary_sensor.xiaomi docs])
+- upgrade pywebpush and PyJWT ([@perosb] - [#8588]) ([notify.html5 docs])
+- Support for Wink oauth application authorization ([@w1ll1am23] - [#8208]) ([wink docs]) (breaking change)
+- Add Intent component ([@balloob] - [#8434]) ([alexa docs]) ([intent docs]) ([intent_script docs]) ([shopping_list docs]) ([snips docs]) (breaking change) (new-platform)
+- Remove code in wink.py overwriting hass.data configurator ([@w1ll1am23] - [#8595]) ([wink docs])
+- bump python-mirobo version for more robust protocol handling, make the platform to update on startup ([@rytilahti] - [#8602]) ([switch.xiaomi_vacuum docs])
+- Binary sensor ping fixed for hassio ([@gollo] - [#8573]) ([binary_sensor.ping docs])
+- Simplified percent conversion, better logging ([@open-homeautomation] - [#8568]) ([sensor.knx docs])
+- make attributes in the fritzdect module easier to process ([@thomasklingbeil] - [#8436]) ([switch.fritzdect docs]) (breaking change)
+- Allow set_cover_position in scenes ([@peckham] - [#8613])
+- better but still not great ([@cribbstechnologies] - [#8618])
+- Upgrade youtube_dl to 2017.7.23 ([@fabaff] - [#8617]) ([media_extractor docs])
+- Upgrade mypy to 0.520 ([@fabaff] - [#8616])
+- REST binary sensor value_template optional ([@philhawthorne] - [#8596]) ([binary_sensor.rest docs])
+- added onvif camera fix for non-virtual env installations ([@matt2005] - [#8592]) ([camera.onvif docs])
+- Cleanup old device_tracker stuff ([@pvizeli] - [#8627])
+- Add support for using credstash as a secret store ([@justin8] - [#8494])
+- Added support for default value when environment variable is missing ([@devspacenine] - [#8484])
+- Manual alarm with MQTT control ([@colinodell] - [#8257]) ([alarm_control_panel.manual_mqtt docs]) (new-platform)
+- Catch and log Lyft API errors ([@armills] - [#8635]) ([sensor.lyft docs])
+- Tweak conversation/intent/shopping list ([@balloob] - [#8636]) ([conversation docs]) ([shopping_list docs])
+- Update dependencies cast + discovery ([@balloob] - [#8646]) ([media_player.cast docs])
+- Add component Light TPLink ([@gollo] - [#8643]) ([light.tplink docs]) (new-platform)
+- Fixes Fitbit sensor to report battery level with the expected device ([@tchellomello] - [#8647]) ([sensor.fitbit docs])
+- Upgrade aiolifx ([@amelchio] - [#8648]) ([light.lifx docs])
+- Velbus ([@thomasdelaet] - [#8076]) ([velbus docs]) ([binary_sensor.velbus docs]) ([light.velbus docs]) (new-platform)
+- Yahoo Weather update, supports forecast for more days ([@fanthos] - [#8626]) ([weather.yweather docs]) (breaking change)
+- History performance improvements for single-entity requests ([@OverloadUT] - [#8632]) ([history docs])
+- Add transition support to light.zha ([@jawilson] - [#8548]) ([light.zha docs])
+- Add uk_transport component. ([@robmarkcole] - [#8600]) ([sensor.uk_transport docs]) (new-platform)
+- Added support for SerenaHoneycombShades to Lutron Caseta ([@809694+kfcook] - [#8662]) ([cover.lutron_caseta docs])
+- MQTT Switch: add availability_topic for online/offline status ([@abmantis] - [#8593]) ([mqtt docs]) ([switch.mqtt docs])
+- Adding support for mapping keys to value in statsd ([@Khabi] - [#8665]) ([statsd docs])
+- Upgrade fuzzywuzzy to 0.15.1 ([@fabaff] - [#8671]) ([conversation docs])
+- Upgrade libnacl to 1.5.2 ([@fabaff] - [#8670]) ([device_tracker.owntracks docs])
+- Upgrade sqlalchemy to 1.1.12 ([@fabaff] - [#8669]) ([recorder docs])
+- Upgrade pyhomematic to 0.1.30 ([@danielperna84] - [#8673]) ([homematic docs])
+- Hass.io: logo support / timeout handling ([@pvizeli] - [#8668]) ([hassio docs])
+- Updated pysnmp to 4.3.9 ([@bgehrich] - [#8675]) ([device_tracker.snmp docs]) ([sensor.snmp docs])
+- Fix COMMAND_CLASS_BARRIER_OPERATOR for dev branch of OpenZwave ([@firstof9] - [#8574]) ([cover docs]) ([cover.zwave docs]) (breaking change)
+- Shopping List: edit name / complete status ([@balloob] - [#8666]) ([shopping_list docs])
+- Support for Wink local control ([@w1ll1am23] - [#8607]) ([wink docs])
+- Persist shopping list + clear completed ([@balloob] - [#8697]) ([shopping_list docs])
+
+[#7801]: https://github.com/home-assistant/home-assistant/pull/7801
+[#8076]: https://github.com/home-assistant/home-assistant/pull/8076
+[#8208]: https://github.com/home-assistant/home-assistant/pull/8208
+[#8257]: https://github.com/home-assistant/home-assistant/pull/8257
+[#8434]: https://github.com/home-assistant/home-assistant/pull/8434
+[#8436]: https://github.com/home-assistant/home-assistant/pull/8436
+[#8479]: https://github.com/home-assistant/home-assistant/pull/8479
+[#8481]: https://github.com/home-assistant/home-assistant/pull/8481
+[#8484]: https://github.com/home-assistant/home-assistant/pull/8484
+[#8485]: https://github.com/home-assistant/home-assistant/pull/8485
+[#8490]: https://github.com/home-assistant/home-assistant/pull/8490
+[#8491]: https://github.com/home-assistant/home-assistant/pull/8491
+[#8492]: https://github.com/home-assistant/home-assistant/pull/8492
+[#8494]: https://github.com/home-assistant/home-assistant/pull/8494
+[#8499]: https://github.com/home-assistant/home-assistant/pull/8499
+[#8501]: https://github.com/home-assistant/home-assistant/pull/8501
+[#8502]: https://github.com/home-assistant/home-assistant/pull/8502
+[#8503]: https://github.com/home-assistant/home-assistant/pull/8503
+[#8507]: https://github.com/home-assistant/home-assistant/pull/8507
+[#8510]: https://github.com/home-assistant/home-assistant/pull/8510
+[#8513]: https://github.com/home-assistant/home-assistant/pull/8513
+[#8518]: https://github.com/home-assistant/home-assistant/pull/8518
+[#8522]: https://github.com/home-assistant/home-assistant/pull/8522
+[#8524]: https://github.com/home-assistant/home-assistant/pull/8524
+[#8528]: https://github.com/home-assistant/home-assistant/pull/8528
+[#8535]: https://github.com/home-assistant/home-assistant/pull/8535
+[#8536]: https://github.com/home-assistant/home-assistant/pull/8536
+[#8537]: https://github.com/home-assistant/home-assistant/pull/8537
+[#8538]: https://github.com/home-assistant/home-assistant/pull/8538
+[#8541]: https://github.com/home-assistant/home-assistant/pull/8541
+[#8542]: https://github.com/home-assistant/home-assistant/pull/8542
+[#8547]: https://github.com/home-assistant/home-assistant/pull/8547
+[#8548]: https://github.com/home-assistant/home-assistant/pull/8548
+[#8549]: https://github.com/home-assistant/home-assistant/pull/8549
+[#8552]: https://github.com/home-assistant/home-assistant/pull/8552
+[#8555]: https://github.com/home-assistant/home-assistant/pull/8555
+[#8558]: https://github.com/home-assistant/home-assistant/pull/8558
+[#8560]: https://github.com/home-assistant/home-assistant/pull/8560
+[#8562]: https://github.com/home-assistant/home-assistant/pull/8562
+[#8568]: https://github.com/home-assistant/home-assistant/pull/8568
+[#8573]: https://github.com/home-assistant/home-assistant/pull/8573
+[#8574]: https://github.com/home-assistant/home-assistant/pull/8574
+[#8576]: https://github.com/home-assistant/home-assistant/pull/8576
+[#8577]: https://github.com/home-assistant/home-assistant/pull/8577
+[#8578]: https://github.com/home-assistant/home-assistant/pull/8578
+[#8581]: https://github.com/home-assistant/home-assistant/pull/8581
+[#8583]: https://github.com/home-assistant/home-assistant/pull/8583
+[#8584]: https://github.com/home-assistant/home-assistant/pull/8584
+[#8586]: https://github.com/home-assistant/home-assistant/pull/8586
+[#8588]: https://github.com/home-assistant/home-assistant/pull/8588
+[#8592]: https://github.com/home-assistant/home-assistant/pull/8592
+[#8593]: https://github.com/home-assistant/home-assistant/pull/8593
+[#8595]: https://github.com/home-assistant/home-assistant/pull/8595
+[#8596]: https://github.com/home-assistant/home-assistant/pull/8596
+[#8600]: https://github.com/home-assistant/home-assistant/pull/8600
+[#8602]: https://github.com/home-assistant/home-assistant/pull/8602
+[#8607]: https://github.com/home-assistant/home-assistant/pull/8607
+[#8613]: https://github.com/home-assistant/home-assistant/pull/8613
+[#8616]: https://github.com/home-assistant/home-assistant/pull/8616
+[#8617]: https://github.com/home-assistant/home-assistant/pull/8617
+[#8618]: https://github.com/home-assistant/home-assistant/pull/8618
+[#8626]: https://github.com/home-assistant/home-assistant/pull/8626
+[#8627]: https://github.com/home-assistant/home-assistant/pull/8627
+[#8632]: https://github.com/home-assistant/home-assistant/pull/8632
+[#8635]: https://github.com/home-assistant/home-assistant/pull/8635
+[#8636]: https://github.com/home-assistant/home-assistant/pull/8636
+[#8643]: https://github.com/home-assistant/home-assistant/pull/8643
+[#8646]: https://github.com/home-assistant/home-assistant/pull/8646
+[#8647]: https://github.com/home-assistant/home-assistant/pull/8647
+[#8648]: https://github.com/home-assistant/home-assistant/pull/8648
+[#8662]: https://github.com/home-assistant/home-assistant/pull/8662
+[#8665]: https://github.com/home-assistant/home-assistant/pull/8665
+[#8666]: https://github.com/home-assistant/home-assistant/pull/8666
+[#8668]: https://github.com/home-assistant/home-assistant/pull/8668
+[#8669]: https://github.com/home-assistant/home-assistant/pull/8669
+[#8670]: https://github.com/home-assistant/home-assistant/pull/8670
+[#8671]: https://github.com/home-assistant/home-assistant/pull/8671
+[#8673]: https://github.com/home-assistant/home-assistant/pull/8673
+[#8675]: https://github.com/home-assistant/home-assistant/pull/8675
+[#8697]: https://github.com/home-assistant/home-assistant/pull/8697
+[@809694+kfcook]: https://github.com/809694+kfcook
+[@Khabi]: https://github.com/Khabi
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@MikeChristianson]: https://github.com/MikeChristianson
+[@OverloadUT]: https://github.com/OverloadUT
+[@abmantis]: https://github.com/abmantis
+[@amelchio]: https://github.com/amelchio
+[@armills]: https://github.com/armills
+[@azogue]: https://github.com/azogue
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bgehrich]: https://github.com/bgehrich
+[@binarybucks]: https://github.com/binarybucks
+[@colinodell]: https://github.com/colinodell
+[@cribbstechnologies]: https://github.com/cribbstechnologies
+[@danielhiversen]: https://github.com/danielhiversen
+[@danielperna84]: https://github.com/danielperna84
+[@devspacenine]: https://github.com/devspacenine
+[@fabaff]: https://github.com/fabaff
+[@fanthos]: https://github.com/fanthos
+[@firstof9]: https://github.com/firstof9
+[@fronzbot]: https://github.com/fronzbot
+[@gollo]: https://github.com/gollo
+[@janLo]: https://github.com/janLo
+[@jawilson]: https://github.com/jawilson
+[@justin8]: https://github.com/justin8
+[@matt2005]: https://github.com/matt2005
+[@minchik]: https://github.com/minchik
+[@namadori]: https://github.com/namadori
+[@open-homeautomation]: https://github.com/open-homeautomation
+[@peckham]: https://github.com/peckham
+[@perosb]: https://github.com/perosb
+[@phil-lavin]: https://github.com/phil-lavin
+[@philhawthorne]: https://github.com/philhawthorne
+[@pvizeli]: https://github.com/pvizeli
+[@robmarkcole]: https://github.com/robmarkcole
+[@rytilahti]: https://github.com/rytilahti
+[@sdague]: https://github.com/sdague
+[@syssi]: https://github.com/syssi
+[@tchellomello]: https://github.com/tchellomello
+[@thomasdelaet]: https://github.com/thomasdelaet
+[@thomasklingbeil]: https://github.com/thomasklingbeil
+[@titilambert]: https://github.com/titilambert
+[@viswa-swami]: https://github.com/viswa-swami
+[@w1ll1am23]: https://github.com/w1ll1am23
+[alarm_control_panel.manual_mqtt docs]: https://home-assistant.io/components/alarm_control_panel.manual_mqtt/
+[alarm_control_panel.simplisafe docs]: https://home-assistant.io/components/alarm_control_panel.simplisafe/
+[alarmdecoder docs]: https://home-assistant.io/components/alarmdecoder/
+[alexa docs]: https://home-assistant.io/components/alexa/
+[automation.state docs]: https://home-assistant.io/docs/automation/trigger/#state-trigger
+[automation.time docs]: https://home-assistant.io/docs/automation/trigger/#time-trigger
+[binary_sensor.ping docs]: https://home-assistant.io/components/binary_sensor.ping/
+[binary_sensor.rest docs]: https://home-assistant.io/components/binary_sensor.rest/
+[binary_sensor.velbus docs]: https://home-assistant.io/components/binary_sensor.velbus/
+[binary_sensor.xiaomi docs]: https://home-assistant.io/components/binary_sensor.xiaomi/
+[camera.onvif docs]: https://home-assistant.io/components/camera.onvif/
+[climate.maxcube docs]: https://home-assistant.io/components/climate.maxcube/
+[conversation docs]: https://home-assistant.io/components/conversation/
+[cover docs]: https://home-assistant.io/components/cover/
+[cover.lutron_caseta docs]: https://home-assistant.io/components/cover.lutron_caseta/
+[cover.xiaomi docs]: https://home-assistant.io/components/cover.xiaomi/
+[cover.zwave docs]: https://home-assistant.io/components/cover.zwave/
+[device_tracker.owntracks docs]: https://home-assistant.io/components/device_tracker.owntracks/
+[device_tracker.snmp docs]: https://home-assistant.io/components/device_tracker.snmp/
+[emulated_hue docs]: https://home-assistant.io/components/emulated_hue/
+[fan.wink docs]: https://home-assistant.io/components/fan.wink/
+[hassio docs]: https://home-assistant.io/components/hassio/
+[history docs]: https://home-assistant.io/components/history/
+[homematic docs]: https://home-assistant.io/components/homematic/
+[image_processing.dlib_face_identify docs]: https://home-assistant.io/components/image_processing.dlib_face_identify/
+[intent docs]: https://home-assistant.io/components/intent/
+[intent_script docs]: https://home-assistant.io/components/intent_script/
+[knx docs]: https://home-assistant.io/components/knx/
+[light docs]: https://home-assistant.io/components/light/
+[light.decora docs]: https://home-assistant.io/components/light.decora/
+[light.hue docs]: https://home-assistant.io/components/light.hue/
+[light.lifx docs]: https://home-assistant.io/components/light.lifx/
+[light.tplink docs]: https://home-assistant.io/components/light.tplink/
+[light.velbus docs]: https://home-assistant.io/components/light.velbus/
+[light.wink docs]: https://home-assistant.io/components/light.wink/
+[light.xiaomi docs]: https://home-assistant.io/components/light.xiaomi/
+[light.zha docs]: https://home-assistant.io/components/light.zha/
+[media_extractor docs]: https://home-assistant.io/components/media_extractor/
+[media_player.cast docs]: https://home-assistant.io/components/media_player.cast/
+[media_player.kodi docs]: https://home-assistant.io/components/media_player.kodi/
+[mqtt docs]: https://home-assistant.io/components/mqtt/
+[notify.html5 docs]: https://home-assistant.io/components/notify.html5/
+[notify.twitter docs]: https://home-assistant.io/components/notify.twitter/
+[python_script docs]: https://home-assistant.io/components/python_script/
+[recorder docs]: https://home-assistant.io/components/recorder/
+[remote.harmony docs]: https://home-assistant.io/components/remote.harmony/
+[sensor.citybikes docs]: https://home-assistant.io/components/sensor.citybikes/
+[sensor.dht docs]: https://home-assistant.io/components/sensor.dht/
+[sensor.fitbit docs]: https://home-assistant.io/components/sensor.fitbit/
+[sensor.google_wifi docs]: https://home-assistant.io/components/sensor.google_wifi/
+[sensor.hydroquebec docs]: https://home-assistant.io/components/sensor.hydroquebec/
+[sensor.knx docs]: https://home-assistant.io/components/sensor.knx/
+[sensor.lyft docs]: https://home-assistant.io/components/sensor.lyft/
+[sensor.octoprint docs]: https://home-assistant.io/components/sensor.octoprint/
+[sensor.pi_hole docs]: https://home-assistant.io/components/sensor.pi_hole/
+[sensor.snmp docs]: https://home-assistant.io/components/sensor.snmp/
+[sensor.uk_transport docs]: https://home-assistant.io/components/sensor.uk_transport/
+[sensor.xiaomi docs]: https://home-assistant.io/components/sensor.xiaomi/
+[shopping_list docs]: https://home-assistant.io/components/shopping_list/
+[snips docs]: https://home-assistant.io/components/snips/
+[statsd docs]: https://home-assistant.io/components/statsd/
+[switch.fritzdect docs]: https://home-assistant.io/components/switch.fritzdect/
+[switch.mqtt docs]: https://home-assistant.io/components/switch.mqtt/
+[switch.wink docs]: https://home-assistant.io/components/switch.wink/
+[switch.xiaomi docs]: https://home-assistant.io/components/switch.xiaomi/
+[switch.xiaomi_vacuum docs]: https://home-assistant.io/components/switch.xiaomi_vacuum/
+[velbus docs]: https://home-assistant.io/components/velbus/
+[weather.yweather docs]: https://home-assistant.io/components/weather.yweather/
+[wink docs]: https://home-assistant.io/components/wink/
+[xiaomi docs]: https://home-assistant.io/components/xiaomi/
+
+
+
+[forum]: https://community.home-assistant.io/
+[issue]: https://github.com/home-assistant/home-assistant/issues
+[discord]: https://discord.gg/c5DvZ4e
+]]>
+
+
-
-Welcome to another great release of Home Assistant! While some of contributors and users are gathering at PyCon US 2017, we still managed to get a great release together!
-
-First thing for this release is a feature that has been requested a lot: an automation editor! It's still experimental - and many things are still in progress - but it works! You can create new automations and edit existing ones. If you start a new config, you're all good to go. Otherwise check [these instructions](https://home-assistant.io/docs/automation/editor/) to get your automations ready for editing in the UI.
-
-
- 
-
-
-
-
-As the editor is experimental, there are some limitations. These include that Chrome/Chromium is the only supported browser, we don't support all triggers and actions and there is no support for conditions yet. But the foundation is there and so if you want to contribute to this, come help!
-
-On the Z-Wave front a lot has happened. The biggest one is that we have a major extension of the Z-Wave panel thanks to [@turbokongen]! You will now be able to change config parameters and manage your devices.
-
-
- 
-
-If you have a security key set in your Open Z-Wave `options.xml`, copy `options.xml` to your Home Assistant configuration directory. This is the only place where options will get persisted. -
- -Next to that [@armills] has lead the charge and managed to get full test coverage for Z-Wave! Thanks for all the hard work! - -This release also contains two integrations which could help you to make non-smart devices a little smarter. The [`file` sensor][sensor.file docs] and the [`seven_segments` OCR image processing platform][image_processing.seven_segments docs]. The first simply reads a plain-text file which was created by a logger or alike. The latter one extracts the value from a captured image that shows a seven-segments display. - -
- 
-
2017
+
+
+
+
+
+Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
Recent Posts
+
+
+
+
+
+ 0.50: Voice control, History improvements, and Xiaomi +
+ +
+
+
+
Last Wednesday we released Hass.io, an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
+The launch has been crazy successful. The 20 minute introduction video by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.
+Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
+Adding the power of voice to integrations
+Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
+But enough about Hass.io, let’s not forget about Home Assistant. This release has completely revamped the way how we deal with voice integrations. We turned Home Assistant into a platform to write voice apps, no matter where the processing of the voice happens. This can be done by Alexa, Google Assistant or in the Home Assistant user interface.
+We are super excited about the new functionality and hope that it will trigger a new type of applications and systems to be built on top of Home Assistant. This release includes a shopping list to show the new functionality. As a user you can add any item to the shopping list with your voice and also ask what is on your shopping list.
+# Example configuration.yaml entry
+shopping_list:
+To make testing these applications easier, we’ve updated the conversation component. The component will now allow sentences to be configured that hook directly into the new voice functionality. Combined with the new interface it will allow for some great interactions!
+ +History improvements
+@OverloadUT has been recently spending a lot of time on optimizing the history database queries. This release includes PR #8632, the first in a list of improvements that he is working on. This PR greatly improves requests for single entities by using an optimized query for this use case.
+The performance change in some of his tests shows this change to be about 300x faster (30 seconds to 0.1 seconds!) (There is no theoretical upper limit due to the issue with multi-entity queries getting worse the longer the current recorder run has been going.)
+Xiaomi integration
+Yes, it has happened! After being in beta for a while, the Xiaomi support is now available to all. @danielhiversen did an amazing job and we now support sensors, switches, lights and covers.
+Velbus integration
+Another awesome integration is that of the Velbus home automation system which has been contributed by @thomasdelaet. It integrates their sensors, covers, fans, lights and switches.
+Manual alarm with MQTT control
+A new version of the manual alarm component is now available with full MQTT control thanks to @colinodell. Using this you can build your own control panel to remotely arm/disarm the alarm. For example, using a Raspberry Pi to create an alarm.
+New Platforms
+-
+
- Initial support for Google Wifi/OnHub (@fronzbot - #8485) (sensor.google_wifi docs) (new-platform) +
- Xiaomi gw support (@danielhiversen - #8555) (xiaomi docs) (binary_sensor.xiaomi docs) (cover.xiaomi docs) (light.xiaomi docs) (sensor.xiaomi docs) (switch.xiaomi docs) (new-platform) +
- Add Intent component (@balloob - #8434) (alexa docs) (intent docs) (intent_script docs) (shopping_list docs) (snips docs) (breaking change) (new-platform) +
- Manual alarm with MQTT control (@colinodell - #8257) (alarm_control_panel.manual_mqtt docs) (new-platform) +
- Add component Light TPLink (@gollo - #8643) (light.tplink docs) (new-platform) +
- Velbus (@thomasdelaet - #8076) (velbus docs) (binary_sensor.velbus docs) (light.velbus docs) (new-platform) +
- Add uk_transport component. (@robmarkcole - #8600) (sensor.uk_transport docs) (new-platform) +
If you need help…
+…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+Reporting Issues
+Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
+ Read on → +@@ -144,6 +206,32 @@ Hass.io dashboard
+
+ Home Assistant Podcast #4 +
+ +
+
+ We quickly cover off a few community items including the move to Discord and Carlo talks with Phil about his use of Floorplan.
+ +@@ -461,63 +549,6 @@ Screenshot of a green dashboard
-
- ZWave Entity IDs -
- -
-
- ZWave entity_ids have long been a source of frustration in Home Assistant. The first problem we faced was that depending on the order of node discovery, entity_ids could be discovered with different names on each run. To solve this we added the node id as a suffix to the entity_id. This ensured that entity_ids were generated deterministically on each run, but additional suffixes had to be added to handle edge cases where there would otherwise be a conflict. The resulting entity_ids worked, but have been difficult to work with and makes ZWave a strange exception among other Home Assistant components.
-Thanks to the awesome work of @turbokongen, a growing number of ZWave configuration options are now available from the new ZWave panel in the Home Assistant frontend. Among these new features is support for renaming of ZWave nodes and their underlying values. (These renames are persisted in zwcfg_*.xml) This is important, because these items are combined to form the Home Assistant entity name, which is used to generate the entity_id. Now that these options are available, ZWave users can rename nodes and values, influencing the entity_ids that are generated by Home Assistant.
-Now that users are able to control these names, we will be making changes to how the entity_ids are generated for ZWave entities. The ZWave entity_ids are going to switch back to using the standard entity_id generation from Home Assistant core, based on the entity names. Moving forward, if there is a conflict when generating entity_ids, a suffix will be added, and it will be the responsibility of the user to rename their nodes and values to avoid the conflict. This is the same as any other platform in Home Assistant where two devices are discovered with the same name.
-With the release of 0.47, this feature will be opt-in. Setting new_entity_ids: true under zwave: in your configuration.yaml will enable the new generation. After 0.48 this feature will become opt-out. From 0.48 onward, unless you’ve declared new_entity_ids: false you will switch to the new entity_id generation. At an undecided point in the future, the old entity_id generation will be removed completely.
I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that breaking changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms.
--
- Linux Action Show special about Home Assistant -
- -
-
- Our founder Paulus Schoutsen is interviewed by Chris Fisher for a Linux Action Show special about home automation, Hass.io and the new Home Assistant podcast.
-
-
-
- diff --git a/blog/posts/10/index.html b/blog/posts/10/index.html index 17210709f5..52df756aef 100644 --- a/blog/posts/10/index.html +++ b/blog/posts/10/index.html @@ -67,6 +67,140 @@
+
+
+
+
+
+
+
+
+
+
+ 0.16: Embedded MQTT broker, Uber, Yamaha receivers and Growl +
+ +
+
+
+
+ Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.
Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).
+Rock on.
+
-
+
- Device Tracker - OwnTracks: Allow entry into passive zones using iBeacons (@pavoni) +
- Tellstick: rewrite to component to address concurrency issues (@stefan-jonasson) +
- Z-Wave: add services to heal and soft reset network (@srcLurker) +
- New component input_slider added (@persandstrom) +
- Light - Hue: Option added to ignore unreachable property (@maddox) +
- Notify: MessageBird support added (@florianholzapfel) +
- HTTP: Failed login attempts are now logged (@fabaff) +
- Vera: rewrite to component to simplify code and organize for reusability (@pavoni) +
- Discovery: support for Squeezebox (Logitech media) server added (@jaharkes) +
- Discovery: fix uPNP discovery crashing some routers (@jaharkes) +
- Switch: Wake on LAN platform added (@joopert) +
- Services for thermostats, notify and media player will now validate passed in parameters (@MartinHjelmare) +
- Switch - Arduino: support for default state and negate port functionality (@tilutza) +
- Switch: PulseAudio loopback now supported (@Cinntax) +
- Sensor: Uber now supported (@robbiet480) +
- Notify: Growl (GNTP) now supported (@robbiet480) +
- Media Player: Yamaha receivers now supported (@aoakeson) +
Breaking changes
+-
+
-
+
Automation: support for old deprecated config has been removed
+
+ -
+
Tellstick configuration has changed
+
+
tellstick:
+ signal_repetitions: X
+-
+
- Vera configuration has changed +
vera:
+ vera_controller_url: http://192.168.1.161:3480/
+ # Optional to exclude devices - this is a list of vera device ids
+ exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
+ # Optional to import switches as lights - this is a list of vera device ids
+ lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
++
+ 0.15: Unforked Open Z-Wave, templated service calls, extended scene support and PEP257 compliance. +
+ +
+
+
+ Two weeks has past so here is 0.15! We have been focussing a lot on quality. Making sure the system is more stable and reliable. I usually try to highlight one cool thing in the release notes but this release has 4 exciting announcements!
+-
+
- @fabaff has upgraded the codebase to follow the PEP257 documentation standard. +
- @partofthething has migrated us to use the main Python Open Z-Wave library instead of our forked version. +
- To make our automations more powerful, @persandstrom added the option to use templates to dynamically create service calls. This works for automation, Alexa, universal media player, template switch. Learn more. +
- @MartinHjelmare has upgraded our scene support to now support all built-in services and components. +
Besides bug fixes, this release also brings:
+
-
+
- Scene: Converted to a platform based component (@sander76) +
- Scene: Hunter Douglas Powerview now supported (@sander76) +
- Lock: MQTT platform added (@fabaff) +
- Device Tracker: OwnTracks will allow filtering inaccurate GPS locations (@HydrelioxGitHub) +
- Binary Sensor: Wemo Motion now supported (@pavoni, @ryanlaux) +
# Example using templates for service and data in service call.
+# Works for automation, Alexa, universal media player, template switch.
+automation:
+ - trigger:
+ - platform: state
+ entity_id: switch.bathroom
+ action:
+ service_template: >
+ {% if is_state('switch.bathroom', 'on') %}
+ switch.turn_on
+ {% else %}
+ switch.turn_off
+ {% endif %}
+ data_template:
+ entity_id: switch.{{ states('input_select.is') }}
+Breaking Changes
+-
+
- Media Player: Attributes to call service play_media has been renamed to
+
media_content_typeandmedia_content_id, to match the corresponding media +player state attributes. This change affects automations, scripts and scenes.
+
@@ -480,105 +614,6 @@ Example of the new views in the frontend. Learn mor
-
- 0.11: Extended support for DIY solutions -
- -
-
- First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.
-
-
-
- MySensors revamped and switch support added (@MartinHjelmare) -
- Full refactor of RPi GPIO. Now includes binary sensor and switch (@sfam) -
- Sensor: YR platform added (@danielhiversen) -
- Device Tracker: Geofancy platform has been renamed to Locative (@philipbl) -
- Automation: Add sun condition (@philipbl) -
- Switch: command_switch can now poll for state (@happyleavesaoc) -
- Switch: wemo now uses subscription to states instead of polling (@pavoni) -
- Telldus Live support added (@molobrakos) -
- Vera now uses subscription to states instead of polling (@pavoni) -
- New template helper method
is_state_attr(entity_id, name, value)added (@andythigpen)
- - Device tracker: OwnTracks transition events now supported (@xifle) -
- Light: Philips Hue platform now supports multiple hubs (@rhooper) -
- Notify: Free Mobile platform added (@HydrelioxGitHub) -
- New MQTT Eventstream component to connect two Home Assistant instances over MQTT (@moonshot) -
- Media player: Cast huge stability improvements (@rmkraus) -
- Media Player: Universal media player added to combine multiple media players (@rmkraus) -
- Sensor: Netatmo platform added (@HydrelioxGitHub) -
- Alarm Control Panel: Alarm.com platform added (@Xorso) -
- Thermostat: Proliphix platform added (@sdague) -
- New component input_boolean will allow for customizing automation (@balloob) -
- Support calling services via Amazon Echo (@balloob) -
Backwards incompatible changes
--
-
- The RPi.GPIO sensor platform has been moved to the
binary_sensorcomponent.
- - MySensors sensor platform now requires the MySensors component to be configured. -
- Geofancy platform has been renamed to Locative. -
-
- 0.10: Amazon Echo, iCloud, Dweet.io, Twitch and templating support! -
- -
-
- Alrighty, it’s time for Home Assistant 0.10. A lot amazing things have changed and sadly we also had to introduce a bunch of backwards incompatible changes. I would like to give a big shoutout to Philip Lundrigan (@philipbl) who put a lot in effort in helping the migration to move towards using templates for a wide variety of platforms.
-
-
-
-
-
-
- Device tracker: iCloud platform added (@xorso, @kevinpanaro) -
- Frontend: Improved caching using service workers if served over SSL (@balloob) -
- Sensor: Twitch platform added (@happyleavesaoc) -
- Template support (@balloob, @philipbl, @fabaff) -
- Thermostat: Heatmiser platform added (@andylockran) -
- Sensor: Dweet.io platform added (@fabaff) -
- Alexa/Amazon echo component added (@balloob) -
- Device Tracker: FritzBox platform added (@deisi, @caiuspb) -
- Sensor: Wink now supports the Egg minders (@w1ll1am23) -
- Sensor: ELIQ Online platform added (@molobrakos) -
- Binary sensor: REST platform added (@fabaff) -
- Sensor: Torque (OBD2) platform added (@happyleavesaoc) -
← Older
Newer →
diff --git a/blog/posts/11/index.html b/blog/posts/11/index.html
index 522965e2e9..2eb2ffbf4c 100644
--- a/blog/posts/11/index.html
+++ b/blog/posts/11/index.html
@@ -67,6 +67,105 @@
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+ 0.11: Extended support for DIY solutions +
+ +
+
+ First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.
+
-
+
- MySensors revamped and switch support added (@MartinHjelmare) +
- Full refactor of RPi GPIO. Now includes binary sensor and switch (@sfam) +
- Sensor: YR platform added (@danielhiversen) +
- Device Tracker: Geofancy platform has been renamed to Locative (@philipbl) +
- Automation: Add sun condition (@philipbl) +
- Switch: command_switch can now poll for state (@happyleavesaoc) +
- Switch: wemo now uses subscription to states instead of polling (@pavoni) +
- Telldus Live support added (@molobrakos) +
- Vera now uses subscription to states instead of polling (@pavoni) +
- New template helper method
is_state_attr(entity_id, name, value)added (@andythigpen)
+ - Device tracker: OwnTracks transition events now supported (@xifle) +
- Light: Philips Hue platform now supports multiple hubs (@rhooper) +
- Notify: Free Mobile platform added (@HydrelioxGitHub) +
- New MQTT Eventstream component to connect two Home Assistant instances over MQTT (@moonshot) +
- Media player: Cast huge stability improvements (@rmkraus) +
- Media Player: Universal media player added to combine multiple media players (@rmkraus) +
- Sensor: Netatmo platform added (@HydrelioxGitHub) +
- Alarm Control Panel: Alarm.com platform added (@Xorso) +
- Thermostat: Proliphix platform added (@sdague) +
- New component input_boolean will allow for customizing automation (@balloob) +
- Support calling services via Amazon Echo (@balloob) +
Backwards incompatible changes
+-
+
- The RPi.GPIO sensor platform has been moved to the
binary_sensorcomponent.
+ - MySensors sensor platform now requires the MySensors component to be configured. +
- Geofancy platform has been renamed to Locative. +
+
+ 0.10: Amazon Echo, iCloud, Dweet.io, Twitch and templating support! +
+ +
+
+ Alrighty, it’s time for Home Assistant 0.10. A lot amazing things have changed and sadly we also had to introduce a bunch of backwards incompatible changes. I would like to give a big shoutout to Philip Lundrigan (@philipbl) who put a lot in effort in helping the migration to move towards using templates for a wide variety of platforms.
+
+
+
+
-
+
- Device tracker: iCloud platform added (@xorso, @kevinpanaro) +
- Frontend: Improved caching using service workers if served over SSL (@balloob) +
- Sensor: Twitch platform added (@happyleavesaoc) +
- Template support (@balloob, @philipbl, @fabaff) +
- Thermostat: Heatmiser platform added (@andylockran) +
- Sensor: Dweet.io platform added (@fabaff) +
- Alexa/Amazon echo component added (@balloob) +
- Device Tracker: FritzBox platform added (@deisi, @caiuspb) +
- Sensor: Wink now supports the Egg minders (@w1ll1am23) +
- Sensor: ELIQ Online platform added (@molobrakos) +
- Binary sensor: REST platform added (@fabaff) +
- Sensor: Torque (OBD2) platform added (@happyleavesaoc) +
@@ -337,89 +436,6 @@ The InfluxDB database is a so-called time se
-
- 0.7.6: Amazon FireTV, Radiotherm thermostats -
- -
-
- 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
-
-
-
- Device tracker: Newer TP-Link routers now supported (@mKeRix) -
- Alarm Control Panel: Manual alarm added (@sfam) -
- Thermostat: Radiotherm now supported (@toddeye) -
- Media Player: Amazon FireTV now supported (@happyleavesaoc) -
- Device Tracker: Geofancy now supported (@wind-rider) -
- New component Shell Command can expose shell commands as services (@balloob) -
- Scripts can now be customized using
customizekey inconfiguration.yaml(@balloob)
- - Light: Hyperion now supported (@MakeMeASandwich) -
- Sensor: aRest can now also read out pins (@balloob) -
- Sensor: Forecast.io now supports specifying units in
configuration.yaml(@balloob)
- - Thermostat: Heat Control has been completely rewritten (@balloob) -
- Switch: Rest now supported (@bachp) -
- Media Player: Plex can now be auto discovered and configure itself (@tomduijf) -
- Downloader will now treat relative paths based on config dir (@tomduijf) -
- Line Charts will use interpolation for sensor data and show current and target temperature for thermostats (@balloob) -
- Device Tracker: OpenWRT via ubus now supported (@krzynio) -
-
- Report the temperature with ESP8266 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.
-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.
-
← Older
Newer →
diff --git a/blog/posts/12/index.html b/blog/posts/12/index.html
index 8de4dce1b1..e71b49f5ea 100644
--- a/blog/posts/12/index.html
+++ b/blog/posts/12/index.html
@@ -67,6 +67,89 @@
+
+
+
+
+
+
+
+
+
+
@@ -359,88 +442,6 @@ Inspried by a
-
-
-
-
-
-
-
+ 0.7.6: Amazon FireTV, Radiotherm thermostats +
+ +
+
+ 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
+
-
+
- Device tracker: Newer TP-Link routers now supported (@mKeRix) +
- Alarm Control Panel: Manual alarm added (@sfam) +
- Thermostat: Radiotherm now supported (@toddeye) +
- Media Player: Amazon FireTV now supported (@happyleavesaoc) +
- Device Tracker: Geofancy now supported (@wind-rider) +
- New component Shell Command can expose shell commands as services (@balloob) +
- Scripts can now be customized using
customizekey inconfiguration.yaml(@balloob)
+ - Light: Hyperion now supported (@MakeMeASandwich) +
- Sensor: aRest can now also read out pins (@balloob) +
- Sensor: Forecast.io now supports specifying units in
configuration.yaml(@balloob)
+ - Thermostat: Heat Control has been completely rewritten (@balloob) +
- Switch: Rest now supported (@bachp) +
- Media Player: Plex can now be auto discovered and configure itself (@tomduijf) +
- Downloader will now treat relative paths based on config dir (@tomduijf) +
- Line Charts will use interpolation for sensor data and show current and target temperature for thermostats (@balloob) +
- Device Tracker: OpenWRT via ubus now supported (@krzynio) +
+
+ Report the temperature with ESP8266 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.
+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.
+
@@ -359,88 +442,6 @@ Inspried by a
-
-
- Verisure devices and modern TP-Link routers now supported
-
-
-
-
- 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.
-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
-
-Verisure Support
-
Home Assistant support to integrate your Verisure alarms, hygrometers, sensors and thermometers has been contributed by @persandstrom.
-# Example configuration.yaml entry
-verisure:
- username: user@example.com
- password: password
- alarm: 1
- hygrometers: 0
- smartplugs: 1
- thermometers: 0
-
-
-
-
- Verisure devices and modern TP-Link routers now supported -
- -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.
-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 -
Verisure Support
- Home Assistant support to integrate your Verisure alarms, hygrometers, sensors and thermometers has been contributed by @persandstrom.
# Example configuration.yaml entry
-verisure:
- username: user@example.com
- password: password
- alarm: 1
- hygrometers: 0
- smartplugs: 1
- thermometers: 0
--
- MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported -
- -
-
- Read on →
-
- 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
-
← Older
Newer →
diff --git a/blog/posts/13/index.html b/blog/posts/13/index.html
index 73726c3256..f420619183 100644
--- a/blog/posts/13/index.html
+++ b/blog/posts/13/index.html
@@ -67,6 +67,88 @@
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+ Verisure devices and modern TP-Link routers now supported +
+ +
+
+
+ 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.
+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 +
Verisure Support
+ Home Assistant support to integrate your Verisure alarms, hygrometers, sensors and thermometers has been contributed by @persandstrom.
# Example configuration.yaml entry
+verisure:
+ username: user@example.com
+ password: password
+ alarm: 1
+ hygrometers: 0
+ smartplugs: 1
+ thermometers: 0
++
+ MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported +
+ +
+
+ Read on →
+
+ 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
+@@ -394,62 +476,6 @@ The old logo, the new detailed logo and the new simple logo.
-
- Home Assistant moving to YAML -
- -
-
- Home Assistant is now using YAML for it’s configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.
-The new file is named configuration.yaml and if it can’t be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.
-The home-assistant.conf.example has been replaced with an updated configuration.yaml.example.
-Users of Home Assistant should migrate as the old configuration format is deprecated.
--
- Streaming updates -
- -
-
- Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.
-A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.
-
← Older
Newer →
diff --git a/blog/posts/14/index.html b/blog/posts/14/index.html
index f771270997..6da13b6778 100644
--- a/blog/posts/14/index.html
+++ b/blog/posts/14/index.html
@@ -67,6 +67,62 @@
+
+
+
+
+
+
+
+
+
+
diff --git a/blog/posts/2/index.html b/blog/posts/2/index.html
index f85f599fbc..c3726d0d56 100644
--- a/blog/posts/2/index.html
+++ b/blog/posts/2/index.html
@@ -67,6 +67,63 @@
+ Home Assistant moving to YAML +
+ +
+
+ Home Assistant is now using YAML for it’s configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.
+The new file is named configuration.yaml and if it can’t be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.
+The home-assistant.conf.example has been replaced with an updated configuration.yaml.example.
+Users of Home Assistant should migrate as the old configuration format is deprecated.
++
+ Streaming updates +
+ +
+
+ Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.
+A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.
+
diff --git a/blog/posts/2/index.html b/blog/posts/2/index.html
index f85f599fbc..c3726d0d56 100644
--- a/blog/posts/2/index.html
+++ b/blog/posts/2/index.html
@@ -67,6 +67,63 @@
+
+
+
+ ZWave Entity IDs
+
+
+
+
+ ZWave entity_ids have long been a source of frustration in Home Assistant. The first problem we faced was that depending on the order of node discovery, entity_ids could be discovered with different names on each run. To solve this we added the node id as a suffix to the entity_id. This ensured that entity_ids were generated deterministically on each run, but additional suffixes had to be added to handle edge cases where there would otherwise be a conflict. The resulting entity_ids worked, but have been difficult to work with and makes ZWave a strange exception among other Home Assistant components.
+Thanks to the awesome work of @turbokongen, a growing number of ZWave configuration options are now available from the new ZWave panel in the Home Assistant frontend. Among these new features is support for renaming of ZWave nodes and their underlying values. (These renames are persisted in zwcfg_*.xml) This is important, because these items are combined to form the Home Assistant entity name, which is used to generate the entity_id. Now that these options are available, ZWave users can rename nodes and values, influencing the entity_ids that are generated by Home Assistant.
+Now that users are able to control these names, we will be making changes to how the entity_ids are generated for ZWave entities. The ZWave entity_ids are going to switch back to using the standard entity_id generation from Home Assistant core, based on the entity names. Moving forward, if there is a conflict when generating entity_ids, a suffix will be added, and it will be the responsibility of the user to rename their nodes and values to avoid the conflict. This is the same as any other platform in Home Assistant where two devices are discovered with the same name.
+With the release of 0.47, this feature will be opt-in. Setting new_entity_ids: true under zwave: in your configuration.yaml will enable the new generation. After 0.48 this feature will become opt-out. From 0.48 onward, unless you’ve declared new_entity_ids: false you will switch to the new entity_id generation. At an undecided point in the future, the old entity_id generation will be removed completely.
+I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that breaking changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms.
+
+
+
+
+
+
+ Linux Action Show special about Home Assistant
+
+
+
+
+ Our founder Paulus Schoutsen is interviewed by Chris Fisher for a Linux Action Show special about home automation, Hass.io and the new Home Assistant podcast.
+
+
+
+
+
+
@@ -426,121 +483,6 @@ If you have a security key set in your Open Z-Wave Podcast.__init__ about Python and Home Assistant. Just realized that we never shared this on the blog, oops. Here it is, enjoy!
-
-
-
-
-
-
- Home Assistant on a Pi Zero W in 30 minutes
-
-
-
-
-
- 
-
-Saw the announcement yesterday for HASSbian 1.21 and got super excited?
-Today we’ll flash the latest HASSbian to a Raspbery Pi Zero W.
-With an added bonus that besides for an USB cable for power, there’s no need for any cables!
-What you’ll need:
-
- - a Raspberry Pi Zero W (an amazing tiny computer with built-in wifi)
- - a microSD card
- - some source of USB power
- - Wifi
- - a desktop or laptop
-
-Let’s get to it!
-First, download the HASSbian 1.21 image from here.
-Unzip it.
-Flash it to the microSD card. If you need a flash tool, try Etcher
-When the flashing finishes, remove it and plug it back in. You should see a drive called “boot”.
-Right in there, not in any folders, create a file called wpa_supplicant.conf.
-The contents of the configuration file should be something like this:
-(You may have to adjust for your configuration, hints here )
-network={
- ssid="YOUR_WIFI_NETWORK_NAME_HERE"
- psk="YOUR_WIFI_PASSWORD_HERE"
- key_mgmt=WPA-PSK
-}
-
-
-Next stick your SD card into the Raspberry Pi Zero W, and plug it in.
-After about a minute, use your SSH client to connect to HASSbian (or hassbian.local from a Mac), with the username pi. The default password is raspberry.
-It’s a good idea to change the password. To do so, use the passwd command.
-Next, type the following two commands into the SSH console:
-$ sudo systemctl enable install_homeassistant.service
-$ sudo systemctl start install_homeassistant.service
-
-
-Wait about 15-20 minutes and voilà you have your Home Assistant on your Raspberry Pi Zero W in 30 minutes.
-To try it out, go to http://hassbian:8123 or http://hassbian.local:8123 if you’re using Mac.
-For further details about HASSbian, take a look at the documentation.
-
-
-
-
-
-
- HASSbian 1.21 - It's about time isn't it
-
-
-
-
- Hassbian 1.21 - It’s about time isn’t it
-Since I, the developer of HASSbian, have been moving, started a new job and so on I’ve had few moments over for HASSbian development. The 1.2 release has been in pre-release for a few months now and just not communicated out that well. Hopefully this release changes that and I’ll do my best to release more often. There’s no simple way to update from 1.1 to 1.21 but 95% of the changes can be done by installing the hassbian-config package. For more information have a look at the hassbian-config page.
-Hassbian 1.22 - Sins of last night
-Development is sometimes fast and joyful but mistakes are made at times.
-With the release of 1.21 a small problem with the OpenZWave build script wasn’t corrected even tough it was a known bug. Problem is simple as it’s only a problem with the symlink created for to the configuration folder for OpenZWave. This has been fixed and we bring some new things since they where ready anyway. The list below has been augmented with the updated information.
- Hassbian-config
-To allow you to customize your installation further, we have included a tool called hassbian-config. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the hassbian-scripts functionality from 1.1.
-
- - Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.
- - Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.
- - Install Libcec. Adds local HDMI CEC support.
- - Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.
- - Install Open Z-Wave. Installs Python Open Z-Wave and OZWCP from git.
- - Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and it’s usage is not recommended if you share your network with others.
- - Install Tellstick. Installs the Tellstick package for controlling and using a connected Tellstick.
- - Install Tradfri. Installs dependencies for using IKEA Trådfri.
-
- Spring cleaning
-With this image there also quite a bit of cleaning of the base system and the script that generates our Raspberry Pi image.
-
- - Replaced the
hassbian-scripts folder with hassbian-config.
- - Update
pi-gen. Our build script has been upgraded to follow the Raspbian image closer once again. Now you could build this image with Docker if your so inclined.
- - Added libtool and autoconf package. Dependencies for some of the pip packages.
- - Pi ZeroW should now work with the image.
-
-To follow discussions about the development of the HASSbian image or to contribute join our Discord chat server.
-To get started with the new image, check out the installation instructions in the getting started section.
diff --git a/blog/posts/3/index.html b/blog/posts/3/index.html
index 86e8afb4c6..05fdacfb5e 100644
--- a/blog/posts/3/index.html
+++ b/blog/posts/3/index.html
@@ -67,6 +67,121 @@
+
+
+
+ Home Assistant on a Pi Zero W in 30 minutes
+
+
+
+
+
+
+
+Saw the announcement yesterday for HASSbian 1.21 and got super excited?
+Today we’ll flash the latest HASSbian to a Raspbery Pi Zero W.
+With an added bonus that besides for an USB cable for power, there’s no need for any cables!
+What you’ll need:
+
+ - a Raspberry Pi Zero W (an amazing tiny computer with built-in wifi)
+ - a microSD card
+ - some source of USB power
+ - Wifi
+ - a desktop or laptop
+
+Let’s get to it!
+First, download the HASSbian 1.21 image from here.
+Unzip it.
+Flash it to the microSD card. If you need a flash tool, try Etcher
+When the flashing finishes, remove it and plug it back in. You should see a drive called “boot”.
+Right in there, not in any folders, create a file called wpa_supplicant.conf.
+The contents of the configuration file should be something like this:
+(You may have to adjust for your configuration, hints here )
+network={
+ ssid="YOUR_WIFI_NETWORK_NAME_HERE"
+ psk="YOUR_WIFI_PASSWORD_HERE"
+ key_mgmt=WPA-PSK
+}
+
+
+Next stick your SD card into the Raspberry Pi Zero W, and plug it in.
+After about a minute, use your SSH client to connect to HASSbian (or hassbian.local from a Mac), with the username pi. The default password is raspberry.
+It’s a good idea to change the password. To do so, use the passwd command.
+Next, type the following two commands into the SSH console:
+$ sudo systemctl enable install_homeassistant.service
+$ sudo systemctl start install_homeassistant.service
+
+
+Wait about 15-20 minutes and voilà you have your Home Assistant on your Raspberry Pi Zero W in 30 minutes.
+To try it out, go to http://hassbian:8123 or http://hassbian.local:8123 if you’re using Mac.
+For further details about HASSbian, take a look at the documentation.
+
+
+
+
+
+
+ HASSbian 1.21 - It's about time isn't it
+
+
+
+
+ Hassbian 1.21 - It’s about time isn’t it
+Since I, the developer of HASSbian, have been moving, started a new job and so on I’ve had few moments over for HASSbian development. The 1.2 release has been in pre-release for a few months now and just not communicated out that well. Hopefully this release changes that and I’ll do my best to release more often. There’s no simple way to update from 1.1 to 1.21 but 95% of the changes can be done by installing the hassbian-config package. For more information have a look at the hassbian-config page.
+Hassbian 1.22 - Sins of last night
+Development is sometimes fast and joyful but mistakes are made at times.
+With the release of 1.21 a small problem with the OpenZWave build script wasn’t corrected even tough it was a known bug. Problem is simple as it’s only a problem with the symlink created for to the configuration folder for OpenZWave. This has been fixed and we bring some new things since they where ready anyway. The list below has been augmented with the updated information.
+ Hassbian-config
+To allow you to customize your installation further, we have included a tool called hassbian-config. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the hassbian-scripts functionality from 1.1.
+
+ - Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.
+ - Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.
+ - Install Libcec. Adds local HDMI CEC support.
+ - Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.
+ - Install Open Z-Wave. Installs Python Open Z-Wave and OZWCP from git.
+ - Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and it’s usage is not recommended if you share your network with others.
+ - Install Tellstick. Installs the Tellstick package for controlling and using a connected Tellstick.
+ - Install Tradfri. Installs dependencies for using IKEA Trådfri.
+
+ Spring cleaning
+With this image there also quite a bit of cleaning of the base system and the script that generates our Raspberry Pi image.
+
+ - Replaced the
hassbian-scripts folder with hassbian-config.
+ - Update
pi-gen. Our build script has been upgraded to follow the Raspbian image closer once again. Now you could build this image with Docker if your so inclined.
+ - Added libtool and autoconf package. Dependencies for some of the pip packages.
+ - Pi ZeroW should now work with the image.
+
+To follow discussions about the development of the HASSbian image or to contribute join our Discord chat server.
+To get started with the new image, check out the installation instructions in the getting started section.
+
+
+
@@ -406,87 +521,6 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
-
-
-
- Home Assistant 0.41: Tado, Volumio, Workday, improved Plex
-
-
-
-
- Welcome to 0.41. There was a lot going on in the last two weeks. Not only from the code side but also from the social one of Home Assistant. Paulus did an interview with OpenSourceCraft, Fabian did a workshop at the Chemnitzer Linux Tage, and we are now an award-winning Open source project (I will cover that in a separate blog post).
-Plex
-@JesseWebDotCom made massive changes to the Plex media player platform. From better metadata support over new configuration options to improved controls and non-controllable clients.
-Component overview
-The Components overview is now powered by search/filtering feature. This will make it faster to get the component/platform you are looking for more quickly. Thanks again, @bdurrer for this.
-Changelog
-The new format of the changelog which was introduced with 0.40 will provide a link to the related pull request. We are not covering everything in our release notes but we think that this addition will make it easier to find details about the change.
-New platforms/components
-
- - Support for Tado climate devices (@wmalgadey)
- - Volumio media player added (@jslove)
- - Workday sensor (@BastianPoe)
-
-Breaking changes
-
- - The Kodi notifier platform was migrated to async and the configuration synced with the Kodi media player platform (#6497).
- - For the Music Player Daemon (MPD) platform was
location replaced with name (#6553).
- - Event decorators were removed (#6634).
- - The Emby mediaplayer platform was changed to avoid name clashes (#6664).
- - In a lot of places were the power and energy units update. This change mostly affects the
switch platforms (#6212).
- - If set to
auto then the MQTT implementation will use the bundled certificates automatically (#6707).
- - Autodiscovery of Android IP Webcam was removed (#6528).
- - The frontend is now using Shadow DOM and this could break your custom panels (#228).
-
-If you need help…
-…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
-Reporting Issues
-Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
- Read on →
-
-
-
-
-
-
- OpenSourceCraft interviews our founder Paulus Schoutsen
-
-
-
-
- Last month Gregg Pollack from OpenSourceCraft visited me in San Diego to talk about Home Assistant. We talked about the community and how all these awesome people make Home Assistant possible. The main interview is embedded below but make sure to check out the full article including extra video material.
-
-
-
-
-
-
← Older
Newer →
diff --git a/blog/posts/4/index.html b/blog/posts/4/index.html
index fc1467d92c..6449440d71 100644
--- a/blog/posts/4/index.html
+++ b/blog/posts/4/index.html
@@ -67,6 +67,87 @@
+
+
+
+ Home Assistant 0.41: Tado, Volumio, Workday, improved Plex
+
+
+
+
+ Welcome to 0.41. There was a lot going on in the last two weeks. Not only from the code side but also from the social one of Home Assistant. Paulus did an interview with OpenSourceCraft, Fabian did a workshop at the Chemnitzer Linux Tage, and we are now an award-winning Open source project (I will cover that in a separate blog post).
+Plex
+@JesseWebDotCom made massive changes to the Plex media player platform. From better metadata support over new configuration options to improved controls and non-controllable clients.
+Component overview
+The Components overview is now powered by search/filtering feature. This will make it faster to get the component/platform you are looking for more quickly. Thanks again, @bdurrer for this.
+Changelog
+The new format of the changelog which was introduced with 0.40 will provide a link to the related pull request. We are not covering everything in our release notes but we think that this addition will make it easier to find details about the change.
+New platforms/components
+
+ - Support for Tado climate devices (@wmalgadey)
+ - Volumio media player added (@jslove)
+ - Workday sensor (@BastianPoe)
+
+Breaking changes
+
+ - The Kodi notifier platform was migrated to async and the configuration synced with the Kodi media player platform (#6497).
+ - For the Music Player Daemon (MPD) platform was
location replaced with name (#6553).
+ - Event decorators were removed (#6634).
+ - The Emby mediaplayer platform was changed to avoid name clashes (#6664).
+ - In a lot of places were the power and energy units update. This change mostly affects the
switch platforms (#6212).
+ - If set to
auto then the MQTT implementation will use the bundled certificates automatically (#6707).
+ - Autodiscovery of Android IP Webcam was removed (#6528).
+ - The frontend is now using Shadow DOM and this could break your custom panels (#228).
+
+If you need help…
+…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+Reporting Issues
+Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
+ Read on →
+
+
+
+
+
+
+ OpenSourceCraft interviews our founder Paulus Schoutsen
+
+
+
+
+ Last month Gregg Pollack from OpenSourceCraft visited me in San Diego to talk about Home Assistant. We talked about the community and how all these awesome people make Home Assistant possible. The main interview is embedded below but make sure to check out the full article including extra video material.
+
+
+
+
+
+
@@ -604,195 +685,6 @@ On the close horizon from @Landrash th
-
-
-
- 0.37: Face detection, Coffee, Wink
-
-
-
-
- No stats, no numbers, and alike this time. Ok, just one number: 0.37. We are back on track with our bi-weekly release cycle. Beside some organizational changes is this release shipping again cool features and new integrations. Please keep an eye on the “Breaking changes” section because there are also massive improvements for some platforms and components.
- Governance
-As announced, the new Governance requires for developers to sign the CLA. Code of Conduct, Contributor License Agreement, and proper Licensing will to protect all involved parties in the Home Assistant eco-system from users and community members to contributors.
- Face recognition using the Microsoft Face API
-@pvizeli has been on a roll with the image processing integrations. This time it’s the Microsoft Face API. This means that now it will be possible to train the API with the people you want to recognize and send images from your camera to the API as another source of automation.
-Want to play a personalized tune when someone enters the house? It is now possible 😎
- Improved camera security
-After a security audit by Stephen O’Conner, he found that our source for randomly generated access tokens for camera feeds were reasonable predictable and could be brute force attacked in 2.5 weeks. A fix has been included in this release that uses the system provided random number generator for maximum randomness and rotates the keys every 10 minutes to reduce the window in which a brute force attack can happen.
-Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.
- New customization options
-@Andrey-git has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.
- Major Wink and HDMI CEC improvements
-@w1ll1am23 did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your configuration.yaml file, no client_id and client_secret are needed, and token which was generated with the generator located in the Wink documentation.
-The new Wink support will cause renaming of all the binary sensors and will also create new sensors for devices that weren’t previously detected or supported in the older version.
-Thanks to @konikvranik the HDMI CEC integration got a huge update with a lot of improvements. This update should make it easier to work with HDMI CEC and give you more control.
- First Coffee Maker supported
-@stu-gott has added support for the first coffee maker in Home Assistant: Mr. Coffee Smart Optimal Brew. Happy brewing!
- All changes
- New platforms/components
-
- - Netatmo: Netatmo Presence support (@gieljnssns)
- - Sensor: Amcrest camera sensors (@tchellomello)
- - Notify: New Discord notification component (@Deinara)
- - Device tracker: Tado device tracker support (@jmvermeulen)
- - Sensor: Add Skybeacon BLE temperature/humidity sensor (@anpetrov)
- - New Zabbix component (@Whytey)
- - Media player: New platform Anthemav Media player (@nugget)
- - Light: Add support for Avion Bluetooth dimmer switches (@mjg59)
- - Binary sensor: Beaglebone Black binary sensor (@MatoKafkac)
- - Light: Piglow support (@xarnze)
- - Face recognition for automation (@pvizeli)
- - Sensor: New Washington State DOT sensor (@partofthething)
- - Support for Wemo CoffeeMaker devices (@stu-gott)
- - Device tracker: Sky hub support (@alexmogavero)
- - Support for Lutron RadioRA 2 (@thecynic)
- - TTS: Amazon Polly TTS platform (@robbiet480)
- - Device tracker: Support for Linksys Access Points (@lukas-hetzenecker)
- - Notify: Make calls with Twilio (@fakezeta)
-
- Improvements
-
- - Script: Fix script release (@balloob)
- - Camera - Amcrest: Add support for direct MJPEG streams from Amcrest cameras (@colinodell)
- - Sensor - Miflora: Removing throttle decorator (@freol35241)
- - Notify - Lannouncer: Fix
get_service method (@mKeRix)
- - Sensor - WAQI: Add station parameter to waqi sensor (@whhsw)
- - Sensor - USPS: Absolute path to save cookie used by USPS sensor (@tchellomello)
- - Nest: Fix python-nest release number (@Danielhiversen)
- - Keyboard remote: Improve support (@MrMep)
- - Device tracker - VolvoOnCall: Fix timedelta (@pvizeli)
- - Climate - eq3btsmart: Expose away attribute (@rytilahti)
- - Remote: Reserve a test port for broken API to fix race (@armills)
- - Climate - Ecobee: Made target temperature sensitive to auto mode (@Duoxilian)
- - Configuration: Fix load_yaml default value (@balloob)
- - Notify - Facebook: Fix encoding error (@Danielhiversen)
- - Emulated_hue: Add
upnp_bind_multicast option, default type to Google, and persist emulated hue IDs (@hoopty, @balloob)
- - Docker: Install phantomjs in Docker container (@jnewland)
- - Media player - MPD: Add listing and selection of available MPD playlists (@partofthething)
- - Media player - Denon AVR: Denon improvements (@glance-)
- - Light - x10.py: Improved x10 state monitoring (@martst)
- - Sensor - DSMR: TCP, reconnecting and V4 CRC support (@aequitas)
- - Media player - Yamaha.py: Fix Yamaha doing I/O in event loop (@balloob)
- - Device tracker UPC: Make upc more robust (@pvizeli)
- - Climate - Generic thermostat: Update (@MrMep)
- - Device tracker - Xiaomi.py: Xiaomi Mi Router token refresh (@RiRomain)
- - Camera - MJPEG: Support still image for thumbmail (@pvizeli)
- - Sensor - ZAMG: Updated valid station id list (@HerrHofrat)
- - Light - ISY994: Not overwrite
state_attributes (@rmkraus)emul-hue
- - Light - Zwave: Use only supported features for devices (@turbokongen)
- - Media player - Kodi: Support for volume stepping (@armills)
- - Media player- roku: Use
is_screensaver, update IDLE state, and use device name (@robbiet480, @xhostplus)
- - Switch - HDMI CEC: Support for devices and commands (@konikvranik)
- - Lock - Zwave: Improvements to Zwave lock platform (@turbokongen)
- - TTS: Invalidate broken file cache entries (@stu-gott)
- - Light - Hue: Improvements (@robbiet480)
- - TTS - YandexTTS: Added speed and emotion to Yandex TTS (@lupin-de-mid)
- - Light - tellstick.py: Tellstick light fix (@stefan-jonasson)
- - Switch - insteon_local.py: only check for devices when not defined in config (@wardcraigj)
- - Notify - Twitter: Allow direct messaging to user (@fabaff)
- - Fan - MQTT: Dont set a speed when fan turns on (@robbiet480)
- - Config: Allow easier customization of whole domain, entity lists, globs (@andrey-git)
- - Sensor - Homematic: Update device support (@danielperna84)
- - Binary sensor - ISS: Add location to attributes and option to show position on the map (@fabaff)
- - Media player - Kodi: Add SSL configuration option (@ecksun)
- - Sensor - WAQI: Add missing particle value (@fabaff)
- - Wink: Support for python-wink 1.0.0 (@w1ll1am23)
- - Binary sensor - RPi GPIO: Add a small sleep before reading the sensor (@snagytx)
- - Sensor - USPS: Add name to configuration (@happyleavesaoc)
- - Sensor - Miflora: Remove throttle decorator from miflora platform (@freol35241)
- - Device tracker - asuswrt.py: Add IPv6 support when parsing neighbors (@leppa)
- - iOS: Discover notify.ios when iOS component loads (@robbiet480)
- - Homematic: Add MAX shutter contact class (@jannau)
- - Sensor - Darksky: Added forecast support (@nordlead2005)
- - Switch - Pilight: Implement echo config option (@janLo)
- - Core: Support customize in packages (@kellerza)
- - Switch - Flux: Allow disabling setting the brightness (@rytilahti)
- - Media player - Sonos: Add
is_coordinator, set coordinator after join/unjoin, and no emtpy image (@pvizeli, @andrey-git, @robbiet480)
- - Climate: Hold mode (@Duoxilian)
- - Switch - TPlink: No longer doing I/O in event bus (@balloob)
- - Light - Insteon local: Improve Insteon configuration (@wardcraigj)
- - Emulated Hue: Emulated Hue “host-ip” fails to bind when running in docker without
--net=host (@jeremydk)
- - Climate - EQ3 BT smart: Add reporting for availability (@rytilahti)
-
-Bugfix: @balloob, @fabaff, @freol35241, @pvizeli, @Danielhiversen, @tdickman, @armills, @rytilahti, @R1chardTM, @asbach, @happyleavesaoc, @robbiet480, @colinodell, @joopert, @dale3h, @pavoni, @jaharkes, @MartinHjelmare, @mezz64, @jabesq, and you if you are missing in this list.
- Release 0.37.1 - February 2
-
- - Do not reject alphanumeric IDs for PiLight (@DavidLP)
- - Fix broken Hue discovery (@DanielHiversen)
- - Fix Amcrest (@tchellomello)
- - Fix Telldus Live dim level error on startup (@molobrakos)
- - Fix Sonos group coordinators (@pvizeli)
- - UPC Connect: Parse XML outside event loop (@pvizeli)
- - Fix Netatmo SSL issue with VPN URL (@jabesq)
- - Homematic: Fix bug with UNREACH device state/restore and variables not updating (@pvizeli)
- - Sonos: Prevent duplicate entries in favorite list (@pvizeli)
- - Fix Schlage Connect deadbolt integration via Z-Wave (@turbokongen)
- - Prevent infinite loop in crossconfigured mqtt event streams (@aequitas)
- - Fix Hue lightgroups failing on startup (@tboyce1)
-
- Breaking changes
-
- - A major breaking change in the
emulated_hue component means that unless you set type: alexa before starting up the newer Home Assistant version you will lose all devices that Alexa has discovered and will need to re-add them as well as create new groups.
- - The platform of the ISS integration was change to
binary_sensor. Please check the platform documentation.
- - The Roku media uses now a new format for the entity IDs.
- - OpenALPR is no longer a component. It’s now a platform for Image processing.
- - Due to massive improvements of the Wink integration, the names of your binary sensors will change and new devices can show up.
- - The MySensors component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you.
- - The Sonos service
sonos_group_players was removed. Use now sonos_join for this function.
- - TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g.
HASH_LANG_PLATFORM.xxx -> HASH_LANG_OPTIONS_PLATFORM.xxx, replace OPTIONS with - on exiting platforms.
-
- If you need help…
-…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
- Reporting Issues
-Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
-
-
-
-
-
-
- Home Assistant Governance [updated]
-
-
-
-
- UPDATE JAN 28, 2017
-After feedback from the community we have updated the CLA and the license that Home Assistant is distributed under. For the CLA, instead of enforcing requirements on the grants and code, we now require contributions to be licensed under the Apache 2.0 license. Special thanks to Matthew Garrett for his feedback and advice.
-Starting with release 0.37, Home Assistant will re-license the current code under the Apache 2.0 license. This is the license that will be used moving forward for all projects under our organization.
-
-The Home Assistant project and community has seen enormous growth in the last three years. Many volunteers work tirelessly everyday to give you all the awesomeness that you see today. Much more work is involved than many people realize. Beyond simply coding Home Assistant, volunteers continually maintain related projects, update documentation, post examples, author blog posts, and moderate the forums and chat. This is something that we want to keep safe and functional, even as we grow.
-Starting today we are announcing a few initiatives to help protect our users, contributors and community members.
- Read on →
-
-
-
← Older
Newer →
diff --git a/blog/posts/5/index.html b/blog/posts/5/index.html
index 74d9d24b67..59c1361425 100644
--- a/blog/posts/5/index.html
+++ b/blog/posts/5/index.html
@@ -67,6 +67,195 @@
+
+
+
+ 0.37: Face detection, Coffee, Wink
+
+
+
+
+ No stats, no numbers, and alike this time. Ok, just one number: 0.37. We are back on track with our bi-weekly release cycle. Beside some organizational changes is this release shipping again cool features and new integrations. Please keep an eye on the “Breaking changes” section because there are also massive improvements for some platforms and components.
+ Governance
+As announced, the new Governance requires for developers to sign the CLA. Code of Conduct, Contributor License Agreement, and proper Licensing will to protect all involved parties in the Home Assistant eco-system from users and community members to contributors.
+ Face recognition using the Microsoft Face API
+@pvizeli has been on a roll with the image processing integrations. This time it’s the Microsoft Face API. This means that now it will be possible to train the API with the people you want to recognize and send images from your camera to the API as another source of automation.
+Want to play a personalized tune when someone enters the house? It is now possible 😎
+ Improved camera security
+After a security audit by Stephen O’Conner, he found that our source for randomly generated access tokens for camera feeds were reasonable predictable and could be brute force attacked in 2.5 weeks. A fix has been included in this release that uses the system provided random number generator for maximum randomness and rotates the keys every 10 minutes to reduce the window in which a brute force attack can happen.
+Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.
+ New customization options
+@Andrey-git has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.
+ Major Wink and HDMI CEC improvements
+@w1ll1am23 did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your configuration.yaml file, no client_id and client_secret are needed, and token which was generated with the generator located in the Wink documentation.
+The new Wink support will cause renaming of all the binary sensors and will also create new sensors for devices that weren’t previously detected or supported in the older version.
+Thanks to @konikvranik the HDMI CEC integration got a huge update with a lot of improvements. This update should make it easier to work with HDMI CEC and give you more control.
+ First Coffee Maker supported
+@stu-gott has added support for the first coffee maker in Home Assistant: Mr. Coffee Smart Optimal Brew. Happy brewing!
+ All changes
+ New platforms/components
+
+ - Netatmo: Netatmo Presence support (@gieljnssns)
+ - Sensor: Amcrest camera sensors (@tchellomello)
+ - Notify: New Discord notification component (@Deinara)
+ - Device tracker: Tado device tracker support (@jmvermeulen)
+ - Sensor: Add Skybeacon BLE temperature/humidity sensor (@anpetrov)
+ - New Zabbix component (@Whytey)
+ - Media player: New platform Anthemav Media player (@nugget)
+ - Light: Add support for Avion Bluetooth dimmer switches (@mjg59)
+ - Binary sensor: Beaglebone Black binary sensor (@MatoKafkac)
+ - Light: Piglow support (@xarnze)
+ - Face recognition for automation (@pvizeli)
+ - Sensor: New Washington State DOT sensor (@partofthething)
+ - Support for Wemo CoffeeMaker devices (@stu-gott)
+ - Device tracker: Sky hub support (@alexmogavero)
+ - Support for Lutron RadioRA 2 (@thecynic)
+ - TTS: Amazon Polly TTS platform (@robbiet480)
+ - Device tracker: Support for Linksys Access Points (@lukas-hetzenecker)
+ - Notify: Make calls with Twilio (@fakezeta)
+
+ Improvements
+
+ - Script: Fix script release (@balloob)
+ - Camera - Amcrest: Add support for direct MJPEG streams from Amcrest cameras (@colinodell)
+ - Sensor - Miflora: Removing throttle decorator (@freol35241)
+ - Notify - Lannouncer: Fix
get_service method (@mKeRix)
+ - Sensor - WAQI: Add station parameter to waqi sensor (@whhsw)
+ - Sensor - USPS: Absolute path to save cookie used by USPS sensor (@tchellomello)
+ - Nest: Fix python-nest release number (@Danielhiversen)
+ - Keyboard remote: Improve support (@MrMep)
+ - Device tracker - VolvoOnCall: Fix timedelta (@pvizeli)
+ - Climate - eq3btsmart: Expose away attribute (@rytilahti)
+ - Remote: Reserve a test port for broken API to fix race (@armills)
+ - Climate - Ecobee: Made target temperature sensitive to auto mode (@Duoxilian)
+ - Configuration: Fix load_yaml default value (@balloob)
+ - Notify - Facebook: Fix encoding error (@Danielhiversen)
+ - Emulated_hue: Add
upnp_bind_multicast option, default type to Google, and persist emulated hue IDs (@hoopty, @balloob)
+ - Docker: Install phantomjs in Docker container (@jnewland)
+ - Media player - MPD: Add listing and selection of available MPD playlists (@partofthething)
+ - Media player - Denon AVR: Denon improvements (@glance-)
+ - Light - x10.py: Improved x10 state monitoring (@martst)
+ - Sensor - DSMR: TCP, reconnecting and V4 CRC support (@aequitas)
+ - Media player - Yamaha.py: Fix Yamaha doing I/O in event loop (@balloob)
+ - Device tracker UPC: Make upc more robust (@pvizeli)
+ - Climate - Generic thermostat: Update (@MrMep)
+ - Device tracker - Xiaomi.py: Xiaomi Mi Router token refresh (@RiRomain)
+ - Camera - MJPEG: Support still image for thumbmail (@pvizeli)
+ - Sensor - ZAMG: Updated valid station id list (@HerrHofrat)
+ - Light - ISY994: Not overwrite
state_attributes (@rmkraus)emul-hue
+ - Light - Zwave: Use only supported features for devices (@turbokongen)
+ - Media player - Kodi: Support for volume stepping (@armills)
+ - Media player- roku: Use
is_screensaver, update IDLE state, and use device name (@robbiet480, @xhostplus)
+ - Switch - HDMI CEC: Support for devices and commands (@konikvranik)
+ - Lock - Zwave: Improvements to Zwave lock platform (@turbokongen)
+ - TTS: Invalidate broken file cache entries (@stu-gott)
+ - Light - Hue: Improvements (@robbiet480)
+ - TTS - YandexTTS: Added speed and emotion to Yandex TTS (@lupin-de-mid)
+ - Light - tellstick.py: Tellstick light fix (@stefan-jonasson)
+ - Switch - insteon_local.py: only check for devices when not defined in config (@wardcraigj)
+ - Notify - Twitter: Allow direct messaging to user (@fabaff)
+ - Fan - MQTT: Dont set a speed when fan turns on (@robbiet480)
+ - Config: Allow easier customization of whole domain, entity lists, globs (@andrey-git)
+ - Sensor - Homematic: Update device support (@danielperna84)
+ - Binary sensor - ISS: Add location to attributes and option to show position on the map (@fabaff)
+ - Media player - Kodi: Add SSL configuration option (@ecksun)
+ - Sensor - WAQI: Add missing particle value (@fabaff)
+ - Wink: Support for python-wink 1.0.0 (@w1ll1am23)
+ - Binary sensor - RPi GPIO: Add a small sleep before reading the sensor (@snagytx)
+ - Sensor - USPS: Add name to configuration (@happyleavesaoc)
+ - Sensor - Miflora: Remove throttle decorator from miflora platform (@freol35241)
+ - Device tracker - asuswrt.py: Add IPv6 support when parsing neighbors (@leppa)
+ - iOS: Discover notify.ios when iOS component loads (@robbiet480)
+ - Homematic: Add MAX shutter contact class (@jannau)
+ - Sensor - Darksky: Added forecast support (@nordlead2005)
+ - Switch - Pilight: Implement echo config option (@janLo)
+ - Core: Support customize in packages (@kellerza)
+ - Switch - Flux: Allow disabling setting the brightness (@rytilahti)
+ - Media player - Sonos: Add
is_coordinator, set coordinator after join/unjoin, and no emtpy image (@pvizeli, @andrey-git, @robbiet480)
+ - Climate: Hold mode (@Duoxilian)
+ - Switch - TPlink: No longer doing I/O in event bus (@balloob)
+ - Light - Insteon local: Improve Insteon configuration (@wardcraigj)
+ - Emulated Hue: Emulated Hue “host-ip” fails to bind when running in docker without
--net=host (@jeremydk)
+ - Climate - EQ3 BT smart: Add reporting for availability (@rytilahti)
+
+Bugfix: @balloob, @fabaff, @freol35241, @pvizeli, @Danielhiversen, @tdickman, @armills, @rytilahti, @R1chardTM, @asbach, @happyleavesaoc, @robbiet480, @colinodell, @joopert, @dale3h, @pavoni, @jaharkes, @MartinHjelmare, @mezz64, @jabesq, and you if you are missing in this list.
+ Release 0.37.1 - February 2
+
+ - Do not reject alphanumeric IDs for PiLight (@DavidLP)
+ - Fix broken Hue discovery (@DanielHiversen)
+ - Fix Amcrest (@tchellomello)
+ - Fix Telldus Live dim level error on startup (@molobrakos)
+ - Fix Sonos group coordinators (@pvizeli)
+ - UPC Connect: Parse XML outside event loop (@pvizeli)
+ - Fix Netatmo SSL issue with VPN URL (@jabesq)
+ - Homematic: Fix bug with UNREACH device state/restore and variables not updating (@pvizeli)
+ - Sonos: Prevent duplicate entries in favorite list (@pvizeli)
+ - Fix Schlage Connect deadbolt integration via Z-Wave (@turbokongen)
+ - Prevent infinite loop in crossconfigured mqtt event streams (@aequitas)
+ - Fix Hue lightgroups failing on startup (@tboyce1)
+
+ Breaking changes
+
+ - A major breaking change in the
emulated_hue component means that unless you set type: alexa before starting up the newer Home Assistant version you will lose all devices that Alexa has discovered and will need to re-add them as well as create new groups.
+ - The platform of the ISS integration was change to
binary_sensor. Please check the platform documentation.
+ - The Roku media uses now a new format for the entity IDs.
+ - OpenALPR is no longer a component. It’s now a platform for Image processing.
+ - Due to massive improvements of the Wink integration, the names of your binary sensors will change and new devices can show up.
+ - The MySensors component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you.
+ - The Sonos service
sonos_group_players was removed. Use now sonos_join for this function.
+ - TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g.
HASH_LANG_PLATFORM.xxx -> HASH_LANG_OPTIONS_PLATFORM.xxx, replace OPTIONS with - on exiting platforms.
+
+ If you need help…
+…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+ Reporting Issues
+Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
+
+
+
+
+
+
+ Home Assistant Governance [updated]
+
+
+
+
+ UPDATE JAN 28, 2017
+After feedback from the community we have updated the CLA and the license that Home Assistant is distributed under. For the CLA, instead of enforcing requirements on the grants and code, we now require contributions to be licensed under the Apache 2.0 license. Special thanks to Matthew Garrett for his feedback and advice.
+Starting with release 0.37, Home Assistant will re-license the current code under the Apache 2.0 license. This is the license that will be used moving forward for all projects under our organization.
+
+The Home Assistant project and community has seen enormous growth in the last three years. Many volunteers work tirelessly everyday to give you all the awesomeness that you see today. Much more work is involved than many people realize. Beyond simply coding Home Assistant, volunteers continually maintain related projects, update documentation, post examples, author blog posts, and moderate the forums and chat. This is something that we want to keep safe and functional, even as we grow.
+Starting today we are announcing a few initiatives to help protect our users, contributors and community members.
+ Read on →
+
+
+
@@ -715,328 +904,6 @@ You have to note:
If you need help…
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
-
-
-
-
-
-
- Explaining the Updater
-
-
-
-
- On Saturday, we released Home Assistant 0.31 which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.
- Read on →
-
-
-
-
-
-
- 0.31: Reading you the news, some serious business, spooky hackery and a breaking Z-Wave change
-
-
-
-
- Hello again friend,
-How are you? Having a good day? We sure are. If you aren’t having a good day, this might cheer you up…
-Every other weekend around here gets a little hectic leading to a big sigh of relief as we release a new version of Home Assistant to the world. And this time is no different. Our developer community has once again built us a beautiful new release with lots of new features and improvements. We hope you like it.
-One last thing before we get going though, I should warn you… @balloob got a bit lazy this week and let me (@robbiet480) step up to the plate again to write the blog post and do the release. I guess I didn’t do such a bad job in 0.27. You’ll never know what surprises I have in store. Now that i’ve got all that stuff out of the way, let’s get started…
- Stats Update
-Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
- Hacktoberfest
-
-October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the home-assistant repository and 209 merged/28 open pull requests submitted to the home-assistant.github.io repository. If you want to get in on the fun check out our Hacktoberfest blog post or the Hacktoberfest website. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
- ⚠️ A greatly improved updater component (Please read this!) ⚠️
-This release includes an update to our updater component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
-It used to be that this component would check with PyPi (the Python package manager) to see if a new update was available. This had a couple of problems:
-
- - We are unable to do a slow rollout
- - We are unable to show the user extra information (like a link to a changelog or the release date)
- - We are unable to warn users for critical security updates
-
-So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
- What you need to know (the important bit!)
-Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
-Each Home Assistant instance running the updater component will generate a unique ID (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called .uuid.
-Opting out
-There are two ways to opt-out. The first way is by using the new opt_out option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
-updater:
- reporting: no
-
-
-You can also disable the updater component entirely by removing updater: from your configuration.yaml although we would not suggest you do this as you would miss any critical updates.
-Finally, you can also reset your unique identifier by deleting the .uuid file and restarting Home Assistant.
-Data stored on the Home Assistant update server
-Here is what my production Home Assistant instance looks like from the server side:
-
-
-
- Name
- Description
- Example
-
-
-
-
- archCPU Architecture
- x86_64
-
- distributionLinux Distribution name (only Linux)
- Ubuntu
-
- dockerTrue if running inside Docker
- false
-
- os_nameOperating system name
- Darwin
-
- os_versionOperating system version
- 10.12
-
- python_versionPython version
- 3.5.2
-
- timezoneTimezone
- America/Los_Angeles
-
- user_agentUser agent used to submit analytics
- python-requests/2.11.1
-
- uuidUnique identifier
- 10321ee6094d4a2ebb5ed55c675d5f5e
-
- versionHome Assistant version
- 0.31.0
-
- virtualenvTrue if running inside virtualenv
- true
-
-
-In addition to the above collected data, the server will also use your IP address to do a geographic IP address lookup to determine the city that you are from. To be extremely, extremely clear about this bit: The Home Assistant updater does not: store your IP address in a database and also does not submit the location information from your configuration.yaml.
-
- 
- Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
-
-The server also adds two timestamps to the data: the original date your instance UUID was first seen and the timestamp of the last time we have seen your instance. This gives us the following extra data:
-
-
-
- Name
- Description
- Example
-
-
-
-
- first_seen_datetimeFirst time instance ID was submitted
- 2016-10-22T19:56:03.542Z
-
- geo_cityGeoIP determined city
- Oakland
-
- geo_country_codeGeoIP determined country code
- US
-
- geo_country_nameGeoIP determined country name
- United States
-
- geo_latitudeGeoIP determined latitude (of the city)
- 37.8047
-
- geo_longitudeGeoIP determined longitude (of the city)
- -122.2124
-
- geo_metro_codeGeoIP determined metro code
- 807
-
- geo_region_codeGeoIP determined region code
- CA
-
- geo_region_nameGeoIP determined region name
- California
-
- geo_time_zoneGeoIP determined time zone
- America/Los_Angeles
-
- geo_zip_codeGeoIP determined zip code
- 94602
-
- last_seen_datetimeMost recent time instance ID was submitted
- 2016-10-22T19:56:03.542Z
-
-
-This data is held in the highest security. The update system runs in a secured Amazon Web Services account owned by me (@robbiet480). I personally have 5 years of experience with complex AWS deployments and have an extensive security background. I have audited the entire system and made sure to take every step to protect the data, including limiting who has access (just @balloob and myself). While not directly personally identifiable we absolutely understand some users hesistance to giving this information out. Please understand that we are only collecting this information to better understand our user base to provide better long term support and feature development then is currently possible.
-We currently have no plans to publicly expose any of this information. If we did do such a thing in the future we would of course notify you in advance. It must also be stated that we will never sell or allow the use of this information for non-Home Assistant purposes.
-We thank you for understanding why we are collecting this data and hope that you leave the feature enabled but fully understand if you feel uncomfortable with this.
-This section was updated on October 24 to be more clear about geo-lookups being on the city level. See original version.
-Now, back to the fun stuff…
- Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
-Home Assistant got a crazy idea recently that it couldn’t do enough already and wanted to challenge itself even more. I really don’t understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
-0.31 adds support for the brand spanking new Alexa Flash Briefing API, allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What’s the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
-
- Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
-
-Now I know how to best get to my real job (no, Home Assistant is not my real job, it does seem like it sometimes though) every morning. Obviously not the best home automation example, but I think you get the idea. I could see this being used to tell you any major events that happened in your home overnight or reading you your hyperlocal weather report. Thanks to the audio support you could even replace all of the default Alexa Flash Briefing sources with your own news feeds. Home Assistant supports both text and audio content as well as displaying data in the Alexa app. I also want to point out that unlike the existing Skill integration, the Flash Briefing API does not require HTTPS (but you should still be using HTTPS if possible). For more information, check out the new docs.
-
- 
- You stay classy, San Diego. (It’s funny, because balloob lives in San Diego))
-
- Major breaking Z-Wave changes ahead
-A rather nasty Z-Wave issue was discovered recently by @lukas-hetzenecker. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
-What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here’s what I had to do:
-
- - Update customizations
- - Update groups
- - Update my
zwave.customize section
- - Update my Alexa skills that used old entity IDs
- - Because I use
emulated_hue with Alexa and emulated_hue uses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
-
-Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It’s not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
-This is super annoying, I know, especially since we had said in 0.12 that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn’t change in the future but obviously we see how that went. To sum up on this section… sorry but it had to happen.
- All changes
-
- - Updater component (@infamy, @robbiet480, @kellerza)
- - Continue to setup other platforms when 1 platform config is invalid (@kellerza)
- - Create persistent notifications when a platform contains invalid config (@kellerza)
- - Logbook: Allow filtering domains and entities to be shown (@wokar)
- - HTTP: Change
approved_ips from string to CIDR validation (@mweinelt)
- - Persistent Notifications: Allow using markdown (@justweb1)
- - Netatmo: Add discovery support (@jabesq)
- - Netatmo Welcome camera: Add binary sensor (@jabesq)
- - Support added for HaveIBeenPwned (@joyrider3774)
- - Device tracker:
known_devices.yaml reading and writing tweaks and fixes (@kellerza)
- - Fix climate platforms showing the wrong temperature unit (@rcloran)
- - Lots of voluptuous love (@fabaff)
- - Ensure proper attribution for weather platforms (@fabaff)
- - Fix Telegram in Docker (@jeanregisser)
- - Support recursive config inclusions in YAML (@lwis)
- - Camera: Synology SS cameras now supported (@jgriff2)
- - History: Allow filtering domains and entities to be shown (@wokar)
- - Media Player - Squeezebox: Now able to show artist and album (@ih8gates)
- - Alexa: Flash Briefing skill support added (@robbiet480)
- - Device Tracker: Add support for Bbox Modem Router (@HydrelioxGithub)
- - Sensor: Add support for Bbox Modem Router (@HydrelioxGithub)
- - Input select: Services added to pick next and prev option (@persandstrom)
- - Sensor: ARWN now supported (@sdague)
- - Pushbullet: Push an URL note if an url is provided inside data (@jabesq)
- - Z-Wave: Allow certain devices to be not added to Home Assistant (@lukas-hetzenecker)
- - New support for Zoneminder added (@Khabi)
- - Weather: Allow tracking severe weather alerts with WUnderground (@tchellomello)
- - Sensor: New support added to track min/max/mean (@fabaff)
- - Convert EntityComponent to be async (@pvizeli, @balloob)
- - Z-Wave: Add assocation service (@turbokongen)
- - Frontend - Services dev tool: persist state and tweak UI (@justweb1)
- - Sensor: Support added for scraping websites (@fabaff)
- - Clean up of tests (@capellini)
- - New
fail filter added to templates to raise on UndefinedError (@jaharkes)
- - Support added for Emoncms history (@joyrider3774)
- - Support for Apple Push Notifications Service (@sam-io)
- - Thermostat: Netatmo now supported (@gieljnssns)
- - Alarm control panel: Concord232 now supported (@JasonCarter80)
- - Notify: Matrix support added (@mweinelt)
- - Device tracker - nmap: Allow specifying multiple inputs for nmap (@hcooper)
- - Device Tracker - snmp: SNMPv3 now supported (@T3m3z)
- - Notify: Telstra SMS now supported (@nvella)
- - Camera: Verisure now supported (@turbokongen)
- - Support added for Neato Connected Robot (@jabesq)
- - Media player: More options for Yamaha AVR (@ehagan)
- - Sensor: Support for Pilight sensor (@DavidLP)
- - iOS support (@robbiet480)
- - Minor features and bug fixes by @mtl010957, @molobrakos, @flyte, @fabaff, @phardy, @sander76, @T3m3z, @c-w, @balloob, @robbiet480, @StaticCube, @vittoriom, @hartmms, @kirichkov, @mezz64, @ishults, @Danielhiversen and @tchellomello.
-
- Release 0.31.1 - October 24
-
- - Identify special character encoding error in YAML files (@kellerza, @lwis)
- - iOS app component bug fixes (@robbiet480)
- - Fix a spelling problem on user-facing error (@robbiet480)
- - YAML includes will ignore dirs/files prefixed with . (@lwis)
-
- Breaking changes
-
- - The HTTP component now takes a different format for authenticating IPs
- - Configuration format has changed for Proximity
- - The Arduino platform are now covered by the configuration check. Please check the documentation to see how.
- - The Z-Wave entity ID change mentioned above
-
- If you need help…
-…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
- Until next time
-Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
-– Robbie
diff --git a/blog/posts/6/index.html b/blog/posts/6/index.html
index b183c12c4e..f626382771 100644
--- a/blog/posts/6/index.html
+++ b/blog/posts/6/index.html
@@ -67,6 +67,328 @@
+
+
+
+ Explaining the Updater
+
+
+
+
+ On Saturday, we released Home Assistant 0.31 which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.
+ Read on →
+
+
+
+
+
+
+ 0.31: Reading you the news, some serious business, spooky hackery and a breaking Z-Wave change
+
+
+
+
+ Hello again friend,
+How are you? Having a good day? We sure are. If you aren’t having a good day, this might cheer you up…
+Every other weekend around here gets a little hectic leading to a big sigh of relief as we release a new version of Home Assistant to the world. And this time is no different. Our developer community has once again built us a beautiful new release with lots of new features and improvements. We hope you like it.
+One last thing before we get going though, I should warn you… @balloob got a bit lazy this week and let me (@robbiet480) step up to the plate again to write the blog post and do the release. I guess I didn’t do such a bad job in 0.27. You’ll never know what surprises I have in store. Now that i’ve got all that stuff out of the way, let’s get started…
+ Stats Update
+Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
+ Hacktoberfest
+
+October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the home-assistant repository and 209 merged/28 open pull requests submitted to the home-assistant.github.io repository. If you want to get in on the fun check out our Hacktoberfest blog post or the Hacktoberfest website. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
+ ⚠️ A greatly improved updater component (Please read this!) ⚠️
+This release includes an update to our updater component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
+It used to be that this component would check with PyPi (the Python package manager) to see if a new update was available. This had a couple of problems:
+
+ - We are unable to do a slow rollout
+ - We are unable to show the user extra information (like a link to a changelog or the release date)
+ - We are unable to warn users for critical security updates
+
+So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
+ What you need to know (the important bit!)
+Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
+Each Home Assistant instance running the updater component will generate a unique ID (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called .uuid.
+Opting out
+There are two ways to opt-out. The first way is by using the new opt_out option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
+updater:
+ reporting: no
+
+
+You can also disable the updater component entirely by removing updater: from your configuration.yaml although we would not suggest you do this as you would miss any critical updates.
+Finally, you can also reset your unique identifier by deleting the .uuid file and restarting Home Assistant.
+Data stored on the Home Assistant update server
+Here is what my production Home Assistant instance looks like from the server side:
+
+
+
+ Name
+ Description
+ Example
+
+
+
+
+ archCPU Architecture
+ x86_64
+
+ distributionLinux Distribution name (only Linux)
+ Ubuntu
+
+ dockerTrue if running inside Docker
+ false
+
+ os_nameOperating system name
+ Darwin
+
+ os_versionOperating system version
+ 10.12
+
+ python_versionPython version
+ 3.5.2
+
+ timezoneTimezone
+ America/Los_Angeles
+
+ user_agentUser agent used to submit analytics
+ python-requests/2.11.1
+
+ uuidUnique identifier
+ 10321ee6094d4a2ebb5ed55c675d5f5e
+
+ versionHome Assistant version
+ 0.31.0
+
+ virtualenvTrue if running inside virtualenv
+ true
+
+
+In addition to the above collected data, the server will also use your IP address to do a geographic IP address lookup to determine the city that you are from. To be extremely, extremely clear about this bit: The Home Assistant updater does not: store your IP address in a database and also does not submit the location information from your configuration.yaml.
+
+
+ Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
+
+The server also adds two timestamps to the data: the original date your instance UUID was first seen and the timestamp of the last time we have seen your instance. This gives us the following extra data:
+
+
+
+ Name
+ Description
+ Example
+
+
+
+
+ first_seen_datetimeFirst time instance ID was submitted
+ 2016-10-22T19:56:03.542Z
+
+ geo_cityGeoIP determined city
+ Oakland
+
+ geo_country_codeGeoIP determined country code
+ US
+
+ geo_country_nameGeoIP determined country name
+ United States
+
+ geo_latitudeGeoIP determined latitude (of the city)
+ 37.8047
+
+ geo_longitudeGeoIP determined longitude (of the city)
+ -122.2124
+
+ geo_metro_codeGeoIP determined metro code
+ 807
+
+ geo_region_codeGeoIP determined region code
+ CA
+
+ geo_region_nameGeoIP determined region name
+ California
+
+ geo_time_zoneGeoIP determined time zone
+ America/Los_Angeles
+
+ geo_zip_codeGeoIP determined zip code
+ 94602
+
+ last_seen_datetimeMost recent time instance ID was submitted
+ 2016-10-22T19:56:03.542Z
+
+
+This data is held in the highest security. The update system runs in a secured Amazon Web Services account owned by me (@robbiet480). I personally have 5 years of experience with complex AWS deployments and have an extensive security background. I have audited the entire system and made sure to take every step to protect the data, including limiting who has access (just @balloob and myself). While not directly personally identifiable we absolutely understand some users hesistance to giving this information out. Please understand that we are only collecting this information to better understand our user base to provide better long term support and feature development then is currently possible.
+We currently have no plans to publicly expose any of this information. If we did do such a thing in the future we would of course notify you in advance. It must also be stated that we will never sell or allow the use of this information for non-Home Assistant purposes.
+We thank you for understanding why we are collecting this data and hope that you leave the feature enabled but fully understand if you feel uncomfortable with this.
+This section was updated on October 24 to be more clear about geo-lookups being on the city level. See original version.
+Now, back to the fun stuff…
+ Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
+Home Assistant got a crazy idea recently that it couldn’t do enough already and wanted to challenge itself even more. I really don’t understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
+0.31 adds support for the brand spanking new Alexa Flash Briefing API, allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What’s the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
+
+ Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
+
+Now I know how to best get to my real job (no, Home Assistant is not my real job, it does seem like it sometimes though) every morning. Obviously not the best home automation example, but I think you get the idea. I could see this being used to tell you any major events that happened in your home overnight or reading you your hyperlocal weather report. Thanks to the audio support you could even replace all of the default Alexa Flash Briefing sources with your own news feeds. Home Assistant supports both text and audio content as well as displaying data in the Alexa app. I also want to point out that unlike the existing Skill integration, the Flash Briefing API does not require HTTPS (but you should still be using HTTPS if possible). For more information, check out the new docs.
+
+
+ You stay classy, San Diego. (It’s funny, because balloob lives in San Diego))
+
+ Major breaking Z-Wave changes ahead
+A rather nasty Z-Wave issue was discovered recently by @lukas-hetzenecker. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
+What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here’s what I had to do:
+
+ - Update customizations
+ - Update groups
+ - Update my
zwave.customize section
+ - Update my Alexa skills that used old entity IDs
+ - Because I use
emulated_hue with Alexa and emulated_hue uses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
+
+Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It’s not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
+This is super annoying, I know, especially since we had said in 0.12 that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn’t change in the future but obviously we see how that went. To sum up on this section… sorry but it had to happen.
+ All changes
+
+ - Updater component (@infamy, @robbiet480, @kellerza)
+ - Continue to setup other platforms when 1 platform config is invalid (@kellerza)
+ - Create persistent notifications when a platform contains invalid config (@kellerza)
+ - Logbook: Allow filtering domains and entities to be shown (@wokar)
+ - HTTP: Change
approved_ips from string to CIDR validation (@mweinelt)
+ - Persistent Notifications: Allow using markdown (@justweb1)
+ - Netatmo: Add discovery support (@jabesq)
+ - Netatmo Welcome camera: Add binary sensor (@jabesq)
+ - Support added for HaveIBeenPwned (@joyrider3774)
+ - Device tracker:
known_devices.yaml reading and writing tweaks and fixes (@kellerza)
+ - Fix climate platforms showing the wrong temperature unit (@rcloran)
+ - Lots of voluptuous love (@fabaff)
+ - Ensure proper attribution for weather platforms (@fabaff)
+ - Fix Telegram in Docker (@jeanregisser)
+ - Support recursive config inclusions in YAML (@lwis)
+ - Camera: Synology SS cameras now supported (@jgriff2)
+ - History: Allow filtering domains and entities to be shown (@wokar)
+ - Media Player - Squeezebox: Now able to show artist and album (@ih8gates)
+ - Alexa: Flash Briefing skill support added (@robbiet480)
+ - Device Tracker: Add support for Bbox Modem Router (@HydrelioxGithub)
+ - Sensor: Add support for Bbox Modem Router (@HydrelioxGithub)
+ - Input select: Services added to pick next and prev option (@persandstrom)
+ - Sensor: ARWN now supported (@sdague)
+ - Pushbullet: Push an URL note if an url is provided inside data (@jabesq)
+ - Z-Wave: Allow certain devices to be not added to Home Assistant (@lukas-hetzenecker)
+ - New support for Zoneminder added (@Khabi)
+ - Weather: Allow tracking severe weather alerts with WUnderground (@tchellomello)
+ - Sensor: New support added to track min/max/mean (@fabaff)
+ - Convert EntityComponent to be async (@pvizeli, @balloob)
+ - Z-Wave: Add assocation service (@turbokongen)
+ - Frontend - Services dev tool: persist state and tweak UI (@justweb1)
+ - Sensor: Support added for scraping websites (@fabaff)
+ - Clean up of tests (@capellini)
+ - New
fail filter added to templates to raise on UndefinedError (@jaharkes)
+ - Support added for Emoncms history (@joyrider3774)
+ - Support for Apple Push Notifications Service (@sam-io)
+ - Thermostat: Netatmo now supported (@gieljnssns)
+ - Alarm control panel: Concord232 now supported (@JasonCarter80)
+ - Notify: Matrix support added (@mweinelt)
+ - Device tracker - nmap: Allow specifying multiple inputs for nmap (@hcooper)
+ - Device Tracker - snmp: SNMPv3 now supported (@T3m3z)
+ - Notify: Telstra SMS now supported (@nvella)
+ - Camera: Verisure now supported (@turbokongen)
+ - Support added for Neato Connected Robot (@jabesq)
+ - Media player: More options for Yamaha AVR (@ehagan)
+ - Sensor: Support for Pilight sensor (@DavidLP)
+ - iOS support (@robbiet480)
+ - Minor features and bug fixes by @mtl010957, @molobrakos, @flyte, @fabaff, @phardy, @sander76, @T3m3z, @c-w, @balloob, @robbiet480, @StaticCube, @vittoriom, @hartmms, @kirichkov, @mezz64, @ishults, @Danielhiversen and @tchellomello.
+
+ Release 0.31.1 - October 24
+
+ - Identify special character encoding error in YAML files (@kellerza, @lwis)
+ - iOS app component bug fixes (@robbiet480)
+ - Fix a spelling problem on user-facing error (@robbiet480)
+ - YAML includes will ignore dirs/files prefixed with . (@lwis)
+
+ Breaking changes
+
+ - The HTTP component now takes a different format for authenticating IPs
+ - Configuration format has changed for Proximity
+ - The Arduino platform are now covered by the configuration check. Please check the documentation to see how.
+ - The Z-Wave entity ID change mentioned above
+
+ If you need help…
+…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
+ Until next time
+Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
+– Robbie
+
+
+
@@ -725,112 +1047,6 @@ So, part 1 of ESP8266
Heatmap
-
-
-
-
-
-
- We Have Apps Now
-
-
-
-
- I have been working on a new subsystem to complement Home Assistant’s Automation and Scripting components. AppDaemon is a python daemon that consumes events from Home Assistant and feeds them to snippets of python code called “Apps”. An App is a Python class that is instantiated possibly multiple times from AppDaemon and registers callbacks for various system events. It is also able to inspect and set state and call services. The API provides a rich environment suited to home automation tasks that can also leverage all the power of Python.
- Read on →
-
-
-
-
-
-
- 0.26: Foursquare, Fast.com, FFMPEG and GPSD
-
-
-
-
- It’s time for 0.26 and it’s again full of new features and fixes. First I want to highlight that we are now having 500 000 monthly pageviews on the website. A big milestone for us! It’s been an amazing journey. Big thanks to the Home Assistant community for being such a delightful bunch.
-This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you’ll have to pick imperial or metric now. This influences the units for your temperature, distance, and weight. This will simplify any platform or component that needs to know this information. Big thanks to @Teagan42 for her hard work on this!
-
-
- - Core: Introduce notion of unit system (deprecates temperature unit option) (@Teagan42)
- - Front end: Speed improvements (@balloob)
- - Front end: Improve layout of state dev tool (@balloob)
- - Proximity: Allow definition of unit of measurement (@Teagan42)
- - Flux: Add mired and kelvin mode (@HBDK)
- - Thermostat - Proliphix: Support for cooling (@sdague)
- - Media Player - LG Netcast TV: Show screenshot of what is currently playing (@shmuelzon)
- - Z-Wave improvements (@jnewland, @turbokongen)
- - Thermostat - heat control: now also able to control an AC (@mtreinish)
- - Thermostat - heat control: allow specifying a minimum duration before switching (@mtreinish)
- - InfluxDB: Whitelist entities option added (@tchellomello)
- - Sensor: Serial particulate matters sensors now supported (@open-homeautomation)
- - Sensor - Fitbit: Fix unit system (@tchellomello)
- - Light - Flux LED: Add support for [color and brightness][color] (@Danielhiversen)
- - Media Player - Plex: Now able to report on music (@abcminiuser)
- - Alarm Control Panel - Verisure: Now able to see who changed the alarm (@persandtrom)
- - Thermostat - Honeywell: Add option to read and control HVAC mode (@Teagan42)
- - Foursquare component to receive instant notifications of checkins (@robbiet480)
- - Camera: New FFMPEG platform allows to stream anything through front end (@pvizeli)
- - Manage secrets with new command line script (@kellerza)
- - Notify - SMTP: Allow embedding of images (@partofthething)
- - Sensor: OhmConnect is now supported (@robbiet480)
- - panel_custom component allows the registering of new panels (@balloob)
- - Light: New mqtt_json platform for working with JSON payload (@corbanmailloux)
- - Sensor: New Fast.com platform to measure network bandwidth performance (@nkgilley)
- - New pilight component to control 433 Mz devices (@DavidLP)
- - Sensor: GPSD now supported (@fabaff)
-
- Hotfix 0.26.1 - August 14
-
- - Fix serial_pm config validation (@open-homeautomation)
- - Check for existence of system mode on Honeywell thermostats (@mKeRix)
- - Fix unknown unit of measurement for hvac and thermostat component (@turbokongen)
-
- Hotfix 0.26.2 - August 15
-
- - Fix Wemo: have PyWemo play nicely with the latest Requests (@pavoni)
-
- Hotfix 0.26.3 - August 19
-
- - Media Player cover art would not work when an API password was set. Thanks to @maddox for reporting it and @balloob for the fix.
-
- Breaking changes
-
- - A new unit system has superseded the temperature unit option in the core configuration. For now it is backwards compatible, but you should update soon:
-
-# Configuration.yaml example
-homeassistant:
- # 'metric' for the metric system, 'imperial' for the imperial system
- unit_system: metric
-
-
diff --git a/blog/posts/7/index.html b/blog/posts/7/index.html
index 37e7e0bed9..4bec62fd79 100644
--- a/blog/posts/7/index.html
+++ b/blog/posts/7/index.html
@@ -67,6 +67,112 @@
+
+
+
+ We Have Apps Now
+
+
+
+
+ I have been working on a new subsystem to complement Home Assistant’s Automation and Scripting components. AppDaemon is a python daemon that consumes events from Home Assistant and feeds them to snippets of python code called “Apps”. An App is a Python class that is instantiated possibly multiple times from AppDaemon and registers callbacks for various system events. It is also able to inspect and set state and call services. The API provides a rich environment suited to home automation tasks that can also leverage all the power of Python.
+ Read on →
+
+
+
+
+
+
+ 0.26: Foursquare, Fast.com, FFMPEG and GPSD
+
+
+
+
+ It’s time for 0.26 and it’s again full of new features and fixes. First I want to highlight that we are now having 500 000 monthly pageviews on the website. A big milestone for us! It’s been an amazing journey. Big thanks to the Home Assistant community for being such a delightful bunch.
+This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you’ll have to pick imperial or metric now. This influences the units for your temperature, distance, and weight. This will simplify any platform or component that needs to know this information. Big thanks to @Teagan42 for her hard work on this!
+
+
+ - Core: Introduce notion of unit system (deprecates temperature unit option) (@Teagan42)
+ - Front end: Speed improvements (@balloob)
+ - Front end: Improve layout of state dev tool (@balloob)
+ - Proximity: Allow definition of unit of measurement (@Teagan42)
+ - Flux: Add mired and kelvin mode (@HBDK)
+ - Thermostat - Proliphix: Support for cooling (@sdague)
+ - Media Player - LG Netcast TV: Show screenshot of what is currently playing (@shmuelzon)
+ - Z-Wave improvements (@jnewland, @turbokongen)
+ - Thermostat - heat control: now also able to control an AC (@mtreinish)
+ - Thermostat - heat control: allow specifying a minimum duration before switching (@mtreinish)
+ - InfluxDB: Whitelist entities option added (@tchellomello)
+ - Sensor: Serial particulate matters sensors now supported (@open-homeautomation)
+ - Sensor - Fitbit: Fix unit system (@tchellomello)
+ - Light - Flux LED: Add support for [color and brightness][color] (@Danielhiversen)
+ - Media Player - Plex: Now able to report on music (@abcminiuser)
+ - Alarm Control Panel - Verisure: Now able to see who changed the alarm (@persandtrom)
+ - Thermostat - Honeywell: Add option to read and control HVAC mode (@Teagan42)
+ - Foursquare component to receive instant notifications of checkins (@robbiet480)
+ - Camera: New FFMPEG platform allows to stream anything through front end (@pvizeli)
+ - Manage secrets with new command line script (@kellerza)
+ - Notify - SMTP: Allow embedding of images (@partofthething)
+ - Sensor: OhmConnect is now supported (@robbiet480)
+ - panel_custom component allows the registering of new panels (@balloob)
+ - Light: New mqtt_json platform for working with JSON payload (@corbanmailloux)
+ - Sensor: New Fast.com platform to measure network bandwidth performance (@nkgilley)
+ - New pilight component to control 433 Mz devices (@DavidLP)
+ - Sensor: GPSD now supported (@fabaff)
+
+ Hotfix 0.26.1 - August 14
+
+ - Fix serial_pm config validation (@open-homeautomation)
+ - Check for existence of system mode on Honeywell thermostats (@mKeRix)
+ - Fix unknown unit of measurement for hvac and thermostat component (@turbokongen)
+
+ Hotfix 0.26.2 - August 15
+
+ - Fix Wemo: have PyWemo play nicely with the latest Requests (@pavoni)
+
+ Hotfix 0.26.3 - August 19
+
+ - Media Player cover art would not work when an API password was set. Thanks to @maddox for reporting it and @balloob for the fix.
+
+ Breaking changes
+
+ - A new unit system has superseded the temperature unit option in the core configuration. For now it is backwards compatible, but you should update soon:
+
+# Configuration.yaml example
+homeassistant:
+ # 'metric' for the metric system, 'imperial' for the imperial system
+ unit_system: metric
+
+
+
+
+
@@ -408,102 +514,6 @@ Over a year ago I participated in the
-
-
- 0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV
-
-
-
-
- It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.
-This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.
-Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.
-On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!
-
-
- - Support for Envisalink added (alarm control panel, binary sensor, sensor) (@cinntax)
- - Support for Homematic added (binary sensor, light, rollershutter, sensor, switch) (@pvizeli, @danielperna84)
- - New HDMI-CEC component (@happyleavesaoc, @lukas-hetzenecker)
- - Major rewrite of Wink which now pushes changes to Home Assistant (@w1ll1am23)
- - Core: new add reload core config service (@balloob)
- - Support for persistent notifications added (@fabaff, @balloob)
- - Garage door: Z-Wave support added (@turbokongen)
- - Rollershutter: Z-Wave support added (@turbokongen)
- - Media Player: Sony Bravia TV now supported (@aparraga)
- - Sensor: Fixer.io now supported (@fabaff)
- - Garage door: Control any garage door using Raspberry Pi GPIO pins (@kellerza)
- - Sensor: OpenExchangeRates support added (@arsaboo)
- - Notify: Pushover now supports target device, sound, URL and priority (@dale3h)
- - Sensor: Netatmo now supports wind, battery and radio signals (@Jypy)
- - Log successful and failed login attemps (@fabaff)
- - Config: allow extracting account info into OS keyring or separate YAML file (@kellerza)
- - Core: add option to not filter out duplicate states per entity (@philipbl)
- - HTTP: Follow Mozilla SSL recommendations (@danieljkemp, @AlucardZero)
- - Light: Z-Wave colorbulb support added (@armills)
- - Core: new elevation config option added (@balloob)
- - Sensor: OneWire support extended with support for DS18S20, DS1822, DS1825 and DS28EA00 temperature sensors + support for bus masters which use fuse to mount device tree. (@Ardetus)
- - Lock: Vera now supported (@rhooper)
- - HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems (@balloob)
-
- Breaking changes
-
- - Homematic thermostat configuration has changed and now depends on the new Homematic component.
-
- Hotfix 0.23.1 - July 2
-
- - Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug (@rhooper)
- - HTTP - SSL: Check for OP_NO_COMPRESSION support before trying to use it (@AlucardZero)
- - Wink: Downgraded pubnub to work around pycryptodome conflicts (@w1ll1am23)
-
- FAQ
-
- elevation: was introduced to the configuration for weather/sunrise data. For existing configurations add the value shown in the warning [homeassistant.config] Incomplete core config. Auto detected elevation: 665 to your configuration.yaml file.
-
-
-
-
-
-
- Using USB webcams with Home Assistant
-
-
-
-
- 
-In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like pygame or SimpleCV but I never finished something. With the Local File camera platform by Landrash and motion you could integrate a local USB webcam with a few very easy steps.
-In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old Logitech QuickCam Orbit AF and a Logitech HD Webcam C270. As a start only the Quickcam is used. No multi-camera setup for now.
- Read on →
-
-
-
← Older
Newer →
diff --git a/blog/posts/8/index.html b/blog/posts/8/index.html
index 83fc2346ad..567cae0783 100644
--- a/blog/posts/8/index.html
+++ b/blog/posts/8/index.html
@@ -67,6 +67,102 @@
+
+
+
+ 0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV
+
+
+
+
+ It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.
+This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.
+Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.
+On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!
+
+
+ - Support for Envisalink added (alarm control panel, binary sensor, sensor) (@cinntax)
+ - Support for Homematic added (binary sensor, light, rollershutter, sensor, switch) (@pvizeli, @danielperna84)
+ - New HDMI-CEC component (@happyleavesaoc, @lukas-hetzenecker)
+ - Major rewrite of Wink which now pushes changes to Home Assistant (@w1ll1am23)
+ - Core: new add reload core config service (@balloob)
+ - Support for persistent notifications added (@fabaff, @balloob)
+ - Garage door: Z-Wave support added (@turbokongen)
+ - Rollershutter: Z-Wave support added (@turbokongen)
+ - Media Player: Sony Bravia TV now supported (@aparraga)
+ - Sensor: Fixer.io now supported (@fabaff)
+ - Garage door: Control any garage door using Raspberry Pi GPIO pins (@kellerza)
+ - Sensor: OpenExchangeRates support added (@arsaboo)
+ - Notify: Pushover now supports target device, sound, URL and priority (@dale3h)
+ - Sensor: Netatmo now supports wind, battery and radio signals (@Jypy)
+ - Log successful and failed login attemps (@fabaff)
+ - Config: allow extracting account info into OS keyring or separate YAML file (@kellerza)
+ - Core: add option to not filter out duplicate states per entity (@philipbl)
+ - HTTP: Follow Mozilla SSL recommendations (@danieljkemp, @AlucardZero)
+ - Light: Z-Wave colorbulb support added (@armills)
+ - Core: new elevation config option added (@balloob)
+ - Sensor: OneWire support extended with support for DS18S20, DS1822, DS1825 and DS28EA00 temperature sensors + support for bus masters which use fuse to mount device tree. (@Ardetus)
+ - Lock: Vera now supported (@rhooper)
+ - HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems (@balloob)
+
+ Breaking changes
+
+ - Homematic thermostat configuration has changed and now depends on the new Homematic component.
+
+ Hotfix 0.23.1 - July 2
+
+ - Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug (@rhooper)
+ - HTTP - SSL: Check for OP_NO_COMPRESSION support before trying to use it (@AlucardZero)
+ - Wink: Downgraded pubnub to work around pycryptodome conflicts (@w1ll1am23)
+
+ FAQ
+
+ elevation: was introduced to the configuration for weather/sunrise data. For existing configurations add the value shown in the warning [homeassistant.config] Incomplete core config. Auto detected elevation: 665 to your configuration.yaml file.
+
+
+
+
+
+
+ Using USB webcams with Home Assistant
+
+
+
+
+
+In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like pygame or SimpleCV but I never finished something. With the Local File camera platform by Landrash and motion you could integrate a local USB webcam with a few very easy steps.
+In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old Logitech QuickCam Orbit AF and a Logitech HD Webcam C270. As a start only the Quickcam is used. No multi-camera setup for now.
+ Read on →
+
+
+
@@ -442,138 +538,6 @@
-
-
-
- Video: How To Configure Home Assistant
-
-
-
-
- Ben from BRUH Automation authors a lot of great video’s about how he is using Home Assistant and how you can get started with it too. The video below will walk you through how to configure Home Assistant. Enjoy!
-Make sure to subscribe to his YouTube channel for more Home Assistant video’s.
-
-
-
-
-
-
-
-
-
- 0.19: Empowering scripts and Alexa
-
-
-
-
- This release is big. Until now, our automations and scripts have been very static. Starting today it should all be a bit more dynamic.
-Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state !). Passing data to script entities is available by passing the data to the script services.
-automation:
- trigger:
- platform: mqtt
- topic: some/notify/topic
- action:
- service: notify.notify
- data_template:
- message:
-
-automation 2:
- trigger:
- platform: state
- entity_id: light.hue
- action:
- service: notify.notify
- data_template:
- message: is now
-
-
-Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room into light.holiday_home_living_room with the following config:
-light:
- platform: hue
- entity_namespace: holiday_home
-
-
-
- - Automation: allow script syntax for action (@balloob)
- - Automation: expose
trigger variable to script templates (@balloob)
- - Script: allow passing variables for script templates in the script service calls (@balloob)
- - Alexa/Amazon Echo: allow script syntax for action (@balloob)
- - Alexa/Amazon Echo: expose intent variables to script templates (@balloob)
- - Script syntax: conditions now supported to interrupt execution (@balloob)
- - Automation: use new condition syntax (@balloob)
- - Script syntax: two new conditions
and and or to combine conditions (@balloob)
- - Any platform: Allow setting entity namespace to prefix entity_ids. (@balloob)
- - Switch: Raspberry Pi generic 433 Mhz GPIO adapters now supported (@milaq)
- - Z-Wave: use more sane defaults (@danieljkemp)
- - Media Player: Snapcast now supports picking a source (@happyleavesaoc)
- - MySensors: major cleanup (@MartinHjelmare)
- - Binary Sensor: Command line sensor now supports classes (@fabaff)
- - MQTT: allow client key authentication (@timharton)
- - Sensor: Forecast.io now supports minutely, hourly and daily summaries (@aceat64)
- - Media Player: Pioneer AVR now supported (@kylehendricks)
- - Switch: Acer Projectors now supported (@deisi)
- - New HVAC component added with Z-Wave support (@turbokongen)
- - Support added for OctoPrint (@w1ll1am23)
- - Configuration.yaml can now refer to environment variables using
!env_var (@bah2830)
- - Lock: Z-Wave now supported (@devdelay)
- - New Dweet component to export data (@fabaff)
- - Media Player now supports stop command + initial kodi support (@hmronline)
- - Zigbee: push updates now supported (@flyte)
- - Wink devices with battery level will now show these (@w1ll1am23)
- - Templates: new
as_timestamp method now available (@srcLurker)
- - API: Add [
/api/discovery_info] with basic instance info (@robbiet480)
- - Sensor: Google Maps travel time added (@Danielhiversen)
- - HTTP: Allow adding CORS headers (@robbiet480)
- - Sensor: Fitbit support added (@robbiet480)
- - Bug fixes and tweaks by @turbokongen, @danieljkemp, @Danielhiversen, @TheRealLink, @persandstrom, @sander76, @fabaff, @ishults, @Bart274, @robbiet480, @Cinntax, @blackdog70, @gwendalg, @JshWright, @kylehendricks, @bradsk88, @shaftoe, @molobrakos, @bah2830, @nkgilley
-
-Deprecations
-
- - Conditions in automations should now specify which condition to use with
condition: instead of platform:. For example condition: state.
- - RFXtrx has a new config format.
-
-Old RFXtrx config format:
- devices:
- 123efab1:
- name: My DI.0 light device
- packetid: 1b2200000890efab1213f60
-
-
-New RFXtrx config format:
- devices:
- 1b2200000890efab1213f60:
- name: My DI.0 light device
-
-
-
-
-
← Older
Newer →
diff --git a/blog/posts/9/index.html b/blog/posts/9/index.html
index e9736f2d9f..c6fc8a0596 100644
--- a/blog/posts/9/index.html
+++ b/blog/posts/9/index.html
@@ -67,6 +67,138 @@
+
+
+
+ Video: How To Configure Home Assistant
+
+
+
+
+ Ben from BRUH Automation authors a lot of great video’s about how he is using Home Assistant and how you can get started with it too. The video below will walk you through how to configure Home Assistant. Enjoy!
+Make sure to subscribe to his YouTube channel for more Home Assistant video’s.
+
+
+
+
+
+
+
+
+
+ 0.19: Empowering scripts and Alexa
+
+
+
+
+ This release is big. Until now, our automations and scripts have been very static. Starting today it should all be a bit more dynamic.
+Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state !). Passing data to script entities is available by passing the data to the script services.
+automation:
+ trigger:
+ platform: mqtt
+ topic: some/notify/topic
+ action:
+ service: notify.notify
+ data_template:
+ message:
+
+automation 2:
+ trigger:
+ platform: state
+ entity_id: light.hue
+ action:
+ service: notify.notify
+ data_template:
+ message: is now
+
+
+Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room into light.holiday_home_living_room with the following config:
+light:
+ platform: hue
+ entity_namespace: holiday_home
+
+
+
+ - Automation: allow script syntax for action (@balloob)
+ - Automation: expose
trigger variable to script templates (@balloob)
+ - Script: allow passing variables for script templates in the script service calls (@balloob)
+ - Alexa/Amazon Echo: allow script syntax for action (@balloob)
+ - Alexa/Amazon Echo: expose intent variables to script templates (@balloob)
+ - Script syntax: conditions now supported to interrupt execution (@balloob)
+ - Automation: use new condition syntax (@balloob)
+ - Script syntax: two new conditions
and and or to combine conditions (@balloob)
+ - Any platform: Allow setting entity namespace to prefix entity_ids. (@balloob)
+ - Switch: Raspberry Pi generic 433 Mhz GPIO adapters now supported (@milaq)
+ - Z-Wave: use more sane defaults (@danieljkemp)
+ - Media Player: Snapcast now supports picking a source (@happyleavesaoc)
+ - MySensors: major cleanup (@MartinHjelmare)
+ - Binary Sensor: Command line sensor now supports classes (@fabaff)
+ - MQTT: allow client key authentication (@timharton)
+ - Sensor: Forecast.io now supports minutely, hourly and daily summaries (@aceat64)
+ - Media Player: Pioneer AVR now supported (@kylehendricks)
+ - Switch: Acer Projectors now supported (@deisi)
+ - New HVAC component added with Z-Wave support (@turbokongen)
+ - Support added for OctoPrint (@w1ll1am23)
+ - Configuration.yaml can now refer to environment variables using
!env_var (@bah2830)
+ - Lock: Z-Wave now supported (@devdelay)
+ - New Dweet component to export data (@fabaff)
+ - Media Player now supports stop command + initial kodi support (@hmronline)
+ - Zigbee: push updates now supported (@flyte)
+ - Wink devices with battery level will now show these (@w1ll1am23)
+ - Templates: new
as_timestamp method now available (@srcLurker)
+ - API: Add [
/api/discovery_info] with basic instance info (@robbiet480)
+ - Sensor: Google Maps travel time added (@Danielhiversen)
+ - HTTP: Allow adding CORS headers (@robbiet480)
+ - Sensor: Fitbit support added (@robbiet480)
+ - Bug fixes and tweaks by @turbokongen, @danieljkemp, @Danielhiversen, @TheRealLink, @persandstrom, @sander76, @fabaff, @ishults, @Bart274, @robbiet480, @Cinntax, @blackdog70, @gwendalg, @JshWright, @kylehendricks, @bradsk88, @shaftoe, @molobrakos, @bah2830, @nkgilley
+
+Deprecations
+
+ - Conditions in automations should now specify which condition to use with
condition: instead of platform:. For example condition: state.
+ - RFXtrx has a new config format.
+
+Old RFXtrx config format:
+ devices:
+ 123efab1:
+ name: My DI.0 light device
+ packetid: 1b2200000890efab1213f60
+
+
+New RFXtrx config format:
+ devices:
+ 1b2200000890efab1213f60:
+ name: My DI.0 light device
+
+
+
+
+
@@ -363,140 +495,6 @@
Your hub should not be affected when your internet breaks down or the company that sold you your hub goes out of business. It should work locally so that it can continue to work even long after the vendor goes out of business or decides to kill it. Preferably, your hub should also be open so that the community can take over development after the vendor stops caring.
Unless you can afford losing a product here and there, be cautious when buying IoT products that depend on the cloud from companies that are not well established. The chances are high that they go bankrupt or get acquired and closed. This however is easier said than done as Gartner predicts that by 2017, 50 percent of IoT solutions will originate in startups that are less than three years old.
-
-
-
-
-
-
- 0.16: Embedded MQTT broker, Uber, Yamaha receivers and Growl
-
-
-
-
- Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.
-Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).
-Rock on.
-
-
- - Device Tracker - OwnTracks: Allow entry into passive zones using iBeacons (@pavoni)
- - Tellstick: rewrite to component to address concurrency issues (@stefan-jonasson)
- - Z-Wave: add services to heal and soft reset network (@srcLurker)
- - New component input_slider added (@persandstrom)
- - Light - Hue: Option added to ignore unreachable property (@maddox)
- - Notify: MessageBird support added (@florianholzapfel)
- - HTTP: Failed login attempts are now logged (@fabaff)
- - Vera: rewrite to component to simplify code and organize for reusability (@pavoni)
- - Discovery: support for Squeezebox (Logitech media) server added (@jaharkes)
- - Discovery: fix uPNP discovery crashing some routers (@jaharkes)
- - Switch: Wake on LAN platform added (@joopert)
- - Services for thermostats, notify and media player will now validate passed in parameters (@MartinHjelmare)
- - Switch - Arduino: support for default state and negate port functionality (@tilutza)
- - Switch: PulseAudio loopback now supported (@Cinntax)
- - Sensor: Uber now supported (@robbiet480)
- - Notify: Growl (GNTP) now supported (@robbiet480)
- - Media Player: Yamaha receivers now supported (@aoakeson)
-
-Breaking changes
-
- -
-
Automation: support for old deprecated config has been removed
-
- -
-
Tellstick configuration has changed
-
-
-tellstick:
- signal_repetitions: X
-
-
-
- - Vera configuration has changed
-
-vera:
- vera_controller_url: http://192.168.1.161:3480/
- # Optional to exclude devices - this is a list of vera device ids
- exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
- # Optional to import switches as lights - this is a list of vera device ids
- lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
-
-
-
-
-
-
-
-
- 0.15: Unforked Open Z-Wave, templated service calls, extended scene support and PEP257 compliance.
-
-
-
-
- Two weeks has past so here is 0.15! We have been focussing a lot on quality. Making sure the system is more stable and reliable. I usually try to highlight one cool thing in the release notes but this release has 4 exciting announcements!
-
- - @fabaff has upgraded the codebase to follow the PEP257 documentation standard.
- - @partofthething has migrated us to use the main Python Open Z-Wave library instead of our forked version.
- - To make our automations more powerful, @persandstrom added the option to use templates to dynamically create service calls. This works for automation, Alexa, universal media player, template switch. Learn more.
- - @MartinHjelmare has upgraded our scene support to now support all built-in services and components.
-
-Besides bug fixes, this release also brings:
-
-
- - Scene: Converted to a platform based component (@sander76)
- - Scene: Hunter Douglas Powerview now supported (@sander76)
- - Lock: MQTT platform added (@fabaff)
- - Device Tracker: OwnTracks will allow filtering inaccurate GPS locations (@HydrelioxGitHub)
- - Binary Sensor: Wemo Motion now supported (@pavoni, @ryanlaux)
-
-# Example using templates for service and data in service call.
-# Works for automation, Alexa, universal media player, template switch.
-automation:
- - trigger:
- - platform: state
- entity_id: switch.bathroom
- action:
- service_template: >
- {% if is_state('switch.bathroom', 'on') %}
- switch.turn_on
- {% else %}
- switch.turn_off
- {% endif %}
- data_template:
- entity_id: switch.{{ states('input_select.is') }}
-
-
-Breaking Changes
-
- - Media Player: Attributes to call service play_media has been renamed to
-
media_content_type and media_content_id, to match the corresponding media
-player state attributes. This change affects automations, scripts and scenes.
-
diff --git a/components/alarm_control_panel.alarmdecoder/index.html b/components/alarm_control_panel.alarmdecoder/index.html
index 8cf8f11cc1..bedea8576b 100644
--- a/components/alarm_control_panel.alarmdecoder/index.html
+++ b/components/alarm_control_panel.alarmdecoder/index.html
@@ -136,6 +136,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.alarmdotcom/index.html b/components/alarm_control_panel.alarmdotcom/index.html
index 9065c8ea6b..5e4fcb0576 100644
--- a/components/alarm_control_panel.alarmdotcom/index.html
+++ b/components/alarm_control_panel.alarmdotcom/index.html
@@ -133,6 +133,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.concord232/index.html b/components/alarm_control_panel.concord232/index.html
index 09cfb385f5..81a5862c08 100644
--- a/components/alarm_control_panel.concord232/index.html
+++ b/components/alarm_control_panel.concord232/index.html
@@ -137,6 +137,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.envisalink/index.html b/components/alarm_control_panel.envisalink/index.html
index e076d7a8f4..2574c85f10 100644
--- a/components/alarm_control_panel.envisalink/index.html
+++ b/components/alarm_control_panel.envisalink/index.html
@@ -136,6 +136,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.manual/index.html b/components/alarm_control_panel.manual/index.html
index 11369c375f..7ff2e3658d 100644
--- a/components/alarm_control_panel.manual/index.html
+++ b/components/alarm_control_panel.manual/index.html
@@ -159,6 +159,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.manual_mqtt/index.html b/components/alarm_control_panel.manual_mqtt/index.html
new file mode 100644
index 0000000000..2ee2f2e016
--- /dev/null
+++ b/components/alarm_control_panel.manual_mqtt/index.html
@@ -0,0 +1,251 @@
+
+
+
+
+
+
+
+
+ Manual Alarm Control Panel with MQTT Support - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Manual Alarm Control Panel With MQTT Support
+
+
+
+ This platform extends the manual alarm by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant.
+It’s essentially the opposite of the MQTT Alarm Panel which allows Home Assistant to observe an existing, fully-featured alarm where all of the alarm logic is embedded in that physical device.
+The component will accept the following commands from your Alarm Panel via the command_topic:
+
+ DISARMARM_HOMEARM_AWAY
+When the state of the manual alarm changes, Home Assistant will publish one of the following states to the state_topic:
+
+ - ‘disarmed’
+ - ‘armed_home’
+ - ‘armed_away’
+ - ‘pending’
+ - ‘triggered’
+
+# Example configuration.yaml entry
+alarm_control_panel:
+ - platform: manual_mqtt
+ state_topic: home/alarm
+ command_topic: home/alarm/set
+
+
+Configuration variables:
+All configuration variables from the base manual alarm platform are available:
+
+ - name (Optional): The name of the alarm. Default is “HA Alarm”.
+ - code (Optional): If defined, specifies a code to enable or disable the alarm in the frontend. This code is not required for MQTT interactions.
+ - pending_time (Optional): The time in seconds of the pending time before arming the alarm. Default is 60 seconds.
+ - trigger_time (Optional): The time in seconds of the trigger time in which the alarm is firing. Default is 120 seconds.
+ - disarm_after_trigger (Optional): If true, the alarm will automatically disarm after it has been triggered instead of returning to the previous state.
+
+Additionally, the following MQTT configuration variables are also available:
+
+ - state_topic (Required): The MQTT topic HA will publish state updates to.
+ - command_topic (Required): The MQTT topic HA will subscribe to to receive commands from a remote device to change the alarm state.
+ - qos (Optional): The maximum QoS level for subscribing and publishing to MQTT messages. Default is 0.
+ - payload_disarm (Optional): The payload to disarm this Alarm Panel. Default is “DISARM”.
+ - payload_arm_home (Optional): The payload to set armed-home mode on this Alarm Panel. Default is “ARM_HOME”.
+ - payload_arm_away (Optional): The payload to set armed-away mode on this Alarm Panel. Default is “ARM_AWAY”.
+
+ Examples
+Refer to the Manual Alarm Control page for some real life examples of how to use this panel.
+ MQTT Control
+The state of this alarm can be controlled using MQTT. Ensure you’ve configured that before adding this component.
+To change the state of the alarm, publish one of the following messages to the command_topic:
+
+ DISARMARM_HOMEARM_AWAY
+To receive state updates from HA, subscribe to the state_topic. Home Assistant will publish a new message whenever the state changes:
+
+ disarmedarmed_homearmed_awaypendingtriggered
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/alarm_control_panel.mqtt/index.html b/components/alarm_control_panel.mqtt/index.html
index e743d2aea5..8a38890b0c 100644
--- a/components/alarm_control_panel.mqtt/index.html
+++ b/components/alarm_control_panel.mqtt/index.html
@@ -187,6 +187,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.nx584/index.html b/components/alarm_control_panel.nx584/index.html
index 76840f9098..281349c79f 100644
--- a/components/alarm_control_panel.nx584/index.html
+++ b/components/alarm_control_panel.nx584/index.html
@@ -137,6 +137,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.simplisafe/index.html b/components/alarm_control_panel.simplisafe/index.html
index 67ecec3500..5affd9ffd6 100644
--- a/components/alarm_control_panel.simplisafe/index.html
+++ b/components/alarm_control_panel.simplisafe/index.html
@@ -133,6 +133,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.spc/index.html b/components/alarm_control_panel.spc/index.html
index e5a7a2ffd4..a3d91d0dfb 100644
--- a/components/alarm_control_panel.spc/index.html
+++ b/components/alarm_control_panel.spc/index.html
@@ -133,6 +133,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.totalconnect/index.html b/components/alarm_control_panel.totalconnect/index.html
index b33f716ead..a78b05be41 100644
--- a/components/alarm_control_panel.totalconnect/index.html
+++ b/components/alarm_control_panel.totalconnect/index.html
@@ -133,6 +133,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.verisure/index.html b/components/alarm_control_panel.verisure/index.html
index 90913037f0..5a5f3422d1 100644
--- a/components/alarm_control_panel.verisure/index.html
+++ b/components/alarm_control_panel.verisure/index.html
@@ -160,6 +160,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.wink/index.html b/components/alarm_control_panel.wink/index.html
index c5e5f55bd0..9e6171f798 100644
--- a/components/alarm_control_panel.wink/index.html
+++ b/components/alarm_control_panel.wink/index.html
@@ -162,6 +162,9 @@ The above devices are confimed to work, but others may work as well.
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel/index.html b/components/alarm_control_panel/index.html
index fd3192db00..43de6e4451 100644
--- a/components/alarm_control_panel/index.html
+++ b/components/alarm_control_panel/index.html
@@ -112,6 +112,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarmdecoder/index.html b/components/alarmdecoder/index.html
index 5931674250..c8fe296218 100644
--- a/components/alarmdecoder/index.html
+++ b/components/alarmdecoder/index.html
@@ -154,6 +154,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -298,6 +301,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -316,6 +322,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/alexa/index.html b/components/alexa/index.html
index 701bb8ff6f..8507dcceb9 100644
--- a/components/alexa/index.html
+++ b/components/alexa/index.html
@@ -76,32 +76,11 @@
There are a few ways that you can use Amazon Echo and Home Assistant together.
- - Turning devices on and off
- Build custom commands to use
- Create a new Flash Briefing source
+ - Alternative: use the Emulated Hue component to trick Alexa to thinking Home Assistant is a Philips Hue hub.
-No matter which method(s) you decide to use, please remember that Amazon Echo requires an active Internet connection to function. If your Internet is down or experiencing issues (or Amazon’s infrastructure is having issues), none of these methods will work.
Amazon has released Echosim, a website that simulates the Alexa service in your browser. That way it is easy to test your skills without having access to a physical Amazon Echo.
- I just want to turn devices on and off using Echo
-If you just want to be able to turn anything with a switch (like lights, switches, media players, etc) on and off, you should enable the Emulated Hue component. It makes your Home Assistant appear as if it were a Phillips Hue bridge, which Echo works with natively.
-Enabling the Emulated Hue component means you can turn things on and off by simply saying
-
- Alexa, turn the living room lights on.
-
-or
-
- Alexa, set the living room lights to twenty percent.
-
-instead of
-
- Alexa, tell Home Assistant to turn the living room lights on.
-
-or
-
- Alexa, tell Home Assistant to set the living room lights to twenty percent.
-
-In addition, you would need to build custom intents for each device and on/off combination using the below method, whereas everything just works without any extra work by using Emulated Hue.
-Please note that you can use Emulated Hue and the built-in Alexa component side-by-side without issue if you wish.
I want to build custom commands to use with Echo
The built-in Alexa component allows you to integrate Home Assistant into Alexa/Amazon Echo. This component will allow you to query information and call services within Home Assistant by using your voice. Home Assistant offers no built-in sentences but offers a framework for you to define your own.
@@ -164,48 +143,7 @@ WhereAreWeIntent where we are
Alexa, ask Home Assistant where we are
Configuring Home Assistant
-Out of the box, the component will do nothing. You have to teach it about all intents you want it to answer to. The way it works is that the answer for each intent is based on templates that you define. Each template will have access to the existing states via the states variable but will also have access to all variables defined in the intent.
-You can use templates for the values of speech/text, card/title and card/content.
-Actions are using the Home Assistant Script Syntax and also have access to the variables from the intent.
-Configuring the Alexa component for the above intents would look like this:
-# Example configuration.yaml entry
-alexa:
- intents:
- WhereAreWeIntent:
- speech:
- type: plaintext
- text: >
- {%- if is_state('device_tracker.paulus', 'home') and
- is_state('device_tracker.anne_therese', 'home') -%}
- You are both home, you silly
- {%- else -%}
- Anne Therese is at {{ states("device_tracker.anne_therese") }}
- and Paulus is at {{ states("device_tracker.paulus") }}
- {% endif %}
-
- LocateIntent:
- action:
- service: notify.notify
- data_template:
- message: The location of {{ User }} has been queried via Alexa.
- speech:
- type: plaintext
- text: >
- {%- for state in states.device_tracker -%}
- {%- if state.name.lower() == User.lower() -%}
- {{ state.name }} is at {{ state.state }}
- {%- elif loop.last -%}
- I am sorry, I do not know where {{ User }} is.
- {%- endif -%}
- {%- else -%}
- Sorry, I don't have any trackers registered.
- {%- endfor -%}
- card:
- type: simple
- title: Sample title
- content: Some more content
-
-
+When activated, the Alexa component will have Home Assistant’s native intent support handle the incoming intents. If you want to run actions based on intents, use the intent_script component.
Working With Scenes
One of the most useful applications of Alexa integrations is to call scenes directly. This is easily achieved with some simple setup on the Home Assistant side and by letting Alexa know which scenes you want to run.
First we will configure Alexa. In the Amazon Interaction module add this to the intent schema:
@@ -231,15 +169,16 @@ Custom slot type for scene support.
ActivateSceneIntent activate {Scene}
-Then add the intent to your Alexa Section in your HA config file:
- ActivateSceneIntent:
- action:
- service: scene.turn_on
- data_template:
- entity_id: scene.{{ Scene | replace(" ", "_") }}
- speech:
- type: plaintext
- text: OK
+Then add the intent to your intent_script section in your HA config file:
+intent_script:
+ ActivateSceneIntent:
+ action:
+ service: scene.turn_on
+ data_template:
+ entity_id: scene.{{ Scene | replace(" ", "_") }}
+ speech:
+ type: plain
+ text: OK
Here we are using templates to take the name we gave to Alexa e.g. downstairs on and replace the space with an underscore so it becomes downstairs_on as Home Assistant expects.
@@ -267,15 +206,16 @@ Custom slot type for script support.
RunScriptIntent run {Script}
-Then add the intent to your Alexa Section in your HA config file:
- RunScriptIntent:
- action:
- service: script.turn_on
- data_template:
- entity_id: script.{{ Script | replace(" ", "_") }}
- speech:
- type: plaintext
- text: OK
+Then add the intent to your intent_script section in your HA config file:
+intent_script:
+ RunScriptIntent:
+ action:
+ service: script.turn_on
+ data_template:
+ entity_id: script.{{ Script | replace(" ", "_") }}
+ speech:
+ type: plain
+ text: OK
Now say Alexa ask homeassistant to run <some script> and Alexa will run that script for you.
@@ -311,32 +251,6 @@ Custom slot type for script support.
Alexa will now respond with a random phrase each time. You can use the include for as many different intents as you like so you only need to create the list once.
-
-As of April 2017, the random filter has been somewhat broken. You’ll get a random response the first time this runs, but subsequent commands will reply with the same randomly-chosen phrase. On reboot, Home Assistant will pick a new random choice, but you’re stuck with that choice till you reboot. To get around that, use the following code in alexa_confirm.yaml:
-
- >
- {% set responses = [
- "OK",
- "Sure",
- "If you insist",
- "Done",
- "No worries",
- "I can do that",
- "Leave it to me",
- "Consider it done",
- "As you wish",
- "By your command",
- "Affirmative",
- "Yes oh revered one",
- "I will",
- "As you decree, so shall it be",
- "No Problem"
- ] %}
- {% set rindex = (range(0, (responses | length - 1) )|random) -%}
- {{responses[rindex]}}
-
-
-
Flash Briefing Skills
As of version 0.31 Home Assistant supports the new Alexa Flash Briefing Skills API. A Flash Briefing Skill adds a new Flash Briefing source that is generated by Home Assistant.
Configuring a Flash Briefing skill in Home Assistant
diff --git a/components/amcrest/index.html b/components/amcrest/index.html
index b17bfac18f..710896b61e 100644
--- a/components/amcrest/index.html
+++ b/components/amcrest/index.html
@@ -160,6 +160,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -304,6 +307,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -322,6 +328,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/android_ip_webcam/index.html b/components/android_ip_webcam/index.html
index 2d417cf76e..f26c4e6a2d 100644
--- a/components/android_ip_webcam/index.html
+++ b/components/android_ip_webcam/index.html
@@ -161,6 +161,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -305,6 +308,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -323,6 +329,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/apcupsd/index.html b/components/apcupsd/index.html
index e0fcb707dc..cb6258c493 100644
--- a/components/apcupsd/index.html
+++ b/components/apcupsd/index.html
@@ -123,6 +123,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -267,6 +270,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -285,6 +291,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/apiai/index.html b/components/apiai/index.html
index 568c978c0b..9b12f419e8 100644
--- a/components/apiai/index.html
+++ b/components/apiai/index.html
@@ -109,70 +109,49 @@
Take a look to “Integrations”, in the left menu, to configure third parties.
Configuring Home Assistant
-Out of the box, the component will do nothing. You have to teach it about all intents you want it to answer to. The way it works is that the answer for each intent is based on templates that you define. Each template will have access to the existing states via the states variable but will also have access to all variables defined in the intent.
-You can use templates for setting speech.
-Actions are using the Home Assistant Script Syntax and also have access to the variables from the intent.
-Example of an Api.ai for the above configuration:
-# Example configuration.yaml entry
-apiai:
- intents:
- GetTemperature:
- speech: We have {{ states.sensor.temperature }} degrees
- async_action: False
- action:
- service: notify.notify
- data_template:
- message: Api.ai has send a request
-
-
-
-Inside an intent we can define this variables:
-
- - speech (Optional): Text or template to return to Api.ai
- - action (Optional): Script definition
- - async_action (Optional): If Home Assistant should execute the action asynchronously (returning response to Api.ai without waiting the action to finish). Should be set to
True if Api.ai is returning the “Cannot connect to Home Assistant or it is taking to long” message, but then you will not be able to use values based on the result of the action. Defaults to False.
-
+When activated, the Alexa component will have Home Assistant’s native intent support handle the incoming intents. If you want to run actions based on intents, use the intent_script component.
Examples
Download this zip and load it in your Api.ai agent (Settings -> Export and Import) for examples intents to use with this configuration:
# Example configuration.yaml entry
apiai:
- intents:
- Temperature:
- speech: The temperature at home is {{ states('sensor.home_temp') }} degrees
- LocateIntent:
- speech: >
- {%- for state in states.device_tracker -%}
- {%- if state.name.lower() == User.lower() -%}
- {{ state.name }} is at {{ state.state }}
- {%- elif loop.last -%}
- I am sorry, I do not know where {{ User }} is.
+
+intent_script:
+ Temperature:
+ speech: The temperature at home is {{ states('sensor.home_temp') }} degrees
+ LocateIntent:
+ speech: >
+ {%- for state in states.device_tracker -%}
+ {%- if state.name.lower() == User.lower() -%}
+ {{ state.name }} is at {{ state.state }}
+ {%- elif loop.last -%}
+ I am sorry, I do not know where {{ User }} is.
+ {%- endif -%}
+ {%- else -%}
+ Sorry, I don't have any trackers registered.
+ {%- endfor -%}
+ WhereAreWeIntent:
+ speech: >
+ {%- if is_state('device_tracker.adri', 'home') and
+ is_state('device_tracker.bea', 'home') -%}
+ You are both home, you silly
+ {%- else -%}
+ Bea is at {{ states("device_tracker.bea") }}
+ and Adri is at {{ states("device_tracker.adri") }}
+ {% endif %}
+ TurnLights:
+ speech: Turning {{ Room }} lights {{ OnOff }}
+ action:
+ - service: notify.pushbullet
+ data_template:
+ message: Someone asked via apiai to turn {{ Room }} lights {{ OnOff }}
+ - service_template: >
+ {%- if OnOff == "on" -%}
+ switch.turn_on
+ {%- else -%}
+ switch.turn_off
{%- endif -%}
- {%- else -%}
- Sorry, I don't have any trackers registered.
- {%- endfor -%}
- WhereAreWeIntent:
- speech: >
- {%- if is_state('device_tracker.adri', 'home') and
- is_state('device_tracker.bea', 'home') -%}
- You are both home, you silly
- {%- else -%}
- Bea is at {{ states("device_tracker.bea") }}
- and Adri is at {{ states("device_tracker.adri") }}
- {% endif %}
- TurnLights:
- speech: Turning {{ Room }} lights {{ OnOff }}
- action:
- - service: notify.pushbullet
- data_template:
- message: Someone asked via apiai to turn {{ Room }} lights {{ OnOff }}
- - service_template: >
- {%- if OnOff == "on" -%}
- switch.turn_on
- {%- else -%}
- switch.turn_off
- {%- endif -%}
- data_template:
- entity_id: "switch.light_{{ Room | replace(' ', '_') }}"
+ data_template:
+ entity_id: "switch.light_{{ Room | replace(' ', '_') }}"
diff --git a/components/apple_tv/index.html b/components/apple_tv/index.html
new file mode 100644
index 0000000000..840d4c0f11
--- /dev/null
+++ b/components/apple_tv/index.html
@@ -0,0 +1,459 @@
+
+
+
+
+
+
+
+
+ Apple TV - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Apple TV
+
+
+
+ The apple_tv platform allows you to control an Apple TV (3rd and 4th generation). See the remote platform if you want to send remote control buttons, e.g. arrow keys.
+
+Currently you must have Home Sharing enabled for this to work. Support for pairing Home Assistant with your device will be supported in a later release.
+
+To use this component, you must first install some system libraries and a compiler. For Debian or a similar system, this should be enough:
+$ sudo apt-get install build-essential libssl-dev libffi-dev python-dev
+
+
+If you want to automatically discover new devices, just make sure you have discovery: in your configuration.yaml file. To manually add one or more Apple TVs to your installation, add the following to your configuration.yaml file:
+# Example configuration.yaml entry
+apple_tv:
+ - host: IP_1
+ login_id: LOGIN_ID_1
+ name: NAME_1
+ start_off: START_OFF_1
+ credentials: CREDENTIALS_1
+ - host: IP_2
+ login_id: LOGIN_ID_2
+ name: NAME_2
+ start_off: START_OFF_2
+ credentials: CREDENTIALS_2
+
+
+Configuration variables:
+
+ - host (Required): The IP-address of the device.
+ - login_id (Required): An identifier used to login to the device, see below.
+ - name (Optional): The name of the device used in the frontend.
+ - start_off (Optional): Set to true if device should start in fake standby.
+ - credentials (Optional): Credentials used for AirPlay playback.
+
+In order to connect to the device you need a login id. The easiest way to obtain this identifier is to use the apple_tv_scan service (described below). Additional information about start_off and credentials can also be found under the guides section.
+ Guides
+ Scanning for devices
+To scan for devices, press the icon in the upper left corner and select the leftmost icon according to the image:
+
+Select apple_tv as domain and apple_tv_scan as service then press the button:
+
+Scanning will be done for three seconds and notification will be shown in the state view with all found devices:
+
+Alternatively you may use the application atvremote. Install it with pip3 install --upgrade pyatv in your Home Assistant environment (note: do not use sudo). Then run atvremote scan to scan for all devices (try again if a device is missing):
+$ atvremote scan
+Found Apple TVs:
+ - Apple TV at 10.0.10.22 (login id: 00000000-1234-5678-9012-345678901234)
+
+Note: You must use 'pair' with devices that have home sharing disabled
+
+
+Just copy and paste the login id from the device you want to add. For more details about atvremote, see: this page.
+ My Apple TV turns on when I restart Home Assistant
+The Apple TV will automatically turn on if a request is sent to it, e.g. if a button is pressed, something is streamed to it via AirPlay or if current state (currently playing) is accessed. This is how Apple has designed it and it will cause problems if you are using HDMI CEC. Every time Home Assistant is started, a new request is sent to the device to figure out what is currently playing. When using CEC, this will wake up your TV and other devices you have configured.
+So, if your TV is randomly turning on, this is probably the reason. As stated, this is by design and there is no real fix for it. There’s also no known way to turn off the Apple TV via the procotol used for communication. You basically have the following options:
+
+ - Do not use this platform
+ - Disable HDMI CEC on your Apple TV
+ - Use “fake standby”
+
+The first two points are quite obvious. Fake standby is a concept implemented in this platform that disables all requests to the device and make it appear as being “off” in the web interface. This will make sure that the device is not woken up, but it will of course not show any information or allow you to control it. It is however easy to turn it on (or off) in the web interface or using an automation with turn_on. To make it more useful, you can write automations that turns it on or off depending on some other device, like the input source on your receiver.
+To put a device into fake standby when starting Home Assistant, add start_off: true to your configuration.
+
+Turning the device on/off in the user interface will not turn the physical device on/off according to description above.
+
+ Setting up device authentication
+If you, when playing media with play_url, get the following error message:
+“This AirPlay connection requires iOS 7.1 or later, OS X 10.10 or later, or iTunes 11.2 or later.”
+then device authentication is required. Press the icon in the upper left corner and select the leftmost icon according to the image below:
+
+Select apple_tv as domain, apple_tv_authenticate as service and enter {'entity_id': 'XXX'} into “Service Data”, but replace XXX with the entity id of your device (e.g. media_player.apple_tv). Press the button and hopefully you are presented with an input dialog asking for a pin code:
+
+If no dialog appears, go back to the states view and display it from there (press CONFIGURE as displayed in the image):
+
+A PIN code should now be visible on your TV, just enter it into the dialog and press “Confirm”. You should see if it succeeded in the state view. Copy the credentials and insert it into your configuration (make sure you copy everything, it should be 81 characters) after credentials: with no line-break:
+# Example configuration.yaml entry
+apple_tv:
+ - host: 10.0.0.20
+ login_id: 00000000-1234-5678-9012-345678901234
+ credentials: 1B8C387DDB59BDF6:CF5ABB6A2C070688F5926ADB7C010F6DF847252C15F9BDB6DA3E09D6591E90E5
+
+
+Restart Home Assistant and you should now be able to use play_url as before.
+ Services
+ Service apple_tv_authenticate
+In order to play media on an Apple TV with device authentication enabled (e.g. ATV4 with tvOS 10.2+), Home Assistant must properly authenticated. This method starts the process and presents the credentials needed for playback as a persistent notification. Please see guide above for usage.
+
+
+
+ Service data attribute
+ Optional
+ Description
+
+
+
+
+ entity_idyes
+ String or list of strings that point at entity_ids of Apple TVs.
+
+
+
+ Service apple_tv_scan
+Scans the local network for Apple TVs. All found devices are presented as a persistent notification.
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/arlo/index.html b/components/arlo/index.html
index b6679488c4..6722f29d55 100644
--- a/components/arlo/index.html
+++ b/components/arlo/index.html
@@ -130,6 +130,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -274,6 +277,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -292,6 +298,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/axis/index.html b/components/axis/index.html
index b0850f9f93..7837f68998 100644
--- a/components/axis/index.html
+++ b/components/axis/index.html
@@ -223,6 +223,9 @@ Any specific levels for triggers needs to be configured on the device.
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -367,6 +370,9 @@ Any specific levels for triggers needs to be configured on the device.
Twilio
+
+ Velbus
+
Velux
@@ -385,6 +391,9 @@ Any specific levels for triggers needs to be configured on the device.
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/binary_sensor.alarmdecoder/index.html b/components/binary_sensor.alarmdecoder/index.html
index 4c5b7d7eb6..c64c842bc5 100644
--- a/components/binary_sensor.alarmdecoder/index.html
+++ b/components/binary_sensor.alarmdecoder/index.html
@@ -248,6 +248,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -260,6 +263,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.android_ip_webcam/index.html b/components/binary_sensor.android_ip_webcam/index.html
index 6bb07df80a..d5278eacf8 100644
--- a/components/binary_sensor.android_ip_webcam/index.html
+++ b/components/binary_sensor.android_ip_webcam/index.html
@@ -247,6 +247,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -259,6 +262,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.apcupsd/index.html b/components/binary_sensor.apcupsd/index.html
index b9fee5f4b9..62532e28b0 100644
--- a/components/binary_sensor.apcupsd/index.html
+++ b/components/binary_sensor.apcupsd/index.html
@@ -151,6 +151,9 @@
Glances
+
+ Google Wifi
+
HDDTemp
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index 0f15e30069..1a21dc47ac 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -274,6 +274,9 @@ This sensor is not suitable for fast state changes because there is a high possi
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -286,6 +289,9 @@ This sensor is not suitable for fast state changes because there is a high possi
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.aurora/index.html b/components/binary_sensor.aurora/index.html
index 4001e20790..b3cf3e0879 100644
--- a/components/binary_sensor.aurora/index.html
+++ b/components/binary_sensor.aurora/index.html
@@ -247,6 +247,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -259,6 +262,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.axis/index.html b/components/binary_sensor.axis/index.html
index c061aebed7..0fa1c07439 100644
--- a/components/binary_sensor.axis/index.html
+++ b/components/binary_sensor.axis/index.html
@@ -253,6 +253,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -265,6 +268,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.bbb_gpio/index.html b/components/binary_sensor.bbb_gpio/index.html
index 6a7a48777b..0e2aca495a 100644
--- a/components/binary_sensor.bbb_gpio/index.html
+++ b/components/binary_sensor.bbb_gpio/index.html
@@ -270,6 +270,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -282,6 +285,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.blink/index.html b/components/binary_sensor.blink/index.html
index a6b29b481d..b6bb5fab20 100644
--- a/components/binary_sensor.blink/index.html
+++ b/components/binary_sensor.blink/index.html
@@ -245,6 +245,9 @@ To get your Blink binary sensors working with Home Assistant, follow the instruc
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -257,6 +260,9 @@ To get your Blink binary sensors working with Home Assistant, follow the instruc
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.bloomsky/index.html b/components/binary_sensor.bloomsky/index.html
index c24bd79478..41bd44032a 100644
--- a/components/binary_sensor.bloomsky/index.html
+++ b/components/binary_sensor.bloomsky/index.html
@@ -265,6 +265,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -277,6 +280,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.command_line/index.html b/components/binary_sensor.command_line/index.html
index d35d912cce..2e2570e9c1 100644
--- a/components/binary_sensor.command_line/index.html
+++ b/components/binary_sensor.command_line/index.html
@@ -302,6 +302,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -314,6 +317,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.concord232/index.html b/components/binary_sensor.concord232/index.html
index 3b31558317..a6d6542ed9 100644
--- a/components/binary_sensor.concord232/index.html
+++ b/components/binary_sensor.concord232/index.html
@@ -248,6 +248,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -260,6 +263,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.digital_ocean/index.html b/components/binary_sensor.digital_ocean/index.html
index afd491fa9c..288f8a0df8 100644
--- a/components/binary_sensor.digital_ocean/index.html
+++ b/components/binary_sensor.digital_ocean/index.html
@@ -154,6 +154,9 @@
Glances
+
+ Google Wifi
+
HDDTemp
diff --git a/components/binary_sensor.ecobee/index.html b/components/binary_sensor.ecobee/index.html
index 112d6cc063..9daf9ad37d 100644
--- a/components/binary_sensor.ecobee/index.html
+++ b/components/binary_sensor.ecobee/index.html
@@ -249,6 +249,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -261,6 +264,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.eight_sleep/index.html b/components/binary_sensor.eight_sleep/index.html
index c251d10260..c68a9c5538 100644
--- a/components/binary_sensor.eight_sleep/index.html
+++ b/components/binary_sensor.eight_sleep/index.html
@@ -244,6 +244,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -256,6 +259,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.enocean/index.html b/components/binary_sensor.enocean/index.html
index 9b6ac1bcee..2bdf2e58f1 100644
--- a/components/binary_sensor.enocean/index.html
+++ b/components/binary_sensor.enocean/index.html
@@ -285,6 +285,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -297,6 +300,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.envisalink/index.html b/components/binary_sensor.envisalink/index.html
index b25cba474c..04620603b7 100644
--- a/components/binary_sensor.envisalink/index.html
+++ b/components/binary_sensor.envisalink/index.html
@@ -248,6 +248,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -260,6 +263,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.ffmpeg_motion/index.html b/components/binary_sensor.ffmpeg_motion/index.html
index 9a5ab072b2..af11d18f06 100644
--- a/components/binary_sensor.ffmpeg_motion/index.html
+++ b/components/binary_sensor.ffmpeg_motion/index.html
@@ -264,6 +264,9 @@ If the ffmpeg process is broken, the sens
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -276,6 +279,9 @@ If the ffmpeg process is broken, the sens
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.ffmpeg_noise/index.html b/components/binary_sensor.ffmpeg_noise/index.html
index 26fb4d7412..e6c71094f8 100644
--- a/components/binary_sensor.ffmpeg_noise/index.html
+++ b/components/binary_sensor.ffmpeg_noise/index.html
@@ -255,6 +255,9 @@ If the ffmpeg process is broken, the sens
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -267,6 +270,9 @@ If the ffmpeg process is broken, the sens
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.flic/index.html b/components/binary_sensor.flic/index.html
index d908f45b4d..72c21bf398 100644
--- a/components/binary_sensor.flic/index.html
+++ b/components/binary_sensor.flic/index.html
@@ -276,6 +276,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -288,6 +291,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.hikvision/index.html b/components/binary_sensor.hikvision/index.html
index 5d1ab0bc6f..1237b8e229 100644
--- a/components/binary_sensor.hikvision/index.html
+++ b/components/binary_sensor.hikvision/index.html
@@ -333,6 +333,9 @@ binary_sensor.home_line_crossing_2
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -345,6 +348,9 @@ binary_sensor.home_line_crossing_2
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.homematic/index.html b/components/binary_sensor.homematic/index.html
index 6bb31da5d5..097e869d1b 100644
--- a/components/binary_sensor.homematic/index.html
+++ b/components/binary_sensor.homematic/index.html
@@ -256,6 +256,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -268,6 +271,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.http/index.html b/components/binary_sensor.http/index.html
index b118e38fe6..1ebe337167 100644
--- a/components/binary_sensor.http/index.html
+++ b/components/binary_sensor.http/index.html
@@ -290,6 +290,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -302,6 +305,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.insteon_plm/index.html b/components/binary_sensor.insteon_plm/index.html
index 1a7708339e..315200d4b8 100644
--- a/components/binary_sensor.insteon_plm/index.html
+++ b/components/binary_sensor.insteon_plm/index.html
@@ -246,6 +246,9 @@ component.
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -258,6 +261,9 @@ component.
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.iss/index.html b/components/binary_sensor.iss/index.html
index a8b0968f73..33f973f3c6 100644
--- a/components/binary_sensor.iss/index.html
+++ b/components/binary_sensor.iss/index.html
@@ -253,6 +253,9 @@ If you set show_on_map show_on_map Nest component configured to u
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -303,6 +306,9 @@ You must have the Nest component configured to u
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.netatmo/index.html b/components/binary_sensor.netatmo/index.html
index 07088c4e3f..bfa27dc066 100644
--- a/components/binary_sensor.netatmo/index.html
+++ b/components/binary_sensor.netatmo/index.html
@@ -296,6 +296,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -308,6 +311,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.nx584/index.html b/components/binary_sensor.nx584/index.html
index 5148da2163..f6982d762f 100644
--- a/components/binary_sensor.nx584/index.html
+++ b/components/binary_sensor.nx584/index.html
@@ -270,6 +270,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -282,6 +285,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.octoprint/index.html b/components/binary_sensor.octoprint/index.html
index 5253da8fd1..015d500fcf 100644
--- a/components/binary_sensor.octoprint/index.html
+++ b/components/binary_sensor.octoprint/index.html
@@ -264,6 +264,9 @@ You must have the OctoPrint component confi
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -276,6 +279,9 @@ You must have the OctoPrint component confi
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.pilight/index.html b/components/binary_sensor.pilight/index.html
index c2adc08d5b..2d64ad400b 100644
--- a/components/binary_sensor.pilight/index.html
+++ b/components/binary_sensor.pilight/index.html
@@ -8,7 +8,7 @@
Pilight Binary Sensor - Home Assistant
-
+
@@ -16,12 +16,12 @@
-
+
-
+
@@ -74,8 +74,8 @@
- This component implement the pilight hub binary sensor functionality.
-Two type of pilight binary sensor configuration available. A normal sensor which send the on and off state cyclical and a trigger sensor which send only a trigger when an event happend (for example lots of cheap PIR motion detector) (see example configuration below).
+ The pilight binary sensor platform implement the pilight hub binary sensor functionality. Two type of Pilight binary sensor configuration available. A normal sensor which send the on and off state cyclical and a trigger sensor which send only a trigger when an event happend (for example lots of cheap PIR motion detector).
+To enable a Pilight binary sensor in your installation, add the following to your configuration.yaml file:
# Example configuration.yml entry
binary_sensor:
- platform: pilight
@@ -276,6 +276,9 @@ Two type of pilight binary sensor configuration available. A normal sensor which
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -288,6 +291,9 @@ Two type of pilight binary sensor configuration available. A normal sensor which
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.ping/index.html b/components/binary_sensor.ping/index.html
index 23915c3ca9..63ef868267 100644
--- a/components/binary_sensor.ping/index.html
+++ b/components/binary_sensor.ping/index.html
@@ -260,6 +260,9 @@ When run on Windows systems, the round trip time attributes are rounded to the n
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -272,6 +275,9 @@ When run on Windows systems, the round trip time attributes are rounded to the n
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.raspihats/index.html b/components/binary_sensor.raspihats/index.html
index e6aca725d3..506ad28b7c 100644
--- a/components/binary_sensor.raspihats/index.html
+++ b/components/binary_sensor.raspihats/index.html
@@ -280,6 +280,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -292,6 +295,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.rest/index.html b/components/binary_sensor.rest/index.html
index b998dd0001..65d6c3fbdc 100644
--- a/components/binary_sensor.rest/index.html
+++ b/components/binary_sensor.rest/index.html
@@ -323,6 +323,9 @@ User-Agent: Home Assistant
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -335,6 +338,9 @@ User-Agent: Home Assistant
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.rfxtrx/index.html b/components/binary_sensor.rfxtrx/index.html
index b688e2dea6..ef8b249dfc 100644
--- a/components/binary_sensor.rfxtrx/index.html
+++ b/components/binary_sensor.rfxtrx/index.html
@@ -347,6 +347,9 @@ to configure your new devices and leave it off otherwise.
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -359,6 +362,9 @@ to configure your new devices and leave it off otherwise.
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.ring/index.html b/components/binary_sensor.ring/index.html
index 1b229d3346..c665e6eff5 100644
--- a/components/binary_sensor.ring/index.html
+++ b/components/binary_sensor.ring/index.html
@@ -259,6 +259,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -271,6 +274,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.rpi_gpio/index.html b/components/binary_sensor.rpi_gpio/index.html
index 2d901e1a66..acb6011721 100644
--- a/components/binary_sensor.rpi_gpio/index.html
+++ b/components/binary_sensor.rpi_gpio/index.html
@@ -267,6 +267,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -279,6 +282,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.rpi_pfio/index.html b/components/binary_sensor.rpi_pfio/index.html
index 9e21e014dc..7a5cd6cbef 100644
--- a/components/binary_sensor.rpi_pfio/index.html
+++ b/components/binary_sensor.rpi_pfio/index.html
@@ -270,6 +270,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -282,6 +285,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.sleepiq/index.html b/components/binary_sensor.sleepiq/index.html
index 5fdd2d393c..b307b041cd 100644
--- a/components/binary_sensor.sleepiq/index.html
+++ b/components/binary_sensor.sleepiq/index.html
@@ -243,6 +243,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -255,6 +258,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.spc/index.html b/components/binary_sensor.spc/index.html
index 0a0214650e..34c0a1296c 100644
--- a/components/binary_sensor.spc/index.html
+++ b/components/binary_sensor.spc/index.html
@@ -245,6 +245,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -257,6 +260,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.tcp/index.html b/components/binary_sensor.tcp/index.html
index 6efe77f14a..e801eeeb2c 100644
--- a/components/binary_sensor.tcp/index.html
+++ b/components/binary_sensor.tcp/index.html
@@ -260,6 +260,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -272,6 +275,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.template/index.html b/components/binary_sensor.template/index.html
index d165aa849f..9f0c33b61e 100644
--- a/components/binary_sensor.template/index.html
+++ b/components/binary_sensor.template/index.html
@@ -361,6 +361,9 @@ and z-wave multisensor presence sensors.
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -373,6 +376,9 @@ and z-wave multisensor presence sensors.
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.threshold/index.html b/components/binary_sensor.threshold/index.html
index 3d4050fc16..e2ab8ff6f8 100644
--- a/components/binary_sensor.threshold/index.html
+++ b/components/binary_sensor.threshold/index.html
@@ -252,6 +252,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -264,6 +267,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.trend/index.html b/components/binary_sensor.trend/index.html
index decbd2db16..b3af66a2e6 100644
--- a/components/binary_sensor.trend/index.html
+++ b/components/binary_sensor.trend/index.html
@@ -277,6 +277,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -289,6 +292,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.velbus/index.html b/components/binary_sensor.velbus/index.html
new file mode 100644
index 0000000000..262fbde3c9
--- /dev/null
+++ b/components/binary_sensor.velbus/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+ Velbus sensors - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Velbus Sensors
+
+
+
+ The velbus binary_sensor allows you to control Velbus connected wall switches.
+To use your Velbus wall switches in your installation, add the following to your configuration.yaml file:
+# Example configuration.yaml entry
+
+binary_sensor:
+ - platform: velbus
+ devices:
+ - name: Wall Switch 1
+ module: 0xda
+ channel: 4
+ - name: Wall Switch 2
+ module: 0xbc
+ channel: 1
+ is_pushbutton: true
+
+
+Configuration variables:
+
+ - devices array (Required): The array contains the binary sensors to configure
+
+ - name (Required): Name of the binary sensor.
+ - module (Required): The hexadecimal module address
+ - channel (Required): The channel number in the module.
+ - is_pushbutton (Optional): Booelan to indicate if a wall switch is a push button or not (default: false)
+
+
+
+For hub configuration, see the Velbus component.
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/binary_sensor.vera/index.html b/components/binary_sensor.vera/index.html
index 49a8bf1711..f0e6001fd8 100644
--- a/components/binary_sensor.vera/index.html
+++ b/components/binary_sensor.vera/index.html
@@ -259,6 +259,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -271,6 +274,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.verisure/index.html b/components/binary_sensor.verisure/index.html
index 7d57c1749c..65e143c3ae 100644
--- a/components/binary_sensor.verisure/index.html
+++ b/components/binary_sensor.verisure/index.html
@@ -254,6 +254,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -266,6 +269,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.wink/index.html b/components/binary_sensor.wink/index.html
index ad946cba7f..01fe04b55e 100644
--- a/components/binary_sensor.wink/index.html
+++ b/components/binary_sensor.wink/index.html
@@ -285,6 +285,9 @@ The above devices are confimed to work, but others may work as well.
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -297,6 +300,9 @@ The above devices are confimed to work, but others may work as well.
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.workday/index.html b/components/binary_sensor.workday/index.html
index fcd349f57f..1cc7f05ef7 100644
--- a/components/binary_sensor.workday/index.html
+++ b/components/binary_sensor.workday/index.html
@@ -265,6 +265,9 @@ If you use the sensor for Canada (CA) wit
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -277,6 +280,9 @@ If you use the sensor for Canada (CA) wit
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.xiaomi/index.html b/components/binary_sensor.xiaomi/index.html
new file mode 100644
index 0000000000..5b2c11175b
--- /dev/null
+++ b/components/binary_sensor.xiaomi/index.html
@@ -0,0 +1,604 @@
+
+
+
+
+
+
+
+
+ Xiaomi Binary Sensor - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Xiaomi Binary Sensor
+
+
+
+ The xiaomi binary sensor platform allows you to get data from your Xiaomi binary sensors.
+The requirement is that you have setup the xiaomi component.
+ Type of sensors supported
+
+ - Motion
+ - Door / Window
+ - Smoke
+ - Gas
+ - Xiaomi Wireless Button
+ - Xiaomi Cube
+
+ Automation examples
+ Motion
+- alias: If there is motion and its dark turn on the gateway light
+ trigger:
+ platform: state
+ entity_id: binary_sensor.motion_sensor_158d000xxxxxc2
+ from: 'off'
+ to: 'on'
+ condition:
+ condition: numeric_state
+ entity_id: sensor.illumination_34ce00xxxx11
+ below: 300
+ action:
+ service: light.turn_on
+ entity_id: light.gateway_light_34ce00xxxx11
+ data:
+ brightness: 5
+- alias: If there no motion for 5 minutes turn off the gateway light
+ trigger:
+ platform: state
+ entity_id: binary_sensor.motion_sensor_158d000xxxxxc2
+ from: 'on'
+ to: 'off'
+ for:
+ minutes: 5
+ action:
+ service: light.turn_off
+ entity_id: light.gateway_light_34ce00xxxx11
+
+
+ Door and/or Window
+- alias: If the window is open turn off the radiator
+ trigger:
+ platform: state
+ entity_id: binary_sensor.door_window_sensor_158d000xxxxxc2
+ from: 'off'
+ to: 'on'
+ action:
+ service: climate.set_operation_mode
+ entity_id: climate.livingroom
+ data:
+ operation_mode: 'Off'
+- alias: If the window is closed for 5 minutes turn on the radiator again
+ trigger:
+ platform: state
+ entity_id: binary_sensor.door_window_sensor_158d000xxxxxc2
+ from: 'on'
+ to: 'off'
+ for:
+ minutes: 5
+ action:
+ service: climate.set_operation_mode
+ entity_id: climate.livingroom
+ data:
+ operation_mode: 'Smart schedule'
+
+
+ Smoke
+- alias: Send notification on fire alarm
+ trigger:
+ platform: state
+ entity_id: binary_sensor.smoke_sensor_158d0001574899
+ from: 'off'
+ to: 'on'
+ action:
+ - service: notify.html5
+ data:
+ title: Fire alarm!
+ message: Fire/Smoke detected!
+ - service: xiaomi.play_ringtone
+ data:
+ gw_mac: xxxxxxxxxxxx
+ ringtone_id: 2
+ ringtone_vol: 100
+
+
+ Gas
+- alias: Send notification on gas alarm
+ trigger:
+ platform: state
+ entity_id: binary_sensor.natgas_sensor_158dxxxxxxxxxx
+ from: 'off'
+ to: 'on'
+ action:
+ - service: notify.html5
+ data_template:
+ title: Gas alarm!
+ message: 'Gas with a density of {{ states.binary_sensor.natgas_sensor_158dxxxxxxxxxx.attributes.density }} detected.'
+
+
+ Xiaomi Wireless Button
+Available events are single, double, hold, long_click_press and long_click_release. For Square version (Aqara brand) only single and double events are supported. Furthermore the space between two clicks to generate a double click must be quite large now.
+- alias: Toggle dining light on single press
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.switch_158d000xxxxxc2
+ click_type: single
+ action:
+ service: switch.toggle
+ entity_id: switch.wall_switch_left_158d000xxxxx01
+- alias: Toggle couch light on double click
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.switch_158d000xxxxxc2
+ click_type: double
+ action:
+ service: switch.toggle
+ entity_id: switch.wall_switch_right_158d000xxxxx01
+- alias: Let a dog bark on long press
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.switch_158d000xxxxxc2
+ click_type: long_click_press
+ action:
+ service: xiaomi.play_ringtone
+ data:
+ gw_mac: xxxxxxxxxxxx
+ ringtone_id: 8
+ ringtone_vol: 8
+
+
+ Xiaomi Cube
+Available events are flip90, flip180, move, tap_twice, shake_air, swing, alert, free_fall and rotate.
+- alias: Cube event flip90
+ trigger:
+ platform: event
+ event_type: cube_action
+ event_data:
+ entity_id: binary_sensor.cube_15xxxxxxxxxxxx
+ action_type: flip90
+ action:
+ - service: light.turn_on
+ entity_id: light.gateway_light_28xxxxxxxxxx
+ data:
+ color_name: "springgreen"
+- alias: Cube event flip180
+ trigger:
+ platform: event
+ event_type: cube_action
+ event_data:
+ entity_id: binary_sensor.cube_15xxxxxxxxxxxx
+ action_type: flip180
+ action:
+ - service: light.turn_on
+ entity_id: light.gateway_light_28xxxxxxxxxx
+ data:
+ color_name: "darkviolet"
+- alias: Cube event move
+ trigger:
+ platform: event
+ event_type: cube_action
+ event_data:
+ entity_id: binary_sensor.cube_15xxxxxxxxxxxx
+ action_type: move
+ action:
+ - service: light.turn_on
+ entity_id: light.gateway_light_28xxxxxxxxxx
+ data:
+ color_name: "gold"
+- alias: Cube event tap_twice
+ trigger:
+ platform: event
+ event_type: cube_action
+ event_data:
+ entity_id: binary_sensor.cube_15xxxxxxxxxxxx
+ action_type: tap_twice
+ action:
+ - service: light.turn_on
+ entity_id: light.gateway_light_28xxxxxxxxxx
+ data:
+ color_name: "deepskyblue"
+- alias: Cube event shake_air
+ trigger:
+ platform: event
+ event_type: cube_action
+ event_data:
+ entity_id: binary_sensor.cube_15xxxxxxxxxxxx
+ action_type: shake_air
+ action:
+ - service: light.turn_on
+ entity_id: light.gateway_light_28xxxxxxxxxx
+ data:
+ color_name: "blue"
+
+
+#### Aqara Wireless Switch
+The Aqara Wireless Switch is available as single-key and double-key version. Each key behaves like the Wireless Button limited to the click event single. The double key version adds a third device called binary_sensor.wall_switch_both_158xxxxxxxxx12 which reports a click event called both if both keys are pressed.
+- alias: Decrease brightness of the gateway light
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.wall_switch_left_158xxxxxxxxx12
+ click_type: single
+ action:
+ service: light.turn_on
+ entity_id: light.gateway_light_34xxxxxxxx13
+ data_template:
+ brightness: >-
+ {% if states.light.gateway_light_34xxxxxxxx13.attributes.brightness %}
+ {% if states.light.gateway_light_34xxxxxxxx13.attributes.brightness - 60 >= 10 %}
+ {{states.light.gateway_light_34xxxxxxxx13.attributes.brightness - 60}}
+ {% else %}
+ {{states.light.gateway_light_34xxxxxxxx13.attributes.brightness}}
+ {% endif %}
+ {% else %}
+ 10
+ {% endif %}
+
+- alias: Increase brightness of the gateway light
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.wall_switch_right_158xxxxxxxxx12
+ click_type: single
+ action:
+ service: light.turn_on
+ entity_id: light.gateway_light_34xxxxxxxx13
+ data_template:
+ brightness: >-
+ {% if states.light.gateway_light_34xxxxxxxx13.attributes.brightness %}
+ {% if states.light.gateway_light_34xxxxxxxx13.attributes.brightness + 60 <= 255 %}
+ {{states.light.gateway_light_34xxxxxxxx13.attributes.brightness + 60}}
+ {% else %}
+ {{states.light.gateway_light_34xxxxxxxx13.attributes.brightness}}
+ {% endif %}
+ {% else %}
+ 10
+ {% endif %}
+
+- alias: Turn off the gateway light
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.wall_switch_both_158xxxxxxxxx12
+ click_type: both
+ action:
+ service: light.turn_off
+ entity_id: light.gateway_light_34xxxxxxxx13
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/binary_sensor.zha/index.html b/components/binary_sensor.zha/index.html
index af8a525d5f..75d3ae0594 100644
--- a/components/binary_sensor.zha/index.html
+++ b/components/binary_sensor.zha/index.html
@@ -246,6 +246,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -258,6 +261,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.zigbee/index.html b/components/binary_sensor.zigbee/index.html
index da9607ab03..e77971df01 100644
--- a/components/binary_sensor.zigbee/index.html
+++ b/components/binary_sensor.zigbee/index.html
@@ -264,6 +264,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -276,6 +279,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.zwave/index.html b/components/binary_sensor.zwave/index.html
index 9dd884bb7c..5481fba38b 100644
--- a/components/binary_sensor.zwave/index.html
+++ b/components/binary_sensor.zwave/index.html
@@ -261,6 +261,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -273,6 +276,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor/index.html b/components/binary_sensor/index.html
index 7a01b764ec..32b6da73c3 100644
--- a/components/binary_sensor/index.html
+++ b/components/binary_sensor/index.html
@@ -247,6 +247,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -259,6 +262,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/blink/index.html b/components/blink/index.html
index a0e755c99d..b1f00043b8 100644
--- a/components/blink/index.html
+++ b/components/blink/index.html
@@ -171,6 +171,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -315,6 +318,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -333,6 +339,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/bloomsky/index.html b/components/bloomsky/index.html
index 65943b9080..31f6204d27 100644
--- a/components/bloomsky/index.html
+++ b/components/bloomsky/index.html
@@ -130,6 +130,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -274,6 +277,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -292,6 +298,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/comfoconnect/index.html b/components/comfoconnect/index.html
index d1ac024b24..b653053be9 100644
--- a/components/comfoconnect/index.html
+++ b/components/comfoconnect/index.html
@@ -146,6 +146,9 @@ Note that it’s not possible to have multiple connection to the bridge at the s
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -290,6 +293,9 @@ Note that it’s not possible to have multiple connection to the bridge at the s
Twilio
+
+ Velbus
+
Velux
@@ -308,6 +314,9 @@ Note that it’s not possible to have multiple connection to the bridge at the s
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/conversation/index.html b/components/conversation/index.html
index 9158e338b3..1e46d0c54a 100644
--- a/components/conversation/index.html
+++ b/components/conversation/index.html
@@ -74,7 +74,7 @@
- The conversation component can process sentences into commands for Home Assistant. It currently has built in functionality to recognize turn <Friendly Name> <on/off>, but custom phrases can be added through configuration.
+ The conversation component can process sentences into commands for Home Assistant. It currently has built in functionality to recognize turn <Friendly Name> <on/off>, but custom phrases can be added through configuration.
To enable the conversation option in your installation, add the following to your configuration.yaml file:
# Example base configuration.yaml entry
conversation:
@@ -89,8 +89,15 @@
service: input_boolean.toggle
-The action keyword uses script
-syntax.
+The action keyword uses script syntax.
+To use the conversation component with the shopping list component add an intent.
+# Example configuration.yaml entry
+conversation:
+ intents:
+ ShoppingListAddItem:
+ - Add {item} to my shopping list
+
+
When this component is active and you are using a supported browser voice commands will be activated in the frontend. Browse to the demo using Chrome or Chromium to see it in action.
diff --git a/components/cover.command_line/index.html b/components/cover.command_line/index.html
index 1b25791d31..a0bbe35a99 100644
--- a/components/cover.command_line/index.html
+++ b/components/cover.command_line/index.html
@@ -214,6 +214,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.garadget/index.html b/components/cover.garadget/index.html
index f6d8683cdd..6da5aecedd 100644
--- a/components/cover.garadget/index.html
+++ b/components/cover.garadget/index.html
@@ -231,6 +231,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.homematic/index.html b/components/cover.homematic/index.html
index 6e3979a809..20f69ca640 100644
--- a/components/cover.homematic/index.html
+++ b/components/cover.homematic/index.html
@@ -172,6 +172,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.isy994/index.html b/components/cover.isy994/index.html
index f0f92b1aa8..b66b283ebd 100644
--- a/components/cover.isy994/index.html
+++ b/components/cover.isy994/index.html
@@ -172,6 +172,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.knx/index.html b/components/cover.knx/index.html
index 74cafd5c5f..a07da34722 100644
--- a/components/cover.knx/index.html
+++ b/components/cover.knx/index.html
@@ -190,6 +190,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.lutron_caseta/index.html b/components/cover.lutron_caseta/index.html
index 305c2136ac..3a946acb0d 100644
--- a/components/cover.lutron_caseta/index.html
+++ b/components/cover.lutron_caseta/index.html
@@ -169,6 +169,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.mqtt/index.html b/components/cover.mqtt/index.html
index 0bbc56e2ab..39940d978e 100644
--- a/components/cover.mqtt/index.html
+++ b/components/cover.mqtt/index.html
@@ -274,6 +274,9 @@ state from state_topic. If these messages
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.myq/index.html b/components/cover.myq/index.html
index 9ee07fa959..b11fda7625 100644
--- a/components/cover.myq/index.html
+++ b/components/cover.myq/index.html
@@ -160,6 +160,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.mysensors/index.html b/components/cover.mysensors/index.html
index 7b33c314d5..ca793b7a4e 100644
--- a/components/cover.mysensors/index.html
+++ b/components/cover.mysensors/index.html
@@ -329,6 +329,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.opengarage/index.html b/components/cover.opengarage/index.html
index b4932c85d4..5827e1fae7 100644
--- a/components/cover.opengarage/index.html
+++ b/components/cover.opengarage/index.html
@@ -238,6 +238,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.rfxtrx/index.html b/components/cover.rfxtrx/index.html
index a5722246a5..393a00814a 100644
--- a/components/cover.rfxtrx/index.html
+++ b/components/cover.rfxtrx/index.html
@@ -206,6 +206,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.rpi_gpio/index.html b/components/cover.rpi_gpio/index.html
index 479e5aba8c..8d8921b0d1 100644
--- a/components/cover.rpi_gpio/index.html
+++ b/components/cover.rpi_gpio/index.html
@@ -205,6 +205,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.scsgate/index.html b/components/cover.scsgate/index.html
index fa93f7eb7f..2aa1d30fbd 100644
--- a/components/cover.scsgate/index.html
+++ b/components/cover.scsgate/index.html
@@ -185,6 +185,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.template/index.html b/components/cover.template/index.html
index 794dd296dd..28f46bca5d 100644
--- a/components/cover.template/index.html
+++ b/components/cover.template/index.html
@@ -221,6 +221,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.vera/index.html b/components/cover.vera/index.html
index 3d5ac18be1..912b7631af 100644
--- a/components/cover.vera/index.html
+++ b/components/cover.vera/index.html
@@ -176,6 +176,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.wink/index.html b/components/cover.wink/index.html
index 7ec96cafef..6f919ca591 100644
--- a/components/cover.wink/index.html
+++ b/components/cover.wink/index.html
@@ -199,6 +199,9 @@ The above devices are confimed to work, but others may work as well.
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.xiaomi/index.html b/components/cover.xiaomi/index.html
new file mode 100644
index 0000000000..c942fee445
--- /dev/null
+++ b/components/cover.xiaomi/index.html
@@ -0,0 +1,235 @@
+
+
+
+
+
+
+
+
+ Xiaomi Cover - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/cover.zwave/index.html b/components/cover.zwave/index.html
index 31ce01698f..4511459c44 100644
--- a/components/cover.zwave/index.html
+++ b/components/cover.zwave/index.html
@@ -178,6 +178,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover/index.html b/components/cover/index.html
index a9722b05b4..eb8f5586f5 100644
--- a/components/cover/index.html
+++ b/components/cover/index.html
@@ -228,6 +228,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/device_tracker.tplink/index.html b/components/device_tracker.tplink/index.html
index ee9b91c7d3..f1b118473c 100644
--- a/components/device_tracker.tplink/index.html
+++ b/components/device_tracker.tplink/index.html
@@ -121,6 +121,9 @@ TP-Link devices typically only allow one login at a time to the admin console.
Related components
+ -
+ TPLink Bulb
+
-
TPLink Switch
diff --git a/components/device_tracker.xiaomi/index.html b/components/device_tracker.xiaomi/index.html
index 2d4d933376..a0d6471437 100644
--- a/components/device_tracker.xiaomi/index.html
+++ b/components/device_tracker.xiaomi/index.html
@@ -105,6 +105,29 @@
This is a platform for
the Device Tracker component.
+
+
+ Related components
+
Category Presence Detection
diff --git a/components/digital_ocean/index.html b/components/digital_ocean/index.html
index 10dad9573e..db89e44e83 100644
--- a/components/digital_ocean/index.html
+++ b/components/digital_ocean/index.html
@@ -127,6 +127,9 @@
-
Android IP Webcam
+ -
+ Apple TV
+
-
Arlo
@@ -271,6 +274,9 @@
-
Twilio
+ -
+ Velbus
+
-
Velux
@@ -289,6 +295,9 @@
-
Wink
+ -
+ Xiaomi Gateway
+
-
Z-Wave
diff --git a/components/dyson/index.html b/components/dyson/index.html
index 5c9564ed19..88f0b230a9 100644
--- a/components/dyson/index.html
+++ b/components/dyson/index.html
@@ -93,7 +93,7 @@
- username (Required): Dyson account username (email address)
- password (Required): Dyson account password
- - language (Required): Dyson account language country code. Known working codes:
FR, NL, UK, AU. But others codes should work.
+ - language (Required): Dyson account language country code. Known working codes:
FR, NL, GB, AU. But others codes should work.
- devices (Optional): List of devices
- device_id (Required): Device ID. Available in the mobiles applications (Settings page)
@@ -156,6 +156,9 @@ To find devices IP address, you can use your router or
Twilio
+ -
+ Velbus
+
-
Velux
@@ -318,6 +324,9 @@ To find devices IP address, you can use your router or som
-
MQTT Fan
+ -
+ Velbus Fans
+
-
Wink Fan
diff --git a/components/fan.velbus/index.html b/components/fan.velbus/index.html
new file mode 100644
index 0000000000..ff7d0b19dd
--- /dev/null
+++ b/components/fan.velbus/index.html
@@ -0,0 +1,221 @@
+
+
+
+
+
+
+
+
+ Velbus Fans - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Velbus Fans
+
+
+
+ The velbus fan allows you to control Velbus connected fans.
+To use your Velbus fans in your installation, add the following to your configuration.yaml file:
+# Example configuration.yaml entry
+
+fan:
+ - platform: velbus
+ devices:
+ - name: Fan 1
+ module: 0xda
+ channel_low: 4
+ channel_medium: 3
+ channel_high: 2
+
+
+Configuration variables:
+
+ - devices array (Required): The array contains the fans to configure
+
+ - name (Required): Name of the fan.
+ - module (Required): The hexadecimal module address
+ - channel_low (Required): The channel number in the module for low-speed.
+ - channel_medium (Required): The channel number in the module for medium-speed.
+ - channel_high (Required): The channel number in the module for high-speed.
+
+
+
+For hub configuration, see the Velbus component.
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/fan.wink/index.html b/components/fan.wink/index.html
index 1f2a7b0cdc..e76e7ef53a 100644
--- a/components/fan.wink/index.html
+++ b/components/fan.wink/index.html
@@ -152,6 +152,9 @@ The above devices are confimed to work, but others may work as well.
-
MQTT Fan
+ -
+ Velbus Fans
+
-
Wink Fan
diff --git a/components/fan.zwave/index.html b/components/fan.zwave/index.html
index 70f8fec596..1d79725e0e 100644
--- a/components/fan.zwave/index.html
+++ b/components/fan.zwave/index.html
@@ -138,6 +138,9 @@
-
MQTT Fan
+ -
+ Velbus Fans
+
-
Wink Fan
diff --git a/components/fan/index.html b/components/fan/index.html
index 2556e7e48a..c4113071f6 100644
--- a/components/fan/index.html
+++ b/components/fan/index.html
@@ -103,6 +103,9 @@
-
MQTT Fan
+ -
+ Velbus Fans
+
-
Wink Fan
diff --git a/components/feedreader/index.html b/components/feedreader/index.html
index 7d65e75451..da29c6eb07 100644
--- a/components/feedreader/index.html
+++ b/components/feedreader/index.html
@@ -112,14 +112,14 @@
notification_id: "{{ trigger.event.data.title }}"
-*Any field under the <entry> tag in the feed can be used for example trigger.event.data.content will get the body of the feed entry.
-For more advanced use cases, a custom component registering to the feedreader event type could be used instead:
-For a drop in packaged complete example of Feedreader, you can use the PodCast notifier.
+Any field under the <entry> tag in the feed can be used for example trigger.event.data.content will get the body of the feed entry.
+For more advanced use cases, a custom component registering to the feedreader event type could be used instead:
EVENT_FEEDREADER = "feedreader"
hass.bus.listen(EVENT_FEEDREADER, event_listener)
To get started developing custom components, please refer to the developers documentation
+For a drop in packaged complete example of Feedreader, you can use the PodCast notifier.
+
+
+
+
+
+
+
+
+
+
@@ -426,121 +483,6 @@ If you have a security key set in your Open Z-Wave
-
- + ZWave Entity IDs +
+ +
+
+ ZWave entity_ids have long been a source of frustration in Home Assistant. The first problem we faced was that depending on the order of node discovery, entity_ids could be discovered with different names on each run. To solve this we added the node id as a suffix to the entity_id. This ensured that entity_ids were generated deterministically on each run, but additional suffixes had to be added to handle edge cases where there would otherwise be a conflict. The resulting entity_ids worked, but have been difficult to work with and makes ZWave a strange exception among other Home Assistant components.
+Thanks to the awesome work of @turbokongen, a growing number of ZWave configuration options are now available from the new ZWave panel in the Home Assistant frontend. Among these new features is support for renaming of ZWave nodes and their underlying values. (These renames are persisted in zwcfg_*.xml) This is important, because these items are combined to form the Home Assistant entity name, which is used to generate the entity_id. Now that these options are available, ZWave users can rename nodes and values, influencing the entity_ids that are generated by Home Assistant.
+Now that users are able to control these names, we will be making changes to how the entity_ids are generated for ZWave entities. The ZWave entity_ids are going to switch back to using the standard entity_id generation from Home Assistant core, based on the entity names. Moving forward, if there is a conflict when generating entity_ids, a suffix will be added, and it will be the responsibility of the user to rename their nodes and values to avoid the conflict. This is the same as any other platform in Home Assistant where two devices are discovered with the same name.
+With the release of 0.47, this feature will be opt-in. Setting new_entity_ids: true under zwave: in your configuration.yaml will enable the new generation. After 0.48 this feature will become opt-out. From 0.48 onward, unless you’ve declared new_entity_ids: false you will switch to the new entity_id generation. At an undecided point in the future, the old entity_id generation will be removed completely.
I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that breaking changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms.
++
+ Linux Action Show special about Home Assistant +
+ +
+
+ Our founder Paulus Schoutsen is interviewed by Chris Fisher for a Linux Action Show special about home automation, Hass.io and the new Home Assistant podcast.
+
+
+
+
@@ -426,121 +483,6 @@ If you have a security key set in your Open Z-Wave Podcast.__init__ about Python and Home Assistant. Just realized that we never shared this on the blog, oops. Here it is, enjoy!
-
-
- Home Assistant on a Pi Zero W in 30 minutes -
- -
-
-
-
-
-
-
Saw the announcement yesterday for HASSbian 1.21 and got super excited?
-Today we’ll flash the latest HASSbian to a Raspbery Pi Zero W. -With an added bonus that besides for an USB cable for power, there’s no need for any cables!
-What you’ll need:
--
-
- a Raspberry Pi Zero W (an amazing tiny computer with built-in wifi) -
- a microSD card -
- some source of USB power -
- Wifi -
- a desktop or laptop -
Let’s get to it!
-First, download the HASSbian 1.21 image from here.
-Unzip it.
-Flash it to the microSD card. If you need a flash tool, try Etcher
-When the flashing finishes, remove it and plug it back in. You should see a drive called “boot”.
-Right in there, not in any folders, create a file called wpa_supplicant.conf.
The contents of the configuration file should be something like this: -(You may have to adjust for your configuration, hints here )
-network={
- ssid="YOUR_WIFI_NETWORK_NAME_HERE"
- psk="YOUR_WIFI_PASSWORD_HERE"
- key_mgmt=WPA-PSK
-}
-Next stick your SD card into the Raspberry Pi Zero W, and plug it in.
-After about a minute, use your SSH client to connect to HASSbian (or hassbian.local from a Mac), with the username pi. The default password is raspberry.
It’s a good idea to change the password. To do so, use the passwd command.
Next, type the following two commands into the SSH console:
-$ sudo systemctl enable install_homeassistant.service
-$ sudo systemctl start install_homeassistant.service
-Wait about 15-20 minutes and voilà you have your Home Assistant on your Raspberry Pi Zero W in 30 minutes.
-To try it out, go to http://hassbian:8123 or http://hassbian.local:8123 if you’re using Mac.
-For further details about HASSbian, take a look at the documentation.
--
- HASSbian 1.21 - It's about time isn't it -
- -
-
Hassbian 1.21 - It’s about time isn’t it
-Since I, the developer of HASSbian, have been moving, started a new job and so on I’ve had few moments over for HASSbian development. The 1.2 release has been in pre-release for a few months now and just not communicated out that well. Hopefully this release changes that and I’ll do my best to release more often. There’s no simple way to update from 1.1 to 1.21 but 95% of the changes can be done by installing the hassbian-config package. For more information have a look at the hassbian-config page.
-Hassbian 1.22 - Sins of last night
-Development is sometimes fast and joyful but mistakes are made at times.
-With the release of 1.21 a small problem with the OpenZWave build script wasn’t corrected even tough it was a known bug. Problem is simple as it’s only a problem with the symlink created for to the configuration folder for OpenZWave. This has been fixed and we bring some new things since they where ready anyway. The list below has been augmented with the updated information.
-Hassbian-config
-To allow you to customize your installation further, we have included a tool called hassbian-config. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the hassbian-scripts functionality from 1.1.
-
-
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai. -
- Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support. -
- Install Libcec. Adds local HDMI CEC support. -
- Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed. -
- Install Open Z-Wave. Installs Python Open Z-Wave and OZWCP from git. -
- Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and it’s usage is not recommended if you share your network with others. -
- Install Tellstick. Installs the Tellstick package for controlling and using a connected Tellstick. -
- Install Tradfri. Installs dependencies for using IKEA Trådfri. -
Spring cleaning
-With this image there also quite a bit of cleaning of the base system and the script that generates our Raspberry Pi image.
--
-
- Replaced the
hassbian-scriptsfolder withhassbian-config.
- - Update
pi-gen. Our build script has been upgraded to follow the Raspbian image closer once again. Now you could build this image with Docker if your so inclined.
- - Added libtool and autoconf package. Dependencies for some of the pip packages. -
- Pi ZeroW should now work with the image. -
To follow discussions about the development of the HASSbian image or to contribute join our Discord chat server.
-To get started with the new image, check out the installation instructions in the getting started section.
diff --git a/blog/posts/3/index.html b/blog/posts/3/index.html index 86e8afb4c6..05fdacfb5e 100644 --- a/blog/posts/3/index.html +++ b/blog/posts/3/index.html @@ -67,6 +67,121 @@
+
+
+
+
+
+
+
+
+
+
+ Home Assistant on a Pi Zero W in 30 minutes +
+ +
+
+
+
+
+
+
Saw the announcement yesterday for HASSbian 1.21 and got super excited?
+Today we’ll flash the latest HASSbian to a Raspbery Pi Zero W. +With an added bonus that besides for an USB cable for power, there’s no need for any cables!
+What you’ll need:
+-
+
- a Raspberry Pi Zero W (an amazing tiny computer with built-in wifi) +
- a microSD card +
- some source of USB power +
- Wifi +
- a desktop or laptop +
Let’s get to it!
+First, download the HASSbian 1.21 image from here.
+Unzip it.
+Flash it to the microSD card. If you need a flash tool, try Etcher
+When the flashing finishes, remove it and plug it back in. You should see a drive called “boot”.
+Right in there, not in any folders, create a file called wpa_supplicant.conf.
The contents of the configuration file should be something like this: +(You may have to adjust for your configuration, hints here )
+network={
+ ssid="YOUR_WIFI_NETWORK_NAME_HERE"
+ psk="YOUR_WIFI_PASSWORD_HERE"
+ key_mgmt=WPA-PSK
+}
+Next stick your SD card into the Raspberry Pi Zero W, and plug it in.
+After about a minute, use your SSH client to connect to HASSbian (or hassbian.local from a Mac), with the username pi. The default password is raspberry.
It’s a good idea to change the password. To do so, use the passwd command.
Next, type the following two commands into the SSH console:
+$ sudo systemctl enable install_homeassistant.service
+$ sudo systemctl start install_homeassistant.service
+Wait about 15-20 minutes and voilà you have your Home Assistant on your Raspberry Pi Zero W in 30 minutes.
+To try it out, go to http://hassbian:8123 or http://hassbian.local:8123 if you’re using Mac.
+For further details about HASSbian, take a look at the documentation.
++
+ HASSbian 1.21 - It's about time isn't it +
+ +
+
+ Hassbian 1.21 - It’s about time isn’t it
+Since I, the developer of HASSbian, have been moving, started a new job and so on I’ve had few moments over for HASSbian development. The 1.2 release has been in pre-release for a few months now and just not communicated out that well. Hopefully this release changes that and I’ll do my best to release more often. There’s no simple way to update from 1.1 to 1.21 but 95% of the changes can be done by installing the hassbian-config package. For more information have a look at the hassbian-config page.
+Hassbian 1.22 - Sins of last night
+Development is sometimes fast and joyful but mistakes are made at times.
+With the release of 1.21 a small problem with the OpenZWave build script wasn’t corrected even tough it was a known bug. Problem is simple as it’s only a problem with the symlink created for to the configuration folder for OpenZWave. This has been fixed and we bring some new things since they where ready anyway. The list below has been augmented with the updated information.
+Hassbian-config
+To allow you to customize your installation further, we have included a tool called hassbian-config. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the hassbian-scripts functionality from 1.1.
-
+
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai. +
- Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support. +
- Install Libcec. Adds local HDMI CEC support. +
- Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed. +
- Install Open Z-Wave. Installs Python Open Z-Wave and OZWCP from git. +
- Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and it’s usage is not recommended if you share your network with others. +
- Install Tellstick. Installs the Tellstick package for controlling and using a connected Tellstick. +
- Install Tradfri. Installs dependencies for using IKEA Trådfri. +
Spring cleaning
+With this image there also quite a bit of cleaning of the base system and the script that generates our Raspberry Pi image.
+-
+
- Replaced the
hassbian-scriptsfolder withhassbian-config.
+ - Update
pi-gen. Our build script has been upgraded to follow the Raspbian image closer once again. Now you could build this image with Docker if your so inclined.
+ - Added libtool and autoconf package. Dependencies for some of the pip packages. +
- Pi ZeroW should now work with the image. +
To follow discussions about the development of the HASSbian image or to contribute join our Discord chat server.
+To get started with the new image, check out the installation instructions in the getting started section.
+@@ -406,87 +521,6 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
-
- Home Assistant 0.41: Tado, Volumio, Workday, improved Plex -
- -
-
- Welcome to 0.41. There was a lot going on in the last two weeks. Not only from the code side but also from the social one of Home Assistant. Paulus did an interview with OpenSourceCraft, Fabian did a workshop at the Chemnitzer Linux Tage, and we are now an award-winning Open source project (I will cover that in a separate blog post).
-Plex
-@JesseWebDotCom made massive changes to the Plex media player platform. From better metadata support over new configuration options to improved controls and non-controllable clients.
-Component overview
-The Components overview is now powered by search/filtering feature. This will make it faster to get the component/platform you are looking for more quickly. Thanks again, @bdurrer for this.
-Changelog
-The new format of the changelog which was introduced with 0.40 will provide a link to the related pull request. We are not covering everything in our release notes but we think that this addition will make it easier to find details about the change.
-New platforms/components
--
-
- Support for Tado climate devices (@wmalgadey) -
- Volumio media player added (@jslove) -
- Workday sensor (@BastianPoe) -
Breaking changes
--
-
- The Kodi notifier platform was migrated to async and the configuration synced with the Kodi media player platform (#6497). -
- For the Music Player Daemon (MPD) platform was
locationreplaced withname(#6553).
- - Event decorators were removed (#6634). -
- The Emby mediaplayer platform was changed to avoid name clashes (#6664). -
- In a lot of places were the power and energy units update. This change mostly affects the
switchplatforms (#6212).
- - If set to
autothen the MQTT implementation will use the bundled certificates automatically (#6707).
- - Autodiscovery of Android IP Webcam was removed (#6528). -
- The frontend is now using Shadow DOM and this could break your custom panels (#228). -
If you need help…
-…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
-Reporting Issues
-Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
- Read on → --
- OpenSourceCraft interviews our founder Paulus Schoutsen -
- -
-
- Last month Gregg Pollack from OpenSourceCraft visited me in San Diego to talk about Home Assistant. We talked about the community and how all these awesome people make Home Assistant possible. The main interview is embedded below but make sure to check out the full article including extra video material.
-
-
-
-
← Older
Newer →
diff --git a/blog/posts/4/index.html b/blog/posts/4/index.html
index fc1467d92c..6449440d71 100644
--- a/blog/posts/4/index.html
+++ b/blog/posts/4/index.html
@@ -67,6 +67,87 @@
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+ Home Assistant 0.41: Tado, Volumio, Workday, improved Plex +
+ +
+
+ Welcome to 0.41. There was a lot going on in the last two weeks. Not only from the code side but also from the social one of Home Assistant. Paulus did an interview with OpenSourceCraft, Fabian did a workshop at the Chemnitzer Linux Tage, and we are now an award-winning Open source project (I will cover that in a separate blog post).
+Plex
+@JesseWebDotCom made massive changes to the Plex media player platform. From better metadata support over new configuration options to improved controls and non-controllable clients.
+Component overview
+The Components overview is now powered by search/filtering feature. This will make it faster to get the component/platform you are looking for more quickly. Thanks again, @bdurrer for this.
+Changelog
+The new format of the changelog which was introduced with 0.40 will provide a link to the related pull request. We are not covering everything in our release notes but we think that this addition will make it easier to find details about the change.
+New platforms/components
+-
+
- Support for Tado climate devices (@wmalgadey) +
- Volumio media player added (@jslove) +
- Workday sensor (@BastianPoe) +
Breaking changes
+-
+
- The Kodi notifier platform was migrated to async and the configuration synced with the Kodi media player platform (#6497). +
- For the Music Player Daemon (MPD) platform was
locationreplaced withname(#6553).
+ - Event decorators were removed (#6634). +
- The Emby mediaplayer platform was changed to avoid name clashes (#6664). +
- In a lot of places were the power and energy units update. This change mostly affects the
switchplatforms (#6212).
+ - If set to
autothen the MQTT implementation will use the bundled certificates automatically (#6707).
+ - Autodiscovery of Android IP Webcam was removed (#6528). +
- The frontend is now using Shadow DOM and this could break your custom panels (#228). +
If you need help…
+…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+Reporting Issues
+Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
+ Read on → ++
+ OpenSourceCraft interviews our founder Paulus Schoutsen +
+ +
+
+ Last month Gregg Pollack from OpenSourceCraft visited me in San Diego to talk about Home Assistant. We talked about the community and how all these awesome people make Home Assistant possible. The main interview is embedded below but make sure to check out the full article including extra video material.
+
+
+
+ @@ -604,195 +685,6 @@ On the close horizon from @Landrash th
-
- 0.37: Face detection, Coffee, Wink -
- -
-
- No stats, no numbers, and alike this time. Ok, just one number: 0.37. We are back on track with our bi-weekly release cycle. Beside some organizational changes is this release shipping again cool features and new integrations. Please keep an eye on the “Breaking changes” section because there are also massive improvements for some platforms and components.
-Governance
-As announced, the new Governance requires for developers to sign the CLA. Code of Conduct, Contributor License Agreement, and proper Licensing will to protect all involved parties in the Home Assistant eco-system from users and community members to contributors.
-Face recognition using the Microsoft Face API
-@pvizeli has been on a roll with the image processing integrations. This time it’s the Microsoft Face API. This means that now it will be possible to train the API with the people you want to recognize and send images from your camera to the API as another source of automation.
-Want to play a personalized tune when someone enters the house? It is now possible 😎
-Improved camera security
-After a security audit by Stephen O’Conner, he found that our source for randomly generated access tokens for camera feeds were reasonable predictable and could be brute force attacked in 2.5 weeks. A fix has been included in this release that uses the system provided random number generator for maximum randomness and rotates the keys every 10 minutes to reduce the window in which a brute force attack can happen.
-Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.
-New customization options
-@Andrey-git has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.
-Major Wink and HDMI CEC improvements
-@w1ll1am23 did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your configuration.yaml file, no client_id and client_secret are needed, and token which was generated with the generator located in the Wink documentation.
The new Wink support will cause renaming of all the binary sensors and will also create new sensors for devices that weren’t previously detected or supported in the older version.
-Thanks to @konikvranik the HDMI CEC integration got a huge update with a lot of improvements. This update should make it easier to work with HDMI CEC and give you more control.
-First Coffee Maker supported
-@stu-gott has added support for the first coffee maker in Home Assistant: Mr. Coffee Smart Optimal Brew. Happy brewing!
-All changes
-New platforms/components
--
-
- Netatmo: Netatmo Presence support (@gieljnssns) -
- Sensor: Amcrest camera sensors (@tchellomello) -
- Notify: New Discord notification component (@Deinara) -
- Device tracker: Tado device tracker support (@jmvermeulen) -
- Sensor: Add Skybeacon BLE temperature/humidity sensor (@anpetrov) -
- New Zabbix component (@Whytey) -
- Media player: New platform Anthemav Media player (@nugget) -
- Light: Add support for Avion Bluetooth dimmer switches (@mjg59) -
- Binary sensor: Beaglebone Black binary sensor (@MatoKafkac) -
- Light: Piglow support (@xarnze) -
- Face recognition for automation (@pvizeli) -
- Sensor: New Washington State DOT sensor (@partofthething) -
- Support for Wemo CoffeeMaker devices (@stu-gott) -
- Device tracker: Sky hub support (@alexmogavero) -
- Support for Lutron RadioRA 2 (@thecynic) -
- TTS: Amazon Polly TTS platform (@robbiet480) -
- Device tracker: Support for Linksys Access Points (@lukas-hetzenecker) -
- Notify: Make calls with Twilio (@fakezeta) -
Improvements
--
-
- Script: Fix script release (@balloob) -
- Camera - Amcrest: Add support for direct MJPEG streams from Amcrest cameras (@colinodell) -
- Sensor - Miflora: Removing throttle decorator (@freol35241) -
- Notify - Lannouncer: Fix
get_servicemethod (@mKeRix)
- - Sensor - WAQI: Add station parameter to waqi sensor (@whhsw) -
- Sensor - USPS: Absolute path to save cookie used by USPS sensor (@tchellomello) -
- Nest: Fix python-nest release number (@Danielhiversen) -
- Keyboard remote: Improve support (@MrMep) -
- Device tracker - VolvoOnCall: Fix timedelta (@pvizeli) -
- Climate - eq3btsmart: Expose away attribute (@rytilahti) -
- Remote: Reserve a test port for broken API to fix race (@armills) -
- Climate - Ecobee: Made target temperature sensitive to auto mode (@Duoxilian) -
- Configuration: Fix load_yaml default value (@balloob) -
- Notify - Facebook: Fix encoding error (@Danielhiversen) -
- Emulated_hue: Add
upnp_bind_multicastoption, default type to Google, and persist emulated hue IDs (@hoopty, @balloob)
- - Docker: Install phantomjs in Docker container (@jnewland) -
- Media player - MPD: Add listing and selection of available MPD playlists (@partofthething) -
- Media player - Denon AVR: Denon improvements (@glance-) -
- Light - x10.py: Improved x10 state monitoring (@martst) -
- Sensor - DSMR: TCP, reconnecting and V4 CRC support (@aequitas) -
- Media player - Yamaha.py: Fix Yamaha doing I/O in event loop (@balloob) -
- Device tracker UPC: Make upc more robust (@pvizeli) -
- Climate - Generic thermostat: Update (@MrMep) -
- Device tracker - Xiaomi.py: Xiaomi Mi Router token refresh (@RiRomain) -
- Camera - MJPEG: Support still image for thumbmail (@pvizeli) -
- Sensor - ZAMG: Updated valid station id list (@HerrHofrat) -
- Light - ISY994: Not overwrite
state_attributes(@rmkraus)emul-hue
- - Light - Zwave: Use only supported features for devices (@turbokongen) -
- Media player - Kodi: Support for volume stepping (@armills) -
- Media player- roku: Use
is_screensaver, update IDLE state, and use device name (@robbiet480, @xhostplus)
- - Switch - HDMI CEC: Support for devices and commands (@konikvranik) -
- Lock - Zwave: Improvements to Zwave lock platform (@turbokongen) -
- TTS: Invalidate broken file cache entries (@stu-gott) -
- Light - Hue: Improvements (@robbiet480) -
- TTS - YandexTTS: Added speed and emotion to Yandex TTS (@lupin-de-mid) -
- Light - tellstick.py: Tellstick light fix (@stefan-jonasson) -
- Switch - insteon_local.py: only check for devices when not defined in config (@wardcraigj) -
- Notify - Twitter: Allow direct messaging to user (@fabaff) -
- Fan - MQTT: Dont set a speed when fan turns on (@robbiet480) -
- Config: Allow easier customization of whole domain, entity lists, globs (@andrey-git) -
- Sensor - Homematic: Update device support (@danielperna84) -
- Binary sensor - ISS: Add location to attributes and option to show position on the map (@fabaff) -
- Media player - Kodi: Add SSL configuration option (@ecksun) -
- Sensor - WAQI: Add missing particle value (@fabaff) -
- Wink: Support for python-wink 1.0.0 (@w1ll1am23) -
- Binary sensor - RPi GPIO: Add a small sleep before reading the sensor (@snagytx) -
- Sensor - USPS: Add name to configuration (@happyleavesaoc) -
- Sensor - Miflora: Remove throttle decorator from miflora platform (@freol35241) -
- Device tracker - asuswrt.py: Add IPv6 support when parsing neighbors (@leppa) -
- iOS: Discover notify.ios when iOS component loads (@robbiet480) -
- Homematic: Add MAX shutter contact class (@jannau) -
- Sensor - Darksky: Added forecast support (@nordlead2005) -
- Switch - Pilight: Implement echo config option (@janLo) -
- Core: Support customize in packages (@kellerza) -
- Switch - Flux: Allow disabling setting the brightness (@rytilahti) -
- Media player - Sonos: Add
is_coordinator, set coordinator after join/unjoin, and no emtpy image (@pvizeli, @andrey-git, @robbiet480)
- - Climate: Hold mode (@Duoxilian) -
- Switch - TPlink: No longer doing I/O in event bus (@balloob) -
- Light - Insteon local: Improve Insteon configuration (@wardcraigj) -
- Emulated Hue: Emulated Hue “host-ip” fails to bind when running in docker without
--net=host(@jeremydk)
- - Climate - EQ3 BT smart: Add reporting for availability (@rytilahti) -
Bugfix: @balloob, @fabaff, @freol35241, @pvizeli, @Danielhiversen, @tdickman, @armills, @rytilahti, @R1chardTM, @asbach, @happyleavesaoc, @robbiet480, @colinodell, @joopert, @dale3h, @pavoni, @jaharkes, @MartinHjelmare, @mezz64, @jabesq, and you if you are missing in this list.
-Release 0.37.1 - February 2
--
-
- Do not reject alphanumeric IDs for PiLight (@DavidLP) -
- Fix broken Hue discovery (@DanielHiversen) -
- Fix Amcrest (@tchellomello) -
- Fix Telldus Live dim level error on startup (@molobrakos) -
- Fix Sonos group coordinators (@pvizeli) -
- UPC Connect: Parse XML outside event loop (@pvizeli) -
- Fix Netatmo SSL issue with VPN URL (@jabesq) -
- Homematic: Fix bug with UNREACH device state/restore and variables not updating (@pvizeli) -
- Sonos: Prevent duplicate entries in favorite list (@pvizeli) -
- Fix Schlage Connect deadbolt integration via Z-Wave (@turbokongen) -
- Prevent infinite loop in crossconfigured mqtt event streams (@aequitas) -
- Fix Hue lightgroups failing on startup (@tboyce1) -
Breaking changes
--
-
- A major breaking change in the
emulated_huecomponent means that unless you settype: alexabefore starting up the newer Home Assistant version you will lose all devices that Alexa has discovered and will need to re-add them as well as create new groups.
- - The platform of the ISS integration was change to
binary_sensor. Please check the platform documentation.
- - The Roku media uses now a new format for the entity IDs. -
- OpenALPR is no longer a component. It’s now a platform for Image processing. -
- Due to massive improvements of the Wink integration, the names of your binary sensors will change and new devices can show up. -
- The MySensors component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you. -
- The Sonos service
sonos_group_playerswas removed. Use nowsonos_joinfor this function.
- - TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g.
HASH_LANG_PLATFORM.xxx->HASH_LANG_OPTIONS_PLATFORM.xxx, replace OPTIONS with-on exiting platforms.
-
If you need help…
-…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
-Reporting Issues
-Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
--
- Home Assistant Governance [updated] -
- -
-
-
- UPDATE JAN 28, 2017
-After feedback from the community we have updated the CLA and the license that Home Assistant is distributed under. For the CLA, instead of enforcing requirements on the grants and code, we now require contributions to be licensed under the Apache 2.0 license. Special thanks to Matthew Garrett for his feedback and advice.
-Starting with release 0.37, Home Assistant will re-license the current code under the Apache 2.0 license. This is the license that will be used moving forward for all projects under our organization.
--
The Home Assistant project and community has seen enormous growth in the last three years. Many volunteers work tirelessly everyday to give you all the awesomeness that you see today. Much more work is involved than many people realize. Beyond simply coding Home Assistant, volunteers continually maintain related projects, update documentation, post examples, author blog posts, and moderate the forums and chat. This is something that we want to keep safe and functional, even as we grow.
-Starting today we are announcing a few initiatives to help protect our users, contributors and community members.
- Read on → -
← Older
Newer →
diff --git a/blog/posts/5/index.html b/blog/posts/5/index.html
index 74d9d24b67..59c1361425 100644
--- a/blog/posts/5/index.html
+++ b/blog/posts/5/index.html
@@ -67,6 +67,195 @@
-
-
-
-
-
-
-
-
-
diff --git a/blog/posts/6/index.html b/blog/posts/6/index.html index b183c12c4e..f626382771 100644 --- a/blog/posts/6/index.html +++ b/blog/posts/6/index.html @@ -67,6 +67,328 @@
-
-
-
-
-
-
-
-
-
diff --git a/blog/posts/7/index.html b/blog/posts/7/index.html index 37e7e0bed9..4bec62fd79 100644 --- a/blog/posts/7/index.html +++ b/blog/posts/7/index.html @@ -67,6 +67,112 @@
+
+
+
+
+
+
+
+
+
+
@@ -715,328 +904,6 @@ You have to note:
-
- + 0.37: Face detection, Coffee, Wink +
+ +
+
+ No stats, no numbers, and alike this time. Ok, just one number: 0.37. We are back on track with our bi-weekly release cycle. Beside some organizational changes is this release shipping again cool features and new integrations. Please keep an eye on the “Breaking changes” section because there are also massive improvements for some platforms and components.
+Governance
+As announced, the new Governance requires for developers to sign the CLA. Code of Conduct, Contributor License Agreement, and proper Licensing will to protect all involved parties in the Home Assistant eco-system from users and community members to contributors.
+Face recognition using the Microsoft Face API
+@pvizeli has been on a roll with the image processing integrations. This time it’s the Microsoft Face API. This means that now it will be possible to train the API with the people you want to recognize and send images from your camera to the API as another source of automation.
+Want to play a personalized tune when someone enters the house? It is now possible 😎
+Improved camera security
+After a security audit by Stephen O’Conner, he found that our source for randomly generated access tokens for camera feeds were reasonable predictable and could be brute force attacked in 2.5 weeks. A fix has been included in this release that uses the system provided random number generator for maximum randomness and rotates the keys every 10 minutes to reduce the window in which a brute force attack can happen.
+Although the old method is not insecure, the new method is a lot more secure. Upgrading to the latest version is encouraged.
+New customization options
+@Andrey-git has added some great new options to the customize functionality. It is now possible to specify customizations as a wildcard for entities or for a specific domain.
+Major Wink and HDMI CEC improvements
+@w1ll1am23 did an amazing job fixing a ton of bugs and issues with the Wink integration. Biggest improvement is that it now is able to automatically refresh the authentication tokens. This means that if you have your email address and password in your configuration.yaml file, no client_id and client_secret are needed, and token which was generated with the generator located in the Wink documentation.
The new Wink support will cause renaming of all the binary sensors and will also create new sensors for devices that weren’t previously detected or supported in the older version.
+Thanks to @konikvranik the HDMI CEC integration got a huge update with a lot of improvements. This update should make it easier to work with HDMI CEC and give you more control.
+First Coffee Maker supported
+@stu-gott has added support for the first coffee maker in Home Assistant: Mr. Coffee Smart Optimal Brew. Happy brewing!
+All changes
+New platforms/components
+-
+
- Netatmo: Netatmo Presence support (@gieljnssns) +
- Sensor: Amcrest camera sensors (@tchellomello) +
- Notify: New Discord notification component (@Deinara) +
- Device tracker: Tado device tracker support (@jmvermeulen) +
- Sensor: Add Skybeacon BLE temperature/humidity sensor (@anpetrov) +
- New Zabbix component (@Whytey) +
- Media player: New platform Anthemav Media player (@nugget) +
- Light: Add support for Avion Bluetooth dimmer switches (@mjg59) +
- Binary sensor: Beaglebone Black binary sensor (@MatoKafkac) +
- Light: Piglow support (@xarnze) +
- Face recognition for automation (@pvizeli) +
- Sensor: New Washington State DOT sensor (@partofthething) +
- Support for Wemo CoffeeMaker devices (@stu-gott) +
- Device tracker: Sky hub support (@alexmogavero) +
- Support for Lutron RadioRA 2 (@thecynic) +
- TTS: Amazon Polly TTS platform (@robbiet480) +
- Device tracker: Support for Linksys Access Points (@lukas-hetzenecker) +
- Notify: Make calls with Twilio (@fakezeta) +
Improvements
+-
+
- Script: Fix script release (@balloob) +
- Camera - Amcrest: Add support for direct MJPEG streams from Amcrest cameras (@colinodell) +
- Sensor - Miflora: Removing throttle decorator (@freol35241) +
- Notify - Lannouncer: Fix
get_servicemethod (@mKeRix)
+ - Sensor - WAQI: Add station parameter to waqi sensor (@whhsw) +
- Sensor - USPS: Absolute path to save cookie used by USPS sensor (@tchellomello) +
- Nest: Fix python-nest release number (@Danielhiversen) +
- Keyboard remote: Improve support (@MrMep) +
- Device tracker - VolvoOnCall: Fix timedelta (@pvizeli) +
- Climate - eq3btsmart: Expose away attribute (@rytilahti) +
- Remote: Reserve a test port for broken API to fix race (@armills) +
- Climate - Ecobee: Made target temperature sensitive to auto mode (@Duoxilian) +
- Configuration: Fix load_yaml default value (@balloob) +
- Notify - Facebook: Fix encoding error (@Danielhiversen) +
- Emulated_hue: Add
upnp_bind_multicastoption, default type to Google, and persist emulated hue IDs (@hoopty, @balloob)
+ - Docker: Install phantomjs in Docker container (@jnewland) +
- Media player - MPD: Add listing and selection of available MPD playlists (@partofthething) +
- Media player - Denon AVR: Denon improvements (@glance-) +
- Light - x10.py: Improved x10 state monitoring (@martst) +
- Sensor - DSMR: TCP, reconnecting and V4 CRC support (@aequitas) +
- Media player - Yamaha.py: Fix Yamaha doing I/O in event loop (@balloob) +
- Device tracker UPC: Make upc more robust (@pvizeli) +
- Climate - Generic thermostat: Update (@MrMep) +
- Device tracker - Xiaomi.py: Xiaomi Mi Router token refresh (@RiRomain) +
- Camera - MJPEG: Support still image for thumbmail (@pvizeli) +
- Sensor - ZAMG: Updated valid station id list (@HerrHofrat) +
- Light - ISY994: Not overwrite
state_attributes(@rmkraus)emul-hue
+ - Light - Zwave: Use only supported features for devices (@turbokongen) +
- Media player - Kodi: Support for volume stepping (@armills) +
- Media player- roku: Use
is_screensaver, update IDLE state, and use device name (@robbiet480, @xhostplus)
+ - Switch - HDMI CEC: Support for devices and commands (@konikvranik) +
- Lock - Zwave: Improvements to Zwave lock platform (@turbokongen) +
- TTS: Invalidate broken file cache entries (@stu-gott) +
- Light - Hue: Improvements (@robbiet480) +
- TTS - YandexTTS: Added speed and emotion to Yandex TTS (@lupin-de-mid) +
- Light - tellstick.py: Tellstick light fix (@stefan-jonasson) +
- Switch - insteon_local.py: only check for devices when not defined in config (@wardcraigj) +
- Notify - Twitter: Allow direct messaging to user (@fabaff) +
- Fan - MQTT: Dont set a speed when fan turns on (@robbiet480) +
- Config: Allow easier customization of whole domain, entity lists, globs (@andrey-git) +
- Sensor - Homematic: Update device support (@danielperna84) +
- Binary sensor - ISS: Add location to attributes and option to show position on the map (@fabaff) +
- Media player - Kodi: Add SSL configuration option (@ecksun) +
- Sensor - WAQI: Add missing particle value (@fabaff) +
- Wink: Support for python-wink 1.0.0 (@w1ll1am23) +
- Binary sensor - RPi GPIO: Add a small sleep before reading the sensor (@snagytx) +
- Sensor - USPS: Add name to configuration (@happyleavesaoc) +
- Sensor - Miflora: Remove throttle decorator from miflora platform (@freol35241) +
- Device tracker - asuswrt.py: Add IPv6 support when parsing neighbors (@leppa) +
- iOS: Discover notify.ios when iOS component loads (@robbiet480) +
- Homematic: Add MAX shutter contact class (@jannau) +
- Sensor - Darksky: Added forecast support (@nordlead2005) +
- Switch - Pilight: Implement echo config option (@janLo) +
- Core: Support customize in packages (@kellerza) +
- Switch - Flux: Allow disabling setting the brightness (@rytilahti) +
- Media player - Sonos: Add
is_coordinator, set coordinator after join/unjoin, and no emtpy image (@pvizeli, @andrey-git, @robbiet480)
+ - Climate: Hold mode (@Duoxilian) +
- Switch - TPlink: No longer doing I/O in event bus (@balloob) +
- Light - Insteon local: Improve Insteon configuration (@wardcraigj) +
- Emulated Hue: Emulated Hue “host-ip” fails to bind when running in docker without
--net=host(@jeremydk)
+ - Climate - EQ3 BT smart: Add reporting for availability (@rytilahti) +
Bugfix: @balloob, @fabaff, @freol35241, @pvizeli, @Danielhiversen, @tdickman, @armills, @rytilahti, @R1chardTM, @asbach, @happyleavesaoc, @robbiet480, @colinodell, @joopert, @dale3h, @pavoni, @jaharkes, @MartinHjelmare, @mezz64, @jabesq, and you if you are missing in this list.
+Release 0.37.1 - February 2
+-
+
- Do not reject alphanumeric IDs for PiLight (@DavidLP) +
- Fix broken Hue discovery (@DanielHiversen) +
- Fix Amcrest (@tchellomello) +
- Fix Telldus Live dim level error on startup (@molobrakos) +
- Fix Sonos group coordinators (@pvizeli) +
- UPC Connect: Parse XML outside event loop (@pvizeli) +
- Fix Netatmo SSL issue with VPN URL (@jabesq) +
- Homematic: Fix bug with UNREACH device state/restore and variables not updating (@pvizeli) +
- Sonos: Prevent duplicate entries in favorite list (@pvizeli) +
- Fix Schlage Connect deadbolt integration via Z-Wave (@turbokongen) +
- Prevent infinite loop in crossconfigured mqtt event streams (@aequitas) +
- Fix Hue lightgroups failing on startup (@tboyce1) +
Breaking changes
+-
+
- A major breaking change in the
emulated_huecomponent means that unless you settype: alexabefore starting up the newer Home Assistant version you will lose all devices that Alexa has discovered and will need to re-add them as well as create new groups.
+ - The platform of the ISS integration was change to
binary_sensor. Please check the platform documentation.
+ - The Roku media uses now a new format for the entity IDs. +
- OpenALPR is no longer a component. It’s now a platform for Image processing. +
- Due to massive improvements of the Wink integration, the names of your binary sensors will change and new devices can show up. +
- The MySensors component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you. +
- The Sonos service
sonos_group_playerswas removed. Use nowsonos_joinfor this function.
+ - TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g.
HASH_LANG_PLATFORM.xxx->HASH_LANG_OPTIONS_PLATFORM.xxx, replace OPTIONS with-on exiting platforms.
+
If you need help…
+…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+Reporting Issues
+Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
++
+ Home Assistant Governance [updated] +
+ +
+
+
+ UPDATE JAN 28, 2017
+After feedback from the community we have updated the CLA and the license that Home Assistant is distributed under. For the CLA, instead of enforcing requirements on the grants and code, we now require contributions to be licensed under the Apache 2.0 license. Special thanks to Matthew Garrett for his feedback and advice.
+Starting with release 0.37, Home Assistant will re-license the current code under the Apache 2.0 license. This is the license that will be used moving forward for all projects under our organization.
++
The Home Assistant project and community has seen enormous growth in the last three years. Many volunteers work tirelessly everyday to give you all the awesomeness that you see today. Much more work is involved than many people realize. Beyond simply coding Home Assistant, volunteers continually maintain related projects, update documentation, post examples, author blog posts, and moderate the forums and chat. This is something that we want to keep safe and functional, even as we grow.
+Starting today we are announcing a few initiatives to help protect our users, contributors and community members.
+ Read on → +
@@ -715,328 +904,6 @@ You have to note:
If you need help…
…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
--
- Explaining the Updater -
- -
-
- On Saturday, we released Home Assistant 0.31 which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.
- Read on → --
- 0.31: Reading you the news, some serious business, spooky hackery and a breaking Z-Wave change -
- -
-
-
-
-
-
-
-
-
Hello again friend,
-How are you? Having a good day? We sure are. If you aren’t having a good day, this might cheer you up…
-Every other weekend around here gets a little hectic leading to a big sigh of relief as we release a new version of Home Assistant to the world. And this time is no different. Our developer community has once again built us a beautiful new release with lots of new features and improvements. We hope you like it.
-One last thing before we get going though, I should warn you… @balloob got a bit lazy this week and let me (@robbiet480) step up to the plate again to write the blog post and do the release. I guess I didn’t do such a bad job in 0.27. You’ll never know what surprises I have in store. Now that i’ve got all that stuff out of the way, let’s get started…
-Stats Update
-Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
-Hacktoberfest
-
October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the home-assistant repository and 209 merged/28 open pull requests submitted to the home-assistant.github.io repository. If you want to get in on the fun check out our Hacktoberfest blog post or the Hacktoberfest website. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
-⚠️ A greatly improved updater component (Please read this!) ⚠️
-This release includes an update to our updater component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
-It used to be that this component would check with PyPi (the Python package manager) to see if a new update was available. This had a couple of problems:
--
-
- We are unable to do a slow rollout -
- We are unable to show the user extra information (like a link to a changelog or the release date) -
- We are unable to warn users for critical security updates -
So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
-What you need to know (the important bit!)
-Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
-Each Home Assistant instance running the updater component will generate a unique ID (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called .uuid.
Opting out
-There are two ways to opt-out. The first way is by using the new opt_out option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
updater:
- reporting: no
-You can also disable the updater component entirely by removing updater: from your configuration.yaml although we would not suggest you do this as you would miss any critical updates.
Finally, you can also reset your unique identifier by deleting the .uuid file and restarting Home Assistant.
Data stored on the Home Assistant update server
-Here is what my production Home Assistant instance looks like from the server side:
-| Name | -Description | -Example | -
|---|---|---|
arch |
- CPU Architecture | -x86_64 |
-
distribution |
- Linux Distribution name (only Linux) | -Ubuntu |
-
docker |
- True if running inside Docker | -false |
-
os_name |
- Operating system name | -Darwin |
-
os_version |
- Operating system version | -10.12 |
-
python_version |
- Python version | -3.5.2 |
-
timezone |
- Timezone | -America/Los_Angeles |
-
user_agent |
- User agent used to submit analytics | -python-requests/2.11.1 |
-
uuid |
- Unique identifier | -10321ee6094d4a2ebb5ed55c675d5f5e |
-
version |
- Home Assistant version | -0.31.0 |
-
virtualenv |
- True if running inside virtualenv | -true |
-
In addition to the above collected data, the server will also use your IP address to do a geographic IP address lookup to determine the city that you are from. To be extremely, extremely clear about this bit: The Home Assistant updater does not: store your IP address in a database and also does not submit the location information from your configuration.yaml.
-
- Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
-
The server also adds two timestamps to the data: the original date your instance UUID was first seen and the timestamp of the last time we have seen your instance. This gives us the following extra data:
-| Name | -Description | -Example | -
|---|---|---|
first_seen_datetime |
- First time instance ID was submitted | -2016-10-22T19:56:03.542Z |
-
geo_city |
- GeoIP determined city | -Oakland |
-
geo_country_code |
- GeoIP determined country code | -US |
-
geo_country_name |
- GeoIP determined country name | -United States |
-
geo_latitude |
- GeoIP determined latitude (of the city) | -37.8047 |
-
geo_longitude |
- GeoIP determined longitude (of the city) | --122.2124 |
-
geo_metro_code |
- GeoIP determined metro code | -807 |
-
geo_region_code |
- GeoIP determined region code | -CA |
-
geo_region_name |
- GeoIP determined region name | -California |
-
geo_time_zone |
- GeoIP determined time zone | -America/Los_Angeles |
-
geo_zip_code |
- GeoIP determined zip code | -94602 |
-
last_seen_datetime |
- Most recent time instance ID was submitted | -2016-10-22T19:56:03.542Z |
-
This data is held in the highest security. The update system runs in a secured Amazon Web Services account owned by me (@robbiet480). I personally have 5 years of experience with complex AWS deployments and have an extensive security background. I have audited the entire system and made sure to take every step to protect the data, including limiting who has access (just @balloob and myself). While not directly personally identifiable we absolutely understand some users hesistance to giving this information out. Please understand that we are only collecting this information to better understand our user base to provide better long term support and feature development then is currently possible.
-We currently have no plans to publicly expose any of this information. If we did do such a thing in the future we would of course notify you in advance. It must also be stated that we will never sell or allow the use of this information for non-Home Assistant purposes.
-We thank you for understanding why we are collecting this data and hope that you leave the feature enabled but fully understand if you feel uncomfortable with this.
-This section was updated on October 24 to be more clear about geo-lookups being on the city level. See original version.
-Now, back to the fun stuff…
-Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
-Home Assistant got a crazy idea recently that it couldn’t do enough already and wanted to challenge itself even more. I really don’t understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
-0.31 adds support for the brand spanking new Alexa Flash Briefing API, allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What’s the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
---Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
-
Now I know how to best get to my real job (no, Home Assistant is not my real job, it does seem like it sometimes though) every morning. Obviously not the best home automation example, but I think you get the idea. I could see this being used to tell you any major events that happened in your home overnight or reading you your hyperlocal weather report. Thanks to the audio support you could even replace all of the default Alexa Flash Briefing sources with your own news feeds. Home Assistant supports both text and audio content as well as displaying data in the Alexa app. I also want to point out that unlike the existing Skill integration, the Flash Briefing API does not require HTTPS (but you should still be using HTTPS if possible). For more information, check out the new docs.
-
-
- You stay classy, San Diego. (It’s funny, because balloob lives in San Diego))
-
Major breaking Z-Wave changes ahead
-A rather nasty Z-Wave issue was discovered recently by @lukas-hetzenecker. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
-What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here’s what I had to do:
--
-
- Update customizations -
- Update groups -
- Update my
zwave.customizesection
- - Update my Alexa skills that used old entity IDs -
- Because I use
emulated_huewith Alexa andemulated_hueuses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
-
Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It’s not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
-This is super annoying, I know, especially since we had said in 0.12 that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn’t change in the future but obviously we see how that went. To sum up on this section… sorry but it had to happen.
-All changes
--
-
- Updater component (@infamy, @robbiet480, @kellerza) -
- Continue to setup other platforms when 1 platform config is invalid (@kellerza) -
- Create persistent notifications when a platform contains invalid config (@kellerza) -
- Logbook: Allow filtering domains and entities to be shown (@wokar) -
- HTTP: Change
approved_ipsfrom string to CIDR validation (@mweinelt)
- - Persistent Notifications: Allow using markdown (@justweb1) -
- Netatmo: Add discovery support (@jabesq) -
- Netatmo Welcome camera: Add binary sensor (@jabesq) -
- Support added for HaveIBeenPwned (@joyrider3774) -
- Device tracker:
known_devices.yamlreading and writing tweaks and fixes (@kellerza)
- - Fix climate platforms showing the wrong temperature unit (@rcloran) -
- Lots of voluptuous love (@fabaff) -
- Ensure proper attribution for weather platforms (@fabaff) -
- Fix Telegram in Docker (@jeanregisser) -
- Support recursive config inclusions in YAML (@lwis) -
- Camera: Synology SS cameras now supported (@jgriff2) -
- History: Allow filtering domains and entities to be shown (@wokar) -
- Media Player - Squeezebox: Now able to show artist and album (@ih8gates) -
- Alexa: Flash Briefing skill support added (@robbiet480) -
- Device Tracker: Add support for Bbox Modem Router (@HydrelioxGithub) -
- Sensor: Add support for Bbox Modem Router (@HydrelioxGithub) -
- Input select: Services added to pick next and prev option (@persandstrom) -
- Sensor: ARWN now supported (@sdague) -
- Pushbullet: Push an URL note if an url is provided inside data (@jabesq) -
- Z-Wave: Allow certain devices to be not added to Home Assistant (@lukas-hetzenecker) -
- New support for Zoneminder added (@Khabi) -
- Weather: Allow tracking severe weather alerts with WUnderground (@tchellomello) -
- Sensor: New support added to track min/max/mean (@fabaff) -
- Convert EntityComponent to be async (@pvizeli, @balloob) -
- Z-Wave: Add assocation service (@turbokongen) -
- Frontend - Services dev tool: persist state and tweak UI (@justweb1) -
- Sensor: Support added for scraping websites (@fabaff) -
- Clean up of tests (@capellini) -
- New
failfilter added to templates to raise on UndefinedError (@jaharkes)
- - Support added for Emoncms history (@joyrider3774) -
- Support for Apple Push Notifications Service (@sam-io) -
- Thermostat: Netatmo now supported (@gieljnssns) -
- Alarm control panel: Concord232 now supported (@JasonCarter80) -
- Notify: Matrix support added (@mweinelt) -
- Device tracker - nmap: Allow specifying multiple inputs for nmap (@hcooper) -
- Device Tracker - snmp: SNMPv3 now supported (@T3m3z) -
- Notify: Telstra SMS now supported (@nvella) -
- Camera: Verisure now supported (@turbokongen) -
- Support added for Neato Connected Robot (@jabesq) -
- Media player: More options for Yamaha AVR (@ehagan) -
- Sensor: Support for Pilight sensor (@DavidLP) -
- iOS support (@robbiet480) -
- Minor features and bug fixes by @mtl010957, @molobrakos, @flyte, @fabaff, @phardy, @sander76, @T3m3z, @c-w, @balloob, @robbiet480, @StaticCube, @vittoriom, @hartmms, @kirichkov, @mezz64, @ishults, @Danielhiversen and @tchellomello. -
Release 0.31.1 - October 24
--
-
- Identify special character encoding error in YAML files (@kellerza, @lwis) -
- iOS app component bug fixes (@robbiet480) -
- Fix a spelling problem on user-facing error (@robbiet480) -
- YAML includes will ignore dirs/files prefixed with . (@lwis) -
Breaking changes
--
-
- The HTTP component now takes a different format for authenticating IPs -
- Configuration format has changed for Proximity -
- The Arduino platform are now covered by the configuration check. Please check the documentation to see how. -
- The Z-Wave entity ID change mentioned above -
If you need help…
-…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
-Until next time
-Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
-– Robbie
diff --git a/blog/posts/6/index.html b/blog/posts/6/index.html index b183c12c4e..f626382771 100644 --- a/blog/posts/6/index.html +++ b/blog/posts/6/index.html @@ -67,6 +67,328 @@
+
+
+
+
+
+
+
+
+
+
@@ -725,112 +1047,6 @@ So, part 1 of ESP8266
-
- + Explaining the Updater +
+ +
+
+ On Saturday, we released Home Assistant 0.31 which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.
+ Read on → ++
+ 0.31: Reading you the news, some serious business, spooky hackery and a breaking Z-Wave change +
+ +
+
+
+
+
+
+
+
+
+ Hello again friend,
+How are you? Having a good day? We sure are. If you aren’t having a good day, this might cheer you up…
+Every other weekend around here gets a little hectic leading to a big sigh of relief as we release a new version of Home Assistant to the world. And this time is no different. Our developer community has once again built us a beautiful new release with lots of new features and improvements. We hope you like it.
+One last thing before we get going though, I should warn you… @balloob got a bit lazy this week and let me (@robbiet480) step up to the plate again to write the blog post and do the release. I guess I didn’t do such a bad job in 0.27. You’ll never know what surprises I have in store. Now that i’ve got all that stuff out of the way, let’s get started…
+Stats Update
+Sadly, no big amazing stats to update you with this time, but we did recently pass 7,000 commits! This release featured submissions from 45 contributors. Hopefully with the new updater component we will be able to give you some really good stats in the 0.32 blog post.
+Hacktoberfest
+
October means Hacktoberfest time and our community has really come through with some excellent improvements and additions. As of this writing, we have 194 merged and 41 open pull requests to the home-assistant repository and 209 merged/28 open pull requests submitted to the home-assistant.github.io repository. If you want to get in on the fun check out our Hacktoberfest blog post or the Hacktoberfest website. You get an awesome t-shirt for free if you have 4 pull requests merged in the month of October! We even have tasks that a non-developer can easily accomplish with a tiny bit of work. Better hurry up though, only 9 days left and most of the easy tasks are gone!
+⚠️ A greatly improved updater component (Please read this!) ⚠️
+This release includes an update to our updater component. The responsibility of the updater component is to check if a new version is available and notify the user if this is the case.
+It used to be that this component would check with PyPi (the Python package manager) to see if a new update was available. This had a couple of problems:
+-
+
- We are unable to do a slow rollout +
- We are unable to show the user extra information (like a link to a changelog or the release date) +
- We are unable to warn users for critical security updates +
So to work around these problems, we decided to start hosting the version check service ourselves. Since we had to get some infrastructure spun up anyway, we figured we would take it a step further. Which leads me to this bit of the update (the most important part):
+What you need to know (the important bit!)
+Remember how I mentioned that up there in the title that there is some serious business in this release? Well, we also added some basic analytics to the updater component which get sent to the server and stored so that we get a better idea of our user base.
+Each Home Assistant instance running the updater component will generate a unique ID (based on UUIDv4) that will be used for the updater to be able to differentiate between instances. This UUID will be stored in your config directory in a file called .uuid.
Opting out
+There are two ways to opt-out. The first way is by using the new opt_out option for the updater. This way the updater will continue to check for updates, but no information about your system will be shared with us.
updater:
+ reporting: no
+You can also disable the updater component entirely by removing updater: from your configuration.yaml although we would not suggest you do this as you would miss any critical updates.
Finally, you can also reset your unique identifier by deleting the .uuid file and restarting Home Assistant.
Data stored on the Home Assistant update server
+Here is what my production Home Assistant instance looks like from the server side:
+| Name | +Description | +Example | +
|---|---|---|
arch |
+ CPU Architecture | +x86_64 |
+
distribution |
+ Linux Distribution name (only Linux) | +Ubuntu |
+
docker |
+ True if running inside Docker | +false |
+
os_name |
+ Operating system name | +Darwin |
+
os_version |
+ Operating system version | +10.12 |
+
python_version |
+ Python version | +3.5.2 |
+
timezone |
+ Timezone | +America/Los_Angeles |
+
user_agent |
+ User agent used to submit analytics | +python-requests/2.11.1 |
+
uuid |
+ Unique identifier | +10321ee6094d4a2ebb5ed55c675d5f5e |
+
version |
+ Home Assistant version | +0.31.0 |
+
virtualenv |
+ True if running inside virtualenv | +true |
+
In addition to the above collected data, the server will also use your IP address to do a geographic IP address lookup to determine the city that you are from. To be extremely, extremely clear about this bit: The Home Assistant updater does not: store your IP address in a database and also does not submit the location information from your configuration.yaml.
+
+ Geo-lookup on my IP resolves to Oakland with latitude/longitude pointing at the geographical center of the city.
+
The server also adds two timestamps to the data: the original date your instance UUID was first seen and the timestamp of the last time we have seen your instance. This gives us the following extra data:
+| Name | +Description | +Example | +
|---|---|---|
first_seen_datetime |
+ First time instance ID was submitted | +2016-10-22T19:56:03.542Z |
+
geo_city |
+ GeoIP determined city | +Oakland |
+
geo_country_code |
+ GeoIP determined country code | +US |
+
geo_country_name |
+ GeoIP determined country name | +United States |
+
geo_latitude |
+ GeoIP determined latitude (of the city) | +37.8047 |
+
geo_longitude |
+ GeoIP determined longitude (of the city) | +-122.2124 |
+
geo_metro_code |
+ GeoIP determined metro code | +807 |
+
geo_region_code |
+ GeoIP determined region code | +CA |
+
geo_region_name |
+ GeoIP determined region name | +California |
+
geo_time_zone |
+ GeoIP determined time zone | +America/Los_Angeles |
+
geo_zip_code |
+ GeoIP determined zip code | +94602 |
+
last_seen_datetime |
+ Most recent time instance ID was submitted | +2016-10-22T19:56:03.542Z |
+
This data is held in the highest security. The update system runs in a secured Amazon Web Services account owned by me (@robbiet480). I personally have 5 years of experience with complex AWS deployments and have an extensive security background. I have audited the entire system and made sure to take every step to protect the data, including limiting who has access (just @balloob and myself). While not directly personally identifiable we absolutely understand some users hesistance to giving this information out. Please understand that we are only collecting this information to better understand our user base to provide better long term support and feature development then is currently possible.
+We currently have no plans to publicly expose any of this information. If we did do such a thing in the future we would of course notify you in advance. It must also be stated that we will never sell or allow the use of this information for non-Home Assistant purposes.
+We thank you for understanding why we are collecting this data and hope that you leave the feature enabled but fully understand if you feel uncomfortable with this.
+This section was updated on October 24 to be more clear about geo-lookups being on the city level. See original version.
+Now, back to the fun stuff…
+Good evening. I’m Ron Burgundy and here’s what happening in your world tonight.
+Home Assistant got a crazy idea recently that it couldn’t do enough already and wanted to challenge itself even more. I really don’t understand how it came up with this kooky idea, but it now thinks that its newest hobby should be a minor career in journalism.
+0.31 adds support for the brand spanking new Alexa Flash Briefing API, allowing you to get updates from Home Assistant anytime you ask Alexa to read your flash briefing. What’s the use case you ask? Well, now when I wake up in the morning and get my flash briefing, Home Assistant adds this to the end of it for me:
+++Drive time with traffic is 35 minutes. There is an UberPOOL that will cost $11.52, estimated to be 2 minutes away, for a total of 37 minutes. BART is currently estimated to take 29 minutes. You should take BART, as it is estimated to be faster by 8 minutes.
+
Now I know how to best get to my real job (no, Home Assistant is not my real job, it does seem like it sometimes though) every morning. Obviously not the best home automation example, but I think you get the idea. I could see this being used to tell you any major events that happened in your home overnight or reading you your hyperlocal weather report. Thanks to the audio support you could even replace all of the default Alexa Flash Briefing sources with your own news feeds. Home Assistant supports both text and audio content as well as displaying data in the Alexa app. I also want to point out that unlike the existing Skill integration, the Flash Briefing API does not require HTTPS (but you should still be using HTTPS if possible). For more information, check out the new docs.
+
+
+ You stay classy, San Diego. (It’s funny, because balloob lives in San Diego))
+
Major breaking Z-Wave changes ahead
+A rather nasty Z-Wave issue was discovered recently by @lukas-hetzenecker. There was a somewhat large chance that if you had multiple of the same model Z-Wave device they may both try to use the same entity IDs. To fix the issue the internal Z-Wave index is now appended to the end of all Z-Wave entity IDs.
+What this means for all you Z-Wave users is that you will need to update your configurations to reflect the change. I personally have quite a few (17) Z-Wave devices and went through the process this week. Here’s what I had to do:
+-
+
- Update customizations +
- Update groups +
- Update my
zwave.customizesection
+ - Update my Alexa skills that used old entity IDs +
- Because I use
emulated_huewith Alexa andemulated_hueuses the entity ID as a unique identifier I also had to remove all Z-Wave devices from Alexa and re-add them.
+
Your todo list may be a little different from mine, I just wanted to outline the steps I took to give you an idea of what you need to think about. It’s not a very hard process, especially when using global find and replace in Sublime Text but did take me about 20 minutes to complete.
+This is super annoying, I know, especially since we had said in 0.12 that Z-Wave IDs should hopefully never change again, but we are now forced to eat those words. I will state again that Z-Wave IDs shouldn’t change in the future but obviously we see how that went. To sum up on this section… sorry but it had to happen.
+All changes
+-
+
- Updater component (@infamy, @robbiet480, @kellerza) +
- Continue to setup other platforms when 1 platform config is invalid (@kellerza) +
- Create persistent notifications when a platform contains invalid config (@kellerza) +
- Logbook: Allow filtering domains and entities to be shown (@wokar) +
- HTTP: Change
approved_ipsfrom string to CIDR validation (@mweinelt)
+ - Persistent Notifications: Allow using markdown (@justweb1) +
- Netatmo: Add discovery support (@jabesq) +
- Netatmo Welcome camera: Add binary sensor (@jabesq) +
- Support added for HaveIBeenPwned (@joyrider3774) +
- Device tracker:
known_devices.yamlreading and writing tweaks and fixes (@kellerza)
+ - Fix climate platforms showing the wrong temperature unit (@rcloran) +
- Lots of voluptuous love (@fabaff) +
- Ensure proper attribution for weather platforms (@fabaff) +
- Fix Telegram in Docker (@jeanregisser) +
- Support recursive config inclusions in YAML (@lwis) +
- Camera: Synology SS cameras now supported (@jgriff2) +
- History: Allow filtering domains and entities to be shown (@wokar) +
- Media Player - Squeezebox: Now able to show artist and album (@ih8gates) +
- Alexa: Flash Briefing skill support added (@robbiet480) +
- Device Tracker: Add support for Bbox Modem Router (@HydrelioxGithub) +
- Sensor: Add support for Bbox Modem Router (@HydrelioxGithub) +
- Input select: Services added to pick next and prev option (@persandstrom) +
- Sensor: ARWN now supported (@sdague) +
- Pushbullet: Push an URL note if an url is provided inside data (@jabesq) +
- Z-Wave: Allow certain devices to be not added to Home Assistant (@lukas-hetzenecker) +
- New support for Zoneminder added (@Khabi) +
- Weather: Allow tracking severe weather alerts with WUnderground (@tchellomello) +
- Sensor: New support added to track min/max/mean (@fabaff) +
- Convert EntityComponent to be async (@pvizeli, @balloob) +
- Z-Wave: Add assocation service (@turbokongen) +
- Frontend - Services dev tool: persist state and tweak UI (@justweb1) +
- Sensor: Support added for scraping websites (@fabaff) +
- Clean up of tests (@capellini) +
- New
failfilter added to templates to raise on UndefinedError (@jaharkes)
+ - Support added for Emoncms history (@joyrider3774) +
- Support for Apple Push Notifications Service (@sam-io) +
- Thermostat: Netatmo now supported (@gieljnssns) +
- Alarm control panel: Concord232 now supported (@JasonCarter80) +
- Notify: Matrix support added (@mweinelt) +
- Device tracker - nmap: Allow specifying multiple inputs for nmap (@hcooper) +
- Device Tracker - snmp: SNMPv3 now supported (@T3m3z) +
- Notify: Telstra SMS now supported (@nvella) +
- Camera: Verisure now supported (@turbokongen) +
- Support added for Neato Connected Robot (@jabesq) +
- Media player: More options for Yamaha AVR (@ehagan) +
- Sensor: Support for Pilight sensor (@DavidLP) +
- iOS support (@robbiet480) +
- Minor features and bug fixes by @mtl010957, @molobrakos, @flyte, @fabaff, @phardy, @sander76, @T3m3z, @c-w, @balloob, @robbiet480, @StaticCube, @vittoriom, @hartmms, @kirichkov, @mezz64, @ishults, @Danielhiversen and @tchellomello. +
Release 0.31.1 - October 24
+-
+
- Identify special character encoding error in YAML files (@kellerza, @lwis) +
- iOS app component bug fixes (@robbiet480) +
- Fix a spelling problem on user-facing error (@robbiet480) +
- YAML includes will ignore dirs/files prefixed with . (@lwis) +
Breaking changes
+-
+
- The HTTP component now takes a different format for authenticating IPs +
- Configuration format has changed for Proximity +
- The Arduino platform are now covered by the configuration check. Please check the documentation to see how. +
- The Z-Wave entity ID change mentioned above +
If you need help…
+…don’t hesitate to use our Forum or join us for a little chat. The release notes have comments enabled but it’s preferred if you the former communication channels. Thanks.
+Until next time
+Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
+– Robbie
+
@@ -725,112 +1047,6 @@ So, part 1 of ESP8266
Heatmap
-
-
- We Have Apps Now -
- -
-
- I have been working on a new subsystem to complement Home Assistant’s Automation and Scripting components. AppDaemon is a python daemon that consumes events from Home Assistant and feeds them to snippets of python code called “Apps”. An App is a Python class that is instantiated possibly multiple times from AppDaemon and registers callbacks for various system events. It is also able to inspect and set state and call services. The API provides a rich environment suited to home automation tasks that can also leverage all the power of Python.
-
- 0.26: Foursquare, Fast.com, FFMPEG and GPSD -
- -
-
It’s time for 0.26 and it’s again full of new features and fixes. First I want to highlight that we are now having 500 000 monthly pageviews on the website. A big milestone for us! It’s been an amazing journey. Big thanks to the Home Assistant community for being such a delightful bunch.
-This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you’ll have to pick imperial or metric now. This influences the units for your temperature, distance, and weight. This will simplify any platform or component that needs to know this information. Big thanks to @Teagan42 for her hard work on this!
-
-
-
- Core: Introduce notion of unit system (deprecates temperature unit option) (@Teagan42) -
- Front end: Speed improvements (@balloob) -
- Front end: Improve layout of state dev tool (@balloob) -
- Proximity: Allow definition of unit of measurement (@Teagan42) -
- Flux: Add mired and kelvin mode (@HBDK) -
- Thermostat - Proliphix: Support for cooling (@sdague) -
- Media Player - LG Netcast TV: Show screenshot of what is currently playing (@shmuelzon) -
- Z-Wave improvements (@jnewland, @turbokongen) -
- Thermostat - heat control: now also able to control an AC (@mtreinish) -
- Thermostat - heat control: allow specifying a minimum duration before switching (@mtreinish) -
- InfluxDB: Whitelist entities option added (@tchellomello) -
- Sensor: Serial particulate matters sensors now supported (@open-homeautomation) -
- Sensor - Fitbit: Fix unit system (@tchellomello) -
- Light - Flux LED: Add support for [color and brightness][color] (@Danielhiversen) -
- Media Player - Plex: Now able to report on music (@abcminiuser) -
- Alarm Control Panel - Verisure: Now able to see who changed the alarm (@persandtrom) -
- Thermostat - Honeywell: Add option to read and control HVAC mode (@Teagan42) -
- Foursquare component to receive instant notifications of checkins (@robbiet480) -
- Camera: New FFMPEG platform allows to stream anything through front end (@pvizeli) -
- Manage secrets with new command line script (@kellerza) -
- Notify - SMTP: Allow embedding of images (@partofthething) -
- Sensor: OhmConnect is now supported (@robbiet480) -
- panel_custom component allows the registering of new panels (@balloob) -
- Light: New mqtt_json platform for working with JSON payload (@corbanmailloux) -
- Sensor: New Fast.com platform to measure network bandwidth performance (@nkgilley) -
- New pilight component to control 433 Mz devices (@DavidLP) -
- Sensor: GPSD now supported (@fabaff) -
Hotfix 0.26.1 - August 14
--
-
- Fix serial_pm config validation (@open-homeautomation) -
- Check for existence of system mode on Honeywell thermostats (@mKeRix) -
- Fix unknown unit of measurement for hvac and thermostat component (@turbokongen) -
Hotfix 0.26.2 - August 15
--
-
- Fix Wemo: have PyWemo play nicely with the latest Requests (@pavoni) -
Hotfix 0.26.3 - August 19
--
-
- Media Player cover art would not work when an API password was set. Thanks to @maddox for reporting it and @balloob for the fix. -
Breaking changes
--
-
- A new unit system has superseded the temperature unit option in the core configuration. For now it is backwards compatible, but you should update soon: -
# Configuration.yaml example
-homeassistant:
- # 'metric' for the metric system, 'imperial' for the imperial system
- unit_system: metric
-diff --git a/blog/posts/7/index.html b/blog/posts/7/index.html index 37e7e0bed9..4bec62fd79 100644 --- a/blog/posts/7/index.html +++ b/blog/posts/7/index.html @@ -67,6 +67,112 @@
+
+
+
+
+
+
+
+
+
+
@@ -408,102 +514,6 @@ Over a year ago I participated in the
-
-
-
-
-
-
-
+ We Have Apps Now +
+ +
+
+ I have been working on a new subsystem to complement Home Assistant’s Automation and Scripting components. AppDaemon is a python daemon that consumes events from Home Assistant and feeds them to snippets of python code called “Apps”. An App is a Python class that is instantiated possibly multiple times from AppDaemon and registers callbacks for various system events. It is also able to inspect and set state and call services. The API provides a rich environment suited to home automation tasks that can also leverage all the power of Python.
+
+ 0.26: Foursquare, Fast.com, FFMPEG and GPSD +
+ +
+
+
+ It’s time for 0.26 and it’s again full of new features and fixes. First I want to highlight that we are now having 500 000 monthly pageviews on the website. A big milestone for us! It’s been an amazing journey. Big thanks to the Home Assistant community for being such a delightful bunch.
+This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you’ll have to pick imperial or metric now. This influences the units for your temperature, distance, and weight. This will simplify any platform or component that needs to know this information. Big thanks to @Teagan42 for her hard work on this!
+
-
+
- Core: Introduce notion of unit system (deprecates temperature unit option) (@Teagan42) +
- Front end: Speed improvements (@balloob) +
- Front end: Improve layout of state dev tool (@balloob) +
- Proximity: Allow definition of unit of measurement (@Teagan42) +
- Flux: Add mired and kelvin mode (@HBDK) +
- Thermostat - Proliphix: Support for cooling (@sdague) +
- Media Player - LG Netcast TV: Show screenshot of what is currently playing (@shmuelzon) +
- Z-Wave improvements (@jnewland, @turbokongen) +
- Thermostat - heat control: now also able to control an AC (@mtreinish) +
- Thermostat - heat control: allow specifying a minimum duration before switching (@mtreinish) +
- InfluxDB: Whitelist entities option added (@tchellomello) +
- Sensor: Serial particulate matters sensors now supported (@open-homeautomation) +
- Sensor - Fitbit: Fix unit system (@tchellomello) +
- Light - Flux LED: Add support for [color and brightness][color] (@Danielhiversen) +
- Media Player - Plex: Now able to report on music (@abcminiuser) +
- Alarm Control Panel - Verisure: Now able to see who changed the alarm (@persandtrom) +
- Thermostat - Honeywell: Add option to read and control HVAC mode (@Teagan42) +
- Foursquare component to receive instant notifications of checkins (@robbiet480) +
- Camera: New FFMPEG platform allows to stream anything through front end (@pvizeli) +
- Manage secrets with new command line script (@kellerza) +
- Notify - SMTP: Allow embedding of images (@partofthething) +
- Sensor: OhmConnect is now supported (@robbiet480) +
- panel_custom component allows the registering of new panels (@balloob) +
- Light: New mqtt_json platform for working with JSON payload (@corbanmailloux) +
- Sensor: New Fast.com platform to measure network bandwidth performance (@nkgilley) +
- New pilight component to control 433 Mz devices (@DavidLP) +
- Sensor: GPSD now supported (@fabaff) +
Hotfix 0.26.1 - August 14
+-
+
- Fix serial_pm config validation (@open-homeautomation) +
- Check for existence of system mode on Honeywell thermostats (@mKeRix) +
- Fix unknown unit of measurement for hvac and thermostat component (@turbokongen) +
Hotfix 0.26.2 - August 15
+-
+
- Fix Wemo: have PyWemo play nicely with the latest Requests (@pavoni) +
Hotfix 0.26.3 - August 19
+-
+
- Media Player cover art would not work when an API password was set. Thanks to @maddox for reporting it and @balloob for the fix. +
Breaking changes
+-
+
- A new unit system has superseded the temperature unit option in the core configuration. For now it is backwards compatible, but you should update soon: +
# Configuration.yaml example
+homeassistant:
+ # 'metric' for the metric system, 'imperial' for the imperial system
+ unit_system: metric
+
@@ -408,102 +514,6 @@ Over a year ago I participated in the
-
-
- 0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV
-
-
-
-
- It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.
-This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.
-Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.
-On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!
-
-
- - Support for Envisalink added (alarm control panel, binary sensor, sensor) (@cinntax)
- - Support for Homematic added (binary sensor, light, rollershutter, sensor, switch) (@pvizeli, @danielperna84)
- - New HDMI-CEC component (@happyleavesaoc, @lukas-hetzenecker)
- - Major rewrite of Wink which now pushes changes to Home Assistant (@w1ll1am23)
- - Core: new add reload core config service (@balloob)
- - Support for persistent notifications added (@fabaff, @balloob)
- - Garage door: Z-Wave support added (@turbokongen)
- - Rollershutter: Z-Wave support added (@turbokongen)
- - Media Player: Sony Bravia TV now supported (@aparraga)
- - Sensor: Fixer.io now supported (@fabaff)
- - Garage door: Control any garage door using Raspberry Pi GPIO pins (@kellerza)
- - Sensor: OpenExchangeRates support added (@arsaboo)
- - Notify: Pushover now supports target device, sound, URL and priority (@dale3h)
- - Sensor: Netatmo now supports wind, battery and radio signals (@Jypy)
- - Log successful and failed login attemps (@fabaff)
- - Config: allow extracting account info into OS keyring or separate YAML file (@kellerza)
- - Core: add option to not filter out duplicate states per entity (@philipbl)
- - HTTP: Follow Mozilla SSL recommendations (@danieljkemp, @AlucardZero)
- - Light: Z-Wave colorbulb support added (@armills)
- - Core: new elevation config option added (@balloob)
- - Sensor: OneWire support extended with support for DS18S20, DS1822, DS1825 and DS28EA00 temperature sensors + support for bus masters which use fuse to mount device tree. (@Ardetus)
- - Lock: Vera now supported (@rhooper)
- - HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems (@balloob)
-
- Breaking changes
-
- - Homematic thermostat configuration has changed and now depends on the new Homematic component.
-
- Hotfix 0.23.1 - July 2
-
- - Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug (@rhooper)
- - HTTP - SSL: Check for OP_NO_COMPRESSION support before trying to use it (@AlucardZero)
- - Wink: Downgraded pubnub to work around pycryptodome conflicts (@w1ll1am23)
-
- FAQ
-
- elevation: was introduced to the configuration for weather/sunrise data. For existing configurations add the value shown in the warning [homeassistant.config] Incomplete core config. Auto detected elevation: 665 to your configuration.yaml file.
-
-
- 0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV -
- -It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.
-This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.
-Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.
-On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!
-
-
-
- Support for Envisalink added (alarm control panel, binary sensor, sensor) (@cinntax) -
- Support for Homematic added (binary sensor, light, rollershutter, sensor, switch) (@pvizeli, @danielperna84) -
- New HDMI-CEC component (@happyleavesaoc, @lukas-hetzenecker) -
- Major rewrite of Wink which now pushes changes to Home Assistant (@w1ll1am23) -
- Core: new add reload core config service (@balloob) -
- Support for persistent notifications added (@fabaff, @balloob) -
- Garage door: Z-Wave support added (@turbokongen) -
- Rollershutter: Z-Wave support added (@turbokongen) -
- Media Player: Sony Bravia TV now supported (@aparraga) -
- Sensor: Fixer.io now supported (@fabaff) -
- Garage door: Control any garage door using Raspberry Pi GPIO pins (@kellerza) -
- Sensor: OpenExchangeRates support added (@arsaboo) -
- Notify: Pushover now supports target device, sound, URL and priority (@dale3h) -
- Sensor: Netatmo now supports wind, battery and radio signals (@Jypy) -
- Log successful and failed login attemps (@fabaff) -
- Config: allow extracting account info into OS keyring or separate YAML file (@kellerza) -
- Core: add option to not filter out duplicate states per entity (@philipbl) -
- HTTP: Follow Mozilla SSL recommendations (@danieljkemp, @AlucardZero) -
- Light: Z-Wave colorbulb support added (@armills) -
- Core: new elevation config option added (@balloob) -
- Sensor: OneWire support extended with support for DS18S20, DS1822, DS1825 and DS28EA00 temperature sensors + support for bus masters which use fuse to mount device tree. (@Ardetus) -
- Lock: Vera now supported (@rhooper) -
- HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems (@balloob) -
Breaking changes
--
-
- Homematic thermostat configuration has changed and now depends on the new Homematic component. -
Hotfix 0.23.1 - July 2
--
-
- Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug (@rhooper) -
- HTTP - SSL: Check for OP_NO_COMPRESSION support before trying to use it (@AlucardZero) -
- Wink: Downgraded pubnub to work around pycryptodome conflicts (@w1ll1am23) -
FAQ
--
-
elevation:was introduced to the configuration for weather/sunrise data. For existing configurations add the value shown in the warning[homeassistant.config] Incomplete core config. Auto detected elevation: 665to yourconfiguration.yamlfile.
-
-
- Using USB webcams with Home Assistant -
- -
-
-
-In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like pygame or SimpleCV but I never finished something. With the Local File camera platform by Landrash and motion you could integrate a local USB webcam with a few very easy steps.
In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old Logitech QuickCam Orbit AF and a Logitech HD Webcam C270. As a start only the Quickcam is used. No multi-camera setup for now.
- Read on → -
← Older
Newer →
diff --git a/blog/posts/8/index.html b/blog/posts/8/index.html
index 83fc2346ad..567cae0783 100644
--- a/blog/posts/8/index.html
+++ b/blog/posts/8/index.html
@@ -67,6 +67,102 @@
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+ 0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV +
+ +
+
+ It’s time for Home Assistant 0.23 and it’s full of goodies. It’s also the release that bumps us over a 1000 tests and to 94% test coverage! Also our install issues on the Raspberry Pi and Synology have been resolved.
+This release brings support for two new ecosystems: Envisalink and Homematic. We can now also control your TV via HDMI using HDMI-CEC (which works on the Pi!) and another cool feature is the persistent notifications which allow you to add a notification to the frontend till dismissed.
+Wink support has been dramatically improved by migrating to the PubNub API. This allows Wink to push changes from their system to Home Assistant. This change came just in time as somehow our Wink integration was causing a lot of requests to their servers. Thanks to Wink for letting us know so we could solve it instead of blocking us.
+On the config side, you can now store your passwords in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings!
+
-
+
- Support for Envisalink added (alarm control panel, binary sensor, sensor) (@cinntax) +
- Support for Homematic added (binary sensor, light, rollershutter, sensor, switch) (@pvizeli, @danielperna84) +
- New HDMI-CEC component (@happyleavesaoc, @lukas-hetzenecker) +
- Major rewrite of Wink which now pushes changes to Home Assistant (@w1ll1am23) +
- Core: new add reload core config service (@balloob) +
- Support for persistent notifications added (@fabaff, @balloob) +
- Garage door: Z-Wave support added (@turbokongen) +
- Rollershutter: Z-Wave support added (@turbokongen) +
- Media Player: Sony Bravia TV now supported (@aparraga) +
- Sensor: Fixer.io now supported (@fabaff) +
- Garage door: Control any garage door using Raspberry Pi GPIO pins (@kellerza) +
- Sensor: OpenExchangeRates support added (@arsaboo) +
- Notify: Pushover now supports target device, sound, URL and priority (@dale3h) +
- Sensor: Netatmo now supports wind, battery and radio signals (@Jypy) +
- Log successful and failed login attemps (@fabaff) +
- Config: allow extracting account info into OS keyring or separate YAML file (@kellerza) +
- Core: add option to not filter out duplicate states per entity (@philipbl) +
- HTTP: Follow Mozilla SSL recommendations (@danieljkemp, @AlucardZero) +
- Light: Z-Wave colorbulb support added (@armills) +
- Core: new elevation config option added (@balloob) +
- Sensor: OneWire support extended with support for DS18S20, DS1822, DS1825 and DS28EA00 temperature sensors + support for bus masters which use fuse to mount device tree. (@Ardetus) +
- Lock: Vera now supported (@rhooper) +
- HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems (@balloob) +
Breaking changes
+-
+
- Homematic thermostat configuration has changed and now depends on the new Homematic component. +
Hotfix 0.23.1 - July 2
+-
+
- Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug (@rhooper) +
- HTTP - SSL: Check for OP_NO_COMPRESSION support before trying to use it (@AlucardZero) +
- Wink: Downgraded pubnub to work around pycryptodome conflicts (@w1ll1am23) +
FAQ
+-
+
elevation:was introduced to the configuration for weather/sunrise data. For existing configurations add the value shown in the warning[homeassistant.config] Incomplete core config. Auto detected elevation: 665to yourconfiguration.yamlfile.
+
+
+ Using USB webcams with Home Assistant +
+ +
+
+
+In the past month I was thinking about ways to integrate USB webcams into Home Assistant again. The main reason was that this would give those devices a second life and enable one to benefit from low-cost video surveillance. There are a couple of options available like pygame or SimpleCV but I never finished something. With the Local File camera platform by Landrash and motion you could integrate a local USB webcam with a few very easy steps.
In this blog post I am using a Fedora 24 (will most likely work on other distributions too) installation with Home Assistant 0.22.1 on a Foxconn nT-330i with an old Logitech QuickCam Orbit AF and a Logitech HD Webcam C270. As a start only the Quickcam is used. No multi-camera setup for now.
+ Read on → +@@ -442,138 +538,6 @@
-
- Video: How To Configure Home Assistant -
- -
-
- Ben from BRUH Automation authors a lot of great video’s about how he is using Home Assistant and how you can get started with it too. The video below will walk you through how to configure Home Assistant. Enjoy!
-Make sure to subscribe to his YouTube channel for more Home Assistant video’s.
-
-
-
- -
- 0.19: Empowering scripts and Alexa -
- -
-
-
-
-
-
- This release is big. Until now, our automations and scripts have been very static. Starting today it should all be a bit more dynamic.
-Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state !). Passing data to script entities is available by passing the data to the script services.
automation:
- trigger:
- platform: mqtt
- topic: some/notify/topic
- action:
- service: notify.notify
- data_template:
- message:
-
-automation 2:
- trigger:
- platform: state
- entity_id: light.hue
- action:
- service: notify.notify
- data_template:
- message: is now
-Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room into light.holiday_home_living_room with the following config:
light:
- platform: hue
- entity_namespace: holiday_home
--
-
- Automation: allow script syntax for action (@balloob) -
- Automation: expose
triggervariable to script templates (@balloob)
- - Script: allow passing variables for script templates in the script service calls (@balloob) -
- Alexa/Amazon Echo: allow script syntax for action (@balloob) -
- Alexa/Amazon Echo: expose intent variables to script templates (@balloob) -
- Script syntax: conditions now supported to interrupt execution (@balloob) -
- Automation: use new condition syntax (@balloob) -
- Script syntax: two new conditions
andandorto combine conditions (@balloob)
- - Any platform: Allow setting entity namespace to prefix entity_ids. (@balloob) -
- Switch: Raspberry Pi generic 433 Mhz GPIO adapters now supported (@milaq) -
- Z-Wave: use more sane defaults (@danieljkemp) -
- Media Player: Snapcast now supports picking a source (@happyleavesaoc) -
- MySensors: major cleanup (@MartinHjelmare) -
- Binary Sensor: Command line sensor now supports classes (@fabaff) -
- MQTT: allow client key authentication (@timharton) -
- Sensor: Forecast.io now supports minutely, hourly and daily summaries (@aceat64) -
- Media Player: Pioneer AVR now supported (@kylehendricks) -
- Switch: Acer Projectors now supported (@deisi) -
- New HVAC component added with Z-Wave support (@turbokongen) -
- Support added for OctoPrint (@w1ll1am23) -
- Configuration.yaml can now refer to environment variables using
!env_var(@bah2830)
- - Lock: Z-Wave now supported (@devdelay) -
- New Dweet component to export data (@fabaff) -
- Media Player now supports stop command + initial kodi support (@hmronline) -
- Zigbee: push updates now supported (@flyte) -
- Wink devices with battery level will now show these (@w1ll1am23) -
- Templates: new
as_timestampmethod now available (@srcLurker)
- - API: Add [
/api/discovery_info] with basic instance info (@robbiet480)
- - Sensor: Google Maps travel time added (@Danielhiversen) -
- HTTP: Allow adding CORS headers (@robbiet480) -
- Sensor: Fitbit support added (@robbiet480) -
- Bug fixes and tweaks by @turbokongen, @danieljkemp, @Danielhiversen, @TheRealLink, @persandstrom, @sander76, @fabaff, @ishults, @Bart274, @robbiet480, @Cinntax, @blackdog70, @gwendalg, @JshWright, @kylehendricks, @bradsk88, @shaftoe, @molobrakos, @bah2830, @nkgilley -
Deprecations
--
-
- Conditions in automations should now specify which condition to use with
condition:instead ofplatform:. For examplecondition: state.
- - RFXtrx has a new config format. -
Old RFXtrx config format:
- devices:
- 123efab1:
- name: My DI.0 light device
- packetid: 1b2200000890efab1213f60
-New RFXtrx config format:
- devices:
- 1b2200000890efab1213f60:
- name: My DI.0 light device
-
← Older
Newer →
diff --git a/blog/posts/9/index.html b/blog/posts/9/index.html
index e9736f2d9f..c6fc8a0596 100644
--- a/blog/posts/9/index.html
+++ b/blog/posts/9/index.html
@@ -67,6 +67,138 @@
-
-
-
-
-
-
-
-
-
diff --git a/components/alarm_control_panel.alarmdecoder/index.html b/components/alarm_control_panel.alarmdecoder/index.html index 8cf8f11cc1..bedea8576b 100644 --- a/components/alarm_control_panel.alarmdecoder/index.html +++ b/components/alarm_control_panel.alarmdecoder/index.html @@ -136,6 +136,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.alarmdotcom/index.html b/components/alarm_control_panel.alarmdotcom/index.html
index 9065c8ea6b..5e4fcb0576 100644
--- a/components/alarm_control_panel.alarmdotcom/index.html
+++ b/components/alarm_control_panel.alarmdotcom/index.html
@@ -133,6 +133,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.concord232/index.html b/components/alarm_control_panel.concord232/index.html
index 09cfb385f5..81a5862c08 100644
--- a/components/alarm_control_panel.concord232/index.html
+++ b/components/alarm_control_panel.concord232/index.html
@@ -137,6 +137,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.envisalink/index.html b/components/alarm_control_panel.envisalink/index.html
index e076d7a8f4..2574c85f10 100644
--- a/components/alarm_control_panel.envisalink/index.html
+++ b/components/alarm_control_panel.envisalink/index.html
@@ -136,6 +136,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.manual/index.html b/components/alarm_control_panel.manual/index.html
index 11369c375f..7ff2e3658d 100644
--- a/components/alarm_control_panel.manual/index.html
+++ b/components/alarm_control_panel.manual/index.html
@@ -159,6 +159,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.manual_mqtt/index.html b/components/alarm_control_panel.manual_mqtt/index.html
new file mode 100644
index 0000000000..2ee2f2e016
--- /dev/null
+++ b/components/alarm_control_panel.manual_mqtt/index.html
@@ -0,0 +1,251 @@
+
+
+
+
+
+
+
+
+ Manual Alarm Control Panel with MQTT Support - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.nx584/index.html b/components/alarm_control_panel.nx584/index.html
index 76840f9098..281349c79f 100644
--- a/components/alarm_control_panel.nx584/index.html
+++ b/components/alarm_control_panel.nx584/index.html
@@ -137,6 +137,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.simplisafe/index.html b/components/alarm_control_panel.simplisafe/index.html
index 67ecec3500..5affd9ffd6 100644
--- a/components/alarm_control_panel.simplisafe/index.html
+++ b/components/alarm_control_panel.simplisafe/index.html
@@ -133,6 +133,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.spc/index.html b/components/alarm_control_panel.spc/index.html
index e5a7a2ffd4..a3d91d0dfb 100644
--- a/components/alarm_control_panel.spc/index.html
+++ b/components/alarm_control_panel.spc/index.html
@@ -133,6 +133,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.totalconnect/index.html b/components/alarm_control_panel.totalconnect/index.html
index b33f716ead..a78b05be41 100644
--- a/components/alarm_control_panel.totalconnect/index.html
+++ b/components/alarm_control_panel.totalconnect/index.html
@@ -133,6 +133,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.verisure/index.html b/components/alarm_control_panel.verisure/index.html
index 90913037f0..5a5f3422d1 100644
--- a/components/alarm_control_panel.verisure/index.html
+++ b/components/alarm_control_panel.verisure/index.html
@@ -160,6 +160,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel.wink/index.html b/components/alarm_control_panel.wink/index.html
index c5e5f55bd0..9e6171f798 100644
--- a/components/alarm_control_panel.wink/index.html
+++ b/components/alarm_control_panel.wink/index.html
@@ -162,6 +162,9 @@ The above devices are confimed to work, but others may work as well.
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarm_control_panel/index.html b/components/alarm_control_panel/index.html
index fd3192db00..43de6e4451 100644
--- a/components/alarm_control_panel/index.html
+++ b/components/alarm_control_panel/index.html
@@ -112,6 +112,9 @@
Manual Alarm Control Panel
+
+ Manual Alarm Control Panel with MQTT Support
+
NX584 Alarm Control Panel
diff --git a/components/alarmdecoder/index.html b/components/alarmdecoder/index.html
index 5931674250..c8fe296218 100644
--- a/components/alarmdecoder/index.html
+++ b/components/alarmdecoder/index.html
@@ -154,6 +154,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -298,6 +301,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -316,6 +322,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/alexa/index.html b/components/alexa/index.html
index 701bb8ff6f..8507dcceb9 100644
--- a/components/alexa/index.html
+++ b/components/alexa/index.html
@@ -76,32 +76,11 @@
+
+
+
+
+
+
+
+
+
+
-
- + Video: How To Configure Home Assistant +
+ +
+
+ Ben from BRUH Automation authors a lot of great video’s about how he is using Home Assistant and how you can get started with it too. The video below will walk you through how to configure Home Assistant. Enjoy!
+Make sure to subscribe to his YouTube channel for more Home Assistant video’s.
+
+
+
+ +
+ 0.19: Empowering scripts and Alexa +
+ +
+
+
+
+
+
+ This release is big. Until now, our automations and scripts have been very static. Starting today it should all be a bit more dynamic.
+Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state !). Passing data to script entities is available by passing the data to the script services.
automation:
+ trigger:
+ platform: mqtt
+ topic: some/notify/topic
+ action:
+ service: notify.notify
+ data_template:
+ message:
+
+automation 2:
+ trigger:
+ platform: state
+ entity_id: light.hue
+ action:
+ service: notify.notify
+ data_template:
+ message: is now
+Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room into light.holiday_home_living_room with the following config:
light:
+ platform: hue
+ entity_namespace: holiday_home
+-
+
- Automation: allow script syntax for action (@balloob) +
- Automation: expose
triggervariable to script templates (@balloob)
+ - Script: allow passing variables for script templates in the script service calls (@balloob) +
- Alexa/Amazon Echo: allow script syntax for action (@balloob) +
- Alexa/Amazon Echo: expose intent variables to script templates (@balloob) +
- Script syntax: conditions now supported to interrupt execution (@balloob) +
- Automation: use new condition syntax (@balloob) +
- Script syntax: two new conditions
andandorto combine conditions (@balloob)
+ - Any platform: Allow setting entity namespace to prefix entity_ids. (@balloob) +
- Switch: Raspberry Pi generic 433 Mhz GPIO adapters now supported (@milaq) +
- Z-Wave: use more sane defaults (@danieljkemp) +
- Media Player: Snapcast now supports picking a source (@happyleavesaoc) +
- MySensors: major cleanup (@MartinHjelmare) +
- Binary Sensor: Command line sensor now supports classes (@fabaff) +
- MQTT: allow client key authentication (@timharton) +
- Sensor: Forecast.io now supports minutely, hourly and daily summaries (@aceat64) +
- Media Player: Pioneer AVR now supported (@kylehendricks) +
- Switch: Acer Projectors now supported (@deisi) +
- New HVAC component added with Z-Wave support (@turbokongen) +
- Support added for OctoPrint (@w1ll1am23) +
- Configuration.yaml can now refer to environment variables using
!env_var(@bah2830)
+ - Lock: Z-Wave now supported (@devdelay) +
- New Dweet component to export data (@fabaff) +
- Media Player now supports stop command + initial kodi support (@hmronline) +
- Zigbee: push updates now supported (@flyte) +
- Wink devices with battery level will now show these (@w1ll1am23) +
- Templates: new
as_timestampmethod now available (@srcLurker)
+ - API: Add [
/api/discovery_info] with basic instance info (@robbiet480)
+ - Sensor: Google Maps travel time added (@Danielhiversen) +
- HTTP: Allow adding CORS headers (@robbiet480) +
- Sensor: Fitbit support added (@robbiet480) +
- Bug fixes and tweaks by @turbokongen, @danieljkemp, @Danielhiversen, @TheRealLink, @persandstrom, @sander76, @fabaff, @ishults, @Bart274, @robbiet480, @Cinntax, @blackdog70, @gwendalg, @JshWright, @kylehendricks, @bradsk88, @shaftoe, @molobrakos, @bah2830, @nkgilley +
Deprecations
+-
+
- Conditions in automations should now specify which condition to use with
condition:instead ofplatform:. For examplecondition: state.
+ - RFXtrx has a new config format. +
Old RFXtrx config format:
+ devices:
+ 123efab1:
+ name: My DI.0 light device
+ packetid: 1b2200000890efab1213f60
+New RFXtrx config format:
+ devices:
+ 1b2200000890efab1213f60:
+ name: My DI.0 light device
+@@ -363,140 +495,6 @@
Your hub should not be affected when your internet breaks down or the company that sold you your hub goes out of business. It should work locally so that it can continue to work even long after the vendor goes out of business or decides to kill it. Preferably, your hub should also be open so that the community can take over development after the vendor stops caring.
Unless you can afford losing a product here and there, be cautious when buying IoT products that depend on the cloud from companies that are not well established. The chances are high that they go bankrupt or get acquired and closed. This however is easier said than done as Gartner predicts that by 2017, 50 percent of IoT solutions will originate in startups that are less than three years old.
--
- 0.16: Embedded MQTT broker, Uber, Yamaha receivers and Growl -
- -
-
-
-
- Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.
Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).
-Rock on.
-
-
-
- Device Tracker - OwnTracks: Allow entry into passive zones using iBeacons (@pavoni) -
- Tellstick: rewrite to component to address concurrency issues (@stefan-jonasson) -
- Z-Wave: add services to heal and soft reset network (@srcLurker) -
- New component input_slider added (@persandstrom) -
- Light - Hue: Option added to ignore unreachable property (@maddox) -
- Notify: MessageBird support added (@florianholzapfel) -
- HTTP: Failed login attempts are now logged (@fabaff) -
- Vera: rewrite to component to simplify code and organize for reusability (@pavoni) -
- Discovery: support for Squeezebox (Logitech media) server added (@jaharkes) -
- Discovery: fix uPNP discovery crashing some routers (@jaharkes) -
- Switch: Wake on LAN platform added (@joopert) -
- Services for thermostats, notify and media player will now validate passed in parameters (@MartinHjelmare) -
- Switch - Arduino: support for default state and negate port functionality (@tilutza) -
- Switch: PulseAudio loopback now supported (@Cinntax) -
- Sensor: Uber now supported (@robbiet480) -
- Notify: Growl (GNTP) now supported (@robbiet480) -
- Media Player: Yamaha receivers now supported (@aoakeson) -
Breaking changes
--
-
-
-
Automation: support for old deprecated config has been removed
-
- -
-
Tellstick configuration has changed
-
-
tellstick:
- signal_repetitions: X
--
-
- Vera configuration has changed -
vera:
- vera_controller_url: http://192.168.1.161:3480/
- # Optional to exclude devices - this is a list of vera device ids
- exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
- # Optional to import switches as lights - this is a list of vera device ids
- lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
--
- 0.15: Unforked Open Z-Wave, templated service calls, extended scene support and PEP257 compliance. -
- -
-
-
Two weeks has past so here is 0.15! We have been focussing a lot on quality. Making sure the system is more stable and reliable. I usually try to highlight one cool thing in the release notes but this release has 4 exciting announcements!
--
-
- @fabaff has upgraded the codebase to follow the PEP257 documentation standard. -
- @partofthething has migrated us to use the main Python Open Z-Wave library instead of our forked version. -
- To make our automations more powerful, @persandstrom added the option to use templates to dynamically create service calls. This works for automation, Alexa, universal media player, template switch. Learn more. -
- @MartinHjelmare has upgraded our scene support to now support all built-in services and components. -
Besides bug fixes, this release also brings:
-
-
-
- Scene: Converted to a platform based component (@sander76) -
- Scene: Hunter Douglas Powerview now supported (@sander76) -
- Lock: MQTT platform added (@fabaff) -
- Device Tracker: OwnTracks will allow filtering inaccurate GPS locations (@HydrelioxGitHub) -
- Binary Sensor: Wemo Motion now supported (@pavoni, @ryanlaux) -
# Example using templates for service and data in service call.
-# Works for automation, Alexa, universal media player, template switch.
-automation:
- - trigger:
- - platform: state
- entity_id: switch.bathroom
- action:
- service_template: >
- {% if is_state('switch.bathroom', 'on') %}
- switch.turn_on
- {% else %}
- switch.turn_off
- {% endif %}
- data_template:
- entity_id: switch.{{ states('input_select.is') }}
-Breaking Changes
--
-
- Media Player: Attributes to call service play_media has been renamed to
-
media_content_typeandmedia_content_id, to match the corresponding media -player state attributes. This change affects automations, scripts and scenes.
-
diff --git a/components/alarm_control_panel.alarmdecoder/index.html b/components/alarm_control_panel.alarmdecoder/index.html index 8cf8f11cc1..bedea8576b 100644 --- a/components/alarm_control_panel.alarmdecoder/index.html +++ b/components/alarm_control_panel.alarmdecoder/index.html @@ -136,6 +136,9 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/alarm_control_panel.mqtt/index.html b/components/alarm_control_panel.mqtt/index.html
index e743d2aea5..8a38890b0c 100644
--- a/components/alarm_control_panel.mqtt/index.html
+++ b/components/alarm_control_panel.mqtt/index.html
@@ -187,6 +187,9 @@
+
+
+
+
+
+
+
+
+
+
+ + Manual Alarm Control Panel With MQTT Support +
++
This platform extends the manual alarm by adding support for MQTT control of the alarm by a remote device. It can be used to create external keypads which simply change the state of the manual alarm in Home Assistant.
+It’s essentially the opposite of the MQTT Alarm Panel which allows Home Assistant to observe an existing, fully-featured alarm where all of the alarm logic is embedded in that physical device.
+The component will accept the following commands from your Alarm Panel via the command_topic:
-
+
DISARM
+ ARM_HOME
+ ARM_AWAY
+
When the state of the manual alarm changes, Home Assistant will publish one of the following states to the state_topic:
-
+
- ‘disarmed’ +
- ‘armed_home’ +
- ‘armed_away’ +
- ‘pending’ +
- ‘triggered’ +
# Example configuration.yaml entry
+alarm_control_panel:
+ - platform: manual_mqtt
+ state_topic: home/alarm
+ command_topic: home/alarm/set
+Configuration variables:
+All configuration variables from the base manual alarm platform are available:
+-
+
- name (Optional): The name of the alarm. Default is “HA Alarm”. +
- code (Optional): If defined, specifies a code to enable or disable the alarm in the frontend. This code is not required for MQTT interactions. +
- pending_time (Optional): The time in seconds of the pending time before arming the alarm. Default is 60 seconds. +
- trigger_time (Optional): The time in seconds of the trigger time in which the alarm is firing. Default is 120 seconds. +
- disarm_after_trigger (Optional): If true, the alarm will automatically disarm after it has been triggered instead of returning to the previous state. +
Additionally, the following MQTT configuration variables are also available:
+-
+
- state_topic (Required): The MQTT topic HA will publish state updates to. +
- command_topic (Required): The MQTT topic HA will subscribe to to receive commands from a remote device to change the alarm state. +
- qos (Optional): The maximum QoS level for subscribing and publishing to MQTT messages. Default is 0. +
- payload_disarm (Optional): The payload to disarm this Alarm Panel. Default is “DISARM”. +
- payload_arm_home (Optional): The payload to set armed-home mode on this Alarm Panel. Default is “ARM_HOME”. +
- payload_arm_away (Optional): The payload to set armed-away mode on this Alarm Panel. Default is “ARM_AWAY”. +
Examples
+Refer to the Manual Alarm Control page for some real life examples of how to use this panel.
+MQTT Control
+The state of this alarm can be controlled using MQTT. Ensure you’ve configured that before adding this component.
+To change the state of the alarm, publish one of the following messages to the command_topic:
-
+
DISARM
+ ARM_HOME
+ ARM_AWAY
+
To receive state updates from HA, subscribe to the state_topic. Home Assistant will publish a new message whenever the state changes:
-
+
disarmed
+ armed_home
+ armed_away
+ pending
+ triggered
+
There are a few ways that you can use Amazon Echo and Home Assistant together.
-
-
- Turning devices on and off
- Build custom commands to use
- Create a new Flash Briefing source +
- Alternative: use the Emulated Hue component to trick Alexa to thinking Home Assistant is a Philips Hue hub.
No matter which method(s) you decide to use, please remember that Amazon Echo requires an active Internet connection to function. If your Internet is down or experiencing issues (or Amazon’s infrastructure is having issues), none of these methods will work.
Amazon has released Echosim, a website that simulates the Alexa service in your browser. That way it is easy to test your skills without having access to a physical Amazon Echo.
-I just want to turn devices on and off using Echo
-If you just want to be able to turn anything with a switch (like lights, switches, media players, etc) on and off, you should enable the Emulated Hue component. It makes your Home Assistant appear as if it were a Phillips Hue bridge, which Echo works with natively.
-Enabling the Emulated Hue component means you can turn things on and off by simply saying
---Alexa, turn the living room lights on.
-
or
---Alexa, set the living room lights to twenty percent.
-
instead of
---Alexa, tell Home Assistant to turn the living room lights on.
-
or
---Alexa, tell Home Assistant to set the living room lights to twenty percent.
-
In addition, you would need to build custom intents for each device and on/off combination using the below method, whereas everything just works without any extra work by using Emulated Hue.
-Please note that you can use Emulated Hue and the built-in Alexa component side-by-side without issue if you wish.
I want to build custom commands to use with Echo
The built-in Alexa component allows you to integrate Home Assistant into Alexa/Amazon Echo. This component will allow you to query information and call services within Home Assistant by using your voice. Home Assistant offers no built-in sentences but offers a framework for you to define your own.
@@ -164,48 +143,7 @@ WhereAreWeIntent where we are
Alexa, ask Home Assistant where we are
+
-
Configuring Home Assistant
-Out of the box, the component will do nothing. You have to teach it about all intents you want it to answer to. The way it works is that the answer for each intent is based on templates that you define. Each template will have access to the existing states via the states variable but will also have access to all variables defined in the intent.
You can use templates for the values of speech/text, card/title and card/content.
Actions are using the Home Assistant Script Syntax and also have access to the variables from the intent.
-Configuring the Alexa component for the above intents would look like this:
-# Example configuration.yaml entry
-alexa:
- intents:
- WhereAreWeIntent:
- speech:
- type: plaintext
- text: >
- {%- if is_state('device_tracker.paulus', 'home') and
- is_state('device_tracker.anne_therese', 'home') -%}
- You are both home, you silly
- {%- else -%}
- Anne Therese is at {{ states("device_tracker.anne_therese") }}
- and Paulus is at {{ states("device_tracker.paulus") }}
- {% endif %}
-
- LocateIntent:
- action:
- service: notify.notify
- data_template:
- message: The location of {{ User }} has been queried via Alexa.
- speech:
- type: plaintext
- text: >
- {%- for state in states.device_tracker -%}
- {%- if state.name.lower() == User.lower() -%}
- {{ state.name }} is at {{ state.state }}
- {%- elif loop.last -%}
- I am sorry, I do not know where {{ User }} is.
- {%- endif -%}
- {%- else -%}
- Sorry, I don't have any trackers registered.
- {%- endfor -%}
- card:
- type: simple
- title: Sample title
- content: Some more content
-When activated, the Alexa component will have Home Assistant’s native intent support handle the incoming intents. If you want to run actions based on intents, use the intent_script component.
Working With Scenes
One of the most useful applications of Alexa integrations is to call scenes directly. This is easily achieved with some simple setup on the Home Assistant side and by letting Alexa know which scenes you want to run.
First we will configure Alexa. In the Amazon Interaction module add this to the intent schema:
@@ -231,15 +169,16 @@ Custom slot type for scene support.ActivateSceneIntent activate {Scene}
Then add the intent to your Alexa Section in your HA config file:
- ActivateSceneIntent:
- action:
- service: scene.turn_on
- data_template:
- entity_id: scene.{{ Scene | replace(" ", "_") }}
- speech:
- type: plaintext
- text: OK
+Then add the intent to your intent_script section in your HA config file:
+intent_script:
+ ActivateSceneIntent:
+ action:
+ service: scene.turn_on
+ data_template:
+ entity_id: scene.{{ Scene | replace(" ", "_") }}
+ speech:
+ type: plain
+ text: OK
Here we are using templates to take the name we gave to Alexa e.g. downstairs on and replace the space with an underscore so it becomes downstairs_on as Home Assistant expects.
@@ -267,15 +206,16 @@ Custom slot type for script support.
RunScriptIntent run {Script}
-Then add the intent to your Alexa Section in your HA config file:
- RunScriptIntent:
- action:
- service: script.turn_on
- data_template:
- entity_id: script.{{ Script | replace(" ", "_") }}
- speech:
- type: plaintext
- text: OK
+Then add the intent to your intent_script section in your HA config file:
+intent_script:
+ RunScriptIntent:
+ action:
+ service: script.turn_on
+ data_template:
+ entity_id: script.{{ Script | replace(" ", "_") }}
+ speech:
+ type: plain
+ text: OK
Now say Alexa ask homeassistant to run <some script> and Alexa will run that script for you.
@@ -311,32 +251,6 @@ Custom slot type for script support.
Alexa will now respond with a random phrase each time. You can use the include for as many different intents as you like so you only need to create the list once.
-
-As of April 2017, the random filter has been somewhat broken. You’ll get a random response the first time this runs, but subsequent commands will reply with the same randomly-chosen phrase. On reboot, Home Assistant will pick a new random choice, but you’re stuck with that choice till you reboot. To get around that, use the following code in alexa_confirm.yaml:
-
- >
- {% set responses = [
- "OK",
- "Sure",
- "If you insist",
- "Done",
- "No worries",
- "I can do that",
- "Leave it to me",
- "Consider it done",
- "As you wish",
- "By your command",
- "Affirmative",
- "Yes oh revered one",
- "I will",
- "As you decree, so shall it be",
- "No Problem"
- ] %}
- {% set rindex = (range(0, (responses | length - 1) )|random) -%}
- {{responses[rindex]}}
-
-
-
Flash Briefing Skills
As of version 0.31 Home Assistant supports the new Alexa Flash Briefing Skills API. A Flash Briefing Skill adds a new Flash Briefing source that is generated by Home Assistant.
Configuring a Flash Briefing skill in Home Assistant
diff --git a/components/amcrest/index.html b/components/amcrest/index.html
index b17bfac18f..710896b61e 100644
--- a/components/amcrest/index.html
+++ b/components/amcrest/index.html
@@ -160,6 +160,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -304,6 +307,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -322,6 +328,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/android_ip_webcam/index.html b/components/android_ip_webcam/index.html
index 2d417cf76e..f26c4e6a2d 100644
--- a/components/android_ip_webcam/index.html
+++ b/components/android_ip_webcam/index.html
@@ -161,6 +161,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -305,6 +308,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -323,6 +329,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/apcupsd/index.html b/components/apcupsd/index.html
index e0fcb707dc..cb6258c493 100644
--- a/components/apcupsd/index.html
+++ b/components/apcupsd/index.html
@@ -123,6 +123,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -267,6 +270,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -285,6 +291,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/apiai/index.html b/components/apiai/index.html
index 568c978c0b..9b12f419e8 100644
--- a/components/apiai/index.html
+++ b/components/apiai/index.html
@@ -109,70 +109,49 @@
Take a look to “Integrations”, in the left menu, to configure third parties.
Configuring Home Assistant
-Out of the box, the component will do nothing. You have to teach it about all intents you want it to answer to. The way it works is that the answer for each intent is based on templates that you define. Each template will have access to the existing states via the states variable but will also have access to all variables defined in the intent.
-You can use templates for setting speech.
-Actions are using the Home Assistant Script Syntax and also have access to the variables from the intent.
-Example of an Api.ai for the above configuration:
-# Example configuration.yaml entry
-apiai:
- intents:
- GetTemperature:
- speech: We have {{ states.sensor.temperature }} degrees
- async_action: False
- action:
- service: notify.notify
- data_template:
- message: Api.ai has send a request
-
-
-
-Inside an intent we can define this variables:
-
- - speech (Optional): Text or template to return to Api.ai
- - action (Optional): Script definition
- - async_action (Optional): If Home Assistant should execute the action asynchronously (returning response to Api.ai without waiting the action to finish). Should be set to
True if Api.ai is returning the “Cannot connect to Home Assistant or it is taking to long” message, but then you will not be able to use values based on the result of the action. Defaults to False.
-
+When activated, the Alexa component will have Home Assistant’s native intent support handle the incoming intents. If you want to run actions based on intents, use the intent_script component.
Examples
Download this zip and load it in your Api.ai agent (Settings -> Export and Import) for examples intents to use with this configuration:
# Example configuration.yaml entry
apiai:
- intents:
- Temperature:
- speech: The temperature at home is {{ states('sensor.home_temp') }} degrees
- LocateIntent:
- speech: >
- {%- for state in states.device_tracker -%}
- {%- if state.name.lower() == User.lower() -%}
- {{ state.name }} is at {{ state.state }}
- {%- elif loop.last -%}
- I am sorry, I do not know where {{ User }} is.
+
+intent_script:
+ Temperature:
+ speech: The temperature at home is {{ states('sensor.home_temp') }} degrees
+ LocateIntent:
+ speech: >
+ {%- for state in states.device_tracker -%}
+ {%- if state.name.lower() == User.lower() -%}
+ {{ state.name }} is at {{ state.state }}
+ {%- elif loop.last -%}
+ I am sorry, I do not know where {{ User }} is.
+ {%- endif -%}
+ {%- else -%}
+ Sorry, I don't have any trackers registered.
+ {%- endfor -%}
+ WhereAreWeIntent:
+ speech: >
+ {%- if is_state('device_tracker.adri', 'home') and
+ is_state('device_tracker.bea', 'home') -%}
+ You are both home, you silly
+ {%- else -%}
+ Bea is at {{ states("device_tracker.bea") }}
+ and Adri is at {{ states("device_tracker.adri") }}
+ {% endif %}
+ TurnLights:
+ speech: Turning {{ Room }} lights {{ OnOff }}
+ action:
+ - service: notify.pushbullet
+ data_template:
+ message: Someone asked via apiai to turn {{ Room }} lights {{ OnOff }}
+ - service_template: >
+ {%- if OnOff == "on" -%}
+ switch.turn_on
+ {%- else -%}
+ switch.turn_off
{%- endif -%}
- {%- else -%}
- Sorry, I don't have any trackers registered.
- {%- endfor -%}
- WhereAreWeIntent:
- speech: >
- {%- if is_state('device_tracker.adri', 'home') and
- is_state('device_tracker.bea', 'home') -%}
- You are both home, you silly
- {%- else -%}
- Bea is at {{ states("device_tracker.bea") }}
- and Adri is at {{ states("device_tracker.adri") }}
- {% endif %}
- TurnLights:
- speech: Turning {{ Room }} lights {{ OnOff }}
- action:
- - service: notify.pushbullet
- data_template:
- message: Someone asked via apiai to turn {{ Room }} lights {{ OnOff }}
- - service_template: >
- {%- if OnOff == "on" -%}
- switch.turn_on
- {%- else -%}
- switch.turn_off
- {%- endif -%}
- data_template:
- entity_id: "switch.light_{{ Room | replace(' ', '_') }}"
+ data_template:
+ entity_id: "switch.light_{{ Room | replace(' ', '_') }}"
diff --git a/components/apple_tv/index.html b/components/apple_tv/index.html
new file mode 100644
index 0000000000..840d4c0f11
--- /dev/null
+++ b/components/apple_tv/index.html
@@ -0,0 +1,459 @@
+
+
+
+
+
+
+
+
+ Apple TV - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Apple TV
+
+
+
+ The apple_tv platform allows you to control an Apple TV (3rd and 4th generation). See the remote platform if you want to send remote control buttons, e.g. arrow keys.
+
+Currently you must have Home Sharing enabled for this to work. Support for pairing Home Assistant with your device will be supported in a later release.
+
+To use this component, you must first install some system libraries and a compiler. For Debian or a similar system, this should be enough:
+$ sudo apt-get install build-essential libssl-dev libffi-dev python-dev
+
+
+If you want to automatically discover new devices, just make sure you have discovery: in your configuration.yaml file. To manually add one or more Apple TVs to your installation, add the following to your configuration.yaml file:
+# Example configuration.yaml entry
+apple_tv:
+ - host: IP_1
+ login_id: LOGIN_ID_1
+ name: NAME_1
+ start_off: START_OFF_1
+ credentials: CREDENTIALS_1
+ - host: IP_2
+ login_id: LOGIN_ID_2
+ name: NAME_2
+ start_off: START_OFF_2
+ credentials: CREDENTIALS_2
+
+
+Configuration variables:
+
+ - host (Required): The IP-address of the device.
+ - login_id (Required): An identifier used to login to the device, see below.
+ - name (Optional): The name of the device used in the frontend.
+ - start_off (Optional): Set to true if device should start in fake standby.
+ - credentials (Optional): Credentials used for AirPlay playback.
+
+In order to connect to the device you need a login id. The easiest way to obtain this identifier is to use the apple_tv_scan service (described below). Additional information about start_off and credentials can also be found under the guides section.
+ Guides
+ Scanning for devices
+To scan for devices, press the icon in the upper left corner and select the leftmost icon according to the image:
+
+Select apple_tv as domain and apple_tv_scan as service then press the button:
+
+Scanning will be done for three seconds and notification will be shown in the state view with all found devices:
+
+Alternatively you may use the application atvremote. Install it with pip3 install --upgrade pyatv in your Home Assistant environment (note: do not use sudo). Then run atvremote scan to scan for all devices (try again if a device is missing):
+$ atvremote scan
+Found Apple TVs:
+ - Apple TV at 10.0.10.22 (login id: 00000000-1234-5678-9012-345678901234)
+
+Note: You must use 'pair' with devices that have home sharing disabled
+
+
+Just copy and paste the login id from the device you want to add. For more details about atvremote, see: this page.
+ My Apple TV turns on when I restart Home Assistant
+The Apple TV will automatically turn on if a request is sent to it, e.g. if a button is pressed, something is streamed to it via AirPlay or if current state (currently playing) is accessed. This is how Apple has designed it and it will cause problems if you are using HDMI CEC. Every time Home Assistant is started, a new request is sent to the device to figure out what is currently playing. When using CEC, this will wake up your TV and other devices you have configured.
+So, if your TV is randomly turning on, this is probably the reason. As stated, this is by design and there is no real fix for it. There’s also no known way to turn off the Apple TV via the procotol used for communication. You basically have the following options:
+
+ - Do not use this platform
+ - Disable HDMI CEC on your Apple TV
+ - Use “fake standby”
+
+The first two points are quite obvious. Fake standby is a concept implemented in this platform that disables all requests to the device and make it appear as being “off” in the web interface. This will make sure that the device is not woken up, but it will of course not show any information or allow you to control it. It is however easy to turn it on (or off) in the web interface or using an automation with turn_on. To make it more useful, you can write automations that turns it on or off depending on some other device, like the input source on your receiver.
+To put a device into fake standby when starting Home Assistant, add start_off: true to your configuration.
+
+Turning the device on/off in the user interface will not turn the physical device on/off according to description above.
+
+ Setting up device authentication
+If you, when playing media with play_url, get the following error message:
+“This AirPlay connection requires iOS 7.1 or later, OS X 10.10 or later, or iTunes 11.2 or later.”
+then device authentication is required. Press the icon in the upper left corner and select the leftmost icon according to the image below:
+
+Select apple_tv as domain, apple_tv_authenticate as service and enter {'entity_id': 'XXX'} into “Service Data”, but replace XXX with the entity id of your device (e.g. media_player.apple_tv). Press the button and hopefully you are presented with an input dialog asking for a pin code:
+
+If no dialog appears, go back to the states view and display it from there (press CONFIGURE as displayed in the image):
+
+A PIN code should now be visible on your TV, just enter it into the dialog and press “Confirm”. You should see if it succeeded in the state view. Copy the credentials and insert it into your configuration (make sure you copy everything, it should be 81 characters) after credentials: with no line-break:
+# Example configuration.yaml entry
+apple_tv:
+ - host: 10.0.0.20
+ login_id: 00000000-1234-5678-9012-345678901234
+ credentials: 1B8C387DDB59BDF6:CF5ABB6A2C070688F5926ADB7C010F6DF847252C15F9BDB6DA3E09D6591E90E5
+
+
+Restart Home Assistant and you should now be able to use play_url as before.
+ Services
+ Service apple_tv_authenticate
+In order to play media on an Apple TV with device authentication enabled (e.g. ATV4 with tvOS 10.2+), Home Assistant must properly authenticated. This method starts the process and presents the credentials needed for playback as a persistent notification. Please see guide above for usage.
+
+
+
+ Service data attribute
+ Optional
+ Description
+
+
+
+
+ entity_idyes
+ String or list of strings that point at entity_ids of Apple TVs.
+
+
+
+ Service apple_tv_scan
+Scans the local network for Apple TVs. All found devices are presented as a persistent notification.
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/arlo/index.html b/components/arlo/index.html
index b6679488c4..6722f29d55 100644
--- a/components/arlo/index.html
+++ b/components/arlo/index.html
@@ -130,6 +130,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -274,6 +277,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -292,6 +298,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/axis/index.html b/components/axis/index.html
index b0850f9f93..7837f68998 100644
--- a/components/axis/index.html
+++ b/components/axis/index.html
@@ -223,6 +223,9 @@ Any specific levels for triggers needs to be configured on the device.
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -367,6 +370,9 @@ Any specific levels for triggers needs to be configured on the device.
Twilio
+
+ Velbus
+
Velux
@@ -385,6 +391,9 @@ Any specific levels for triggers needs to be configured on the device.
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/binary_sensor.alarmdecoder/index.html b/components/binary_sensor.alarmdecoder/index.html
index 4c5b7d7eb6..c64c842bc5 100644
--- a/components/binary_sensor.alarmdecoder/index.html
+++ b/components/binary_sensor.alarmdecoder/index.html
@@ -248,6 +248,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -260,6 +263,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.android_ip_webcam/index.html b/components/binary_sensor.android_ip_webcam/index.html
index 6bb07df80a..d5278eacf8 100644
--- a/components/binary_sensor.android_ip_webcam/index.html
+++ b/components/binary_sensor.android_ip_webcam/index.html
@@ -247,6 +247,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -259,6 +262,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.apcupsd/index.html b/components/binary_sensor.apcupsd/index.html
index b9fee5f4b9..62532e28b0 100644
--- a/components/binary_sensor.apcupsd/index.html
+++ b/components/binary_sensor.apcupsd/index.html
@@ -151,6 +151,9 @@
Glances
+
+ Google Wifi
+
HDDTemp
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index 0f15e30069..1a21dc47ac 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -274,6 +274,9 @@ This sensor is not suitable for fast state changes because there is a high possi
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -286,6 +289,9 @@ This sensor is not suitable for fast state changes because there is a high possi
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.aurora/index.html b/components/binary_sensor.aurora/index.html
index 4001e20790..b3cf3e0879 100644
--- a/components/binary_sensor.aurora/index.html
+++ b/components/binary_sensor.aurora/index.html
@@ -247,6 +247,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -259,6 +262,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.axis/index.html b/components/binary_sensor.axis/index.html
index c061aebed7..0fa1c07439 100644
--- a/components/binary_sensor.axis/index.html
+++ b/components/binary_sensor.axis/index.html
@@ -253,6 +253,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -265,6 +268,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.bbb_gpio/index.html b/components/binary_sensor.bbb_gpio/index.html
index 6a7a48777b..0e2aca495a 100644
--- a/components/binary_sensor.bbb_gpio/index.html
+++ b/components/binary_sensor.bbb_gpio/index.html
@@ -270,6 +270,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -282,6 +285,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.blink/index.html b/components/binary_sensor.blink/index.html
index a6b29b481d..b6bb5fab20 100644
--- a/components/binary_sensor.blink/index.html
+++ b/components/binary_sensor.blink/index.html
@@ -245,6 +245,9 @@ To get your Blink binary sensors working with Home Assistant, follow the instruc
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -257,6 +260,9 @@ To get your Blink binary sensors working with Home Assistant, follow the instruc
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.bloomsky/index.html b/components/binary_sensor.bloomsky/index.html
index c24bd79478..41bd44032a 100644
--- a/components/binary_sensor.bloomsky/index.html
+++ b/components/binary_sensor.bloomsky/index.html
@@ -265,6 +265,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -277,6 +280,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.command_line/index.html b/components/binary_sensor.command_line/index.html
index d35d912cce..2e2570e9c1 100644
--- a/components/binary_sensor.command_line/index.html
+++ b/components/binary_sensor.command_line/index.html
@@ -302,6 +302,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -314,6 +317,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.concord232/index.html b/components/binary_sensor.concord232/index.html
index 3b31558317..a6d6542ed9 100644
--- a/components/binary_sensor.concord232/index.html
+++ b/components/binary_sensor.concord232/index.html
@@ -248,6 +248,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -260,6 +263,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.digital_ocean/index.html b/components/binary_sensor.digital_ocean/index.html
index afd491fa9c..288f8a0df8 100644
--- a/components/binary_sensor.digital_ocean/index.html
+++ b/components/binary_sensor.digital_ocean/index.html
@@ -154,6 +154,9 @@
Glances
+
+ Google Wifi
+
HDDTemp
diff --git a/components/binary_sensor.ecobee/index.html b/components/binary_sensor.ecobee/index.html
index 112d6cc063..9daf9ad37d 100644
--- a/components/binary_sensor.ecobee/index.html
+++ b/components/binary_sensor.ecobee/index.html
@@ -249,6 +249,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -261,6 +264,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.eight_sleep/index.html b/components/binary_sensor.eight_sleep/index.html
index c251d10260..c68a9c5538 100644
--- a/components/binary_sensor.eight_sleep/index.html
+++ b/components/binary_sensor.eight_sleep/index.html
@@ -244,6 +244,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -256,6 +259,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.enocean/index.html b/components/binary_sensor.enocean/index.html
index 9b6ac1bcee..2bdf2e58f1 100644
--- a/components/binary_sensor.enocean/index.html
+++ b/components/binary_sensor.enocean/index.html
@@ -285,6 +285,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -297,6 +300,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.envisalink/index.html b/components/binary_sensor.envisalink/index.html
index b25cba474c..04620603b7 100644
--- a/components/binary_sensor.envisalink/index.html
+++ b/components/binary_sensor.envisalink/index.html
@@ -248,6 +248,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -260,6 +263,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.ffmpeg_motion/index.html b/components/binary_sensor.ffmpeg_motion/index.html
index 9a5ab072b2..af11d18f06 100644
--- a/components/binary_sensor.ffmpeg_motion/index.html
+++ b/components/binary_sensor.ffmpeg_motion/index.html
@@ -264,6 +264,9 @@ If the ffmpeg process is broken, the sens
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -276,6 +279,9 @@ If the ffmpeg process is broken, the sens
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.ffmpeg_noise/index.html b/components/binary_sensor.ffmpeg_noise/index.html
index 26fb4d7412..e6c71094f8 100644
--- a/components/binary_sensor.ffmpeg_noise/index.html
+++ b/components/binary_sensor.ffmpeg_noise/index.html
@@ -255,6 +255,9 @@ If the ffmpeg process is broken, the sens
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -267,6 +270,9 @@ If the ffmpeg process is broken, the sens
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.flic/index.html b/components/binary_sensor.flic/index.html
index d908f45b4d..72c21bf398 100644
--- a/components/binary_sensor.flic/index.html
+++ b/components/binary_sensor.flic/index.html
@@ -276,6 +276,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -288,6 +291,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.hikvision/index.html b/components/binary_sensor.hikvision/index.html
index 5d1ab0bc6f..1237b8e229 100644
--- a/components/binary_sensor.hikvision/index.html
+++ b/components/binary_sensor.hikvision/index.html
@@ -333,6 +333,9 @@ binary_sensor.home_line_crossing_2
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -345,6 +348,9 @@ binary_sensor.home_line_crossing_2
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.homematic/index.html b/components/binary_sensor.homematic/index.html
index 6bb31da5d5..097e869d1b 100644
--- a/components/binary_sensor.homematic/index.html
+++ b/components/binary_sensor.homematic/index.html
@@ -256,6 +256,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -268,6 +271,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.http/index.html b/components/binary_sensor.http/index.html
index b118e38fe6..1ebe337167 100644
--- a/components/binary_sensor.http/index.html
+++ b/components/binary_sensor.http/index.html
@@ -290,6 +290,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -302,6 +305,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.insteon_plm/index.html b/components/binary_sensor.insteon_plm/index.html
index 1a7708339e..315200d4b8 100644
--- a/components/binary_sensor.insteon_plm/index.html
+++ b/components/binary_sensor.insteon_plm/index.html
@@ -246,6 +246,9 @@ component.
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -258,6 +261,9 @@ component.
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.iss/index.html b/components/binary_sensor.iss/index.html
index a8b0968f73..33f973f3c6 100644
--- a/components/binary_sensor.iss/index.html
+++ b/components/binary_sensor.iss/index.html
@@ -253,6 +253,9 @@ If you set show_on_map show_on_map Nest component configured to u
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -303,6 +306,9 @@ You must have the Nest component configured to u
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.netatmo/index.html b/components/binary_sensor.netatmo/index.html
index 07088c4e3f..bfa27dc066 100644
--- a/components/binary_sensor.netatmo/index.html
+++ b/components/binary_sensor.netatmo/index.html
@@ -296,6 +296,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -308,6 +311,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.nx584/index.html b/components/binary_sensor.nx584/index.html
index 5148da2163..f6982d762f 100644
--- a/components/binary_sensor.nx584/index.html
+++ b/components/binary_sensor.nx584/index.html
@@ -270,6 +270,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -282,6 +285,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.octoprint/index.html b/components/binary_sensor.octoprint/index.html
index 5253da8fd1..015d500fcf 100644
--- a/components/binary_sensor.octoprint/index.html
+++ b/components/binary_sensor.octoprint/index.html
@@ -264,6 +264,9 @@ You must have the OctoPrint component confi
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -276,6 +279,9 @@ You must have the OctoPrint component confi
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.pilight/index.html b/components/binary_sensor.pilight/index.html
index c2adc08d5b..2d64ad400b 100644
--- a/components/binary_sensor.pilight/index.html
+++ b/components/binary_sensor.pilight/index.html
@@ -8,7 +8,7 @@
Pilight Binary Sensor - Home Assistant
-
+
@@ -16,12 +16,12 @@
-
+
-
+
@@ -74,8 +74,8 @@
- This component implement the pilight hub binary sensor functionality.
-Two type of pilight binary sensor configuration available. A normal sensor which send the on and off state cyclical and a trigger sensor which send only a trigger when an event happend (for example lots of cheap PIR motion detector) (see example configuration below).
+ The pilight binary sensor platform implement the pilight hub binary sensor functionality. Two type of Pilight binary sensor configuration available. A normal sensor which send the on and off state cyclical and a trigger sensor which send only a trigger when an event happend (for example lots of cheap PIR motion detector).
+To enable a Pilight binary sensor in your installation, add the following to your configuration.yaml file:
# Example configuration.yml entry
binary_sensor:
- platform: pilight
@@ -276,6 +276,9 @@ Two type of pilight binary sensor configuration available. A normal sensor which
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -288,6 +291,9 @@ Two type of pilight binary sensor configuration available. A normal sensor which
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.ping/index.html b/components/binary_sensor.ping/index.html
index 23915c3ca9..63ef868267 100644
--- a/components/binary_sensor.ping/index.html
+++ b/components/binary_sensor.ping/index.html
@@ -260,6 +260,9 @@ When run on Windows systems, the round trip time attributes are rounded to the n
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -272,6 +275,9 @@ When run on Windows systems, the round trip time attributes are rounded to the n
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.raspihats/index.html b/components/binary_sensor.raspihats/index.html
index e6aca725d3..506ad28b7c 100644
--- a/components/binary_sensor.raspihats/index.html
+++ b/components/binary_sensor.raspihats/index.html
@@ -280,6 +280,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -292,6 +295,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.rest/index.html b/components/binary_sensor.rest/index.html
index b998dd0001..65d6c3fbdc 100644
--- a/components/binary_sensor.rest/index.html
+++ b/components/binary_sensor.rest/index.html
@@ -323,6 +323,9 @@ User-Agent: Home Assistant
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -335,6 +338,9 @@ User-Agent: Home Assistant
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.rfxtrx/index.html b/components/binary_sensor.rfxtrx/index.html
index b688e2dea6..ef8b249dfc 100644
--- a/components/binary_sensor.rfxtrx/index.html
+++ b/components/binary_sensor.rfxtrx/index.html
@@ -347,6 +347,9 @@ to configure your new devices and leave it off otherwise.
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -359,6 +362,9 @@ to configure your new devices and leave it off otherwise.
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.ring/index.html b/components/binary_sensor.ring/index.html
index 1b229d3346..c665e6eff5 100644
--- a/components/binary_sensor.ring/index.html
+++ b/components/binary_sensor.ring/index.html
@@ -259,6 +259,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -271,6 +274,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.rpi_gpio/index.html b/components/binary_sensor.rpi_gpio/index.html
index 2d901e1a66..acb6011721 100644
--- a/components/binary_sensor.rpi_gpio/index.html
+++ b/components/binary_sensor.rpi_gpio/index.html
@@ -267,6 +267,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -279,6 +282,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.rpi_pfio/index.html b/components/binary_sensor.rpi_pfio/index.html
index 9e21e014dc..7a5cd6cbef 100644
--- a/components/binary_sensor.rpi_pfio/index.html
+++ b/components/binary_sensor.rpi_pfio/index.html
@@ -270,6 +270,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -282,6 +285,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.sleepiq/index.html b/components/binary_sensor.sleepiq/index.html
index 5fdd2d393c..b307b041cd 100644
--- a/components/binary_sensor.sleepiq/index.html
+++ b/components/binary_sensor.sleepiq/index.html
@@ -243,6 +243,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -255,6 +258,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.spc/index.html b/components/binary_sensor.spc/index.html
index 0a0214650e..34c0a1296c 100644
--- a/components/binary_sensor.spc/index.html
+++ b/components/binary_sensor.spc/index.html
@@ -245,6 +245,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -257,6 +260,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.tcp/index.html b/components/binary_sensor.tcp/index.html
index 6efe77f14a..e801eeeb2c 100644
--- a/components/binary_sensor.tcp/index.html
+++ b/components/binary_sensor.tcp/index.html
@@ -260,6 +260,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -272,6 +275,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.template/index.html b/components/binary_sensor.template/index.html
index d165aa849f..9f0c33b61e 100644
--- a/components/binary_sensor.template/index.html
+++ b/components/binary_sensor.template/index.html
@@ -361,6 +361,9 @@ and z-wave multisensor presence sensors.
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -373,6 +376,9 @@ and z-wave multisensor presence sensors.
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.threshold/index.html b/components/binary_sensor.threshold/index.html
index 3d4050fc16..e2ab8ff6f8 100644
--- a/components/binary_sensor.threshold/index.html
+++ b/components/binary_sensor.threshold/index.html
@@ -252,6 +252,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -264,6 +267,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.trend/index.html b/components/binary_sensor.trend/index.html
index decbd2db16..b3af66a2e6 100644
--- a/components/binary_sensor.trend/index.html
+++ b/components/binary_sensor.trend/index.html
@@ -277,6 +277,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -289,6 +292,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.velbus/index.html b/components/binary_sensor.velbus/index.html
new file mode 100644
index 0000000000..262fbde3c9
--- /dev/null
+++ b/components/binary_sensor.velbus/index.html
@@ -0,0 +1,366 @@
+
+
+
+
+
+
+
+
+ Velbus sensors - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Velbus Sensors
+
+
+
+ The velbus binary_sensor allows you to control Velbus connected wall switches.
+To use your Velbus wall switches in your installation, add the following to your configuration.yaml file:
+# Example configuration.yaml entry
+
+binary_sensor:
+ - platform: velbus
+ devices:
+ - name: Wall Switch 1
+ module: 0xda
+ channel: 4
+ - name: Wall Switch 2
+ module: 0xbc
+ channel: 1
+ is_pushbutton: true
+
+
+Configuration variables:
+
+ - devices array (Required): The array contains the binary sensors to configure
+
+ - name (Required): Name of the binary sensor.
+ - module (Required): The hexadecimal module address
+ - channel (Required): The channel number in the module.
+ - is_pushbutton (Optional): Booelan to indicate if a wall switch is a push button or not (default: false)
+
+
+
+For hub configuration, see the Velbus component.
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/binary_sensor.vera/index.html b/components/binary_sensor.vera/index.html
index 49a8bf1711..f0e6001fd8 100644
--- a/components/binary_sensor.vera/index.html
+++ b/components/binary_sensor.vera/index.html
@@ -259,6 +259,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -271,6 +274,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.verisure/index.html b/components/binary_sensor.verisure/index.html
index 7d57c1749c..65e143c3ae 100644
--- a/components/binary_sensor.verisure/index.html
+++ b/components/binary_sensor.verisure/index.html
@@ -254,6 +254,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -266,6 +269,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.wink/index.html b/components/binary_sensor.wink/index.html
index ad946cba7f..01fe04b55e 100644
--- a/components/binary_sensor.wink/index.html
+++ b/components/binary_sensor.wink/index.html
@@ -285,6 +285,9 @@ The above devices are confimed to work, but others may work as well.
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -297,6 +300,9 @@ The above devices are confimed to work, but others may work as well.
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.workday/index.html b/components/binary_sensor.workday/index.html
index fcd349f57f..1cc7f05ef7 100644
--- a/components/binary_sensor.workday/index.html
+++ b/components/binary_sensor.workday/index.html
@@ -265,6 +265,9 @@ If you use the sensor for Canada (CA) wit
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -277,6 +280,9 @@ If you use the sensor for Canada (CA) wit
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.xiaomi/index.html b/components/binary_sensor.xiaomi/index.html
new file mode 100644
index 0000000000..5b2c11175b
--- /dev/null
+++ b/components/binary_sensor.xiaomi/index.html
@@ -0,0 +1,604 @@
+
+
+
+
+
+
+
+
+ Xiaomi Binary Sensor - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Xiaomi Binary Sensor
+
+
+
+ The xiaomi binary sensor platform allows you to get data from your Xiaomi binary sensors.
+The requirement is that you have setup the xiaomi component.
+ Type of sensors supported
+
+ - Motion
+ - Door / Window
+ - Smoke
+ - Gas
+ - Xiaomi Wireless Button
+ - Xiaomi Cube
+
+ Automation examples
+ Motion
+- alias: If there is motion and its dark turn on the gateway light
+ trigger:
+ platform: state
+ entity_id: binary_sensor.motion_sensor_158d000xxxxxc2
+ from: 'off'
+ to: 'on'
+ condition:
+ condition: numeric_state
+ entity_id: sensor.illumination_34ce00xxxx11
+ below: 300
+ action:
+ service: light.turn_on
+ entity_id: light.gateway_light_34ce00xxxx11
+ data:
+ brightness: 5
+- alias: If there no motion for 5 minutes turn off the gateway light
+ trigger:
+ platform: state
+ entity_id: binary_sensor.motion_sensor_158d000xxxxxc2
+ from: 'on'
+ to: 'off'
+ for:
+ minutes: 5
+ action:
+ service: light.turn_off
+ entity_id: light.gateway_light_34ce00xxxx11
+
+
+ Door and/or Window
+- alias: If the window is open turn off the radiator
+ trigger:
+ platform: state
+ entity_id: binary_sensor.door_window_sensor_158d000xxxxxc2
+ from: 'off'
+ to: 'on'
+ action:
+ service: climate.set_operation_mode
+ entity_id: climate.livingroom
+ data:
+ operation_mode: 'Off'
+- alias: If the window is closed for 5 minutes turn on the radiator again
+ trigger:
+ platform: state
+ entity_id: binary_sensor.door_window_sensor_158d000xxxxxc2
+ from: 'on'
+ to: 'off'
+ for:
+ minutes: 5
+ action:
+ service: climate.set_operation_mode
+ entity_id: climate.livingroom
+ data:
+ operation_mode: 'Smart schedule'
+
+
+ Smoke
+- alias: Send notification on fire alarm
+ trigger:
+ platform: state
+ entity_id: binary_sensor.smoke_sensor_158d0001574899
+ from: 'off'
+ to: 'on'
+ action:
+ - service: notify.html5
+ data:
+ title: Fire alarm!
+ message: Fire/Smoke detected!
+ - service: xiaomi.play_ringtone
+ data:
+ gw_mac: xxxxxxxxxxxx
+ ringtone_id: 2
+ ringtone_vol: 100
+
+
+ Gas
+- alias: Send notification on gas alarm
+ trigger:
+ platform: state
+ entity_id: binary_sensor.natgas_sensor_158dxxxxxxxxxx
+ from: 'off'
+ to: 'on'
+ action:
+ - service: notify.html5
+ data_template:
+ title: Gas alarm!
+ message: 'Gas with a density of {{ states.binary_sensor.natgas_sensor_158dxxxxxxxxxx.attributes.density }} detected.'
+
+
+ Xiaomi Wireless Button
+Available events are single, double, hold, long_click_press and long_click_release. For Square version (Aqara brand) only single and double events are supported. Furthermore the space between two clicks to generate a double click must be quite large now.
+- alias: Toggle dining light on single press
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.switch_158d000xxxxxc2
+ click_type: single
+ action:
+ service: switch.toggle
+ entity_id: switch.wall_switch_left_158d000xxxxx01
+- alias: Toggle couch light on double click
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.switch_158d000xxxxxc2
+ click_type: double
+ action:
+ service: switch.toggle
+ entity_id: switch.wall_switch_right_158d000xxxxx01
+- alias: Let a dog bark on long press
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.switch_158d000xxxxxc2
+ click_type: long_click_press
+ action:
+ service: xiaomi.play_ringtone
+ data:
+ gw_mac: xxxxxxxxxxxx
+ ringtone_id: 8
+ ringtone_vol: 8
+
+
+ Xiaomi Cube
+Available events are flip90, flip180, move, tap_twice, shake_air, swing, alert, free_fall and rotate.
+- alias: Cube event flip90
+ trigger:
+ platform: event
+ event_type: cube_action
+ event_data:
+ entity_id: binary_sensor.cube_15xxxxxxxxxxxx
+ action_type: flip90
+ action:
+ - service: light.turn_on
+ entity_id: light.gateway_light_28xxxxxxxxxx
+ data:
+ color_name: "springgreen"
+- alias: Cube event flip180
+ trigger:
+ platform: event
+ event_type: cube_action
+ event_data:
+ entity_id: binary_sensor.cube_15xxxxxxxxxxxx
+ action_type: flip180
+ action:
+ - service: light.turn_on
+ entity_id: light.gateway_light_28xxxxxxxxxx
+ data:
+ color_name: "darkviolet"
+- alias: Cube event move
+ trigger:
+ platform: event
+ event_type: cube_action
+ event_data:
+ entity_id: binary_sensor.cube_15xxxxxxxxxxxx
+ action_type: move
+ action:
+ - service: light.turn_on
+ entity_id: light.gateway_light_28xxxxxxxxxx
+ data:
+ color_name: "gold"
+- alias: Cube event tap_twice
+ trigger:
+ platform: event
+ event_type: cube_action
+ event_data:
+ entity_id: binary_sensor.cube_15xxxxxxxxxxxx
+ action_type: tap_twice
+ action:
+ - service: light.turn_on
+ entity_id: light.gateway_light_28xxxxxxxxxx
+ data:
+ color_name: "deepskyblue"
+- alias: Cube event shake_air
+ trigger:
+ platform: event
+ event_type: cube_action
+ event_data:
+ entity_id: binary_sensor.cube_15xxxxxxxxxxxx
+ action_type: shake_air
+ action:
+ - service: light.turn_on
+ entity_id: light.gateway_light_28xxxxxxxxxx
+ data:
+ color_name: "blue"
+
+
+#### Aqara Wireless Switch
+The Aqara Wireless Switch is available as single-key and double-key version. Each key behaves like the Wireless Button limited to the click event single. The double key version adds a third device called binary_sensor.wall_switch_both_158xxxxxxxxx12 which reports a click event called both if both keys are pressed.
+- alias: Decrease brightness of the gateway light
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.wall_switch_left_158xxxxxxxxx12
+ click_type: single
+ action:
+ service: light.turn_on
+ entity_id: light.gateway_light_34xxxxxxxx13
+ data_template:
+ brightness: >-
+ {% if states.light.gateway_light_34xxxxxxxx13.attributes.brightness %}
+ {% if states.light.gateway_light_34xxxxxxxx13.attributes.brightness - 60 >= 10 %}
+ {{states.light.gateway_light_34xxxxxxxx13.attributes.brightness - 60}}
+ {% else %}
+ {{states.light.gateway_light_34xxxxxxxx13.attributes.brightness}}
+ {% endif %}
+ {% else %}
+ 10
+ {% endif %}
+
+- alias: Increase brightness of the gateway light
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.wall_switch_right_158xxxxxxxxx12
+ click_type: single
+ action:
+ service: light.turn_on
+ entity_id: light.gateway_light_34xxxxxxxx13
+ data_template:
+ brightness: >-
+ {% if states.light.gateway_light_34xxxxxxxx13.attributes.brightness %}
+ {% if states.light.gateway_light_34xxxxxxxx13.attributes.brightness + 60 <= 255 %}
+ {{states.light.gateway_light_34xxxxxxxx13.attributes.brightness + 60}}
+ {% else %}
+ {{states.light.gateway_light_34xxxxxxxx13.attributes.brightness}}
+ {% endif %}
+ {% else %}
+ 10
+ {% endif %}
+
+- alias: Turn off the gateway light
+ trigger:
+ platform: event
+ event_type: click
+ event_data:
+ entity_id: binary_sensor.wall_switch_both_158xxxxxxxxx12
+ click_type: both
+ action:
+ service: light.turn_off
+ entity_id: light.gateway_light_34xxxxxxxx13
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/binary_sensor.zha/index.html b/components/binary_sensor.zha/index.html
index af8a525d5f..75d3ae0594 100644
--- a/components/binary_sensor.zha/index.html
+++ b/components/binary_sensor.zha/index.html
@@ -246,6 +246,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -258,6 +261,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.zigbee/index.html b/components/binary_sensor.zigbee/index.html
index da9607ab03..e77971df01 100644
--- a/components/binary_sensor.zigbee/index.html
+++ b/components/binary_sensor.zigbee/index.html
@@ -264,6 +264,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -276,6 +279,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor.zwave/index.html b/components/binary_sensor.zwave/index.html
index 9dd884bb7c..5481fba38b 100644
--- a/components/binary_sensor.zwave/index.html
+++ b/components/binary_sensor.zwave/index.html
@@ -261,6 +261,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -273,6 +276,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/binary_sensor/index.html b/components/binary_sensor/index.html
index 7a01b764ec..32b6da73c3 100644
--- a/components/binary_sensor/index.html
+++ b/components/binary_sensor/index.html
@@ -247,6 +247,9 @@
Trend Binary Sensor
+
+ Velbus sensors
+
Vera Binary Sensor
@@ -259,6 +262,9 @@
Workday Binary Sensor
+
+ Xiaomi Binary Sensor
+
Z-Wave Binary Sensor
diff --git a/components/blink/index.html b/components/blink/index.html
index a0e755c99d..b1f00043b8 100644
--- a/components/blink/index.html
+++ b/components/blink/index.html
@@ -171,6 +171,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -315,6 +318,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -333,6 +339,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/bloomsky/index.html b/components/bloomsky/index.html
index 65943b9080..31f6204d27 100644
--- a/components/bloomsky/index.html
+++ b/components/bloomsky/index.html
@@ -130,6 +130,9 @@
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -274,6 +277,9 @@
Twilio
+
+ Velbus
+
Velux
@@ -292,6 +298,9 @@
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/comfoconnect/index.html b/components/comfoconnect/index.html
index d1ac024b24..b653053be9 100644
--- a/components/comfoconnect/index.html
+++ b/components/comfoconnect/index.html
@@ -146,6 +146,9 @@ Note that it’s not possible to have multiple connection to the bridge at the s
Android IP Webcam
+
+ Apple TV
+
Arlo
@@ -290,6 +293,9 @@ Note that it’s not possible to have multiple connection to the bridge at the s
Twilio
+
+ Velbus
+
Velux
@@ -308,6 +314,9 @@ Note that it’s not possible to have multiple connection to the bridge at the s
Wink
+
+ Xiaomi Gateway
+
Z-Wave
diff --git a/components/conversation/index.html b/components/conversation/index.html
index 9158e338b3..1e46d0c54a 100644
--- a/components/conversation/index.html
+++ b/components/conversation/index.html
@@ -74,7 +74,7 @@
- The conversation component can process sentences into commands for Home Assistant. It currently has built in functionality to recognize turn <Friendly Name> <on/off>, but custom phrases can be added through configuration.
+ The conversation component can process sentences into commands for Home Assistant. It currently has built in functionality to recognize turn <Friendly Name> <on/off>, but custom phrases can be added through configuration.
To enable the conversation option in your installation, add the following to your configuration.yaml file:
# Example base configuration.yaml entry
conversation:
@@ -89,8 +89,15 @@
service: input_boolean.toggle
-The action keyword uses script
-syntax.
+The action keyword uses script syntax.
+To use the conversation component with the shopping list component add an intent.
+# Example configuration.yaml entry
+conversation:
+ intents:
+ ShoppingListAddItem:
+ - Add {item} to my shopping list
+
+
When this component is active and you are using a supported browser voice commands will be activated in the frontend. Browse to the demo using Chrome or Chromium to see it in action.
diff --git a/components/cover.command_line/index.html b/components/cover.command_line/index.html
index 1b25791d31..a0bbe35a99 100644
--- a/components/cover.command_line/index.html
+++ b/components/cover.command_line/index.html
@@ -214,6 +214,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.garadget/index.html b/components/cover.garadget/index.html
index f6d8683cdd..6da5aecedd 100644
--- a/components/cover.garadget/index.html
+++ b/components/cover.garadget/index.html
@@ -231,6 +231,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.homematic/index.html b/components/cover.homematic/index.html
index 6e3979a809..20f69ca640 100644
--- a/components/cover.homematic/index.html
+++ b/components/cover.homematic/index.html
@@ -172,6 +172,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.isy994/index.html b/components/cover.isy994/index.html
index f0f92b1aa8..b66b283ebd 100644
--- a/components/cover.isy994/index.html
+++ b/components/cover.isy994/index.html
@@ -172,6 +172,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.knx/index.html b/components/cover.knx/index.html
index 74cafd5c5f..a07da34722 100644
--- a/components/cover.knx/index.html
+++ b/components/cover.knx/index.html
@@ -190,6 +190,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.lutron_caseta/index.html b/components/cover.lutron_caseta/index.html
index 305c2136ac..3a946acb0d 100644
--- a/components/cover.lutron_caseta/index.html
+++ b/components/cover.lutron_caseta/index.html
@@ -169,6 +169,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.mqtt/index.html b/components/cover.mqtt/index.html
index 0bbc56e2ab..39940d978e 100644
--- a/components/cover.mqtt/index.html
+++ b/components/cover.mqtt/index.html
@@ -274,6 +274,9 @@ state from state_topic. If these messages
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.myq/index.html b/components/cover.myq/index.html
index 9ee07fa959..b11fda7625 100644
--- a/components/cover.myq/index.html
+++ b/components/cover.myq/index.html
@@ -160,6 +160,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.mysensors/index.html b/components/cover.mysensors/index.html
index 7b33c314d5..ca793b7a4e 100644
--- a/components/cover.mysensors/index.html
+++ b/components/cover.mysensors/index.html
@@ -329,6 +329,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.opengarage/index.html b/components/cover.opengarage/index.html
index b4932c85d4..5827e1fae7 100644
--- a/components/cover.opengarage/index.html
+++ b/components/cover.opengarage/index.html
@@ -238,6 +238,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.rfxtrx/index.html b/components/cover.rfxtrx/index.html
index a5722246a5..393a00814a 100644
--- a/components/cover.rfxtrx/index.html
+++ b/components/cover.rfxtrx/index.html
@@ -206,6 +206,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.rpi_gpio/index.html b/components/cover.rpi_gpio/index.html
index 479e5aba8c..8d8921b0d1 100644
--- a/components/cover.rpi_gpio/index.html
+++ b/components/cover.rpi_gpio/index.html
@@ -205,6 +205,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.scsgate/index.html b/components/cover.scsgate/index.html
index fa93f7eb7f..2aa1d30fbd 100644
--- a/components/cover.scsgate/index.html
+++ b/components/cover.scsgate/index.html
@@ -185,6 +185,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.template/index.html b/components/cover.template/index.html
index 794dd296dd..28f46bca5d 100644
--- a/components/cover.template/index.html
+++ b/components/cover.template/index.html
@@ -221,6 +221,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.vera/index.html b/components/cover.vera/index.html
index 3d5ac18be1..912b7631af 100644
--- a/components/cover.vera/index.html
+++ b/components/cover.vera/index.html
@@ -176,6 +176,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.wink/index.html b/components/cover.wink/index.html
index 7ec96cafef..6f919ca591 100644
--- a/components/cover.wink/index.html
+++ b/components/cover.wink/index.html
@@ -199,6 +199,9 @@ The above devices are confimed to work, but others may work as well.
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover.xiaomi/index.html b/components/cover.xiaomi/index.html
new file mode 100644
index 0000000000..c942fee445
--- /dev/null
+++ b/components/cover.xiaomi/index.html
@@ -0,0 +1,235 @@
+
+
+
+
+
+
+
+
+ Xiaomi Cover - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/cover.zwave/index.html b/components/cover.zwave/index.html
index 31ce01698f..4511459c44 100644
--- a/components/cover.zwave/index.html
+++ b/components/cover.zwave/index.html
@@ -178,6 +178,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/cover/index.html b/components/cover/index.html
index a9722b05b4..eb8f5586f5 100644
--- a/components/cover/index.html
+++ b/components/cover/index.html
@@ -228,6 +228,9 @@
Wink Cover
+
+ Xiaomi Cover
+
Z-Wave Cover
diff --git a/components/device_tracker.tplink/index.html b/components/device_tracker.tplink/index.html
index ee9b91c7d3..f1b118473c 100644
--- a/components/device_tracker.tplink/index.html
+++ b/components/device_tracker.tplink/index.html
@@ -121,6 +121,9 @@ TP-Link devices typically only allow one login at a time to the admin console.
Related components
+ -
+ TPLink Bulb
+
-
TPLink Switch
diff --git a/components/device_tracker.xiaomi/index.html b/components/device_tracker.xiaomi/index.html
index 2d4d933376..a0d6471437 100644
--- a/components/device_tracker.xiaomi/index.html
+++ b/components/device_tracker.xiaomi/index.html
@@ -105,6 +105,29 @@
This is a platform for
the Device Tracker component.
+
+
+ Related components
+
Category Presence Detection
diff --git a/components/digital_ocean/index.html b/components/digital_ocean/index.html
index 10dad9573e..db89e44e83 100644
--- a/components/digital_ocean/index.html
+++ b/components/digital_ocean/index.html
@@ -127,6 +127,9 @@
-
Android IP Webcam
+ -
+ Apple TV
+
-
Arlo
@@ -271,6 +274,9 @@
-
Twilio
+ -
+ Velbus
+
-
Velux
@@ -289,6 +295,9 @@
-
Wink
+ -
+ Xiaomi Gateway
+
-
Z-Wave
diff --git a/components/dyson/index.html b/components/dyson/index.html
index 5c9564ed19..88f0b230a9 100644
--- a/components/dyson/index.html
+++ b/components/dyson/index.html
@@ -93,7 +93,7 @@
- username (Required): Dyson account username (email address)
- password (Required): Dyson account password
- - language (Required): Dyson account language country code. Known working codes:
FR, NL, UK, AU. But others codes should work.
+ - language (Required): Dyson account language country code. Known working codes:
FR, NL, GB, AU. But others codes should work.
- devices (Optional): List of devices
- device_id (Required): Device ID. Available in the mobiles applications (Settings page)
@@ -156,6 +156,9 @@ To find devices IP address, you can use your router or
Twilio
+ -
+ Velbus
+
-
Velux
@@ -318,6 +324,9 @@ To find devices IP address, you can use your router or som
-
MQTT Fan
+ -
+ Velbus Fans
+
-
Wink Fan
diff --git a/components/fan.velbus/index.html b/components/fan.velbus/index.html
new file mode 100644
index 0000000000..ff7d0b19dd
--- /dev/null
+++ b/components/fan.velbus/index.html
@@ -0,0 +1,221 @@
+
+
+
+
+
+
+
+
+ Velbus Fans - Home Assistant
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Velbus Fans
+
+
+
+ The velbus fan allows you to control Velbus connected fans.
+To use your Velbus fans in your installation, add the following to your configuration.yaml file:
+# Example configuration.yaml entry
+
+fan:
+ - platform: velbus
+ devices:
+ - name: Fan 1
+ module: 0xda
+ channel_low: 4
+ channel_medium: 3
+ channel_high: 2
+
+
+Configuration variables:
+
+ - devices array (Required): The array contains the fans to configure
+
+ - name (Required): Name of the fan.
+ - module (Required): The hexadecimal module address
+ - channel_low (Required): The channel number in the module for low-speed.
+ - channel_medium (Required): The channel number in the module for medium-speed.
+ - channel_high (Required): The channel number in the module for high-speed.
+
+
+
+For hub configuration, see the Velbus component.
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/components/fan.wink/index.html b/components/fan.wink/index.html
index 1f2a7b0cdc..e76e7ef53a 100644
--- a/components/fan.wink/index.html
+++ b/components/fan.wink/index.html
@@ -152,6 +152,9 @@ The above devices are confimed to work, but others may work as well.
-
MQTT Fan
+ -
+ Velbus Fans
+
-
Wink Fan
diff --git a/components/fan.zwave/index.html b/components/fan.zwave/index.html
index 70f8fec596..1d79725e0e 100644
--- a/components/fan.zwave/index.html
+++ b/components/fan.zwave/index.html
@@ -138,6 +138,9 @@
-
MQTT Fan
+ -
+ Velbus Fans
+
-
Wink Fan
diff --git a/components/fan/index.html b/components/fan/index.html
index 2556e7e48a..c4113071f6 100644
--- a/components/fan/index.html
+++ b/components/fan/index.html
@@ -103,6 +103,9 @@
-
MQTT Fan
+ -
+ Velbus Fans
+
-
Wink Fan
diff --git a/components/feedreader/index.html b/components/feedreader/index.html
index 7d65e75451..da29c6eb07 100644
--- a/components/feedreader/index.html
+++ b/components/feedreader/index.html
@@ -112,14 +112,14 @@
notification_id: "{{ trigger.event.data.title }}"
-*Any field under the <entry> tag in the feed can be used for example trigger.event.data.content will get the body of the feed entry.
-For more advanced use cases, a custom component registering to the feedreader event type could be used instead:
-For a drop in packaged complete example of Feedreader, you can use the PodCast notifier.
+Any field under the <entry> tag in the feed can be used for example trigger.event.data.content will get the body of the feed entry.
+For more advanced use cases, a custom component registering to the feedreader event type could be used instead:
EVENT_FEEDREADER = "feedreader"
hass.bus.listen(EVENT_FEEDREADER, event_listener)
To get started developing custom components, please refer to the developers documentation
+For a drop in packaged complete example of Feedreader, you can use the PodCast notifier.