update_interval: - # At least one of these must be specified: - days: 0 - hours: 0 - minutes: 3 - seconds: 30 - milliseconds: 0 -+ ## Notes diff --git a/source/_components/sensor.metoffice.markdown b/source/_components/sensor.metoffice.markdown new file mode 100644 index 00000000000..59dd4b8ff3b --- /dev/null +++ b/source/_components/sensor.metoffice.markdown @@ -0,0 +1,51 @@ +--- +layout: page +title: "Met Office Sensor" +description: "Instructions on how to integrate Met Office weather conditions into Home Assistant." +date: 2017-03-23 22:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: metoffice.jpg +ha_category: Weather +ha_release: 0.42 +--- + +The `metoffice` sensor platform uses the Met Office's [DataPoint API][datapoint] for weather data. + +- Each sensor will be given the `device_id` of "Met Office [condition]" +- The sensor checks for new data every minute, starting 30 minutes after the timestamp of the most recent data as the data is updated every half-hour. + +To add the Met Office weather to your installation you'll need to register for a free api key at the link above and then add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +sensor: + - platform: metoffice + api_key: "my-api-key" + monitored_conditions: + - weather + - temperature + - feels_like_temperature + - wind_speed + - wind_direction + - wind_gust + - visibility + - uv + - precipitation + - humidity +``` + +Your location will be detected from your home `latitude` and `longitude` settings. + +Configuration variables: + +- **api_key** (*Required*): Your personal API key from the [Datapoint website][datapoint]. + +
+This sensor is an alternative to the [`metoffice`](/components/weather.metoffice/) weather platform. +The weather platform is easier to configure but less customisable. +
+ +[datapoint]: http://www.metoffice.gov.uk/datapoint diff --git a/source/_components/sensor.netatmo.markdown b/source/_components/sensor.netatmo.markdown index 1aa1bc8fac8..da931ecd21c 100644 --- a/source/_components/sensor.netatmo.markdown +++ b/source/_components/sensor.netatmo.markdown @@ -52,7 +52,7 @@ Configuration variables: - **sum_rain_1**: Rainfall in the last hour in mm. - **sum_rain_24**: Rainfall in mm from 00:00am - 23:59pm. - **WindAngle**: Wind angle - - **WingStrength**: Wind strength + - **WindStrength**: Wind strength - **GustAngle**: Wind gust angle - **GustStrength**: Wind gust strength - **min_temp**: Min temperature for today diff --git a/source/_components/switch.zoneminder.markdown b/source/_components/switch.zoneminder.markdown index e9312a7ca09..5b4702f3256 100644 --- a/source/_components/switch.zoneminder.markdown +++ b/source/_components/switch.zoneminder.markdown @@ -16,7 +16,7 @@ ha_release: 0.31 The `zoneminder` switch platform allows you to toggle the current function of all cameras attached to your [ZoneMinder](https://www.zoneminder.com) instance.-You must have the [ZoneMinder component](/components/zoneminder/) configured to use this. +You must have the [ZoneMinder component](/components/zoneminder/) configured to use this and if ZoneMinder authentication is enabled the account specified in the component configuration must have "Edit" permission for "System".
To enable this switch, add the following lines to your `configuration.yaml` file: diff --git a/source/_components/weather.metoffice.markdown b/source/_components/weather.metoffice.markdown new file mode 100644 index 00000000000..efd8b10daa6 --- /dev/null +++ b/source/_components/weather.metoffice.markdown @@ -0,0 +1,34 @@ +--- +layout: page +title: "Met Office" +description: "Instructions on how to integrate Met Office weather conditions into Home Assistant." +date: 2017-03-23 22:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: metoffice.jpg +ha_category: Weather +ha_release: 0.42 +--- + +The `metoffice` weather platform uses the Met Office's [DataPoint API][datapoint] for weather data. + +To add the Met Office weather platform to your installation you'll need to register for a free api key at the link above and then add the following to your `configuration.yaml` file: + +```yaml +weather: + - platform: metoffice + api_key: "my-api-key" +``` + +Configuration variables: + +- **api_key** (*Required*): Your personal API key from the [Datapoint website][datapoint]. + ++This platform is an alternative to the [`metoffice`](/components/sensor.metoffice/) sensor. +The weather platform is easier to configure but less customisable. +
+ +[datapoint]: http://www.metoffice.gov.uk/datapoint diff --git a/source/_cookbook/configuration_yaml_by_stanvx b/source/_cookbook/configuration_yaml_by_stanvx new file mode 100644 index 00000000000..a40ec0e30be --- /dev/null +++ b/source/_cookbook/configuration_yaml_by_stanvx @@ -0,0 +1,12 @@ +--- +layout: page +title: "Configuration.yaml by Stanvx" +description: "" +date: 2017-04-09 21:35 +sidebar: true +comments: false +sharing: true +footer: true +ha_category: Example configuration.yaml +ha_external_link: https://github.com/stanvx/Home-Assistant-Configuration +--- diff --git a/source/_cookbook/python_component_basic_state.markdown b/source/_cookbook/python_component_basic_state.markdown index b2c1e838e56..623135363b0 100644 --- a/source/_cookbook/python_component_basic_state.markdown +++ b/source/_cookbook/python_component_basic_state.markdown @@ -23,7 +23,7 @@ To get started, create the file `- If your are using the Python Keyring, [autostarting](/getting-started/autostart/) of Home Assistant will no longer work. + If you are using the Python Keyring, [autostarting](/getting-started/autostart/) of Home Assistant will no longer work.
diff --git a/source/_docs/ecosystem/backup/backup_github.markdown b/source/_docs/ecosystem/backup/backup_github.markdown index 2af70720c5c..da9a5521cd6 100644 --- a/source/_docs/ecosystem/backup/backup_github.markdown +++ b/source/_docs/ecosystem/backup/backup_github.markdown @@ -77,6 +77,9 @@ harmony_media_room.conf pyozw.sqlite .* !/.gitignore +html5_push_registrations.conf +ip_bans.yaml +/icloud/* ``` More information on the layout of the file can be found in the [.gitignore manual](https://git-scm.com/docs/gitignore). diff --git a/source/_docs/ecosystem/certificates/lets_encrypt.markdown b/source/_docs/ecosystem/certificates/lets_encrypt.markdown index 5a6918009cb..caac6eb191c 100644 --- a/source/_docs/ecosystem/certificates/lets_encrypt.markdown +++ b/source/_docs/ecosystem/certificates/lets_encrypt.markdown @@ -9,8 +9,8 @@ sharing: true footer: true --- --Before exposing your Home Aassistant instance to the outside world it is ESSENTIAL that you have set a password following the advice on the [http](https://home-assistant.io/docs/configuration/basic/) page. +
+Before exposing your Home Assistant instance to the outside world it is ESSENTIAL that you have set a password following the advice on the [http](https://home-assistant.io/docs/configuration/basic/) page.
@@ -19,7 +19,7 @@ This guide was added by mf_social on 16/03/2017 and was valid at the time of wri * You can access your Home Assistant instance across your local network, and access the device that it is on via SSH from your local network. * You know the internal IP address of your router and can access your router's configuration pages. * You have already set up a password for your Home Assistant instance, following the advice on this page: [http](https://home-assistant.io/docs/configuration/basic/) - * You want to access your Home Assistant instance when you are away from home (ie, not connected to your local network) and secure it with an TLS/SSL certificate. + * You want to access your Home Assistant instance when you are away from home (ie, not connected to your local network) and secure it with a TLS/SSL certificate. * You have a basic understanding of the phrases I have used so far. * You are not currently running anything on port 80 on your network (you'd know if you were). * If you are not using Home Assistant on a Debian/Raspian/Hassbian system you will be able to convert any of the terminology I use in to the correct syntax for your system. @@ -49,7 +49,7 @@ Now, to speak to the outside world your connection goes through a router. Your r So, when we want to connect to our Home Assistant instance from outside our network we will need to call the correct extension number, at the correct phone number, in the correct area code. -We will be looking for a system to run like this (in this example I will pretend our exernal IP is 12.12.12.12): +We will be looking for a system to run like this (in this example I will pretend our external IP is 12.12.12.12): ```text Outside world -> 12.12.12.12:8123 -> your router -> 192.168.0.200:8123 @@ -65,7 +65,7 @@ So, we can use a static IP to ensure that whenever our device running Home Assis We then have no control over our external IP, as our Service Provider will give us a new one at random intervals. To fix this we will use a service called DuckDNS which will give us a name for our connection (something like examplehome.duckdns.org) and behind the scenes will continue to update your external IP. So no matter how many times the IP address changes, typing examplehome.duckdns.org in to our browser will convert to the correct, up-to-date, IP address. This is covered in step 3 below. -To get around the issue of not being able to chain the IP addresses together (I can't say I want to call 12:12:12:12 and be put through to 192.168.0.200, and then be put through to extension 8123) we use port forwarding. Port forwarding is the process of telling your router which device to allow the outside connection to speak to. In the doctors surgery example, port forwarding is the receptionist. This takes a call from outside, and forwards it to the correct extension number inside. It is important to note that port forwarding can forward an incoming request for one port to a different port on your internal network if you so choose, and we will be doing this later on. The end result being that when we have our SSL certificate our incoming call will be requesting port 443 (because that is the SSL port, like the SSH port is always 22), but our port forwarding rule will forward this to our HA instance on port 8123. When this guide is completed we will run something like this: +To get around the issue of not being able to chain the IP addresses together (I can't say I want to call 12:12:12:12 and be put through to 192.168.0.200, and then be put through to extension 8123) we use port forwarding. Port forwarding is the process of telling your router which device to allow the outside connection to speak to. In the doctors surgery example, port forwarding is the receptionist. This takes a call from outside, and forwards it to the correct extension number inside. It is important to note that port forwarding can forward an incoming request for one port to a different port on your internal network if you so choose, and we will be doing this later on. The end result being that when we have our TSL/SSL certificate our incoming call will be requesting port 443 (because that is the SSL port, like the SSH port is always 22), but our port forwarding rule will forward this to our HA instance on port 8123. When this guide is completed we will run something like this: ```text Outside world -> https://examplehome.duckdns.org -> 12.12.12.12:443 -> your router -> 192.168.0.200:8123 @@ -86,7 +86,10 @@ $ ifconfig You will receive an ouput similar to the image below: - +
+ 
+ Screenshot
+
If you're running the 'standard' setup on a Raspberry Pi the chances are you just logged in as the 'pi' user. If not, you may have logged in as the Home Assistant user. There are commands below that require the Home Assistant user to be on the `sudoers` list. If you are not using the 'standard' pi setup it is presumed you will know how to get your Home Assistant user on the `sudoers` list before continuing. If you are running the 'standard' pi setup, from your 'pi' user issue the following command (where `hass` is the Home Assistant user): -```bash +``` $ sudo adduser hass sudo ```
@@ -262,7 +265,7 @@ $ wget https://dl.eff.org/certbot-auto $ chmod a+x certbot-auto ``` -Now we will run the certbot program to get our ssl certificate. You will need to include your email address and your DuckDNS url in the appropriate places: +Now we will run the certbot program to get our ssl certificate. You will need to include your email address and your DuckDNS URL in the appropriate places: ```text $ ./certbot-auto certonly --standalone --preferred-challenges http-01 --email your@email.address -d examplehome.duckdns.org @@ -276,7 +279,7 @@ Confirm this file has been populated: $ ls /etc/letsencrypt/live/ ``` -This should show a folder named exactly after your DuckDNS url. +This should show a folder named exactly after your DuckDNS URL. Our Home Assistant user needs access to files within the letsencrypt folder, so issue the following commands to change the permissions. @@ -292,7 +295,7 @@ Did all of that go without a hitch? Wahoo! Your Let's Encrypt certificate is nowFollowing on from Step 4 your SSH will still be in the certbot folder. If you edit your configuration files over SSH you will need to change to your `homeassistant` folder: -```bash +``` $ cd ~/.homeassistant ``` @@ -333,7 +336,7 @@ In step 3 we accessed our Home Assistant from the outside world with our DuckDNS https://examplehome.duckdns.org ``` -Note the S after http, and that no port number is added. This is because https will use port 443 automatically, and we have already set up our port forward to redirect this request to our Home Assistant instance on port 8123. +Note the **S** after http, and that no port number is added. This is because https will use port 443 automatically, and we have already set up our port forward to redirect this request to our Home Assistant instance on port 8123. You should now be able to see your Home Assistant instance via your DuckDNS URL, and importantly note that your browser shows the connection as secure. @@ -347,7 +350,7 @@ https://YOUR-HA-IP:8123 ...and accepting the browsers warning that you are connecting to an insecure site. This warning occurs because your certificate expects your incoming connection to come via your DuckDNS URL. It does not mean that your device has suddenly become insecure. -Some cases such as this are where your router does not allow 'loopback' or where there is a problem with incoming connections due to technical failure. In these cases you can still use your internal connection and ignore the warnings. +Some cases such as this are where your router does not allow 'loopback' or where there is a problem with incoming connections due to technical failure. In these cases you can still use your internal connection and safely ignore the warnings. If you were previously using a webapp on your phone/tablet to access your Home Assistant you should delete the old one and create a new one with the new address. The old one will no longer work as it is not keyed to your new, secure URL. Instructions for creating your new webapp can be found here: @@ -504,7 +507,7 @@ Add the following sections to your configuration.yaml ```yaml shell_command: - renew_ssl: ./certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges http-01 + renew_ssl: ~/certbot/certbot-auto renew --quiet --no-self-upgrade --standalone --preferred-challenges http-01 automation: - alias: 'Auto Renew SSL Cert' diff --git a/source/_docs/ecosystem/ios.markdown b/source/_docs/ecosystem/ios.markdown index 9a176f006bd..6959ade8f13 100644 --- a/source/_docs/ecosystem/ios.markdown +++ b/source/_docs/ecosystem/ios.markdown @@ -17,19 +17,14 @@ The Home Assistant for iOS app offers a companion app for iOS which is deeply in * Basic control of all Home Assistant entities * Integration with third party apps -
-Currently, the app is only available via a closed beta. It will be on the App Store within the next few weeks. -
+The app is available on the iOS App Store in every country that Apple supports. -
- 
- An example of a Home Assistant group as seen in the iOS app.
-
## Basic requirements * iOS device running at least iOS 9, but iOS 10 is greatly preferred. -* Home Assistant 0.31.1 or higher for push notification support. +* Home Assistant 0.42.4 or higher for push notification support. * SSL is strongly recommended. Self-signed SSL certificates will not work due to Apple's limitations. The `ios` component is the companion component for the Home Assistant iOS app. While not required, adding the `ios` component to your setup will greatly enhance the iOS app with new notification, location and sensor functions not possible with a standalone app. @@ -45,7 +40,9 @@ The `ios` component will automatically be loaded under the following circumstanc 1. The [`discovery`][discovery] component is enabled. 2. You have just installed the app and are at the getting started screen. -Automated discovery and component loaded can only happen at first install of the app. You may need to wait a few minutes for the iOS component to load as the `discovery` component only scans the network every 5 minutes. +Automated discovery and component loading only happens at first install of the app. You may need to wait a few minutes for the iOS component to load as the `discovery` component only scans the network every 5 minutes. + +After the first automated setup you need to add `ios:` to your configuration so that the component loads by default even after restarting Home Assistant. ### Manual Setup @@ -58,10 +55,10 @@ ios: Configuration variables: -- **push** (*Optional*): Push notification configuration. See the [iOS `notify` platform][ios-notify] for more information. +- **push** (*Optional*): Actionable push notifications configuration. See the [actionable notifications documentation][actionable-notifications] for more information. [discovery]: /components/discovery [device-tracker]: /components/device_tracker [zeroconf]: /components/zeroconf [notify]: /components/notify -[ios-notify]: /ecosystem/ios/notifications/ +[actionable-notifications]: /docs/ecosystem/ios/notifications/actions/ diff --git a/source/_docs/ecosystem/ios/location.markdown b/source/_docs/ecosystem/ios/location.markdown index ac344227c2b..6ee15213b5c 100644 --- a/source/_docs/ecosystem/ios/location.markdown +++ b/source/_docs/ecosystem/ios/location.markdown @@ -32,6 +32,10 @@ What's the real story on significant-change location updates? Who knows, because At launch, Home Assistant for iOS sets up geofences for all zones in your Home Assistant configuration. Enter and exit notifications are sent to Home Assistant. +### Configuration + +Add `track_ios: true` to your zone configurations to enable it for tracking in all connected iOS apps. + [apple-energy-guide]: https://developer.apple.com/library/content/documentation/Performance/Conceptual/EnergyGuide-iOS/LocationBestPractices.html#//apple_ref/doc/uid/TP40015243-CH24-SW4 [apple-location-programming-guide]: https://developer.apple.com/library/content/documentation/UserExperience/Conceptual/LocationAwarenessPG/CoreLocation/CoreLocation.html#//apple_ref/doc/uid/TP40009497-CH2-SW9 [stackoverflow]: http://stackoverflow.com/a/13331625/486182 diff --git a/source/_docs/ecosystem/ios/notifications.markdown b/source/_docs/ecosystem/ios/notifications.markdown index 68854e1b4b9..c5e8f372543 100644 --- a/source/_docs/ecosystem/ios/notifications.markdown +++ b/source/_docs/ecosystem/ios/notifications.markdown @@ -12,4 +12,13 @@ redirect_from: /ecosystem/ios/notifications/ The `ios` notify platform enables sending push notifications to the Home Assistant iOS app. -The 'ios' component will automatically load the notify service. No extra configuration is needed or supported. +The 'ios' component will automatically load the notify service. +The service component can be called using `service: notify.ios_
-
+
- {% active_link /developers/asyncio_101/ Introduction to asyncio %}
- {% active_link /developers/asyncio_categorizing_functions/ Categorizing Functions %}
- {% active_link /developers/asyncio_working_with_async/ Working with Async %}
- {% active_link /developers/asyncio_misc/ Miscellaneous %} diff --git a/source/_includes/asides/docs_navigation.html b/source/_includes/asides/docs_navigation.html index 5839ef04b86..553fb482170 100644 --- a/source/_includes/asides/docs_navigation.html +++ b/source/_includes/asides/docs_navigation.html @@ -113,6 +113,26 @@
- {% active_link /docs/mqtt/processing_json/ Processing JSON %}
-
+
- {% active_link /docs/ecosystem/ios/notifications/basic/ Basic notifications %} +
- {% active_link /docs/ecosystem/ios/notifications/sounds/ Sounds %} +
- {% active_link /docs/ecosystem/ios/notifications/architecture/ Architecture %} +
- {% active_link /docs/ecosystem/ios/notifications/privacy_security_rate_limits/ Privacy, rate limiting and security %} +
- Advanced notifications +
- {% active_link /docs/ecosystem/ios/notifications/attachments/ Attachments %} +
- {% active_link /docs/ecosystem/ios/notifications/content_extensions/ Dynamic content %} +
- {% active_link /docs/ecosystem/ios/notifications/actions/ Actionable notifications %} +
- {% active_link /docs/ecosystem/ios/notifications/requesting_location_updates/ Requesting location updates %} +
- {% active_link /docs/ecosystem/ios/location/ Location Tracking %} +
- {% active_link /docs/ecosystem/ios/integration/ Integration with other apps %} +
-
+
-
+
-
@@ -162,26 +182,6 @@
- {% active_link /docs/ecosystem/notebooks/stats/ Statistics %}
-
-
- {% active_link /docs/ecosystem/ios/notifications/basic/ Basic notifications %} -
- {% active_link /docs/ecosystem/ios/notifications/sounds/ Sounds %} -
- {% active_link /docs/ecosystem/ios/notifications/architecture/ Architecture %} -
- {% active_link /docs/ecosystem/ios/notifications/privacy_security_rate_limits/ Privacy, rate limiting and security %} -
- Advanced notifications -
- {% active_link /docs/ecosystem/ios/notifications/attachments/ Attachments %} -
- {% active_link /docs/ecosystem/ios/notifications/content_extensions/ Dynamic content %} -
- {% active_link /docs/ecosystem/ios/notifications/actions/ Actionable notifications %} -
- {% active_link /docs/ecosystem/ios/notifications/requesting_location_updates/ Requesting location updates %} -
- {% active_link /docs/ecosystem/ios/location/ Location Tracking %} -
- {% active_link /docs/ecosystem/ios/integration/ Integration with other apps %} -
-
-
-
-
-
diff --git a/source/_posts/2017-03-25-todo-volumio-workday.markdown b/source/_posts/2017-03-25-todo-volumio-workday.markdown
index ee84aa9f129..ccdb7c5afcf 100644
--- a/source/_posts/2017-03-25-todo-volumio-workday.markdown
+++ b/source/_posts/2017-03-25-todo-volumio-workday.markdown
@@ -45,6 +45,7 @@ The new format of the changelog which was introduced with 0.40 will provide a li
## Reporting Issues
Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
+
## All changes
- Bugfix android camera autodiscovery settings ([@pvizeli] - [#6510])
diff --git a/source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown b/source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown
index 85548c41319..b6beaa99e46 100644
--- a/source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown
+++ b/source/_posts/2017-04-08-eddystone-beacons--lockitron-locks--total-connect.markdown
@@ -13,7 +13,7 @@ og_image: /images/blog/2017-04-0.42/social.png
-It's time for Home Assistant 0.43. This release has been focused on refining the system and fixing a lot of bugs. We have also upgraded to the latest version of our HTTP library which should give us a significant boost serving files and API.
+It's time for Home Assistant 0.42. This release has been focused on refining the system and fixing a lot of bugs. We have also upgraded to the latest version of our HTTP library which should give us a significant boost serving files and API.
On our social media front, we have crossed the 1000 likes on [our Facebook page][hass-fb]! Also on the social media front, the YouTube channel diyAutomate has been putting out a lot of great getting started videos about Home Assistant, [go check them out!][diyAutomate]
@@ -84,6 +84,38 @@ sensor:
- volume
```
+## If you need help...
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+## Reporting Issues
+Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
+
+## {% linkable_title Release 0.42.1 - April 9 %}
+
+- Upgrade aiohttp to 2.0.6
+- Make discovery not cause startup warning
+
+## {% linkable_title Release 0.42.1 - April 9 %}
+
+ - Revert upgrade to aiothttp 2.0.6
+
+## {% linkable_title Release 0.42.3 - April 11 %}
+
+- Fix Synology camera content type ([@balloob] - [#7010])
+- Fix two more instances of JSON parsing synology ([@balloob] - [#7014])
+- Bump pyalarmdotcom to support new version of aiohttp ([@Xorso] - [#7021])
+- Fix US states check (fixes #7015) ([@fabaff] - [#7017])
+- Plug file leak on LIFX unregister ([@amelchio] - [#7031])
+- Bugfix wait on start event ([@pvizeli] - [#7013])
+
+## {% linkable_title Release 0.42.4 - April 17 %}
+
+- Version bump to 0.42.4 ([@balloob])
+- Fix mysensors callback ([@MartinHjelmare] - [#7057])
+- Upgrade aiohttp to 2.0.7 ([@fabaff] - [#7106])
+- Make version number optional and a string to fix identify issue introduced in iOS 1.0.1 ([@robbiet480] - [#7141])
+- Fix for zwave RGB setting ([@armills] - [#7137])
+
## All changes
- Flux led update lib ([@danielhiversen] - [#6763])
@@ -315,25 +347,32 @@ sensor:
[#6981]: https://github.com/home-assistant/home-assistant/pull/6981
[#6986]: https://github.com/home-assistant/home-assistant/pull/6986
[#6990]: https://github.com/home-assistant/home-assistant/pull/6990
+[#7010]: https://github.com/home-assistant/home-assistant/pull/7010
+[#7013]: https://github.com/home-assistant/home-assistant/pull/7013
+[#7014]: https://github.com/home-assistant/home-assistant/pull/7014
+[#7017]: https://github.com/home-assistant/home-assistant/pull/7017
+[#7021]: https://github.com/home-assistant/home-assistant/pull/7021
+[#7031]: https://github.com/home-assistant/home-assistant/pull/7031
+[@Xorso]: https://github.com/Xorso
+[@amelchio]: https://github.com/amelchio
+[@balloob]: https://github.com/balloob
+[@fabaff]: https://github.com/fabaff
+[@pvizeli]: https://github.com/pvizeli
[@ChristianKuehnel]: https://github.com/ChristianKuehnel
[@DavidMStraub]: https://github.com/DavidMStraub
[@KlaasH]: https://github.com/KlaasH
[@MartinHjelmare]: https://github.com/MartinHjelmare
-[@Xorso]: https://github.com/Xorso
[@aarya123]: https://github.com/aarya123
[@aequitas]: https://github.com/aequitas
-[@amelchio]: https://github.com/amelchio
[@andrey-git]: https://github.com/andrey-git
[@armills]: https://github.com/armills
[@aufano]: https://github.com/aufano
-[@balloob]: https://github.com/balloob
[@bdurrer]: https://github.com/bdurrer
[@citruz]: https://github.com/citruz
[@danielhiversen]: https://github.com/danielhiversen
[@danieljkemp]: https://github.com/danieljkemp
[@danielperna84]: https://github.com/danielperna84
[@diogos88]: https://github.com/diogos88
-[@fabaff]: https://github.com/fabaff
[@geekofweek]: https://github.com/geekofweek
[@goto100]: https://github.com/goto100
[@gurumitts]: https://github.com/gurumitts
@@ -348,7 +387,6 @@ sensor:
[@micw]: https://github.com/micw
[@nugget]: https://github.com/nugget
[@pavoni]: https://github.com/pavoni
-[@pvizeli]: https://github.com/pvizeli
[@quadportnick]: https://github.com/quadportnick
[@rytilahti]: https://github.com/rytilahti
[@tantecky]: https://github.com/tantecky
@@ -359,3 +397,11 @@ sensor:
[@w1ll1am23]: https://github.com/w1ll1am23
[@wardcraigj]: https://github.com/wardcraigj
[@wmalgadey]: https://github.com/wmalgadey
+[forum]: https://community.home-assistant.io/
+[gitter]: https://gitter.im/home-assistant/home-assistant
+[issue]: https://github.com/home-assistant/home-assistant/issues
+[#7057]: https://github.com/home-assistant/home-assistant/pull/7057
+[#7106]: https://github.com/home-assistant/home-assistant/pull/7106
+[#7137]: https://github.com/home-assistant/home-assistant/pull/7137
+[#7141]: https://github.com/home-assistant/home-assistant/pull/7141
+[@robbiet480]: https://github.com/robbiet480
diff --git a/source/_posts/2017-04-15-ios.markdown b/source/_posts/2017-04-15-ios.markdown
new file mode 100644
index 00000000000..5f5ba913b6b
--- /dev/null
+++ b/source/_posts/2017-04-15-ios.markdown
@@ -0,0 +1,44 @@
+---
+layout: post
+title: "1 year and 22 days ago I had an idea..."
+description: "An Easter gift from Home Assistant for all iOS fans"
+date: 2017-04-15 08:04:05 +0000
+date_formatted: "April 16, 2017"
+author: Robbie Trencheny
+author_twitter: robbie
+comments: true
+categories: Announcements
+---
+
+1 year and 22 days ago, or 387 days ago, on March 25th, 2016, I started a project to bring Home Assistant to the iPhone.
+
+I thought the existing notification and location solutions were lacking in one way or another and had wanted for _years_ to have a project I could call my own which would allow me to learn iOS development. What better way then implementing an extremely complex application like Home Assistant?
+
+I started with a lot of steam. I remember cranking out the initial work that night and showing Paulus who was astounded at how fast the UI was coming together.
+
+Little would I know how many problems I would create and uncover throughout the process. Writing a mobile app for a project that moves as fast as Home Assistant is... tricky, to say the least. In the time since I started writing the app, Home Assistant had 90 releases. I started writing the day before 0.16 was released. Now we are at 0.42.3. Time flies...
+
+I couldn't have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.
+
+I received emails and forum posts almost every day, even when the app would go without an update for weeks and sometimes months at a time as my life got busier and busier.
+
+I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.
+
+It may not look the way that I wanted it to initially, with beautiful native UI components, but thats okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.
+
+Just because the app is released doesn't mean we are at the end of the road. It's only the beginning. There's plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that's pretty hard with how fast the project moves.
+
+The biggest request I have is for more developers on the project. As many of you know, I have my hands in many different parts of Home Assistant, from governance and organization to managing the forums to writing this app, managing the Homebridge plugin and even sometimes writing code for the actual core codebase! I can't do it all, and I'm still a new iOS developer who doesn't know all the best practices.
+
+The app is [open source](https://github.com/home-assistant/home-assistant-iOS), has been for the last few months when I first prepared to submit it to Apple for review. I invite Swift developers to come and join me in building it. Trust me, there's tons to do.
+
+**1 year and 22 days ago, on March 25th, 2016 I began work on Home Assistant for iOS.**
+
+**Today, April 16th, 2017, I am _extremely_ excited to announce that Home Assistant for iOS has been approved by Apple and is now available to download for ~~a monthly subscription starting at $9.99~~ free! (had to get a joke in here somewhere!) on the iOS App Store in every country.**
+
++ +_Please note, you must have Home Assistant 0.42.4 or later installed for the app to function properly._ + +Thanks for everything so far, I'm looking forward to the road that lies ahead for Home Assistant on iOS! + diff --git a/source/developers/asyncio.markdown b/source/developers/asyncio.markdown index 72cbb76c6c4..3cbee37c1b2 100644 --- a/source/developers/asyncio.markdown +++ b/source/developers/asyncio.markdown @@ -21,7 +21,7 @@ For a task to be able to suspend itself, all code that it calls has to have this The backwards compatible API works by scheduling a task from a different thread and blocking that thread until the task has been processed by the event loop. -### [Next step: Categorizing Functions »](/developers/asyncio_categorizing_functions/) +### [Next step: asyncio 101 »](/developers/asyncio_101/) [0.29]: https://home-assistant.io/blog/2016/09/29/async-sleepiq-emoncms-stocks/ [ben]: https://github.com/bbangert/ diff --git a/source/developers/asyncio_101.markdown b/source/developers/asyncio_101.markdown new file mode 100644 index 00000000000..c88265119fd --- /dev/null +++ b/source/developers/asyncio_101.markdown @@ -0,0 +1,20 @@ +--- +layout: page +title: "Asyncio 101" +description: "An introduction to asyncio." +date: 2017-04-08 21:49 +sidebar: true +comments: false +sharing: true +footer: true +--- + +If you are not familiar yet with asyncio, please watch the below video. It's a great introduction by [Robert Smallshire][rob] in how and why asyncio works the way it does. + +
+
+
+
+### [Next step: Categorizing Functions »](/developers/asyncio_categorizing_functions/)
+
+[rob]: https://github.com/rob-smallshire
\ No newline at end of file
diff --git a/source/developers/development_environment.markdown b/source/developers/development_environment.markdown
index 0e972b6a7e8..f8ae40fba9d 100644
--- a/source/developers/development_environment.markdown
+++ b/source/developers/development_environment.markdown
@@ -27,8 +27,16 @@ $ git remote add upstream https://github.com/home-assistant/home-assistant.git
Install the core dependencies.
```bash
-$ sudo apt-get install python3-pip python3-dev libssl-dev
+$ sudo apt-get install python3-pip python3-dev
```
+
+#### {% linkable_title Platform dependencies %}
+
+In order to run `script/setup` below you will need some more dependencies.
+```bash
+$ sudo apt-get install libssl-dev libxml2-dev libxslt1-dev libjpeg-dev libffi-dev
+```
+
Different distributions have different package installation mechanisms and sometimes packages names as well. For example Centos would use: `sudo yum install epel-release && sudo yum install python34 python34-devel mysql-devel`
diff --git a/source/getting-started/automation.markdown b/source/getting-started/automation.markdown index 31812056d94..2f420b19db4 100644 --- a/source/getting-started/automation.markdown +++ b/source/getting-started/automation.markdown @@ -18,7 +18,7 @@ automation: - alias: Check sensor value and show notification trigger: platform: numeric_state - entity_id: sensor.random + entity_id: sensor.random_sensor above: 10 action: service: persistent_notification.create diff --git a/source/images/supported_brands/crimereports.png b/source/images/supported_brands/crimereports.png new file mode 100644 index 00000000000..316060b040d Binary files /dev/null and b/source/images/supported_brands/crimereports.png differ diff --git a/source/images/supported_brands/metoffice.jpg b/source/images/supported_brands/metoffice.jpg new file mode 100644 index 00000000000..eadb9954b9a Binary files /dev/null and b/source/images/supported_brands/metoffice.jpg differ diff --git a/source/images/supported_brands/mystrom.png b/source/images/supported_brands/mystrom.png index 51a50a3dd44..b2f1b5285f6 100644 Binary files a/source/images/supported_brands/mystrom.png and b/source/images/supported_brands/mystrom.png differ