From 9ff55add23312c7e2d89dd4b176ecdaf5635f62f Mon Sep 17 00:00:00 2001 From: Travis CI Date: Sat, 7 Oct 2017 22:49:56 +0000 Subject: [PATCH] Site updated at 2017-10-07 22:49:55 UTC --- addons/configurator/index.html | 2 +- addons/dhcp_server/index.html | 2 +- addons/dnsmasq/index.html | 2 +- addons/mariadb/index.html | 2 +- addons/samba/index.html | 2 +- atom.xml | 18 +- .../index.html | 2 +- .../index.html | 2 +- .../2015/02/08/looking-at-the-past/index.html | 2 +- blog/2015/02/24/streaming-updates/index.html | 2 +- .../index.html | 2 +- .../12/07/influxdb-and-grafana/index.html | 2 +- .../index.html | 2 +- .../index.html | 2 +- .../index.html | 2 +- .../index.html | 6 +- .../esp8266-and-micropython-part1/index.html | 2 +- blog/2016/08/16/we-have-apps-now/index.html | 2 +- .../notify-group-reload-api-pihole/index.html | 2 +- .../08/hassbian-rest-digital-ocean/index.html | 2 +- .../index.html | 2 +- .../12/03/remote-websockets-sonarr/index.html | 2 +- blog/2016/12/19/thank-you/index.html | 2 +- .../index.html | 2 +- blog/2017/01/28/face-coffee-wink/index.html | 2 +- blog/2017/02/03/babyphone/index.html | 2 +- .../index.html | 4 +- .../2017/03/28/http-to-mqtt-bridge/index.html | 2 +- blog/2017/04/01/thomas-krenn-award/index.html | 2 +- .../04/22/ikea-tradfri-spotify/index.html | 4 +- blog/2017/06/04/release-46/index.html | 2 +- blog/2017/07/29/release-50/index.html | 2 +- blog/2017/09/09/release-53/index.html | 2 +- blog/2017/10/07/release-55/index.html | 12 +- blog/categories/announcements/atom.xml | 2 +- blog/categories/community/atom.xml | 2 +- blog/categories/device-tracking/atom.xml | 2 +- blog/categories/esp8266/atom.xml | 4 +- blog/categories/how-to/atom.xml | 4 +- blog/categories/ibeacons/atom.xml | 2 +- blog/categories/internet-of-things/atom.xml | 6 +- blog/categories/iot-data/atom.xml | 2 +- blog/categories/media/atom.xml | 2 +- blog/categories/merchandise/atom.xml | 2 +- blog/categories/micropython/atom.xml | 4 +- blog/categories/mqtt/atom.xml | 4 +- blog/categories/organisation/atom.xml | 2 +- blog/categories/owntracks/atom.xml | 2 +- blog/categories/presence-detection/atom.xml | 2 +- .../public-service-announcement/atom.xml | 2 +- blog/categories/release-notes/atom.xml | 12 +- blog/categories/survey/atom.xml | 2 +- blog/categories/talks/atom.xml | 2 +- blog/categories/technology/atom.xml | 2 +- blog/categories/user-stories/atom.xml | 2 +- blog/categories/video/atom.xml | 2 +- blog/categories/website/atom.xml | 2 +- blog/posts/12/index.html | 4 +- blog/posts/13/index.html | 2 +- blog/posts/15/index.html | 8 +- blog/posts/2/index.html | 2 +- blog/posts/5/index.html | 4 +- blog/posts/6/index.html | 10 +- blog/posts/7/index.html | 6 +- components/alert/index.html | 4 +- components/automation/index.html | 4 +- components/binary_sensor.wink/index.html | 2 +- components/counter/index.html | 4 +- .../device_sun_light_trigger/index.html | 4 +- components/dweet/index.html | 2 +- components/ffmpeg/index.html | 2 +- components/hdmi_cec/index.html | 4 +- components/ifttt/index.html | 4 +- components/index.html | 4 +- components/input_boolean/index.html | 4 +- components/input_datetime/index.html | 4 +- components/input_number/index.html | 349 ++++++++++++++++++ components/input_select/index.html | 4 +- components/input_slider/index.html | 349 +----------------- components/input_text/index.html | 4 +- components/keyboard/index.html | 4 +- components/light.decora/index.html | 2 +- components/lirc/index.html | 4 +- components/lock.nello/index.html | 2 +- components/media_extractor/index.html | 2 +- .../media_player.frontier_silicon/index.html | 2 +- components/notify.discord/index.html | 2 +- components/proximity/index.html | 4 +- components/python_script/index.html | 4 +- components/rest_command/index.html | 4 +- components/script/index.html | 4 +- components/sensor.airvisual/index.html | 2 +- components/sensor.dweet/index.html | 2 +- components/sensor.vera/index.html | 2 +- components/shell_command/index.html | 10 +- components/switch.flux/index.html | 4 +- components/tts.yandextts/index.html | 2 +- cookbook/dim_and_brighten_lights/index.html | 16 +- cookbook/sonos_say/index.html | 2 +- demo/frontend.html | 4 +- developers/credits/index.html | 95 +++-- developers/hassio/addon_config/index.html | 2 +- developers/website/index.html | 2 +- docs/autostart/init.d/index.html | 2 +- docs/autostart/upstart/index.html | 2 +- docs/configuration/events/index.html | 4 +- docs/configuration/packages/index.html | 2 +- docs/configuration/yaml/index.html | 10 +- docs/ecosystem/appdaemon/api/index.html | 32 +- .../appdaemon/configuration/index.html | 2 +- docs/ecosystem/appdaemon/index.html | 2 +- docs/ecosystem/appdaemon/tutorial/index.html | 2 +- docs/ecosystem/appdaemon/windows/index.html | 2 +- .../backup/backup_dropbox/index.html | 4 +- .../ecosystem/backup/backup_github/index.html | 6 +- docs/ecosystem/backup/backup_usb/index.html | 2 +- .../certificates/lets_encrypt/index.html | 10 +- docs/ecosystem/hass-configurator/index.html | 2 +- docs/ecosystem/ios/location/index.html | 2 +- docs/ecosystem/scenegen/index.html | 2 +- .../raspberry-pi-all-in-one/index.html | 4 +- docs/installation/raspberry-pi/index.html | 6 +- docs/scripts/index.html | 4 +- docs/tools/scripts/index.html | 4 +- faq/documentation-tool/index.html | 2 +- faq/index.html | 4 +- faq/missing-documentation/index.html | 2 +- sitemap.xml | 88 ++--- 128 files changed, 676 insertions(+), 657 deletions(-) create mode 100644 components/input_number/index.html diff --git a/addons/configurator/index.html b/addons/configurator/index.html index 6bf5c5445f..5861dc404b 100644 --- a/addons/configurator/index.html +++ b/addons/configurator/index.html @@ -87,7 +87,7 @@ Screenshot of the HASS Configurator.
  • Upload and download files.
  • Stage and commit changes in Git repositories, create and switch between branches, push to remotes.
  • Lists of available triggers, events, entities, conditions and services. Selected element gets inserted into the editor at the last cursor position.
    • -
  • Restart Home Assitant directly with the click of a button. Reloading groups, automations etc. can be done as well. An API-password is required.
    • +
  • Restart Home Assistant directly with the click of a button. Reloading groups, automations etc. can be done as well. An API-password is required.
  • SSL support.
  • Optional authentication and IP filtering for added security.
  • Direct links to Home Assistant documentation and icons.
    • diff --git a/addons/dhcp_server/index.html b/addons/dhcp_server/index.html index 9f266d170f..9b6cbb2775 100644 --- a/addons/dhcp_server/index.html +++ b/addons/dhcp_server/index.html @@ -112,7 +112,7 @@  - broadcast (Required): Network broadcast address.  - gateway (Required): A List of gateways.
  • hosts (Optional): A list of fixed IPs for devices. diff --git a/addons/dnsmasq/index.html b/addons/dnsmasq/index.html index 39f8f8b16d..d58626f643 100644 --- a/addons/dnsmasq/index.html +++ b/addons/dnsmasq/index.html @@ -96,7 +96,7 @@
  • defaults (Required): A list of dns server to forward default requests.
  • forwards (Optional): A list of domains that will forward to a specific server.
  • hosts (Optional): A list of hosts to resolve it static.
    • -
  • interface (Optional): If a interface is set, it listen only on this interface. Need to set for resinos. Normaly is eth0 for ethernet wired connection and wlan0 for wireless connection.
    • +
  • interface (Optional): If a interface is set, it listen only on this interface. Need to set for resinos. Normally is eth0 for ethernet wired connection and wlan0 for wireless connection.
    • diff --git a/addons/mariadb/index.html b/addons/mariadb/index.html index e66328fa63..56eeea60e8 100644 --- a/addons/mariadb/index.html +++ b/addons/mariadb/index.html @@ -75,7 +75,7 @@
    -

    Set up a mariadb SQL server. It support multible database, users and permission. If you want only connect from inside use core-mariadb as host address.

    +

    Set up a mariadb SQL server. It support multiple database, users and permission. If you want only connect from inside use core-mariadb as host address.

    {
   "databases": ["homeassistant"],
   "logins": [
diff --git a/addons/samba/index.html b/addons/samba/index.html
index 969c67bce8..9ff6b90a52 100644
--- a/addons/samba/index.html
+++ b/addons/samba/index.html
@@ -101,7 +101,7 @@
   
  • map (Optional): Control which folder will be expose. config is for Home Assistant configuration folder. addons for local custom repositiory. share is a folder that can access from add-ons and Home Assistant too. backup for access to snapshot files. ssl for certificate storage, be careful with this option! Defaults all to true, except for ssl.
    • 
   
  • username (Optional): The username for logging in if guest login is not used.
    • 
   
  • password (Optional): Password for username. An empty password is not supported.
    • 
-  
  • interface (Optional): Interface on that will start the share. Normaly is eth0 for ethernet wired connection and wlan0 for wireless connection.
    • 
+  
  • interface (Optional): Interface on that will start the share. Normally is eth0 for ethernet wired connection and wlan0 for wireless connection.
    •
    diff --git a/atom.xml b/atom.xml index 854322d6eb..151e6972c9 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ @@ -99,7 +99,7 @@
  • Clean up OwnTracks (@balloob - #9569) (device_tracker.owntracks docs)
  • MQTT Cover: Add availability topic and configurable payloads (@marthoc - #9445) (cover.mqtt docs)
  • Upgrade dsmr_parser to 0.11 (@fabaff - #9576) (sensor.dsmr docs)
    • -
  • Added new statistic attributes (@sti0 - #9433) (vacuum.xiaomi docs)
    • +
  • Added new statistic attributes (@sti0 - #9433) (vacuum.xiaomi docs)
  • Upgrade youtube_dl to 2017.9.24 (@fabaff - #9575) (media_extractor docs)
  • Upgrade lyft_rides to 0.2 (@enriquegh - #9578) (sensor.lyft docs)
  • Increase Comed timeout since it sometimes takes a long time for the API to respond (@joe248 - #9536) (sensor.comed_hourly_pricing docs)
    • @@ -115,7 +115,7 @@
  • Add OwnTracks over HTTP (@balloob - #9582) (http docs) (device_tracker.owntracks docs) (device_tracker.owntracks_http docs) (new-platform)
  • upgrade python-ecobee-api (@nkgilley - #9612) (ecobee docs)
  • Change TP-Link Switch power statistics attribute names (@djchen - #9607) (switch.tplink docs) (breaking change)
    • -
  • Migrate Alexa smart home to registry (@balloob - #9616) (alexa.smart_home docs)
    • +
  • Migrate Alexa smart home to registry (@balloob - #9616) (alexa.smart_home docs)
  • Add an input_datetime (@tinloaf - #9313) (input_datetime docs) (new-platform)
  • Cover component for RFlink (@passie - #9432) (rflink docs) (cover.rflink docs) (new-platform)
  • Introducing support to Melnor RainCloud sprinkler systems (@tchellomello - #9287) (raincloud docs) (binary_sensor.raincloud docs) (sensor.raincloud docs) (switch.raincloud docs) (new-platform)
    • @@ -143,23 +143,23 @@
  • Upgrade googlemaps to 2.5.1 (@fabaff - #9653) (sensor.google_travel_time docs)
  • mqtt_statestream: Add options to publish attributes/timestamps (@mw-white - #9645) (mqtt_statestream docs)
  • Fixed bugs related to exception handling in pythonegardia. Updating package requirement accordingly (@jeroenterheerdt - #9663) (alarm_control_panel.egardia docs)
    • -
  • Update google-api-python-client to 1.6.4 (@arsaboo - #9658) (google docs)
    • +
  • Update google-api-python-client to 1.6.4 (@arsaboo - #9658) (google docs)
  • Bump abode to 0.11.9 (@MisterWil - #9660) (abode docs)
  • Unit tests to improve core coverage (@armills - #9659)
  • Upgrade pyitachip2ir to 0.0.7 (@alanfischer - #9669) (remote.itach docs)
  • Fix typo in cancel_command description (@FletcherAU - #9671)
  • Rename input_slider to input_number and add numeric text box option (@BioSehnsucht - #9494) (demo docs) (input_number docs) (breaking change)
  • Properly handle an invalid end_time (@alanfischer - #9675) (history docs)
    • -
  • Support new feature to push API data to hassio (@pvizeli - #9679) (hassio docs)
    • +
  • Support new feature to push API data to hassio (@pvizeli - #9679) (hassio docs)
  • Adding ignore capability to Egardia component (@jeroenterheerdt - #9676) (alarm_control_panel.egardia docs)
    • -
  • Fix Google Calendar/oauth2client warning (@mbrrg - #9677) (google docs)
    • +
  • Fix Google Calendar/oauth2client warning (@mbrrg - #9677) (google docs)
  • Implement DSMR5 support. (@aequitas - #9686) (sensor.dsmr docs)
  • Add Tibber sensor (@danielhiversen - #9661) (sensor.tibber docs) (new-platform)
  • Add recorder purge service, rework purge timer (@milanvo - #9523) (breaking change)
  • Fix restore state by filter out null value row from DB query (@milanvo - #9690) (history docs)
  • Updating clicksendaudio component based on feedback (@jeroenterheerdt - #9692) (notify.clicksendaudio docs) (new-platform)
  • Refactoring of onewire sensor component (@bestlibre - #9691) (sensor.onewire docs)
    • -
  • HassIO replace config changes (@pvizeli - #9695) (hassio docs)
    • +
  • HassIO replace config changes (@pvizeli - #9695) (hassio docs)
  • Fixed typo in opencv (@arsaboo - #9697) (image_processing.opencv docs) (breaking change)
  • [light.tradfri] async support with resource observation. (@lwis - #7815) (tradfri docs) (light.tradfri docs) (breaking change)
  • Create secrets file in default config (@balloob - #9685)
    • @@ -665,7 +665,7 @@ Screenshot of the new customize editor.
  • Skip automatic events older than latest data (@armills - #9230) (device_tracker.automatic docs)
  • title and message was swapped in pushbullet (@danielhiversen - #9241) (notify.pushbullet docs)
  • Fix possible KeyError (@MartinHjelmare - #9242) (mysensors docs)
    • -
  • WIP: Homematic improvments with new hass interfaces (@pvizeli - #9058) (homematic docs) (binary_sensor.homematic docs) (climate.homematic docs) (cover.homematic docs) (light.homematic docs) (sensor.homematic docs) (switch.homematic docs) (breaking change)
    • +
  • WIP: Homematic improvements with new hass interfaces (@pvizeli - #9058) (homematic docs) (binary_sensor.homematic docs) (climate.homematic docs) (cover.homematic docs) (light.homematic docs) (sensor.homematic docs) (switch.homematic docs) (breaking change)
  • Add available to sonos (@pvizeli - #9243) (media_player.sonos docs)
  • Make sure Ring binary_sensor state will update only if device_id matches (@tchellomello - #9247) (binary_sensor.ring docs)
  • @@ -1198,7 +1198,7 @@ Screenshot of the new customize editor.
  • Fix TP-Link light brightness issue #8744. (@gollo - #8755)
  • Fix typo in script error (@n8henrie - #8754)
  • Fix tradfri error spam (@MartinHjelmare - #8738) (light.tradfri docs)
    • -
  • Media Player - Pioneer: Supress exception if host is not available (fixes #8684) (@fabaff - #8732) (media_player.pioneer docs)
    • +
  • Media Player - Pioneer: Suppress exception if host is not available (fixes #8684) (@fabaff - #8732) (media_player.pioneer docs)
  • Telegram Bot: Retry set_webhook up to three times, reduce timeout to 5s again (@azogue - #8716) (telegram_bot.webhooks docs)
  • Fixed sensor issue with Google Wifi routers in bridge mode (@fronzbot - #8710) (sensor.google_wifi docs)
  • Fix alexa cards (@balloob - #8708) (alexa docs)
    • diff --git a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html index 8c32ca2ce2..63ed1d2b77 100644 --- a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html +++ b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html @@ -88,7 +88,7 @@

    The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home. This article will try to explain how they all relate.

    -

    The first thing to introduce is the Internet of Things (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.

    +

    The first thing to introduce is the Internet of Things (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its reservoir.

    There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a hub.

    As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers home control.

    diff --git a/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html b/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html index b67adefb68..7aa7abf5d6 100644 --- a/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html +++ b/blog/2015/01/11/bootstrapping-your-setup-with-discovery/index.html @@ -87,7 +87,7 @@

    Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.

    -

    The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The intial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.

    +

    The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The initial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.

    Most devices still require some sort of interaction from the user after being discovered - be it a button being pressed or some sort of authentication. This is a challenge that will be solved in the future.

    To enable the discovery component, add the following to your home-assistant.conf:

    [discovery]
diff --git a/blog/2015/02/08/looking-at-the-past/index.html b/blog/2015/02/08/looking-at-the-past/index.html
index 428282840e..ed890595e4 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -100,7 +100,7 @@
   
 
    
 
    
-Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time.
+Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transferred to anyone at any time.
 
    
 
 
    Tracking history is an exciting next step for Home Assistant and will power the next generation of features. Here a list of some of the cool things that can now be build:
    
diff --git a/blog/2015/02/24/streaming-updates/index.html b/blog/2015/02/24/streaming-updates/index.html
index 9bf3a670b3..02c6dd2db0 100644
--- a/blog/2015/02/24/streaming-updates/index.html
+++ b/blog/2015/02/24/streaming-updates/index.html
@@ -87,7 +87,7 @@

    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.

    +

    A new toggle has been added to 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.

    Streaming updates has been implemented using the HTML5 EventSource tag. Implementation is pretty straight forward as all the reconnection logic will be handled by the event source tag. The server-side code is 50 lines and the client-side code is 80 lines of code.

    diff --git a/blog/2015/10/11/rfxtrx-blinkstick-and-snmp-support/index.html b/blog/2015/10/11/rfxtrx-blinkstick-and-snmp-support/index.html index 479e11a803..dc2fe718c4 100644 --- a/blog/2015/10/11/rfxtrx-blinkstick-and-snmp-support/index.html +++ b/blog/2015/10/11/rfxtrx-blinkstick-and-snmp-support/index.html @@ -86,7 +86,7 @@ >Comments -

    We discovered two issues annoying enough to warrent the release of 0.7.5:

    +

    We discovered two issues annoying enough to warrant the release of 0.7.5:

    • Home Assistant package did not include the CloudMQTT certificate.
    • A bug in the core caused issues when some platforms are loaded twice.
      • diff --git a/blog/2015/12/07/influxdb-and-grafana/index.html b/blog/2015/12/07/influxdb-and-grafana/index.html index 7e5c432915..804c177596 100644 --- a/blog/2015/12/07/influxdb-and-grafana/index.html +++ b/blog/2015/12/07/influxdb-and-grafana/index.html @@ -86,7 +86,7 @@

      -The InfluxDB database is a so-called time series database primarly designed to store sensor data and real-time analytics.

      +The InfluxDB database is a so-called time series database primarily designed to store sensor data and real-time analytics.

      The influxdb component makes it possible to transfer all state changes from Home Assistant to an external InfluxDB database.

      The first step is to install the InfluxDB packages. If you are not running Fedora, check the installation section for further details.

      diff --git a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html index 4813010bf3..b7dec73a1f 100644 --- a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html +++ b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html @@ -87,7 +87,7 @@

      Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.

      -

      I would like to give a shout out to Greg Dowling (@pavoni) as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!

      +

      I would like to give a shout out to Greg Dowling (@pavoni) as every release includes new work from him. He is constantly adding support for new platforms or improving the reliability of existing components and platforms. Keep up the good work!

      This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See the demo to see this in action and read more in the group documentation how to get started.

      diff --git a/blog/2016/02/09/Smarter-Smart-Things-with-MQTT-and-Home-Assistant/index.html b/blog/2016/02/09/Smarter-Smart-Things-with-MQTT-and-Home-Assistant/index.html index 036e5881e9..222c6a4ccf 100644 --- a/blog/2016/02/09/Smarter-Smart-Things-with-MQTT-and-Home-Assistant/index.html +++ b/blog/2016/02/09/Smarter-Smart-Things-with-MQTT-and-Home-Assistant/index.html @@ -154,7 +154,7 @@ broker: localhost -

      Replace localhost with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path smartthings/<Device Name>/<Atribute>

      +

      Replace localhost with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path smartthings/<Device Name>/<Attribute>

      For example, my Dimmer Z-Wave Lamp is called “Fireplace Lights” in SmartThings. The following topics are published:

      diff --git a/blog/2016/02/12/classifying-the-internet-of-things/index.html b/blog/2016/02/12/classifying-the-internet-of-things/index.html index f116168b33..3fda7975a7 100644 --- a/blog/2016/02/12/classifying-the-internet-of-things/index.html +++ b/blog/2016/02/12/classifying-the-internet-of-things/index.html @@ -194,7 +194,7 @@

      No control available

      These devices are not able to be controlled. They will only offer state.

      Poll State after sending command

      -

      These devices will require the state to be polled after sending a command to see if a command was successfull.

      +

      These devices will require the state to be polled after sending a command to see if a command was successful.

      Advantages:

      • The state will be known right after the command was issued.
        • diff --git a/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-sony-bravia-tv/index.html b/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-sony-bravia-tv/index.html index 9a6601d393..596e8b78d1 100644 --- a/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-sony-bravia-tv/index.html +++ b/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-sony-bravia-tv/index.html @@ -8,7 +8,7 @@ 0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV - Home Assistant - + @@ -16,13 +16,13 @@ - + - + diff --git a/blog/2016/07/28/esp8266-and-micropython-part1/index.html b/blog/2016/07/28/esp8266-and-micropython-part1/index.html index 61fb4da7b3..b2afa8d9f3 100644 --- a/blog/2016/07/28/esp8266-and-micropython-part1/index.html +++ b/blog/2016/07/28/esp8266-and-micropython-part1/index.html @@ -110,7 +110,7 @@ Leaving...

        Now reset the device. You should then be able to use the REPL (Read Evaluate Print Loop). On Linux there is minicom or picocom, on a Mac you can use screen (eg. screen /dev/tty.SLAB_USBtoUART 115200), and on Windows there is Putty to open a serial connection and get the REPL prompt.

        -

        The WebREPL work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at http://micropython.org/webrepl. Alternatively, you can create a local clone of their GitHub repository. This is neccessary if your want to use the command-line tool webrepl_cli.py which is mentionend later in this post.

        +

        The WebREPL work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at http://micropython.org/webrepl. Alternatively, you can create a local clone of their GitHub repository. This is necessary if your want to use the command-line tool webrepl_cli.py which is mentionend later in this post.

        $ sudo minicom -D /dev/ttyUSB0
 #4 ets_task(4020e374, 29, 3fff70e8, 10)                                                          
 WebREPL daemon started on ws://192.168.4.1:8266
diff --git a/blog/2016/08/16/we-have-apps-now/index.html b/blog/2016/08/16/we-have-apps-now/index.html
index 14683839e9..1535b219a7 100644
--- a/blog/2016/08/16/we-have-apps-now/index.html
+++ b/blog/2016/08/16/we-have-apps-now/index.html
@@ -109,7 +109,7 @@
   
      • Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened
        • 
   
      • All the power of Python - use any of Python’s libraries, create your own modules, share variables, refactor and re-use code, create a single app to do everything, or multiple apps for individual tasks - nothing is off limits!
        •
      -

      It is in fact a testament to Home Assistant’s open nature that a component like AppDaemon can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant’s underlying design is that it makes no assumptions whatever about what it is controlling or reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for AppDaemon - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner - the bulk of the work after that was adding additonal functions to make things that were already possible easier.

      +

      It is in fact a testament to Home Assistant’s open nature that a component like AppDaemon can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant’s underlying design is that it makes no assumptions whatever about what it is controlling or reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for AppDaemon - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner - the bulk of the work after that was adding additional functions to make things that were already possible easier.

      How it Works

      The best way to show what AppDaemon does is through a few simple examples.

      Sunrise/Sunset Lighting

      diff --git a/blog/2016/09/10/notify-group-reload-api-pihole/index.html b/blog/2016/09/10/notify-group-reload-api-pihole/index.html index 8f1aee8fa9..c8687dcb7f 100644 --- a/blog/2016/09/10/notify-group-reload-api-pihole/index.html +++ b/blog/2016/09/10/notify-group-reload-api-pihole/index.html @@ -97,7 +97,7 @@

      Climate and cover

      There are countless bugfixes included in this release which will make your experience with the climate and the cover platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to @turbokongen, @pvizeli, @djbanks, @danielperna84, and others the improvements on the code and the frontend side is continuing…

      API documentation

      -

      The Home Assistant API Documentation is a great addition to the already exisiting user documentation. The focus is not end-users but developers who whant to get details about the code without actually browsing the code on Github.

      +

      The Home Assistant API Documentation is a great addition to the already exisiting user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.

      Configuration validation

      The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to @kellerza, @fabaff, @Teagan42, and @pvizeli for your effort!

      All changes

      diff --git a/blog/2016/10/08/hassbian-rest-digital-ocean/index.html b/blog/2016/10/08/hassbian-rest-digital-ocean/index.html index 9c9debe378..b569ab005d 100644 --- a/blog/2016/10/08/hassbian-rest-digital-ocean/index.html +++ b/blog/2016/10/08/hassbian-rest-digital-ocean/index.html @@ -87,7 +87,7 @@

      Yes, after only nine days comes 0.30. Don’t worry, we will try to keep our usual release cycle and not start to release every day.

      -

      We guess that you already know: The Raspberry Pi image is available now. For Hassbian, @Landrash has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to recieve feedback, issue report, and suggestions to improve it.

      +

      We guess that you already know: The Raspberry Pi image is available now. For Hassbian, @Landrash has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to receive feedback, issue report, and suggestions to improve it.

      A large amount of resources of the development are still focusing on the effort to move Home Assistant further to asynchronous programming. It’s a labor-intensive task, comes with segmentation faults, and unstable instances when certain combinations of sensors are used. The benefit will be more speed in the near future.

      To reduce the run-time of your tests, @balloob did a lot of tweaking. For now the RFXtrx tests are excluded which cut the needed time for running on your Pull Request in half.

      Documentation

      diff --git a/blog/2016/10/22/flash-briefing-updater-hacktoberfest/index.html b/blog/2016/10/22/flash-briefing-updater-hacktoberfest/index.html index 521e1af916..8aea4745a4 100644 --- a/blog/2016/10/22/flash-briefing-updater-hacktoberfest/index.html +++ b/blog/2016/10/22/flash-briefing-updater-hacktoberfest/index.html @@ -319,7 +319,7 @@
    • 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)
      • +
    • Z-Wave: Add association service (@turbokongen)
    • Frontend - Services dev tool: persist state and tweak UI (@justweb1)
    • Sensor: Support added for scraping websites (@fabaff)
    • Clean up of tests (@capellini)
      • diff --git a/blog/2016/12/03/remote-websockets-sonarr/index.html b/blog/2016/12/03/remote-websockets-sonarr/index.html index 3231fb42d2..d5369cdfcc 100644 --- a/blog/2016/12/03/remote-websockets-sonarr/index.html +++ b/blog/2016/12/03/remote-websockets-sonarr/index.html @@ -183,7 +183,7 @@
    • Fix InfluxDB without authentication (@balloob)
    • Fix Kodi without authentication (@balloob)
    • Fix incorrect caching of /api/error_log (@armills)
      • -
    • Fix incorrect ordering of service calls which could cause delays inbetween turning on multiple entities (@balloob)
      • +
    • Fix incorrect ordering of service calls which could cause delays between turning on multiple entities (@balloob)
    • Fix Nest Climate temperature issues (@technicalpickles)

      • Release 0.34.5 - December 12

      diff --git a/blog/2016/12/19/thank-you/index.html b/blog/2016/12/19/thank-you/index.html index ec2792988e..79c1497604 100644 --- a/blog/2016/12/19/thank-you/index.html +++ b/blog/2016/12/19/thank-you/index.html @@ -87,7 +87,7 @@

      A year ago Home Assistant 0.10 landed. Last weekend we released 0.35. Doing 25 releases in a year is a big accomplishment by the community and each release has moved us forwards leaps and bounds. In this year alone we have seen 2800 pull requests on the main repo alone, that’s more than 7 a day!

      -

      One of the things that Jon Walker, the founder of the company I work for (AppFolio), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Everytime you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.

      +

      One of the things that Jon Walker, the founder of the company I work for (AppFolio), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Every time you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.

      That’s why I structured Home Assistant around a two week release cycle. It makes sure that features get out fast and it also forces us to not accumulate a backlog of things to document or test properly. Every two weeks we can start fresh. This makes it easy for new people to start contributing because it’s clear when things go out and people are not afraid to miss a release.

      However, being on a two week release cycle also means that the community has to rally each two weeks to make sure everything is ready to go. A lot of people are involved in making sure that all pieces are in place, to all of those: thank you! Thank you for all the time and effort you put in to make Home Assistant the best home automation software out there.

      Another big thanks goes out to the developers of the Python language and all the open source libraries and tools that Home Assistant depends on. Making quality software is not a small feat and all of you can be proud of yourself.

      diff --git a/blog/2017/01/03/control-my-christmas-tree-stats/index.html b/blog/2017/01/03/control-my-christmas-tree-stats/index.html index 6127a803f8..8ac82f72ee 100644 --- a/blog/2017/01/03/control-my-christmas-tree-stats/index.html +++ b/blog/2017/01/03/control-my-christmas-tree-stats/index.html @@ -88,7 +88,7 @@

      Hello and Happy New Year!

      I am not Paulus. My name is Ben. I’m the creator of the BRUH Automation YouTube channel. If you’ve ever seen any of my videos then you’ll know I love home automation and Home Assistant.

      -

      I wanted to share some exciting stats from one of my latest projects - Control My Christmas tree! For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publically accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.

      +

      I wanted to share some exciting stats from one of my latest projects - Control My Christmas tree! For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publicly accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.

      I added three devices to the Home Assistant instance - a Wemo Insight, Sonoff Switch (running MQTT firmware), and a DIY MQTT Digital LED strip. After adding a few 3D printed Star War decorations, the tree was ready to go!

      diff --git a/blog/2017/01/28/face-coffee-wink/index.html b/blog/2017/01/28/face-coffee-wink/index.html index 47def875b2..ce2ea7d496 100644 --- a/blog/2017/01/28/face-coffee-wink/index.html +++ b/blog/2017/01/28/face-coffee-wink/index.html @@ -165,7 +165,7 @@

    • 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)
      • +
    • Fan - MQTT: Don’t 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)
      • diff --git a/blog/2017/02/03/babyphone/index.html b/blog/2017/02/03/babyphone/index.html index 0c2eaabd80..39b93af8b5 100644 --- a/blog/2017/02/03/babyphone/index.html +++ b/blog/2017/02/03/babyphone/index.html @@ -85,7 +85,7 @@ >Comments -

      One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.

      +

      One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assistant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.

      Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.

      Setup

      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 8ea76bf4c9..859f935c15 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 @@ -240,7 +240,7 @@ Screenshot of all the different functionality the IP webcam integration offers.
    • twilio component (@happyleavesaoc)
    • Add Z-Wave battery level as a sensor. (@andrey-git)
    • OwnTrack Async (@pvizeli)
      • -
    • Fix possibility that have multible topic subscribe mqtt (@pvizeli)
      • +
    • Fix possibility that have multiple topic subscribe mqtt (@pvizeli)
    • Migrate mqtt tracker and arwn sensor to async / cleanup owntrack (@pvizeli)
    • Z-Wave prevent I/O event loop (@balloob)
    • Update pwaqi to 3.0 to use public API (@valentinalexeev)
      • @@ -290,7 +290,7 @@ Screenshot of all the different functionality the IP webcam integration offers.
    • Allow configurable conditions for Pi-Hole sensor (@colinodell)
    • Improved iCloud 2FA support. (@reedriley)
    • Update pymyq requirement (@arraylabs)
      • -
    • Not always asume manufacturername is present (@balloob)
      • +
    • Not always assume manufacturername is present (@balloob)
    • Add first pass at Z-Wave light tests (@balloob)
    • Bugfix mqtt socket memory error (@pvizeli)
    • Increase upper limit on light transitions (@amelchio)
      • 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 125d9ea1a5..14ecf627a9 100644 --- a/blog/2017/03/28/http-to-mqtt-bridge/index.html +++ b/blog/2017/03/28/http-to-mqtt-bridge/index.html @@ -85,7 +85,7 @@ >Comments -

      The idea of creating HTTP to MQTT bridge appeared when I was trying to integrate Google Assistant with my Home Assistant after watching BRUH Automation video. Right now there is no MQTT service available in IFTTT. Existing integration solution uses Maker Webhooks which requires that your Home Assistant instance is publically accessible, which I think brings some security concerns or simply not always possible to set up.

      +

      The idea of creating HTTP to MQTT bridge appeared when I was trying to integrate Google Assistant with my Home Assistant after watching BRUH Automation video. Right now there is no MQTT service available in IFTTT. Existing integration solution uses Maker Webhooks which requires that your Home Assistant instance is publicly accessible, which I think brings some security concerns or simply not always possible to set up.

      The HTTP to MQTT bridge should fill that gap. The idea is to receive messages using HTTP requests and transfer them to your MQTT broker, which can be contacted by Home Assistant. The HTTP to MQTT bridge is written using Node.js with Express for the server part and MQTT.js for the client.

      The app could be hosted on any Node.js hosting. I prefer Heroku: Cloud Application Platform for its simplicity.

      diff --git a/blog/2017/04/01/thomas-krenn-award/index.html b/blog/2017/04/01/thomas-krenn-award/index.html index 41e787e5c3..95349a4ac0 100644 --- a/blog/2017/04/01/thomas-krenn-award/index.html +++ b/blog/2017/04/01/thomas-krenn-award/index.html @@ -85,7 +85,7 @@ >Comments -

      You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the Thomas-Krenn-Award put us on the 2nd place. This is an awesome achievment for an independent community project.

      +

      You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the Thomas-Krenn-Award put us on the 2nd place. This is an awesome achievement for an independent community project.

      I would like to thanks all contributors. Your endless effort made this possible.

      The prize beside the very nice trophy contains hardware and we want to give that hardware partically away. We won four Low Energy Server v2 (LES) units with an Intel Celeron N2930, 8 GB of RAM, and a mSATA of 128 GB (one unit with 64 GB). We were thinking about to keep one of those units in Europe and one in North America for testing and to use during workshops and events. But the other two will go to interested parties.

      diff --git a/blog/2017/04/22/ikea-tradfri-spotify/index.html b/blog/2017/04/22/ikea-tradfri-spotify/index.html index 2a9bfd9ed0..5a959b5a40 100644 --- a/blog/2017/04/22/ikea-tradfri-spotify/index.html +++ b/blog/2017/04/22/ikea-tradfri-spotify/index.html @@ -208,7 +208,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
    • Upgrade sendgrid to 4.0.0 (@fabaff - #7038) (notify.sendgrid docs)
    • Missing line name restriction added (fixes #7039) (@DavidMStraub - #7040) (sensor.mvglive docs)
    • Plug file leak on LIFX unregister (@amelchio - #7031) (light.lifx docs)
      • -
    • Make core to look avilable state of device on servicecall (@pvizeli - #7045)
      • +
    • Make core to look available state of device on servicecall (@pvizeli - #7045)
    • Remove configuration sample (@fabaff - #7048)
    • Bugfix wait on start event (@pvizeli - #7013)
    • Bugfix slider (@pvizeli - #7047) (input_slider docs)
      • @@ -271,7 +271,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
    • Value of 0 should not be considered unknown. (@aequitas - #7139)
    • Upgrade netdisco (@balloob - #7171)
    • Added new services to platform kodi (@alexmogavero - #6426) (media_player docs) (media_player.kodi docs)
      • -
    • Supress trackback and upgrade PyMata to 2.14 (@fabaff - #7176) (arduino docs)
      • +
    • Suppress trackback and upgrade PyMata to 2.14 (@fabaff - #7176) (arduino docs)
    • Disable invalid-sequence-index (@fabaff - #7177)
    • Upgrade mypy to 0.501 (was renamed from mypy-lang) (@fabaff - #7117)
    • Add condition for API failure (@sytone - #7181)
      • diff --git a/blog/2017/06/04/release-46/index.html b/blog/2017/06/04/release-46/index.html index f751249336..5d98960cca 100644 --- a/blog/2017/06/04/release-46/index.html +++ b/blog/2017/06/04/release-46/index.html @@ -218,7 +218,7 @@
    • Use expected behvaior for above/below (@armills - #7857) (breaking change)
    • log time delay of domain setup in info level (@azogue - #7808)
    • Optimize history_stats efficiency and database usage (@bokub - #7858) (sensor.history_stats docs)
      • -
    • dont use default for switch name, so that the object id is used (@abmantis - #7845) (switch.broadlink docs) (breaking change)
      • +
    • don’t use default for switch name, so that the object id is used (@abmantis - #7845) (switch.broadlink docs) (breaking change)
    • Disallow ambiguous color descriptors in the light.turn_on schema (@amelchio - #7765) (breaking change)
    • Make monkey patch work in Python 3.6 (@balloob - #7848)
    • fix permissions issue for Insteon Local #6558 (@wardcraigj - #7860) (insteon_local docs)
      • diff --git a/blog/2017/07/29/release-50/index.html b/blog/2017/07/29/release-50/index.html index 9fe0532779..17454014b1 100644 --- a/blog/2017/07/29/release-50/index.html +++ b/blog/2017/07/29/release-50/index.html @@ -126,7 +126,7 @@
    • Fix TP-Link light brightness issue #8744. (@gollo - #8755)
    • Fix typo in script error (@n8henrie - #8754)
    • Fix tradfri error spam (@MartinHjelmare - #8738) (light.tradfri docs)
      • -
    • Media Player - Pioneer: Supress exception if host is not available (fixes #8684) (@fabaff - #8732) (media_player.pioneer docs)
      • +
    • Media Player - Pioneer: Suppress exception if host is not available (fixes #8684) (@fabaff - #8732) (media_player.pioneer docs)
    • Telegram Bot: Retry set_webhook up to three times, reduce timeout to 5s again (@azogue - #8716) (telegram_bot.webhooks docs)
    • Fixed sensor issue with Google Wifi routers in bridge mode (@fronzbot - #8710) (sensor.google_wifi docs)
    • Fix alexa cards (@balloob - #8708) (alexa docs)
      • diff --git a/blog/2017/09/09/release-53/index.html b/blog/2017/09/09/release-53/index.html index 2e9fad9cf1..6a1985374a 100644 --- a/blog/2017/09/09/release-53/index.html +++ b/blog/2017/09/09/release-53/index.html @@ -214,7 +214,7 @@ Screenshot of the new customize editor.
    • Skip automatic events older than latest data (@armills - #9230) (device_tracker.automatic docs)
    • title and message was swapped in pushbullet (@danielhiversen - #9241) (notify.pushbullet docs)
    • Fix possible KeyError (@MartinHjelmare - #9242) (mysensors docs)
      • -
    • WIP: Homematic improvments with new hass interfaces (@pvizeli - #9058) (homematic docs) (binary_sensor.homematic docs) (climate.homematic docs) (cover.homematic docs) (light.homematic docs) (sensor.homematic docs) (switch.homematic docs) (breaking change)
      • +
    • WIP: Homematic improvements with new hass interfaces (@pvizeli - #9058) (homematic docs) (binary_sensor.homematic docs) (climate.homematic docs) (cover.homematic docs) (light.homematic docs) (sensor.homematic docs) (switch.homematic docs) (breaking change)
    • Add available to sonos (@pvizeli - #9243) (media_player.sonos docs)
    • Make sure Ring binary_sensor state will update only if device_id matches (@tchellomello - #9247) (binary_sensor.ring docs)
    • diff --git a/blog/2017/10/07/release-55/index.html b/blog/2017/10/07/release-55/index.html index 17bf8d98ef..6fea612f2f 100644 --- a/blog/2017/10/07/release-55/index.html +++ b/blog/2017/10/07/release-55/index.html @@ -152,7 +152,7 @@
    • Clean up OwnTracks (@balloob - #9569) (device_tracker.owntracks docs)
    • MQTT Cover: Add availability topic and configurable payloads (@marthoc - #9445) (cover.mqtt docs)
    • Upgrade dsmr_parser to 0.11 (@fabaff - #9576) (sensor.dsmr docs)
      • -
    • Added new statistic attributes (@sti0 - #9433) (vacuum.xiaomi docs)
      • +
    • Added new statistic attributes (@sti0 - #9433) (vacuum.xiaomi docs)
    • Upgrade youtube_dl to 2017.9.24 (@fabaff - #9575) (media_extractor docs)
    • Upgrade lyft_rides to 0.2 (@enriquegh - #9578) (sensor.lyft docs)
    • Increase Comed timeout since it sometimes takes a long time for the API to respond (@joe248 - #9536) (sensor.comed_hourly_pricing docs)
      • @@ -168,7 +168,7 @@
    • Add OwnTracks over HTTP (@balloob - #9582) (http docs) (device_tracker.owntracks docs) (device_tracker.owntracks_http docs) (new-platform)
    • upgrade python-ecobee-api (@nkgilley - #9612) (ecobee docs)
    • Change TP-Link Switch power statistics attribute names (@djchen - #9607) (switch.tplink docs) (breaking change)
      • -
    • Migrate Alexa smart home to registry (@balloob - #9616) (alexa.smart_home docs)
      • +
    • Migrate Alexa smart home to registry (@balloob - #9616) (alexa.smart_home docs)
    • Add an input_datetime (@tinloaf - #9313) (input_datetime docs) (new-platform)
    • Cover component for RFlink (@passie - #9432) (rflink docs) (cover.rflink docs) (new-platform)
    • Introducing support to Melnor RainCloud sprinkler systems (@tchellomello - #9287) (raincloud docs) (binary_sensor.raincloud docs) (sensor.raincloud docs) (switch.raincloud docs) (new-platform)
      • @@ -196,23 +196,23 @@
    • Upgrade googlemaps to 2.5.1 (@fabaff - #9653) (sensor.google_travel_time docs)
    • mqtt_statestream: Add options to publish attributes/timestamps (@mw-white - #9645) (mqtt_statestream docs)
    • Fixed bugs related to exception handling in pythonegardia. Updating package requirement accordingly (@jeroenterheerdt - #9663) (alarm_control_panel.egardia docs)
      • -
    • Update google-api-python-client to 1.6.4 (@arsaboo - #9658) (google docs)
      • +
    • Update google-api-python-client to 1.6.4 (@arsaboo - #9658) (google docs)
    • Bump abode to 0.11.9 (@MisterWil - #9660) (abode docs)
    • Unit tests to improve core coverage (@armills - #9659)
    • Upgrade pyitachip2ir to 0.0.7 (@alanfischer - #9669) (remote.itach docs)
    • Fix typo in cancel_command description (@FletcherAU - #9671)
    • Rename input_slider to input_number and add numeric text box option (@BioSehnsucht - #9494) (demo docs) (input_number docs) (breaking change)
    • Properly handle an invalid end_time (@alanfischer - #9675) (history docs)
      • -
    • Support new feature to push API data to hassio (@pvizeli - #9679) (hassio docs)
      • +
    • Support new feature to push API data to hassio (@pvizeli - #9679) (hassio docs)
    • Adding ignore capability to Egardia component (@jeroenterheerdt - #9676) (alarm_control_panel.egardia docs)
      • -
    • Fix Google Calendar/oauth2client warning (@mbrrg - #9677) (google docs)
      • +
    • Fix Google Calendar/oauth2client warning (@mbrrg - #9677) (google docs)
    • Implement DSMR5 support. (@aequitas - #9686) (sensor.dsmr docs)
    • Add Tibber sensor (@danielhiversen - #9661) (sensor.tibber docs) (new-platform)
    • Add recorder purge service, rework purge timer (@milanvo - #9523) (breaking change)
    • Fix restore state by filter out null value row from DB query (@milanvo - #9690) (history docs)
    • Updating clicksendaudio component based on feedback (@jeroenterheerdt - #9692) (notify.clicksendaudio docs) (new-platform)
    • Refactoring of onewire sensor component (@bestlibre - #9691) (sensor.onewire docs)
      • -
    • HassIO replace config changes (@pvizeli - #9695) (hassio docs)
      • +
    • HassIO replace config changes (@pvizeli - #9695) (hassio docs)
    • Fixed typo in opencv (@arsaboo - #9697) (image_processing.opencv docs) (breaking change)
    • [light.tradfri] async support with resource observation. (@lwis - #7815) (tradfri docs) (light.tradfri docs) (breaking change)
    • Create secrets file in default config (@balloob - #9685)
      • diff --git a/blog/categories/announcements/atom.xml b/blog/categories/announcements/atom.xml index 759ebc202a..a597ec4ab6 100644 --- a/blog/categories/announcements/atom.xml +++ b/blog/categories/announcements/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Announcements | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index 0ab3263c11..3efcd57e95 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index e419f02ef4..23e63ff850 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-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 944b6e5ea1..dce7d62837 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ @@ -151,7 +151,7 @@ Leaving... Now reset the device. You should then be able to use the [REPL (Read Evaluate Print Loop)](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#getting-a-micropython-repl-prompt). On Linux there is `minicom` or `picocom`, on a Mac you can use `screen` (eg. `screen /dev/tty.SLAB_USBtoUART 115200`), and on Windows there is Putty to open a serial connection and get the REPL prompt. -The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is neccessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post. +The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is necessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post. ```bash $ sudo minicom -D /dev/ttyUSB0 diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index eaf6259980..b73bc56a17 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-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ @@ -315,7 +315,7 @@ Instead of running [InfluxDB](https://www.influxdata.com/) and Grafana on a Rasp 2017-03-28T06:00:00+00:00 https://home-assistant.io/blog/2017/03/28/http-to-mqtt-bridge - - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml index 296f34a869..d3af6347ee 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-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ @@ -309,7 +309,7 @@ Controlling a device can, just like state, be done through cloud and/or local co These devices are not able to be controlled. They will only offer state. ### Poll State after sending command -These devices will require the state to be polled after sending a command to see if a command was successfull. +These devices will require the state to be polled after sending a command to see if a command was successful. Advantages: @@ -392,7 +392,7 @@ When this happens, your house should be able to keep functioning. The cloud shou - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/media/atom.xml b/blog/categories/media/atom.xml index 7f290ed9fb..82c6fa4267 100644 --- a/blog/categories/media/atom.xml +++ b/blog/categories/media/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Media | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/merchandise/atom.xml b/blog/categories/merchandise/atom.xml index 37a6f48130..4e14cc5fbc 100644 --- a/blog/categories/merchandise/atom.xml +++ b/blog/categories/merchandise/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Merchandise | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index 9d6aa5bc62..a310e8db82 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ @@ -168,7 +168,7 @@ Leaving... Now reset the device. You should then be able to use the [REPL (Read Evaluate Print Loop)](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#getting-a-micropython-repl-prompt). On Linux there is `minicom` or `picocom`, on a Mac you can use `screen` (eg. `screen /dev/tty.SLAB_USBtoUART 115200`), and on Windows there is Putty to open a serial connection and get the REPL prompt. -The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is neccessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post. +The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is necessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post. ```bash $ sudo minicom -D /dev/ttyUSB0 diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index c1c69e8534..d4c363e1f3 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ @@ -220,7 +220,7 @@ mqtt: broker: localhost ``` -Replace `localhost` with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path `smartthings//` +Replace `localhost` with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path `smartthings//` For example, my Dimmer Z-Wave Lamp is called "Fireplace Lights" in SmartThings. The following topics are published: diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index 0d68a68d75..4234a6138e 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 965875436a..c22adbb87f 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index 45795684ea..56f0ff72f0 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-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml index f56864ec44..915ff06ea0 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-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index adeff17c2f..ebe2b02ac7 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-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ @@ -305,7 +305,7 @@ Experiencing issues introduced by this release? Please report them in our [issue [abode docs]: https://home-assistant.io/components/abode/ [alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/ [alarm_control_panel.manual_mqtt docs]: https://home-assistant.io/components/alarm_control_panel.manual_mqtt/ -[alexa.smart_home docs]: https://home-assistant.io/components/alexa.smart_home/ +[alexa.smart_home docs]: https://home-assistant.io/components/alexa/ [apple_tv docs]: https://home-assistant.io/components/apple_tv/ [arlo docs]: https://home-assistant.io/components/arlo/ [binary_sensor.raincloud docs]: https://home-assistant.io/components/binary_sensor.raincloud/ @@ -324,9 +324,9 @@ Experiencing issues introduced by this release? Please report them in our [issue [duckdns docs]: https://home-assistant.io/components/duckdns/ [ecobee docs]: https://home-assistant.io/components/ecobee/ [emulated_hue docs]: https://home-assistant.io/components/emulated_hue/ -[google docs]: https://home-assistant.io/components/google/ +[google docs]: https://home-assistant.io/components/calendar.google/ [group docs]: https://home-assistant.io/components/group/ -[hassio docs]: https://home-assistant.io/components/hassio/ +[hassio docs]: https://home-assistant.io/hassio/ [history docs]: https://home-assistant.io/components/history/ [homematic docs]: https://home-assistant.io/components/homematic/ [http docs]: https://home-assistant.io/components/http/ @@ -381,7 +381,7 @@ Experiencing issues introduced by this release? Please report them in our [issue [tradfri docs]: https://home-assistant.io/components/tradfri/ [upnp docs]: https://home-assistant.io/components/upnp/ [usps docs]: https://home-assistant.io/components/usps/ -[vacuum.xiaomi docs]: https://home-assistant.io/components/vacuum.xiaomi/ +[vacuum.xiaomi docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/ [wink docs]: https://home-assistant.io/components/wink/ [zwave docs]: https://home-assistant.io/components/zwave/ [forum]: https://community.home-assistant.io/ @@ -889,7 +889,7 @@ frontend: - Skip automatic events older than latest data ([@armills] - [#9230]) ([device_tracker.automatic docs]) - title and message was swapped in pushbullet ([@danielhiversen] - [#9241]) ([notify.pushbullet docs]) - Fix possible KeyError ([@MartinHjelmare] - [#9242]) ([mysensors docs]) -- WIP: Homematic improvments with new hass interfaces ([@pvizeli] - [#9058]) ([homematic docs]) ([binary_sensor.homematic docs]) ([climate.homematic docs]) ([cover.homematic docs]) ([light.homematic docs]) ([sensor.homematic docs]) ([switch.homematic docs]) (breaking change) +- WIP: Homematic improvements with new hass interfaces ([@pvizeli] - [#9058]) ([homematic docs]) ([binary_sensor.homematic docs]) ([climate.homematic docs]) ([cover.homematic docs]) ([light.homematic docs]) ([sensor.homematic docs]) ([switch.homematic docs]) (breaking change) - Add available to sonos ([@pvizeli] - [#9243]) ([media_player.sonos docs]) - Make sure Ring binary_sensor state will update only if device_id matches ([@tchellomello] - [#9247]) ([binary_sensor.ring docs]) - Added configurable timeout for receiver HTTP requests | Additional AV… ([@scarface-4711] - [#9244]) ([media_player.denonavr docs]) diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index f39460d491..4512e761f6 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index 59f31282ae..736bee6b34 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index b7c44d656b..d1b0de009b 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index 09d1258fbe..62e92e25bc 100644 --- a/blog/categories/user-stories/atom.xml +++ b/blog/categories/user-stories/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: User-Stories | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index eaf124c376..7958f9d163 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 7746760bf9..838ccaf9eb 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2017-10-07T22:15:46+00:00 + 2017-10-07T22:42:05+00:00 https://home-assistant.io/ diff --git a/blog/posts/12/index.html b/blog/posts/12/index.html index 6c90498560..7898d6894d 100644 --- a/blog/posts/12/index.html +++ b/blog/posts/12/index.html @@ -89,7 +89,7 @@

      Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.

      -

      I would like to give a shout out to Greg Dowling (@pavoni) as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!

      +

      I would like to give a shout out to Greg Dowling (@pavoni) as every release includes new work from him. He is constantly adding support for new platforms or improving the reliability of existing components and platforms. Keep up the good work!

      This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See the demo to see this in action and read more in the group documentation how to get started.

      @@ -368,7 +368,7 @@ In this tutorial I will explain how you can activate Tasker tasks from Home Assi

      -The InfluxDB database is a so-called time series database primarly designed to store sensor data and real-time analytics.

      +The InfluxDB database is a so-called time series database primarily designed to store sensor data and real-time analytics.

      The influxdb component makes it possible to transfer all state changes from Home Assistant to an external InfluxDB database.

      Read on →
      diff --git a/blog/posts/13/index.html b/blog/posts/13/index.html index f2f899f5de..3988be48d3 100644 --- a/blog/posts/13/index.html +++ b/blog/posts/13/index.html @@ -252,7 +252,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
      -

      We discovered two issues annoying enough to warrent the release of 0.7.5:

      +

      We discovered two issues annoying enough to warrant the release of 0.7.5:

      • Home Assistant package did not include the CloudMQTT certificate.
      • A bug in the core caused issues when some platforms are loaded twice.
        • diff --git a/blog/posts/15/index.html b/blog/posts/15/index.html index 435103f6d4..eca86cfb05 100644 --- a/blog/posts/15/index.html +++ b/blog/posts/15/index.html @@ -202,7 +202,7 @@ The old logo, the new detailed logo and the new simple logo.

        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.

        +

        A new toggle has been added to 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.

        Read on →
        @@ -243,7 +243,7 @@ The old logo, the new detailed logo and the new simple logo.

        -Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time. +Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transferred to anyone at any time.

        Read on →
      @@ -349,7 +349,7 @@ Home Assistant now supports --open-ui and

      Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.

      -

      The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The intial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.

      +

      The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The initial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.

      Most devices still require some sort of interaction from the user after being discovered - be it a button being pressed or some sort of authentication. This is a challenge that will be solved in the future.

      To enable the discovery component, add the following to your home-assistant.conf:

      [discovery]
@@ -414,7 +414,7 @@ Home Assistant now supports --open-ui and
   
      
     
      The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home.
 This article will try to explain how they all relate.
      
-
      The first thing to introduce is the Internet of Things (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.
      
+
      The first thing to introduce is the Internet of Things (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its reservoir.
      
 
      There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a hub.
      
 
      As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers home control.
      
 
      
diff --git a/blog/posts/2/index.html b/blog/posts/2/index.html
index ae18810af6..e0744fb7bd 100644
--- a/blog/posts/2/index.html
+++ b/blog/posts/2/index.html
@@ -231,7 +231,7 @@
   
    • Fix TP-Link light brightness issue #8744. (@gollo - #8755)
      • 
   
    • Fix typo in script error (@n8henrie - #8754)
      • 
   
    • Fix tradfri error spam (@MartinHjelmare - #8738) (light.tradfri docs)
      • 
-  
    • Media Player - Pioneer: Supress exception if host is not available (fixes #8684) (@fabaff - #8732) (media_player.pioneer docs)
      • 
+  
    • Media Player - Pioneer: Suppress exception if host is not available (fixes #8684) (@fabaff - #8732) (media_player.pioneer docs)
      • 
   
    • Telegram Bot: Retry set_webhook up to three times, reduce timeout to 5s again (@azogue - #8716) (telegram_bot.webhooks docs)
      • 
   
    • Fixed sensor issue with Google Wifi routers in bridge mode (@fronzbot - #8710) (sensor.google_wifi docs)
      • 
   
    • Fix alexa cards (@balloob - #8708) (alexa docs)
      • 
diff --git a/blog/posts/5/index.html b/blog/posts/5/index.html
index d7ebb21452..56a4b08eae 100644
--- a/blog/posts/5/index.html
+++ b/blog/posts/5/index.html
@@ -88,7 +88,7 @@
   
      
 
   
      
-    
      You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the Thomas-Krenn-Award put us on the 2nd place. This is an awesome achievment for an independent community project.
      
+    
      You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the Thomas-Krenn-Award put us on the 2nd place. This is an awesome achievement for an independent community project.
      
 
      I would like to thanks all contributors. Your endless effort made this possible.
      
 
      
 
      The prize beside the very nice trophy contains hardware and we want to give that hardware partically away. We won four Low Energy Server v2 (LES) units with an Intel Celeron N2930, 8 GB of RAM, and a mSATA of 128 GB (one unit with 64 GB). We were thinking about to keep one of those units in Europe and one in North America for testing and to use during workshops and events. But the other two will go to interested parties.
      
@@ -126,7 +126,7 @@
   
      
 
   
      
-    
      The idea of creating HTTP to MQTT bridge appeared when I was trying to integrate Google Assistant with my Home Assistant after watching BRUH Automation video. Right now there is no MQTT service available in IFTTT. Existing integration solution uses Maker Webhooks which requires that your Home Assistant instance is publically accessible, which I think brings some security concerns or simply not always possible to set up.
      
+    
      The idea of creating HTTP to MQTT bridge appeared when I was trying to integrate Google Assistant with my Home Assistant after watching BRUH Automation video. Right now there is no MQTT service available in IFTTT. Existing integration solution uses Maker Webhooks which requires that your Home Assistant instance is publicly accessible, which I think brings some security concerns or simply not always possible to set up.
      
 
      The HTTP to MQTT bridge should fill that gap. The idea is to receive messages using HTTP requests and transfer them to your MQTT broker, which can be contacted by Home Assistant. The HTTP to MQTT bridge is written using Node.js with Express for the server part and MQTT.js for the client.
      
       Read on →
   
      
diff --git a/blog/posts/6/index.html b/blog/posts/6/index.html
index a4047876b6..4bf801fccd 100644
--- a/blog/posts/6/index.html
+++ b/blog/posts/6/index.html
@@ -152,7 +152,7 @@ On the close horizon from @Landrash th
      -

      One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.

      +

      One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assistant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.

      Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.

      Read on →
      @@ -258,7 +258,7 @@ On the close horizon from @Landrash th
    • 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)
      • +
    • Fan - MQTT: Don’t 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)
      • @@ -517,7 +517,7 @@ You have to note:

      Hello and Happy New Year!

      I am not Paulus. My name is Ben. I’m the creator of the BRUH Automation YouTube channel. If you’ve ever seen any of my videos then you’ll know I love home automation and Home Assistant.

      -

      I wanted to share some exciting stats from one of my latest projects - Control My Christmas tree! For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publically accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.

      +

      I wanted to share some exciting stats from one of my latest projects - Control My Christmas tree! For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publicly accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.

      I added three devices to the Home Assistant instance - a Wemo Insight, Sonoff Switch (running MQTT firmware), and a DIY MQTT Digital LED strip. After adding a few 3D printed Star War decorations, the tree was ready to go!

      @@ -549,7 +549,7 @@ You have to note:

      A year ago Home Assistant 0.10 landed. Last weekend we released 0.35. Doing 25 releases in a year is a big accomplishment by the community and each release has moved us forwards leaps and bounds. In this year alone we have seen 2800 pull requests on the main repo alone, that’s more than 7 a day!

      -

      One of the things that Jon Walker, the founder of the company I work for (AppFolio), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Everytime you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.

      +

      One of the things that Jon Walker, the founder of the company I work for (AppFolio), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Every time you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.

      That’s why I structured Home Assistant around a two week release cycle. It makes sure that features get out fast and it also forces us to not accumulate a backlog of things to document or test properly. Every two weeks we can start fresh. This makes it easy for new people to start contributing because it’s clear when things go out and people are not afraid to miss a release.

      However, being on a two week release cycle also means that the community has to rally each two weeks to make sure everything is ready to go. A lot of people are involved in making sure that all pieces are in place, to all of those: thank you! Thank you for all the time and effort you put in to make Home Assistant the best home automation software out there.

      Another big thanks goes out to the developers of the Python language and all the open source libraries and tools that Home Assistant depends on. Making quality software is not a small feat and all of you can be proud of yourself.

      @@ -773,7 +773,7 @@ You have to note:
    • Fix InfluxDB without authentication (@balloob)
    • Fix Kodi without authentication (@balloob)
    • Fix incorrect caching of /api/error_log (@armills)
      • -
    • Fix incorrect ordering of service calls which could cause delays inbetween turning on multiple entities (@balloob)
      • +
    • Fix incorrect ordering of service calls which could cause delays between turning on multiple entities (@balloob)
    • Fix Nest Climate temperature issues (@technicalpickles)

      • Release 0.34.5 - December 12

      diff --git a/blog/posts/7/index.html b/blog/posts/7/index.html index d48f3e1b94..88ccd52de3 100644 --- a/blog/posts/7/index.html +++ b/blog/posts/7/index.html @@ -548,7 +548,7 @@
    • 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)
      • +
    • Z-Wave: Add association service (@turbokongen)
    • Frontend - Services dev tool: persist state and tweak UI (@justweb1)
    • Sensor: Support added for scraping websites (@fabaff)
    • Clean up of tests (@capellini)
      • @@ -612,7 +612,7 @@

      Yes, after only nine days comes 0.30. Don’t worry, we will try to keep our usual release cycle and not start to release every day.

      -

      We guess that you already know: The Raspberry Pi image is available now. For Hassbian, @Landrash has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to recieve feedback, issue report, and suggestions to improve it.

      +

      We guess that you already know: The Raspberry Pi image is available now. For Hassbian, @Landrash has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to receive feedback, issue report, and suggestions to improve it.

      A large amount of resources of the development are still focusing on the effort to move Home Assistant further to asynchronous programming. It’s a labor-intensive task, comes with segmentation faults, and unstable instances when certain combinations of sensors are used. The benefit will be more speed in the near future.

      To reduce the run-time of your tests, @balloob did a lot of tweaking. For now the RFXtrx tests are excluded which cut the needed time for running on your Pull Request in half.

      Documentation

      @@ -936,7 +936,7 @@

      Climate and cover

      There are countless bugfixes included in this release which will make your experience with the climate and the cover platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to @turbokongen, @pvizeli, @djbanks, @danielperna84, and others the improvements on the code and the frontend side is continuing…

      API documentation

      -

      The Home Assistant API Documentation is a great addition to the already exisiting user documentation. The focus is not end-users but developers who whant to get details about the code without actually browsing the code on Github.

      +

      The Home Assistant API Documentation is a great addition to the already exisiting user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.

      Configuration validation

      The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to @kellerza, @fabaff, @Teagan42, and @pvizeli for your effort!

      All changes

      diff --git a/components/alert/index.html b/components/alert/index.html index 930fac7733..620e98f0b8 100644 --- a/components/alert/index.html +++ b/components/alert/index.html @@ -206,10 +206,10 @@ Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/automation/index.html b/components/automation/index.html index 29d5ddc2da..892b18115e 100644 --- a/components/automation/index.html +++ b/components/automation/index.html @@ -126,10 +126,10 @@ Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/binary_sensor.wink/index.html b/components/binary_sensor.wink/index.html index b41a6f6de0..5b5d76dc65 100644 --- a/components/binary_sensor.wink/index.html +++ b/components/binary_sensor.wink/index.html @@ -82,7 +82,7 @@
    • Window/Door sensors
    • Motion sensors
    • Ring Door bells (No hub required)
      • -
    • Liquid presense sensors
      • +
    • Liquid presence sensors
    • Z-wave lock key codes
    • Lutron connected bulb remote buttons
    • Wink Relay buttons and presence detection
      • diff --git a/components/counter/index.html b/components/counter/index.html index 664c3773c3..27c6595be1 100644 --- a/components/counter/index.html +++ b/components/counter/index.html @@ -199,10 +199,10 @@ Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/device_sun_light_trigger/index.html b/components/device_sun_light_trigger/index.html index 1c3ec16f6c..075ab58649 100644 --- a/components/device_sun_light_trigger/index.html +++ b/components/device_sun_light_trigger/index.html @@ -139,10 +139,10 @@ Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/dweet/index.html b/components/dweet/index.html index c52e3acb45..4bf61f5eea 100644 --- a/components/dweet/index.html +++ b/components/dweet/index.html @@ -86,7 +86,7 @@ dweet: name: HAExport whitelist: - - input_slider.brightness + - input_number.brightness - input_boolean.notify_home - sensor.weather_temperature - sensor.cpu diff --git a/components/ffmpeg/index.html b/components/ffmpeg/index.html index 7fa2d2fae8..15f8861f70 100644 --- a/components/ffmpeg/index.html +++ b/components/ffmpeg/index.html @@ -79,7 +79,7 @@ You need the ffmpeg binary in your system path. On Debian 8 or Raspbian (Jessie) you can install it from debian-backports. If you want hardware acceleration support on a Raspberry Pi, you will need to build from source by yourself. Windows binaries are available on the FFmpeg website.

      -If you are using Hass.io then just move forward to the configuration as all requirements are already fullfilled. +If you are using Hass.io then just move forward to the configuration as all requirements are already fulfilled.

      To set it up, add the following information to your configuration.yaml file:

      ffmpeg:
diff --git a/components/hdmi_cec/index.html b/components/hdmi_cec/index.html
index 3f1e64dc3a..014303e747 100644
--- a/components/hdmi_cec/index.html
+++ b/components/hdmi_cec/index.html
@@ -282,10 +282,10 @@ language:      ???
             Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/ifttt/index.html b/components/ifttt/index.html index 0567cdceeb..d84eb3926b 100644 --- a/components/ifttt/index.html +++ b/components/ifttt/index.html @@ -222,10 +222,10 @@ You need to setup a unique trigger for each event you sent to IFTTT. Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/index.html b/components/index.html index f0ae40a103..4982605a13 100644 --- a/components/index.html +++ b/components/index.html @@ -432,8 +432,8 @@ var allComponents = [ {url:"/components/sensor.influxdb/", title:"InfluxDB Sensor", cat:"sensor", featured: false, v: "0.32", logo: "influxdb.png"}, {url:"/components/input_boolean/", title:"Input Boolean", cat:"automation", featured: false, v: "0.0", logo: "home-assistant.png"}, {url:"/components/input_datetime/", title:"Input Datetime", cat:"automation", featured: false, v: "0.55", logo: "home-assistant.png"}, +{url:"/components/input_number/", title:"Input Number", cat:"automation", featured: false, v: "0.16", logo: "home-assistant.png"}, {url:"/components/input_select/", title:"Input Select", cat:"automation", featured: false, v: "0.13", logo: "home-assistant.png"}, -{url:"/components/input_slider/", title:"Input Slider", cat:"automation", featured: false, v: "0.16", logo: "home-assistant.png"}, {url:"/components/input_text/", title:"Input Text", cat:"automation", featured: false, v: "0.53", logo: "home-assistant.png"}, {url:"/components/notify.instapush/", title:"Instapush", cat:"notifications", featured: false, v: "0.7", logo: "instapush.png"}, {url:"/components/fan.insteon_local/", title:"Insteon (Local) Fan", cat:"fan", featured: false, v: "0.0", logo: "insteon.png"}, @@ -1397,8 +1397,8 @@ allComponents.pop(); // remove placeholder element at the end
    • InfluxDB Sensor
    • Input Boolean
    • Input Datetime
      • +
    • Input Number
    • Input Select
      • -
    • Input Slider
    • Input Text
    • Instapush
    • Insteon (Local) Fan
      • diff --git a/components/input_boolean/index.html b/components/input_boolean/index.html index f428f401e5..f7786f56ae 100644 --- a/components/input_boolean/index.html +++ b/components/input_boolean/index.html @@ -156,10 +156,10 @@ Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/input_datetime/index.html b/components/input_datetime/index.html index b203c6e18f..5f15bd0efc 100644 --- a/components/input_datetime/index.html +++ b/components/input_datetime/index.html @@ -151,10 +151,10 @@ Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/input_number/index.html b/components/input_number/index.html new file mode 100644 index 0000000000..164251e186 --- /dev/null +++ b/components/input_number/index.html @@ -0,0 +1,349 @@ + + + + + + + + + Input Number - Home Assistant + + + + + + + + + + + + + + + + + + + + + + +
      +
      +
      +
      + + + Home Assistant + +
      +
      + + +
      +
      +
      +
      +
      +
      +
      +
      +
      +

      + Input Number +

      +
      +
      +

      The input_number component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. The frontend can display a slider, or a numeric input box. Changes to the slider or numeric input box generate state events. These state events can be utilized as automation triggers as well.

      +

      To enable this input number in your installation, add the following lines to your configuration.yaml:

      +
      # Example configuration.yaml entry
+input_number:
+  slider1:
+    name: Slider
+    initial: 30
+    min: -20
+    max: 35
+    step: 1
+  box1:
+    name: Numeric Input Box
+    initial: 30
+    min: -20
+    max: 35
+    step: 1
+    mode: box
+
      +
      +

      Configuration variables:

      +
        +
      • [alias] (Required): Alias for the input. Multiple entries are allowed. +
          +
        • min (Required): Minimum value.
          • +
        • max (Required): Maximum value.
          • +
        • name (Optional): Friendly name of the input.
          • +
        • initial (Optional): Initial value when Home Assistant starts. Defaults to 0.
          • +
        • step (Optional): Step value for the slider. Defaults to 1.
          • +
        • mode (Optional): Can specify box, or slider. Defaults to slider.
          • +
        +
        • +
      +

      Automation Examples

      +

      Here’s an example of input_number being used as a trigger in an automation.

      +
      
+# Example configuration.yaml entry using 'input_number' as a trigger in an automation
+
+# Define input_number
+input_number:
+  bedroom_brightness:
+    name: Brightness
+    initial: 254
+    min: 0
+    max: 254
+    step: 1
+
+# Automation.     
+automation:
+  - alias: Bedroom Light - Adjust Brightness
+    trigger:
+      platform: state
+      entity_id: input_number.bedroom_brightness
+    action:
+      - service: light.turn_on
+# Note the use of 'data_template:' below rather than the normal 'data:' if you weren't using an input variable
+        data_template:
+          entity_id: light.bedroom
+          brightness: '{{ trigger.to_state.state | int }}'
+
+
      +
      +

      Another code example using input_number, this time being used in an action in an automation.

      +
      
+# Example configuration.yaml entry using 'input_number' in an action in an automation
+
+# Define 'input_select'
+input_select:
+  scene_bedroom:
+    name: Scene
+    options:
+      - Select
+      - Concentrate
+      - Energize
+      - Reading
+      - Relax
+      - 'OFF'
+    initial: 'Select'
+    
+# Define input_number
+input_number:
+  bedroom_brightness:
+    name: Brightness
+    initial: 254
+    min: 0
+    max: 254
+    step: 1
+
+# Automation.     
+automation:
+  - alias: Bedroom Light - Custom
+    trigger:
+      platform: state
+      entity_id: input_select.scene_bedroom
+      to: CUSTOM
+    action:
+      - service: light.turn_on
+# Again, note the use of 'data_template:' rather than the normal 'data:' if you weren't using an input variable.
+        data_template:
+          entity_id: light.bedroom
+          brightness: '{{ states.input_number.bedroom_brightness.state | int }}'
+
+
      +
      +

      Example of input_number being used in a bidirectional manner, both being set by and controlled by an MQTT action in an automation.

      +
      
+# Example configuration.yaml entry using 'input_number' in an action in an automation
+   
+# Define input_number
+input_number:
+  target_temp:
+    name: Target Heater Temperature Slider
+    min: 1
+    max: 30
+    step: 1
+    unit_of_measurement: step  
+    icon: mdi:target
+
+# Automation.     
+ # This automation script runs when a value is received via MQTT on retained topic: setTemperature
+ # It sets the value slider on the GUI. This slides also had its own automation when the value is changed.
+- alias: Set temp slider
+  trigger:
+    platform: mqtt
+    topic: "setTemperature"
+   # entity_id: input_number.target_temp
+  action:
+     service: input_number.set_value
+     data_template:
+      entity_id: input_number.target_temp
+      value: '{{ trigger.payload}}'
+
+ # This automation script runs when the target temperature slider is moved.
+ # It publishes its value to the same MQTT topic it is also subscribed to.
+- alias: Temp slider moved
+  trigger:
+    platform: state
+    entity_id: input_number.target_temp
+  action:
+    service: mqtt.publish
+    data_template:
+      topic: "setTemperature"
+      retain: true
+      payload: '{{ states.input_number.target_temp.state | int }}'
+
+
      +
      +
      +
      + +
      +
      + + + + + + + diff --git a/components/input_select/index.html b/components/input_select/index.html index d7396baf3e..602d88dca9 100644 --- a/components/input_select/index.html +++ b/components/input_select/index.html @@ -236,10 +236,10 @@ Because YAML defines booleans as eq Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/input_slider/index.html b/components/input_slider/index.html index 4b5c8fc405..baffd2f98b 100644 --- a/components/input_slider/index.html +++ b/components/input_slider/index.html @@ -1,341 +1,10 @@ - - - - - - - - - Input Slider - Home Assistant - - - - - - - - - - - - - - - - - - - - - - -
      -
      -
      -
      - - - Home Assistant - -
      -
      - - -
      -
      -
      -
      -
      -
      -
      -
      -
      -

      - Input Slider -

      -
      -
      -

      The input_slider component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the slider generate state events. These state events can be utilized as automation triggers as well.

      -

      To enable this input sliders in your installation, add the following lines to your configuration.yaml:

      -
      # Example configuration.yaml entry
-input_slider:
-  slider1:
-    name: Slider 1
-    initial: 30
-    min: -20
-    max: 35
-    step: 1
-
      -
      -

      Configuration variables:

      -
        -
      • [alias] (Required): Alias for the slider input. Multiple entries are allowed. -
          -
        • min (Required): Minimum value for the slider.
          • -
        • max (Required): Maximum value for the slider.
          • -
        • name (Optional): Friendly name of the slider input.
          • -
        • initial (Optional): Initial value when Home Assistant starts. Defaults to 0.
          • -
        • step (Optional): Step value for the slider. Defaults to 1.
          • -
        -
        • -
      -

      Automation Examples

      -

      Here’s an example of input_slider being used as a trigger in an automation.

      -
      
-# Example configuration.yaml entry using 'input_slider' as a trigger in an automation
-
-# Define input_slider
-input_slider:
-  bedroom_brightness:
-    name: Brightness
-    initial: 254
-    min: 0
-    max: 254
-    step: 1
-
-# Automation.     
-automation:
-  - alias: Bedroom Light - Adjust Brightness
-    trigger:
-      platform: state
-      entity_id: input_slider.bedroom_brightness
-    action:
-      - service: light.turn_on
-# Note the use of 'data_template:' below rather than the normal 'data:' if you weren't using an input variable
-        data_template:
-          entity_id: light.bedroom
-          brightness: '{{ trigger.to_state.state | int }}'
-
-
      -
      -

      Another code example using input_slider, this time being used in an action in an automation.

      -
      
-# Example configuration.yaml entry using 'input_slider' in an action in an automation
-
-# Define 'input_select'
-input_select:
-  scene_bedroom:
-    name: Scene
-    options:
-      - Select
-      - Concentrate
-      - Energize
-      - Reading
-      - Relax
-      - 'OFF'
-    initial: 'Select'
-    
-# Define input_slider
-input_slider:
-  bedroom_brightness:
-    name: Brightness
-    initial: 254
-    min: 0
-    max: 254
-    step: 1
-
-# Automation.     
-automation:
-  - alias: Bedroom Light - Custom
-    trigger:
-      platform: state
-      entity_id: input_select.scene_bedroom
-      to: CUSTOM
-    action:
-      - service: light.turn_on
-# Again, note the use of 'data_template:' rather than the normal 'data:' if you weren't using an input variable.
-        data_template:
-          entity_id: light.bedroom
-          brightness: '{{ states.input_slider.bedroom_brightness.state | int }}'
-
-
      -
      -

      Example of input_slider being used in a bidirectional manner, both being set by and controlled by an MQTT action in an automation.

      -
      
-# Example configuration.yaml entry using 'input_slider' in an action in an automation
-   
-# Define input_slider
-input_slider:
-  target_temp:
-    name: Target Heater Temperature Slider
-    min: 1
-    max: 30
-    step: 1
-    unit_of_measurement: step  
-    icon: mdi:target
-
-# Automation.     
- # This automation script runs when a value is received via MQTT on retained topic: setTemperature
- # It sets the value slider on the GUI. This slides also had its own automation when the value is changed.
-- alias: Set temp slider
-  trigger:
-    platform: mqtt
-    topic: "setTemperature"
-   # entity_id: input_slider.target_temp
-  action:
-     service: input_slider.select_value
-     data_template:
-      entity_id: input_slider.target_temp
-      value: '{{ trigger.payload}}'
-
- # This automation script runs when the target temperature slider is moved.
- # It publishes its value to the same MQTT topic it is also subscribed to.
-- alias: Temp slider moved
-  trigger:
-    platform: state
-    entity_id: input_slider.target_temp
-  action:
-    service: mqtt.publish
-    data_template:
-      topic: "setTemperature"
-      retain: true
-      payload: '{{ states.input_slider.target_temp.state | int }}'
-
-
      -
      -
      -
      - -
      -
      - - - - - - + + + + Redirecting… + + +

      Redirecting…

      + Click here if you are not redirected. + diff --git a/components/input_text/index.html b/components/input_text/index.html index 9f377c4990..72901a62d7 100644 --- a/components/input_text/index.html +++ b/components/input_text/index.html @@ -138,10 +138,10 @@ Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/keyboard/index.html b/components/keyboard/index.html index ea778e501f..d65ccf5417 100644 --- a/components/keyboard/index.html +++ b/components/keyboard/index.html @@ -135,10 +135,10 @@ Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/light.decora/index.html b/components/light.decora/index.html index 9c956b0855..954f990a2c 100644 --- a/components/light.decora/index.html +++ b/components/light.decora/index.html @@ -92,7 +92,7 @@
    • [mac address] (Required): The bluetooth address of the switch.
      • name (Optional): The custom name to use in the frontend.
        • -
      • api_key (Required): The API key to acces the device.
        • +
      • api_key (Required): The API key to access the device.
      • diff --git a/components/lirc/index.html b/components/lirc/index.html index f872ad0e6a..933fd86904 100644 --- a/components/lirc/index.html +++ b/components/lirc/index.html @@ -176,10 +176,10 @@ end Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/lock.nello/index.html b/components/lock.nello/index.html index 979430b612..7ed53d696d 100644 --- a/components/lock.nello/index.html +++ b/components/lock.nello/index.html @@ -109,7 +109,7 @@ Be aware that if you use your main account for Home Assistant you may not be abl
      • - + diff --git a/components/media_extractor/index.html b/components/media_extractor/index.html index 16deb07060..9607d51cb4 100644 --- a/components/media_extractor/index.html +++ b/components/media_extractor/index.html @@ -97,7 +97,7 @@ Media extractor doesn’t transcode streams, it just tries to find stream that m music: bestaudio[ext=mp3] -

      This configuration sets query for all service calls like: {"entity_id": "media_player.my_sonos", "media_content_id": "https://soundcloud.com/bruttoband/brutto-11", "media_content_type": "music"} to ‘bestaudio’ with mp3 extention.

      +

      This configuration sets query for all service calls like: {"entity_id": "media_player.my_sonos", "media_content_id": "https://soundcloud.com/bruttoband/brutto-11", "media_content_type": "music"} to ‘bestaudio’ with mp3 extension.

      Query examples with explanations:

      • bestvideo - best video only stream
        • diff --git a/components/media_player.frontier_silicon/index.html b/components/media_player.frontier_silicon/index.html index 4501f2d870..7477883609 100644 --- a/components/media_player.frontier_silicon/index.html +++ b/components/media_player.frontier_silicon/index.html @@ -99,7 +99,7 @@
      • port (Optional): The port number. Defaults to 80.
      • password (Optional): PIN code of the Internet Radio. Defaults to 1234.
      -

      Some models use a seperate port (2244) for API access, this can be verified by visiting http://[host]:[port]/device.

      +

      Some models use a separate port (2244) for API access, this can be verified by visiting http://[host]:[port]/device.

      In case your device (friendly name) is called badezimmer, an example automation can look something like this:

      # Example configuration.yaml automation
 alias: "Bathroom Motion Detected"
diff --git a/components/notify.discord/index.html b/components/notify.discord/index.html
index 3b105661f6..41026459dc 100644
--- a/components/notify.discord/index.html
+++ b/components/notify.discord/index.html
@@ -75,7 +75,7 @@
   
   
      
   
      The Discord service is a platform for the notify component. This allows components to send messages to the user using Discord.
      
-
      In order to get a token you need to go to the Discord My Apps page and create a new application. Once the application is ready, create a bot user (Create a Bot User) and activate Require OAuth2 Code Grant. Retreive the Client ID and the (hidden) Token of your bot for later.
      
+
      In order to get a token you need to go to the Discord My Apps page and create a new application. Once the application is ready, create a bot user (Create a Bot User) and activate Require OAuth2 Code Grant. Retrieve the Client ID and the (hidden) Token of your bot for later.
      
 
      When setting up the application you can use this icon.
      
 
      To use Discord notifications, add the following to your configuration.yaml file:
      
 
      # Example configuration.yaml entry
diff --git a/components/proximity/index.html b/components/proximity/index.html
index f66ca38914..29b0c1b752 100644
--- a/components/proximity/index.html
+++ b/components/proximity/index.html
@@ -179,10 +179,10 @@
             Input Datetime
         
         
    • 
-            Input Select
+            Input Number
         
      • 
         
    • 
-            Input Slider
+            Input Select
         
      • 
         
    • 
             Input Text
diff --git a/components/python_script/index.html b/components/python_script/index.html
index 6fa8e15172..6b04f1892a 100644
--- a/components/python_script/index.html
+++ b/components/python_script/index.html
@@ -158,10 +158,10 @@
             Input Datetime
         
      • 
         
    • 
-            Input Select
+            Input Number
         
      • 
         
    • 
-            Input Slider
+            Input Select
         
      • 
         
    • 
             Input Text
diff --git a/components/rest_command/index.html b/components/rest_command/index.html
index 0da5a5d77d..28c99dd3ed 100644
--- a/components/rest_command/index.html
+++ b/components/rest_command/index.html
@@ -140,10 +140,10 @@
             Input Datetime
         
      • 
         
    • 
-            Input Select
+            Input Number
         
      • 
         
    • 
-            Input Slider
+            Input Select
         
      • 
         
    • 
             Input Text
diff --git a/components/script/index.html b/components/script/index.html
index 05707ec35d..62807151c5 100644
--- a/components/script/index.html
+++ b/components/script/index.html
@@ -201,10 +201,10 @@ The preferred way to separate words for better readability is to use underscore
             Input Datetime
         
      • 
         
    • 
-            Input Select
+            Input Number
         
      • 
         
    • 
-            Input Slider
+            Input Select
         
      • 
         
    • 
             Input Text
diff --git a/components/sensor.airvisual/index.html b/components/sensor.airvisual/index.html
index a95b8a0776..809c950c09 100644
--- a/components/sensor.airvisual/index.html
+++ b/components/sensor.airvisual/index.html
@@ -206,7 +206,7 @@ for the overall “health” of the air.
      • dateDate when the event occured.Date when the event occurred.
      description
      -

      Air Polution Level

      +

      Air Pollution Level

      Description: This sensor displays the associated Status (from the above table) for the current AQI.

      Sample Sensor Name: sensor.us_air_pollution_level

      diff --git a/components/sensor.dweet/index.html b/components/sensor.dweet/index.html index 2b6b020ecf..d5a4bde0cc 100644 --- a/components/sensor.dweet/index.html +++ b/components/sensor.dweet/index.html @@ -118,7 +118,7 @@ {'thing': 'ha-sensor', 'created': '2015-12-10T09:46:08.559Z', 'content': {'humiditiy': 81, 'temperature': 23}}       -

      Recieve the latest dweet.

      +

      Receive the latest dweet.

      >>> dweepy.get_latest_dweet_for('ha-sensor')
 [{'thing': 'ha-sensor'', 'created': '2015-12-10T09:43:31.133Z', 'content': {'humidity': 65, 'temperature': 40}}]
      diff --git a/components/sensor.vera/index.html b/components/sensor.vera/index.html index b31023bdb0..27cfd039b4 100644 --- a/components/sensor.vera/index.html +++ b/components/sensor.vera/index.html @@ -76,7 +76,7 @@

      The vera platform allows you to get data from your Vera sensors from within Home Assistant.

      They will be automatically discovered if the vera component is loaded.

      -

      Please note that some vera sensors (such as motion and flood sensors) are armable which means that vera will send alerts (email messages ot txts) when they are armed an change state.

      +

      Please note that some vera sensors (such as motion and flood sensors) are armable which means that vera will send alerts (email messages to txts) when they are armed an change state.

      Home Assistant will display the state of these sensors regardless of the armed state.

      To allow you to change the armed state - Home Assistant will create a switch as well as a sensor for each Armable sensor. You can hide these switches using customization if you wish.

      diff --git a/components/shell_command/index.html b/components/shell_command/index.html index 0979b5eaea..e029bff3d5 100644 --- a/components/shell_command/index.html +++ b/components/shell_command/index.html @@ -94,11 +94,11 @@ - alias: run_set_ac trigger: platform: state - entity_id: input_slider.ac_temperature + entity_id: input_number.ac_temperature action: service: shell_command.set_ac_to_slider -input_slider: +input_number: ac_temperature: name: A/C Setting initial: 24 @@ -108,7 +108,7 @@ shell_command: - set_ac_to_slider: 'irsend SEND_ONCE DELONGHI AC_{{ states.input_slider.ac_temperature.state }}_AUTO' + set_ac_to_slider: 'irsend SEND_ONCE DELONGHI AC_{{ states.input_number.ac_temperature.state }}_AUTO'
      @@ -149,10 +149,10 @@ Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/switch.flux/index.html b/components/switch.flux/index.html index 472d2a19f9..0d17a73880 100644 --- a/components/switch.flux/index.html +++ b/components/switch.flux/index.html @@ -153,10 +153,10 @@ Input Datetime
    • - Input Select + Input Number
    • - Input Slider + Input Select
    • Input Text diff --git a/components/tts.yandextts/index.html b/components/tts.yandextts/index.html index d2f8093bc4..836cdeeeb6 100644 --- a/components/tts.yandextts/index.html +++ b/components/tts.yandextts/index.html @@ -88,7 +88,7 @@
    • language (Optional): The language to use. Defaults to en-US. Supported en-US, ru-RU, uk-UK, tr-TR.
    • codec (Optional): Audio codec. Default is mp3. Supported us mp3, wav, opus.
    • voice (Optional): Speaker voice. Default is zahar. Supported female voices are jane, oksana, alyss, omazh and male voices are zahar and ermil.
      • -
    • emotion (Optional): Speaker emotional intonation. Default is neutral. Also supported are good (freindly) and evil (angry)
      • +
    • emotion (Optional): Speaker emotional intonation. Default is neutral. Also supported are good (friendly) and evil (angry)
    • speed (Optional): Speech speed. Default value is 1. Highest speed is 3 and lowest 0,1

    Please check the API documentation for details. It seems that the English version of documentation is outdated. You could request an API key by email or online.

    diff --git a/cookbook/dim_and_brighten_lights/index.html b/cookbook/dim_and_brighten_lights/index.html index 9c576193a2..231b20d163 100644 --- a/cookbook/dim_and_brighten_lights/index.html +++ b/cookbook/dim_and_brighten_lights/index.html @@ -138,8 +138,8 @@

    There are 2 variables that control the speed of the change for the scripts below. The first is the step, small steps create a smooth transition. The second is the delay, larger delays will create a slower transition.

    -

    To allow flexibility, an Input Slider is used for the step (at the time of writing this, it’s not possible to template the delay when the delay uses milliseconds). Two additional Input Sliders are used to set the minimum and maximum brightness, so that it’s easy to tune that (or manage it through an automation).

    -
    input_slider:
+
    To allow flexibility, an Input Number is used for the step (at the time of writing this, it’s not possible to template the delay when the delay uses milliseconds). Two additional Input Numbers are used to set the minimum and maximum brightness, so that it’s easy to tune that (or manage it through an automation).
    
+
    input_number:
   light_step:
     name: 'Step the lights this much'
     initial: 20
@@ -172,10 +172,10 @@
             entity_id: light.YOUR_LIGHT
             brightness: >-
               {% set current = states.light.YOUR_LIGHT.attributes.brightness|default(0)|int %}
-              {% set step = states('input_slider.light_step')|int %}
+              {% set step = states('input_number.light_step')|int %}
               {% set next = current + step %}
-              {% if next > states('input_slider.light_maximum')|int %}
-                {% set next = states('input_slider.light_maximum')|int %}
+              {% if next > states('input_number.light_maximum')|int %}
+                {% set next = states('input_number.light_maximum')|int %}
               {% endif %}
               {{ next }}
 
@@ -198,10 +198,10 @@
             entity_id: light.YOUR_LIGHT
             brightness: >-
               {% set current = states.light.YOUR_LIGHT.attributes.brightness|default(0)|int %}
-              {% set step = states('input_slider.light_step')|int %}
+              {% set step = states('input_number.light_step')|int %}
               {% set next = current - step %}
-              {% if next < states('input_slider.light_minimum')|int %}
-                {% set next = states('input_slider.light_minimum')|int %}
+              {% if next < states('input_number.light_minimum')|int %}
+                {% set next = states('input_number.light_minimum')|int %}
               {% endif %}
               {{ next }}
 
diff --git a/cookbook/sonos_say/index.html b/cookbook/sonos_say/index.html
index 3cb96c5f04..48a4872812 100644
--- a/cookbook/sonos_say/index.html
+++ b/cookbook/sonos_say/index.html
@@ -111,7 +111,7 @@
         data:
           sonos_entity: media_player.office
           volume: 0.5
-          message: 'Your husband comming home!'
+          message: 'Your husband coming home!'
           delay: '00:00:05'
 
    
 
    
diff --git a/demo/frontend.html b/demo/frontend.html
index ca813ce680..0cb5b14886 100644
--- a/demo/frontend.html
+++ b/demo/frontend.html
@@ -1,5 +1,5 @@
 
\ No newline at end of file
+t},updateStyles:function(e){e&&this.mixin(this.customStyle,e),i?t.updateNativeStyleProperties(this,this.customStyle):(this.isAttached?this._needsStyleProperties()?this._updateStyleProperties():this._styleProperties=null:this.__stylePropertiesInvalid=!0,this._styleCache&&this._styleCache.clear(),this._updateRootStyles())},_updateRootStyles:function(e){e=e||this.root;for(var t,n=Polymer.dom(e)._query(function(e){return e.shadyRoot||e.shadowRoot}),r=0,s=n.length;r0&&l.push(t);return[{removed:a,added:l}]}},Polymer.Collection.get=function(e){return Polymer._collections.get(e)||new Polymer.Collection(e)},Polymer.Collection.applySplices=function(e,t){var n=Polymer._collections.get(e);return n?n._applySplices(t):null},Polymer({is:"dom-repeat",extends:"template",_template:null,properties:{items:{type:Array},as:{type:String,value:"item"},indexAs:{type:String,value:"index"},sort:{type:Function,observer:"_sortChanged"},filter:{type:Function,observer:"_filterChanged"},observe:{type:String,observer:"_observeChanged"},delay:Number,renderedItemCount:{type:Number,notify:!0,readOnly:!0},initialCount:{type:Number,observer:"_initializeChunking"},targetFramerate:{type:Number,value:20},_targetFrameTime:{type:Number,computed:"_computeFrameTime(targetFramerate)"}},behaviors:[Polymer.Templatizer],observers:["_itemsChanged(items.*)"],created:function(){this._instances=[],this._pool=[],this._limit=1/0;var e=this;this._boundRenderChunk=function(){e._renderChunk()}},detached:function(){this.__isDetached=!0;for(var e=0;e=0;t--){var n=this._instances[t];n.isPlaceholder&&t=this._limit&&(n=this._downgradeInstance(t,n.__key__)),e[n.__key__]=t,n.isPlaceholder||n.__setProperty(this.indexAs,t,!0)}this._pool.length=0,this._setRenderedItemCount(this._instances.length),this.fire("dom-change"),this._tryRenderChunk()},_applyFullRefresh:function(){var e,t=this.collection;if(this._sortFn)e=t?t.getKeys():[];else{e=[];var n=this.items;if(n)for(var r=0;r=r;a--)this._detachAndRemoveInstance(a)},_numericSort:function(e,t){return e-t},_applySplicesUserSort:function(e){for(var t,n,r=this.collection,s={},i=0;i=0;i--){var h=a[i];void 0!==h&&this._detachAndRemoveInstance(h)}var c=this;if(l.length){this._filterFn&&(l=l.filter(function(e){return c._filterFn(r.getItem(e))})),l.sort(function(e,t){return c._sortFn(r.getItem(e),r.getItem(t))});var u=0;for(i=0;i>1,a=this._instances[o].__key__,l=this._sortFn(n.getItem(a),r);if(l<0)e=o+1;else{if(!(l>0)){i=o;break}s=o-1}}return i<0&&(i=s+1),this._insertPlaceholder(i,t),i},_applySplicesArrayOrder:function(e){for(var t,n=0;n=0?(e=this.as+"."+e.substring(n+1),i._notifyPath(e,t,!0)):i.__setProperty(this.as,t,!0))}},itemForElement:function(e){var t=this.modelForElement(e);return t&&t[this.as]},keyForElement:function(e){var t=this.modelForElement(e);return t&&t.__key__},indexForElement:function(e){var t=this.modelForElement(e);return t&&t[this.indexAs]}}),Polymer({is:"array-selector",_template:null,properties:{items:{type:Array,observer:"clearSelection"},multi:{type:Boolean,value:!1,observer:"clearSelection"},selected:{type:Object,notify:!0},selectedItem:{type:Object,notify:!0},toggle:{type:Boolean,value:!1}},clearSelection:function(){if(Array.isArray(this.selected))for(var e=0;e
    diff --git a/developers/credits/index.html b/developers/credits/index.html index cc2bc66051..01fc2dbb9b 100644 --- a/developers/credits/index.html +++ b/developers/credits/index.html @@ -77,12 +77,12 @@

    This page contains a list of people who have contributed in one way or another to Home Assistant. Hover over a username to see their contributions.

    Author

    Contributors

    (in alphabetical order)

    This page is irregularly updated using the credits_generator tool. If you think that you are missing, please let us know.

    -

    This page was last updated Wednesday, October 4th 2017, 8:40:03 am UTC.

    +

    This page was last updated Saturday, October 7th 2017, 10:31:01 pm UTC.