diff --git a/source/_posts/2015-08-25-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown b/source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown similarity index 100% rename from source/_posts/2015-08-25-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown rename to source/_posts/2015-08-26-laundry-automation-with-moteino-mqtt-and-home-assistant.markdown diff --git a/source/_posts/2015-08-31-version-7-revamped-ui-and-improved-distribution.markdown b/source/_posts/2015-08-31-version-7-revamped-ui-and-improved-distribution.markdown new file mode 100644 index 00000000000..6bf73efdc47 --- /dev/null +++ b/source/_posts/2015-08-31-version-7-revamped-ui-and-improved-distribution.markdown @@ -0,0 +1,124 @@ +--- +layout: post +title: "0.7: Better UI and improved distribution" +description: "Home Assistant gains a version number and a face lift." +date: 2015-08-31 14:12 -0700 +date_formatted: "August 31, 2015" +comments: true +categories: user-stories +og_image: /images/screenshots/ui2015.png +--- + +As Home Assistant is gaining more and more users we started to feel the pain from not having a +proper release mechanism. We had no version numbering and required users to checkout the source +using Git to get started. On top of that, as the number of devices that we support keeps raising, so +did the number of dependencies that are used. That's why we decided to change the way we roll. From +now on: + + - Each release will have a version number, starting with version 0.7. This was chosen because it + shows that we have been around for some time but are not considering ourselves to be fully + stable. + - Each release will be pushed to PyPi. This will be the only supported method of distribution. + - Home Assistant is available after installation as a command-line utility `hass`. + - The default configuration location has been moved from `config` in the current working directory + to `~/.homeassistant` (`%APPDATA%/.homeassistant` on Windows). + - Requirements for components and platforms are no longer installed into the current Python + environment (being virtual or not) but will be installed in `/lib`. + +A huge shout out to [Ryan Kraus](https://github.com/rmkraus) for making this all possible. Please +make sure you read [the full blog post][self] for details on how to migrate your existing setup. + +[self]: /blog/2015/08/31/version-7-revamped-ui-and-improved-distribution/#read-more + +And while Ryan was fixing distribution, I have been hard at work in giving Home Assistant a face +lift. We already looked pretty good but lacked proper form of organization for users with many +devices. The new UI moves away from a card per entity and has cards per group and domain instead. +[The demo](/demo/) has been updated so give it a spin. + +

+ + + + Screenshots of the new UI +

