Add 0.7.4 release blog post

source/components/alarm_control_panel.mqtt.markdown

@@ -10,10 +10,10 @@ footer: true
 ---
 
 <img src='/images/supported_brands/mqtt.png' class='brand pull-right' />
-This platform enables the possibility to control an MQTT alarm. The alarm will only change state after receiving the a new state from `state_topic`. If these messages are published with RETAIN flag, the MQTT alarm will receive an instant state update after subscription and will start with correct state. Otherwise, the initial state will
-be `unknown`.
-
-To enable this alarm, add the following lines to your `configuration.yaml` for a GET request:
+This platform enables the possibility to control an MQTT alarm. The alarm will only change state after
+receiving the a new state from `state_topic`. If these messages are published with RETAIN flag, the MQTT
+alarm will receive an instant state update after subscription and will start with correct state. Otherwise,
+the initial state will be `unknown`.
 
 ```yaml
 # Example configuration.yaml entry

source/components/automation.markdown

@@ -30,16 +30,16 @@ automation:
       offset: '-01:00:00'
     - platform: state
       entity_id: group.all_devices
-      state: home
+      state: 'home'
   condition:
     # Prefix the first line of each condition configuration
     # with a '-'' to enter multiple
     - platform: state
       entity_id: group.all_devices
-      state: home
+      state: 'home'
     - platform: time
-      after: "16:00:00"
-      before: "23:00:00"
+      after: '16:00:00'
+      before: '23:00:00'
   action:
     service: homeassistant.turn_on
     entity_id: group.living_room
@@ -70,10 +70,6 @@ automation:
       message: 'Paulus left the house'
 ```
 
-<p class='note'>
-With the updated automation layout, you are now able to list all rules under on a single `automation:` entry.  Use `-alias` to define the start of each rule.
-</p>
-
  - [Jump to conditions](#conditions)
  - [Jump to actions](#actions)
  - [Jump to troubleshooting](#troubleshooting)
@@ -134,11 +130,11 @@ automation:
     platform: state
     entity_id: device_tracker.paulus
     # Optional
-    from: "not_home"
-    to: "home"
+    from: 'not_home'
+    to: 'home'
 ```
 
-<p class='note'>
+<p class='note warning'>
   Use quotes around your values for <code>from</code> and <code>to</code> to avoid the YAML parser
   interpreting some values as booleans.
 </p>
@@ -170,7 +166,7 @@ automation:
     # All following are optional.
     # When 'after' is used, you cannot also match on hour, minute, seconds.
     # Military time format.
-    # after: "15:32:00"
+    # after: '15:32:00'
     hours: 0
     minutes: 5
     seconds: 0
@@ -258,8 +254,8 @@ automation:
   condition:
     platform: time
     # At least one of the following is required.
-    after: "15:00:00"
-    before: "23:00:00"
+    after: '15:00:00'
+    before: '23:00:00'
     weekday:
       - mon
       - wed

source/components/mqtt.markdown

@@ -114,7 +114,8 @@ of CloudMQTT (port range 20 000 - 30 000).
  - [MQTT Switch](/components/switch.mqtt.html)
  - [MQTT Device Tracker](/components/device_tracker.mqtt.html)
  - [OwnTracks Device Tracker](/components/device_tracker.owntracks.html)
- - [MQTT-automation rule](/components/automation.html#mqtt-based-automation)
+ - [MQTT automation rule](/components/automation.html#mqtt-based-automation)
+ - [MQTT alarm](/components/alarm_control_panel.mqtt.html)
  - Integrating it into a component. See the [MQTT example component](https://github.com/balloob/home-assistant/blob/dev/config/custom_components/mqtt_example.py) how to do this.
 
 ## {% linkable_title Testing your setup %}

source/components/zwave.markdown

@@ -9,6 +9,11 @@ sharing: true
 footer: true
 ---
 
+<p class='note warning'>
+Z-Wave support is currently broken as we're unable to compile
+<a href='https://github.com/OpenZWave/python-openzwave/tree/python3'>Python Open Z-Wave</a>.
+</p>
+
 <img src='/images/supported_brands/z-wave.png' class='brand pull-right' />
 
 [Z-Wave](http://www.z-wave.com/) support for Home Assistant is very new. We have started now by integrating only the sensors.