diff --git a/_config.yml b/_config.yml
index 77f78049d6b..f62bb660786 100644
--- a/_config.yml
+++ b/_config.yml
@@ -142,12 +142,12 @@ social:
# Home Assistant release details
current_major_version: 0
-current_minor_version: 51
-current_patch_version: 2
-date_released: 2017-08-14
+current_minor_version: 52
+current_patch_version: 0
+date_released: 2017-08-26
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.
# Major release:
-patch_version_notes: "#release-0512--august-14"
+patch_version_notes: "#"
# Minor release (Example #release-0431---april-25):
diff --git a/source/_components/abode.markdown b/source/_components/abode.markdown
index 5b1368d4c6d..59b247f7bf7 100644
--- a/source/_components/abode.markdown
+++ b/source/_components/abode.markdown
@@ -2,7 +2,7 @@
layout: page
title: "Abode Home Security"
description: "Instructions on integrating Abode home security with Home Assistant."
-date: 2017-08-26 13:28
+date: 2017-08-26 0:28
sidebar: true
comments: false
sharing: true
diff --git a/source/_components/alarm_control_panel.abode.markdown b/source/_components/alarm_control_panel.abode.markdown
index 4b140acdb06..593735b7d20 100644
--- a/source/_components/alarm_control_panel.abode.markdown
+++ b/source/_components/alarm_control_panel.abode.markdown
@@ -2,7 +2,7 @@
layout: page
title: "Abode Alarm Control Panel"
description: "Instructions how to setup the Abode Alarm control panel within Home Assistant."
-date: 2017-08-26 13:28
+date: 2017-08-26 0:28
sidebar: true
comments: false
sharing: true
diff --git a/source/_components/binary_sensor.abode.markdown b/source/_components/binary_sensor.abode.markdown
index d0ee36ad392..35dfeda1713 100644
--- a/source/_components/binary_sensor.abode.markdown
+++ b/source/_components/binary_sensor.abode.markdown
@@ -2,7 +2,7 @@
layout: page
title: "Abode Binary Sensor"
description: "Instructions how to integrate Abode binary sensors into Home Assistant."
-date: 2017-08-26 13:28
+date: 2017-08-26 0:28
sidebar: true
comments: false
sharing: true
diff --git a/source/_components/sensor.londond_air.markdown b/source/_components/sensor.london_air.markdown
similarity index 100%
rename from source/_components/sensor.londond_air.markdown
rename to source/_components/sensor.london_air.markdown
diff --git a/source/_docs/automation/editor.markdown b/source/_docs/automation/editor.markdown
index 83b1de0f29e..e8a60039668 100644
--- a/source/_docs/automation/editor.markdown
+++ b/source/_docs/automation/editor.markdown
@@ -1,7 +1,7 @@
---
layout: page
title: "Automation Editor"
-description: "Instructions on how to use the new automation editor."
+description: "Instructions on how to use the automation editor."
date: 2016-04-24 08:30 +0100
sidebar: true
comments: false
@@ -9,11 +9,9 @@ sharing: true
footer: true
---
-In Home Assistant 0.45 we have introduced the first version of our automation editor. The editor is still in a very early stage and rough around the edges. For now we are only supporting Chrome but better browser support is planned for the future.
+In Home Assistant 0.45 we introduced the first version of our automation editor. If you just created a new configuration with Home Assistant then you're all set! Go to the UI and enjoy.
-If you just created a new configuration with Home Assistant then you're all set! Go to the UI and enjoy.
-
-From the UI choose **Automation** which is located in the sidebar. Press the **+** sign in the lower right corner to get started. This example is based on the manual steps described in the [Getting started section](/getting-started/automation/) for a [`random` sensor](/components/sensor.random/).
+From the UI choose **Configuration** which is located in the sidebar, then click on **Automation** to go to the automation editor. Press the **+** sign in the lower right corner to get started. This example is based on the manual steps described in the [Getting started section](/getting-started/automation/) for a [`random` sensor](/components/sensor.random/).
Choose a meaningful name for your automation rules.
diff --git a/source/_docs/scripts/editor.markdown b/source/_docs/scripts/editor.markdown
new file mode 100644
index 00000000000..e5cc30c2272
--- /dev/null
+++ b/source/_docs/scripts/editor.markdown
@@ -0,0 +1,28 @@
+---
+layout: page
+title: "Script Editor"
+description: "Instructions on how to use the new script editor."
+date: 2016-08-26 03:30 +0000
+sidebar: true
+comments: false
+sharing: true
+footer: true
+redirect_from: /docs/script/editor/
+---
+
+In Home Assistant 0.52 we introduced the first version of our automation editor. If you just created a new configuration with Home Assistant then you're all set! Go to the UI and enjoy.
+
+
+
+
+
+## {% linkable_title Updating your configuration to use the editor %}
+
+The script editor reads and writes to the file `scripts.yaml` in your [configuration](/docs/configuration/) folder. Make sure that you have set up the script component to read from it:
+
+```yaml
+# Configuration.yaml example
+script: !include scripts.yaml
+```
+
+The conten that was under `script:` should now be moved to `scripts.yaml` to be editable.
diff --git a/source/_includes/asides/docs_navigation.html b/source/_includes/asides/docs_navigation.html
index 83fa9419bb0..c113f371a5a 100644
--- a/source/_includes/asides/docs_navigation.html
+++ b/source/_includes/asides/docs_navigation.html
@@ -78,6 +78,7 @@
{% active_link /docs/scripts/service-calls/ Service Calls %}
diff --git a/source/_posts/2017-08-26-release-0-52.markdown b/source/_posts/2017-08-26-release-0-52.markdown
new file mode 100644
index 00000000000..152d0621d7c
--- /dev/null
+++ b/source/_posts/2017-08-26-release-0-52.markdown
@@ -0,0 +1,376 @@
+---
+layout: post
+title: "0.51: Massive history speed up, finished automation editor and official vacuum cleaner support"
+description: "Lots of frontend bugs have been squashed, the automation editor now supports all triggers and actions and vacuum cleaners are now an official component."
+date: 2017-08-26 00:11:05
+date_formatted: "August 26, 2017"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: Release-Notes
+og_image: /images/blog/2017-08-0.52/components.png
+---
+
+
+
+Although the summer is in full progress, the development hasn't stalled. This release brings bug fixes, clean ups and another 8 new integrations. On top of that we are also introducing a new [script editor](/docs/scripts/editor/)!
+
+To use the scripts editor, create a new file in your config directory named `scripts.yaml` and copy your existing scripts over:
+
+```yaml
+# scripts.yaml
+turn_on_some_lights:
+ alias: Turn on the lights
+ sequence:
+ - data: {}
+ service: light.turn_on
+```
+
+ Than update your `configuration.yaml` to look like this:
+
+```yaml
+# Configuration.yaml example
+script: !include scripts.yaml
+```
+
+
+
+
+
+## New Platforms
+
+- Add version sensor ([@fabaff] - [#8912]) ([sensor.version docs]) (new-platform)
+- Nello.io lock support ([@pschmitt] - [#8957]) ([lock.nello docs]) (new-platform)
+- Add HipChat notify service. ([@BioSehnsucht] - [#8918]) ([notify.hipchat docs]) (new-platform)
+- Refactor USPS into component with Sensors+Camera ([@mezz64] - [#8679]) ([usps docs]) ([camera.usps docs]) ([sensor.usps docs]) (breaking change) (new-platform)
+- Adds London_air component ([@robmarkcole] - [#9020]) ([sensor.london_air docs]) (new-platform)
+- Add Abode home security component ([@arsaboo] - [#9030]) ([abode docs]) ([alarm_control_panel.abode docs]) ([binary_sensor.abode docs]) (new-platform)
+- Add support for Prowl notifications. ([@mbrrg] - [#9028]) ([notify.prowl docs]) (new-platform)
+- Add worldtidesinfo sensor component ([@aetolus] - [#8860]) ([sensor.worldtidesinfo docs]) (new-platform)
+
+## {% linkable_title If you need help... %}
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+
+## {% linkable_title Reporting Issues %}
+Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
+
+
+## Breaking Changes
+
+- Remove spaces from Xiami switch attributes ([@syssi] - [#8952]) ([switch.xiaomi docs]) (breaking change)
+- MQTT Switch: command and availability payload are now no longer linked. Command and availability payload default to ON/OFF and must be configured individually if custom values are required. ([@timstanley1985] - [#8934]) ([switch.mqtt docs]) (breaking change)
+
+```yaml
+ - platform: mqtt
+ name: "Kitchen"
+ state_topic: "stat/sonoff_1/POWER"
+ command_topic: "cmnd/sonoff_1/POWER"
+ availability_topic: "tele/sonoff_1/LWT"
+ payload_available: "Online"
+ payload_not_available: "Offline"
+ retain: true
+```
+
+- Refactor USPS into component with Sensors+Camera ([@mezz64] - [#8679]) ([usps docs]) ([camera.usps docs]) ([sensor.usps docs]) (breaking change) (new-platform)
+
+```yaml
+usps:
+ username: user
+ password: pass
+ name: optional
+```
+
+- eliqonline: The optional channel_id configuration variable of the Eliqonline sensor needs to be a positive integer. ([@molobrakos] - [#9072]) ([sensor.eliqonline docs]) (breaking change)
+- MySensors: Not a breaking change per se but users that have not been following the mysensors [serial API](https://www.mysensors.org/download/serial_api_20) could face dropped messages after this change. Messages are now validated according to the API before being passed along from/to devices. See [0.11 release notes](https://github.com/theolind/pymysensors/releases/tag/0.11) for more info. ([@MartinHjelmare] - [#9069]) ([mysensors docs]) ([binary_sensor.mysensors docs]) ([climate.mysensors docs]) ([cover.mysensors docs]) ([device_tracker.mysensors docs]) ([light.mysensors docs]) ([notify.mysensors docs]) ([sensor.mysensors docs]) ([switch.mysensors docs]) (breaking change)
+- Automatic has disabled password authentication on their API. Home Assistant will now use OAuth2 to authenticate accounts. The following steps must be taken to transition your setup:
+ 1) Log in to your Automatic developer account. In the Automatic Developer Apps Manager, specify the OAuth Redirect URL in the developer page. This should be configured to `/api/automatic/callback`. (Example: `http://hassio.local:8123/api/automatic/callback`) Note that this URL only needs to be accessible from the browser you use to perform the authentication.
+ 2) Remove username/password from your automatic device tracker configuration in configuration.yaml.
+ 3) If you have authorized your account for `scope:current_location`, add `current_location: true` to your automatic device tracker configuration in configuration.yaml.
+ 4) When you restart home assistant, click on the Automatic Configure link in the Configurator card, and follow the instructions to authorize Home Assistant.