+ + + +### {% linkable_title Migration to version 0.7 %} + +For this example, let's say we have an old Home Assistant installation in +`/home/paulus/home-assistant`. + +If you want to migrate your existing configuration to be used as the default configuration: + +```bash +cp -r /home/paulus/home-assistant ~/.homeassistant +``` + +It If you want to have the configuration in a different location, for example +`/home/paulus/home-assistant-config`, you will have to point Home Assistant at this configuration +folder when launching: + +```bash +hass --config /home/paulus/home-assistant-config +``` + +### {% linkable_title New platforms %} + +And last, but not least: new platforms! + +__MQTT Sensors and Switches__
+ +[@sfam](https://github.com/sfam) has blessed us with two more MQTT platforms to extend our +integration with MQTTT: [sensor][mqtt-sensor] and [switch][mqtt-switch]. Both platforms require the +MQTT component to be connected to a broker. + +[mqtt-sensor]: /components/sensor.mqtt.html +[mqtt-switch]: /components/switch.mqtt.html + +```yaml +# Example configuration.yml entr +sensor: + platform: mqtt + name: "MQTT Sensor" + state_topic: "home/bedroom/temperature" + unit_of_measurement: "ºC" + +switch: + platform: mqtt + name: "Bedroom Switch" + state_topic: "home/bedroom/switch1" + command_topic: "home/bedroom/switch1/set" + payload_on: "ON" + payload_off: "OFF" + optimistic: false +``` + +__Actiontec MI424WR Verizon FIOS Wireless router__
+ +[Nolan](https://github.com/nkgilley) has contributed support for Actiontec wireless routers. + +```yaml +# Example configuration.yaml entry +device_tracker: + platform: actiontec + host: YOUR_ROUTER_IP + username: YOUR_ADMIN_USERNAME + password: YOUR_ADMIN_PASSWORD +``` + +__DHT temperature and humidty sensors__
+[@MakeMeASandwich](https://github.com/makemeasandwich) has contributed support for DHT temperature +and humidity sensors. It allows you to get the current temperature and humidity from a DHT11, DHT22, +or AM2302 device. + +```yaml +# Example configuration.yaml entry +sensor: + platform: dht + sensor: DHT22 + pin: 23 + monitored_conditions: + - temperature + - humidity +``` diff --git a/source/components/discovery.markdown b/source/components/discovery.markdown index 97d3b1927b6..64193b2eb88 100644 --- a/source/components/discovery.markdown +++ b/source/components/discovery.markdown @@ -15,6 +15,7 @@ Home Assistant can discover and automatically configure zeroconf/mDNS and uPnP d * Google Chromecast * Belkin WeMo switches * Philips Hue + * Netgear routers It will be able to add Google Chreomcasts and Belkin WeMo switches automatically, for Philips Hue it will require some configuration from the user. diff --git a/source/components/mqtt.markdown b/source/components/mqtt.markdown index 97962444823..cb5648db31e 100644 --- a/source/components/mqtt.markdown +++ b/source/components/mqtt.markdown @@ -33,7 +33,10 @@ The MQTT component has no TLS support at the moment. This means that only plain- ## Building on top of MQTT -There are two ways to integrate MQTT into your process. One is by using the [MQTT-automation rule](/components/automation.html#mqtt-based-automation). The other one is by 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. + - [MQTT Sensor](/components/sensor.mqtt.html) + - [MQTT Switch](/components/switch.mqtt.html) + - [MQTT-automation rule](/components/automation.html#mqtt-based-automation). + - 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. ## Testing diff --git a/source/components/sensor.bitcoin.markdown b/source/components/sensor.bitcoin.markdown index 0d2d6865ffc..13ee0753607 100644 --- a/source/components/sensor.bitcoin.markdown +++ b/source/components/sensor.bitcoin.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Bitcoin support" -description: "Instructions how to integrate the time and the date within Home Assistant." +description: "Instructions how to integrate Bitcoin data within Home Assistant." date: 2015-05-08 17:15 sidebar: false comments: false diff --git a/source/components/sensor.dht.markdown b/source/components/sensor.dht.markdown index 0c4fded0563..4feed1facee 100644 --- a/source/components/sensor.dht.markdown +++ b/source/components/sensor.dht.markdown @@ -24,7 +24,7 @@ sensor: - humidity ``` -The name of the pin to which the sensor is connected has a different names on different platfroms. 'P8_11' for Beaglebone, '23' for Raspberry Pi. +The name of the pin to which the sensor is connected has different names on different platforms. 'P8_11' for Beaglebone, '23' for Raspberry Pi.

As this requires access to the GPIO, you will need to run Home Assistant as root. diff --git a/source/components/sensor.mqtt.markdown b/source/components/sensor.mqtt.markdown new file mode 100644 index 00000000000..a07f9edb8cd --- /dev/null +++ b/source/components/sensor.mqtt.markdown @@ -0,0 +1,31 @@ +--- +layout: page +title: "MQTT Sensor support" +description: "Instructions how to integrate MQTT sensors within Home Assistant." +date: 2015-05-30 23:21 +sidebar: false +comments: false +sharing: true +footer: true +--- + + +This generic sensor implementation uses the MQTT message payload +as the sensor value. If messages in this state_topic are published +with RETAIN flag, the sensor will receive an instant update with +last known value. Otherwise, the initial state will be undefined. + +```yaml +# Example configuration.yml entry +sensor: + platform: mqtt + name: "MQTT Sensor" + state_topic: "home/bedroom/temperature" + unit_of_measurement: "ºC" +``` + +state_topic: The MQTT topic subscribed to receive sensor values. *Required* + +name: The name of the sensor. Default is 'MQTT Sensor'. *Optional* + +unit_of_measurement: Defines the units of measurement of the sensor, if any. *Optional* diff --git a/source/components/switch.mqtt.markdown b/source/components/switch.mqtt.markdown new file mode 100644 index 00000000000..69a1552806a --- /dev/null +++ b/source/components/switch.mqtt.markdown @@ -0,0 +1,49 @@ +--- +layout: page +title: "MQTT switch support" +description: "Instructions how to integrate MQTT switches into Home Assistant." +date: 2015-08-30 23:38 +sidebar: false +comments: false +sharing: true +footer: true +--- + + +In an ideal scenario, the MQTT device will have a state topic to publish +state changes. If these messages are published with RETAIN flag, the MQTT +switch will receive an instant state update after subscription and will +start with correct state. Otherwise, the initial state of the switch will +be false/off. + +When a state topic is not available, the switch will work in optimistic mode. +In this mode, the switch will immediately change state after every command. +Otherwise, the switch will wait for state confirmation from device +(message from state_topic). + +Optimistic mode can be forced, even if state topic is available. +Try to enable it, if experiencing incorrect switch operation. + +```yaml +# Example configuration.yml entr +switch: + platform: mqtt + name: "Bedroom Switch" + state_topic: "home/bedroom/switch1" + command_topic: "home/bedroom/switch1/set" + payload_on: "ON" + payload_off: "OFF" + optimistic: false +``` + +command_topic: The MQTT topic to publish commands to change the switch state. *Required* + +name: The name of the switch. Default is 'MQTT Switch'. *Optional* + +state_topic: The MQTT topic subscribed to receive state updates. *Optional* + +payload_on: The payload that represents enabled state. Default is "ON". *Optional* + +payload_off: The payload that represents disabled state. Default is "OFF". *Optional* + +optimistic: Flag that defines if switch works in optimistic mode. Default is true if no state topic defined, else false. *Optional* diff --git a/source/components/switch.wemo.markdown b/source/components/switch.wemo.markdown index 1d680f2f54d..d5f9c62cbb5 100644 --- a/source/components/switch.wemo.markdown +++ b/source/components/switch.wemo.markdown @@ -9,10 +9,10 @@ sharing: true footer: true --- - -The wemo platform allows you to control your [Belkin WeMo](http://www.belkin.com/us/p/P-F7C027/) switches from within Home Assistant. + +The wemo platform allows you to control your [Belkin WeMo](http://www.belkin.com/us/p/P-F7C027/) switches from within Home Assistant. -To add Wemo switches to your installation, add the following to your `configuration.yaml` file: +They will be automatically discovered if the discovery component is enabled. ```yaml # Example configuration.yaml entry diff --git a/source/images/screenshots/ui2015.png b/source/images/screenshots/ui2015.png new file mode 100644 index 00000000000..a5e278b0394 Binary files /dev/null and b/source/images/screenshots/ui2015.png differ