diff --git a/_config.yml b/_config.yml
index 1481314883d..0ff86dc495c 100644
--- a/_config.yml
+++ b/_config.yml
@@ -131,9 +131,9 @@ social:
 # Home Assistant release details
 current_major_version: 0
 current_minor_version: 34
-current_patch_version: 0
-date_released: 2016-12-03
+current_patch_version: 1
+date_released: 2016-12-04
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
-patch_version_notes: "#"
+patch_version_notes: "#release-0341---december-4"
diff --git a/source/_components/emulated_hue.markdown b/source/_components/emulated_hue.markdown
index 5d71a26ec90..fd510f3c5e5 100644
--- a/source/_components/emulated_hue.markdown
+++ b/source/_components/emulated_hue.markdown
@@ -21,15 +21,24 @@ entities. The driving use case behind this functionality is to allow Home Assist
 
 ### {% linkable_title Configuration %}
 
-To enable the emulated Hue bridge, add the following to your `configuration.yaml` file:
+To enable the emulated Hue bridge, add one of the following configs to your `configuration.yaml` file:
 
 ```yaml
-# Example configuration.yaml entry
+# Amazon Echo example configuration.yaml entry
 emulated_hue:
 ```
 
+```yaml
+# Google Home example configuration.yaml entry
+emulated_hue:
+  type: google_home
+  # Google Home does not work on different ports.
+  listen_port: 80
+```
+
 Configuration variables:
 
+- **type** (*Optional*): The type of assistant who we are emulated for. Either `alexa` or `google_home`.
 - **host_ip** (*Optional*): The IP address that your Home Assistant installation is running on. If you do not specify this option, the component will attempt to determine the IP address on its own.
 - **listen_port** (*Optional*): The port the Hue bridge API web server will run on. If not specified, this defaults to 8300. This can be any free port on your system.
 - **off_maps_to_on_domains** (*Optional*): The domains that maps an "off" command to an "on" command.
diff --git a/source/_components/sensor.broadlink.markdown b/source/_components/sensor.broadlink.markdown
index 944a6965b80..c9602c98c8d 100644
--- a/source/_components/sensor.broadlink.markdown
+++ b/source/_components/sensor.broadlink.markdown
@@ -2,7 +2,7 @@
 layout: page
 title: "Broadlink RM2 and A1 sensor"
 description: "Instructions how to integrate Broadlink RM2 and/or A1 E-air sensors within Home Assistant."
-date: 2020-11-08 21:59
+date: 2016-12-03 21:59
 sidebar: true
 comments: false
 sharing: true
@@ -13,7 +13,7 @@ ha_release: 0.34
 ---
 
 
-The `broadlink` sensor platform let you monitor data from an RM2 and A1 E-air. 
+The `broadlink` sensor platform let you monitor data from an RM2 and A1 E-air.
 There is currently no support for the cloud API.
 
 To set it up, add the following information to your `configuration.yaml` file:
diff --git a/source/_posts/2016-12-03-remote-websockets-sonarr.markdown b/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
index 4835b64fc43..317ba9ac9b4 100644
--- a/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
+++ b/source/_posts/2016-12-03-remote-websockets-sonarr.markdown
@@ -76,7 +76,30 @@ This release includes a new [websockets][websockets] based API by [@balloob] to
 - Minor and not so minor features and bug fixes by [@turbokongen], [@sdague], [@pvizeli], [@fabaff], [@chapple], [@mweinelt], [@Khabi], [@balloob], [@mnestor], [@kellerza], [@Morrisai],
 [@michaelarnauts], [@tchellomello], [@lwis], [@bjarniivarsson], [@danielperna84], [@LinuxChristian], [@MartinHjelmare], [@dethpickle], [@jnewland], [@lichtteil], [@brandonweeks], [@partofthething], [@mnoorenberghe], [@bah2830], and [@albertoarias].
 
-## {% linkable_title Breaking changes %}
+### {% linkable_title Release 0.34.1 - December 4 %}
+
+This release has a bunch of bug fixes including a big one: emulated_hue will now work with Google Home! We usually reserve patch releases for small bug fixes but we considered this more impactful bug fix so important that we're including it now instead of having people wait two weeks.
+
+To make the fix backwards compatible (it is a patch release after all) you will have to add two new configuration option to emulated_hue to have it work with Google Home:
+
+```yaml
+emulated_hue:
+  type: google_home
+  # This is important. Sadly, Google Home will not work with other ports.
+  listen_port: 80
+```
+
+We are working on a better solution for 0.35.
+
+- Fix emulated_hue with Google Home ([@balloob])
+- Fix Sonos invalid config error ([@pvizeli])
+- Fix Synology DSM doing I/O inside event loop ([@balloob])
+- Fix Nest camera issues ([@technicalpickles])
+- Fix occasional hangs in Homematic ([@pvizeli])
+- Revert TP-Link upgrade to fix issues ([@mweinelt])
+- Fix CORS ([@balloob])
+
+### {% linkable_title Breaking changes %}
 
 - The [HomeMatic][homematic] component now uses a different syntax for hosts and the `set_value` service has been renamed.
 - All [RFXtrx][rfxtrx] sensors will get a new entity ID.
@@ -153,7 +176,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 [amcrest]: https://home-assistant.io/components/camera.amcrest/
 [boradlink]: https://home-assistant.io/components/sensor.broadlink/
 [dsmr]: https://home-assistant.io/components/sensor.dsmr/
-[dunehd]: https://home-assistant.io/components/dunehd/
+[dunehd]: https://home-assistant.io/components/media_player.dunehd/
 [efergy]: https://home-assistant.io/components/sensor.efergy/
 [filtering]: https://home-assistant.io/components/http/
 [gpslogger]: https://home-assistant.io/components/device_tracker.gpslogger/