diff --git a/source/_components/input_slider.markdown b/source/_components/input_slider.markdown new file mode 100644 index 00000000000..5fd9d136c42 --- /dev/null +++ b/source/_components/input_slider.markdown @@ -0,0 +1,33 @@ +--- +layout: page +title: "Input Slider" +description: "Instructions how to integrate the Input Slider component into Home Assistant." +date: 2016-03-15 06:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: home-assistant.png +ha_category: Automation +--- + +The `input_slider` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. + +```yaml +# Example configuration.yaml entry +input_slider: + slider1: + name: Slider 1 + initial: 30 + min: -20 + max: 35 +``` + +Configuration variables: + +- **[alias]** (*Required*): Alias for the slider input. +- **name** (*Optional*): Friendly name of the slider input. +- **initial** (*Optional*): Initial value when Home Assistant starts. +- **min** (*Optional*): Minimum value for the slider. +- **max** (*Optional*): Maximum value for the slider. + diff --git a/source/_components/media_player.markdown b/source/_components/media_player.markdown index 24d81c3b2e9..0589f06e938 100644 --- a/source/_components/media_player.markdown +++ b/source/_components/media_player.markdown @@ -13,31 +13,38 @@ Interacts with media players on your network. Please check the sidebar for a ful ## {% linkable_title Services %} - ### {% linkable_title Media control services %} -Available services: `turn_off`, `volume_up`, `volume_down`, `media_play_pause`, `media_play`, `media_pause`, `media_next_track` +Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`, `media_play_pause`, `media_play`, `media_pause`, `media_next_track`, `media_previous_track` | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | yes | Target a specific media player. Defaults to all. -### {% linkable_title Media play services %} - -There are three services to start playing YouTube video's on the media player. - -#### {% linkable_title Service `media_player/play_youtube_video` %} - -Service to start playing a YouTube video on the media player. +#### {% linkable_title Service `media_player/mute_volume` %} | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | yes | Target a specific media player. Defaults to all. -| `video` | no | YouTube video to be played, ie. `L0MK7qz13bU` +| `mute` | no | True/false for mute/unmute -#### {% linkable_title Service `media_player/start_fireplace` and `media_player/start_epic_sax` %} - -Will either start a fireplace or Epic Sax Guy 10h on the media player. +#### {% linkable_title Service `media_player/set_volume_level` %} | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | yes | Target a specific media player. Defaults to all. +| `volume` | no | Integer for volume level + +#### {% linkable_title Service `media_player/media_seek` %} + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | yes | Target a specific media player. Defaults to all. +| `position` | no | Position to seek to. The format is platform dependent. + +#### {% linkable_title Service `media_player/play_media` %} + +| Service data attribute | Optional | Description | +| ------------------------------- | -------- | ----------- | +| `entity_id` | yes | Target a specific media player. Defaults to all. +| `media_content_id` | no | A media identifier. The format of this is component dependent. For example, you can provide URLs to Sonos and Cast but only a playlist ID to iTunes. +| `media_content_type` | no | A media type. Must be one of `MUSIC`, `TVSHOW`, `VIDEO`, `EPISODE`, `CHANNEL` or `PLAYLIST`. For example, to play music you would set `media_content_type` to `MUSIC`. diff --git a/source/_components/media_player.yamaha.markdown b/source/_components/media_player.yamaha.markdown new file mode 100644 index 00000000000..9888cf684bf --- /dev/null +++ b/source/_components/media_player.yamaha.markdown @@ -0,0 +1,42 @@ +--- +layout: page +title: "Yamaha Network Receivers" +description: "Instructions how to integrate Yamaha Network Receivers into Home Assistant." +date: 2016-03-26 0:58 -0700 +sidebar: true +comments: false +sharing: true +footer: true +logo: yamaha.png +ha_category: Media Player +--- + + +The `yamaha` platform allows you to control [Yamaha Network Receivers](http://usa.yamaha.com/products/audio-visual/av-receivers-amps/rx) from Home Assistant. + +Supported devices: + +- HTR-4065 +- RX-V473 +- RX-V573 +- RX-V673 +- RX-V773 +- And more + +To add a Yamaha Network Receiver to your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +media_player: + platform: yamaha + name: 'Basement Receiver' +``` +Configuration variables: + +- **name** (*Optional*): Name of the device + +A few notes: + +- This will automatically search your network for Yamaha receivers. It will add a media player device for each one. +- Currently the only controls that are available is Power On/Off, Mute, and Volume control. Other functions such as source select are in progress of being developed. + diff --git a/source/_components/mqtt.markdown b/source/_components/mqtt.markdown index 2f37a9abf1c..614af9061f8 100644 --- a/source/_components/mqtt.markdown +++ b/source/_components/mqtt.markdown @@ -42,7 +42,30 @@ Configuration variables: ## {% linkable_title Picking a broker %} -The MQTT component needs you to run an MQTT broker for Home Assistant to connect to. There are three options, each with various degrees of ease of setup and privacy. +The MQTT component needs you to run an MQTT broker for Home Assistant to connect to. There are four options, each with various degrees of ease of setup and privacy. + +#### {% linkable_title Use the embedded broker %} + +Home Assistant contains an embedded MQTT broker. If no broker configuration is given, the [HBMQTT broker](https://pypi.python.org/pypi/hbmqtt) is started and Home Asssistant connects to it. Default settings for the embedded broker: + +| Setting | Value | +| ------- | ----- | +| Host | localhost +| Port | 1883 +| Version | 3.1 +| User | homeassistant +| Password | Your API password +| Websocket port | 8080 + +If you want to customize the settings of the embedded broker, use `embedded:` and the values shown in the [HBMQTT Broker configuration](http://hbmqtt.readthedocs.org/en/latest/references/broker.html#broker-configuration). + +```yaml +# Example configuration.yaml entry +mqtt: + embedded: + # Your HBMQTT config here. Example at: + # http://hbmqtt.readthedocs.org/en/latest/references/broker.html#broker-configuration +``` #### {% linkable_title Run your own %} @@ -143,12 +166,24 @@ The MQTT component will register the service `publish` which allows publishing m ## {% linkable_title Testing your setup %} -For debugging purposes `mosquitto` is shipping commandline tools to send and recieve MQTT messages. For sending test messages to a broker running on localhost: +The `mosquitto` broker package is shipping commandline tools to send and recieve MQTT messages. As an alternative have a look at [hbmqtt_pub](http://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_pub.html) and [hbmqtt_sub](http://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_sub.html) which are provied by HBMQTT. For sending test messages to a broker running on localhost check the example below: ```bash $ mosquitto_pub -h 127.0.0.1 -t home-assistant/switch/1/on -m "Switch is ON" ``` +If you are using the embeeded MQTT broker, the command looks a little different because you need to add the MQTT protocol version. + +```bash +$ mosquitto_pub -V mqttv311 -t hello -m world +``` + +or if you are using a API password. + +```bash +$ mosquitto_pub -V mqttv311 -u homeassistant -P -t "hello" -m world +``` + Another way to send MQTT messages by hand is to use the "Developer Tools" in the Frontend. Choose "Call Service" and then `mqtt/mqtt_send` under "Available Services". Enter something similar to the example below into the "Service Data" field. ```json @@ -170,6 +205,14 @@ For reading all messages sent on the topic `home-assistant` to a broker running $ mosquitto_sub -h 127.0.0.1 -v -t "home-assistant/#" ``` +For the embeeded MQTT broker the command looks like the sample below. + +```bash +$ mosquitto_sub -V mqttv311 -t # -v +``` + +Add the username `homeassistant` and your API password if needed. + ## {% linkable_title Processing JSON %} The MQTT switch and sensor platforms support processing JSON over MQTT messages and parse them using JSONPath. JSONPath allows you to specify where in the JSON the value resides that you want to use. The following examples will always return the value `100`. diff --git a/source/_components/notify.gntp.markdown b/source/_components/notify.gntp.markdown new file mode 100644 index 00000000000..f54d0344b22 --- /dev/null +++ b/source/_components/notify.gntp.markdown @@ -0,0 +1,35 @@ +--- +layout: page +title: "GNTP (Growl)" +description: "Instructions for adding GNTP/Growl notifications to Home Assistant." +date: 2016-03-25 18:18 +sidebar: true +comments: false +sharing: true +footer: true +logo: gntp.png +ha_category: Notifications +--- + + +[GNTP](http://www.growlforwindows.com/gfw/help/gntp.aspx) is a specification for sending and receiving notifications between computers. The most well known server implementations are [Growl](http://growl.info) for Mac and [Growl for Windows](http://www.growlforwindows.com/gfw/). + +To use GNTP notifications, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +notify: + name: NOTIFER_NAME + platform: gntp +``` + +GNTP will attempt to connect to a local server running on port 23053 if no `hostname` is provided. + +Configuration variables: + +- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. +- **app_name** (*Optional*): The application name that will be displayed on every notification and will be registered with the server. +- **app_icon** (*Optional*): The icon that will be displayed on every notification. You can provide a HTTP URL or a `file://` URL. File URLs only work if Home Assistant and the GNTP server are running on the same machine. If no `app_icon` is set a local copy of the Home Assistant logo will be used. If you choose to use a HTTP URL please make the maximum image size 150 px by 150 px as Growl for Mac will sometimes timeout when registering. +- **hostname** (*Optional*): The hostname or IP address of the GNTP server to contact. +- **password** (*Optional*): The password to authenticate to the GNTP server with. +- **port** (*Optional*): The port that the GNTP server runs on. The specification states that servers should not allow users to use any port other than 23053 but `port` is provided here just in case. diff --git a/source/_components/notify.message_bird.markdown b/source/_components/notify.message_bird.markdown new file mode 100644 index 00000000000..82209bda957 --- /dev/null +++ b/source/_components/notify.message_bird.markdown @@ -0,0 +1,44 @@ +--- +layout: page +title: "MessageBird" +description: "Instructions how to add user notifications to Home Assistant." +date: 2016-03-15 17:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: message_bird.png +ha_category: Notifications +--- + +The `MessageBird` notification platform sends notifications as SMS messages using [MessageBird](https://www.messagebird.com/) to your mobile phone. + +To enable MessageBird notifications in your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +notify: + platform: message_bird + api_key: YOUR_API_KEY + name: NOTIFIER_NAME + sender: SENDER_NAME +``` + +Configuration variables: + +- **api_key** (*Required*): Enter the API key for MessageBird. Go to https://www.messagebird.com/ to retrieve your API key. +- **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. +- **sender** (*Optional*): Setting the optional parameter `sender`. This will be the sender of the SMS. It may be either a telephone number (e.g. `+4915112345678`) or a text with a maximum length of 11 characters. Defaults to `HA`. + +### {% linkable_title Usage %} + +MessageBird is a notify platform and thus can be controlled by calling the notify service [as described here](/components/notify/). It will send a notification to the specified mobile phone number(s). + +#### {% linkable_title Example service payload %} + +```json +{ + "message": "A message for many people", + "target": [ "+49123456789", "+43123456789" ] +} +``` diff --git a/source/_components/sensor.bitcoin.markdown b/source/_components/sensor.bitcoin.markdown index 56145a9d814..e575411c0aa 100644 --- a/source/_components/sensor.bitcoin.markdown +++ b/source/_components/sensor.bitcoin.markdown @@ -12,11 +12,7 @@ ha_category: Sensor --- -The `bitcoin` platform displays various details about the [Bitcoin](https://bitcoin.org) network. - -If you have an online wallet from [Blockchain.info](https://blockchain.info/) the sensor is capable to show your current balance. - -You need to enable the API access for your online wallet to get the balance. To do that log in and move to 'Account Setting', choose 'IP Restrictions', and check 'Enable Api Access'. You will get an email message from blockchain.info where you must authorize the API access. +The `bitcoin` sensor platform displays various details about the [Bitcoin](https://bitcoin.org) network. To add the Bitcoin sensor to your installation, add a selection of the available display options to your `configuration.yaml` file: @@ -24,8 +20,6 @@ To add the Bitcoin sensor to your installation, add a selection of the available # Example configuration.yaml entry sensor: platform: bitcoin - wallet: 'YOUR WALLET_ID' - password: YOUR_ACCOUNT_PASSWORD currency: YOUR CURRENCY display_options: - exchangerate @@ -53,8 +47,6 @@ sensor: Configuration variables: -- **wallet** (*Optional*): This is your wallet identifier from https://blockchain.info to access the online wallet. -- **password** (*Optional*): Password for your online wallet. - **currency** (*Optional*): The currency to exchange to, eg. CHF, USD, EUR, etc. Default is USD. - **display_options** array (*Required*): Options to display in the frontend. - **exchangerate**: Exchange rate of 1 BTC diff --git a/source/_components/sensor.uber.markdown b/source/_components/sensor.uber.markdown new file mode 100644 index 00000000000..6b1dee6a78e --- /dev/null +++ b/source/_components/sensor.uber.markdown @@ -0,0 +1,43 @@ +--- +layout: page +title: "Uber" +description: "How to integrate Uber in Home Assistant" +date: 2016-03-24 23:04 +sidebar: true +comments: false +sharing: true +footer: true +logo: uber.png +ha_category: Sensor +ha_iot_class: "Cloud Polling" +--- + + +The `uber` sensor will give you time and price estimates for all available [Uber](https://uber.com) products at the given `start_latitude` and `start_longitude`.The `ATTRIBUTES` are used to provide extra information about products, such as estimated trip duration, distance and vehicle capacity. By default, 2 sensors will be created for each product at the given `start` location, one for pickup time and one for current price. The sensor is powered by the official Uber [API](https://developer.uber.com/). + + +You must create an application [here](https://developer.uber.com/dashboard/create) to obtain a `server_token`. + +To enable this sensor, add the following lines to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +sensor: + platform: uber + start_latitude: 37.8116380 + start_longitude: -122.2648050 + end_latitude: 37.7768520 + end_longitude: -122.4155500 + server_token: 'BeAPPTDsWZSHLf7fd9OWjZkIezweRw18Q8NltY27' + product_ids: + - '04a497f5-380d-47f2-bf1b-ad4cfdcb51f2' +``` + +Configuration variables: + +- **start_latitude** (*Required*): The starting latitude for a trip. +- **start_longitude** (*Required*): The starting longitude for a trip. +- **end_latitude** (*Optional*): The ending latitude for a trip. While `end_latitude` is optional, it is strongly recommended to provide an `end_latitude`/`end_longitude` when possible as you will get more accurate price and time estimates. +- **end_longitude** (*Optional*): The ending longitude for a trip. While `end_longitude` is optional, it is strongly recommended to provide an `end_latitude`/`end_longitude` when possible as you will get more accurate price and time estimates. +- **server_token** (*Required*): A server token obtained from [developer.uber.com](https://developer.uber.com) after [creating an app](https://developer.uber.com/dashboard/create). +- **product_ids** (*Options*): A list of Uber product UUIDs. If provided, sensors will only be created for the given product IDs. Please note that product IDs are region and some times even more specific geographies based. The easiest way to find a UUID is to click on a sensor in the Home Assistant frontend and look for "Product ID" in the attributes. diff --git a/source/_components/switch.arduino.markdown b/source/_components/switch.arduino.markdown index b2a1b7ef5cd..c888d85d71a 100644 --- a/source/_components/switch.arduino.markdown +++ b/source/_components/switch.arduino.markdown @@ -24,6 +24,8 @@ switch: 11: name: Fan Office type: digital + default: on + negate: true 12: name: Light Desk type: digital @@ -34,6 +36,8 @@ Configuration variables: - **pins** (*Required*): Array of pins to use. The number corresponds with the pin numbering schema of your board. - **name**: Name that will be used in the frontend for the pin. - **type**: The type of the pin. At the moment only 'digital' is supported. + - **default**: The initial value for this port. + - **negate**: If this pin should be inverted. The digital pins are numbered from 0 to 13. The available pins are 2 till 13. For testing purposes you can use pin 13 because with that pin you can control the internal LED. diff --git a/source/_components/switch.pulseaudio_loopback.markdown b/source/_components/switch.pulseaudio_loopback.markdown new file mode 100644 index 00000000000..afb00a30957 --- /dev/null +++ b/source/_components/switch.pulseaudio_loopback.markdown @@ -0,0 +1,50 @@ +--- +layout: page +title: "PulseAudio Loopback Switch" +description: "Instructions how to use Pulseaudio loopback modules to build a flexible whole-home audio system." +date: 2016-03-22 21:00:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: pulseaudio.png +ha_category: Switch +--- + + +The goal behind this switch is to allow a very flexible whole home audio system based upon PulseAudio. + +For example, for a system with a 7.1 surround sound card, and 3 instances of mpd running, it is possible to quickly route the output of any mpd instance to any of the 8 possible (4 stereo) channels on the sound card, by loading/unloading a loopback module. This loading/unloading functionality is provided by this component. When the switch is 'on', the loopback module is loaded. When the switch is 'off', the module is not loaded. + +The benefit of this approach is that this audio routing can occur without modifying the design-time configuration of mpd or PulseAudio. + +This component uses a TCP connection to control a local or remote PulseAudio server- so there are no local dependencies. + +To enable this switch, add the following lines to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +switch: + platform: pulseaudio_loopback + name: mpd1 -> bedroom + host: 127.0.0.1 + port: 4712 + source_name: mpd1.monitor + sink_name: bedroom +``` + +Configuration variables: + +- **sink_name** (*Required*): The name of the Pulseaudio sink that will recieve the audio. +- **source_name** (*Required*): The name of the Pulseaudio source that will supply the audio. +- **name** (*Optional*): Name of the switch. +- **host** (*Optional*): The IP address or host name of the PulseAudio server. If not specified, 127.0.0.1 is used. +- **port** (*Optional*): The port that Pulseaudio is listening on. Defaults to 4712. +- **buffer_size** (*Optional*): How much data to load from Pulseaudio at once. Default is 1KB. +- **tcp_timeout** (*Optional*): How long to wait for a response from Pulseaudio before giving up. Default is 3 seconds. + +

+This component relies on raw TCP commands to PulseAudio. In order for PulseAudio to accept commands with +this component, module-cli-protocol must be loaded on the PulseAudio server. +

+ diff --git a/source/_components/switch.wake_on_lan.markdown b/source/_components/switch.wake_on_lan.markdown new file mode 100644 index 00000000000..53e9e125045 --- /dev/null +++ b/source/_components/switch.wake_on_lan.markdown @@ -0,0 +1,36 @@ +--- +layout: page +title: "Wake on LAN Switch" +description: "Instructions how to integrate a wake on lan switch." +date: 2016-03-18 18:00 +sidebar: true +comments: false +sharing: true +footer: true +logo: ethernet.png +ha_category: Switch +--- + +The `wake_on_lan` (WOL) switch platform allows you to turn on a [WOL](https://en.wikipedia.org/wiki/Wake-on-LAN) enabled computer. + +

+The WOL switch can only turn on your computer and monitor the state. There is no universal way to turn off a computer remotely. +

+ +To enable this switch in your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yml entry +switch: + platform: wake_on_lan + mac_address: "00-01-02-03-04-05" + name: "WOL" + host: "192.168.1.1" +``` + +Configuration variables: + +- **mac_address** (*Required*): MAC address to send the wake up command to. +- **name** (*Optional*): The name of the switch. Default is 'Wake on LAN'. +- **host** (*Optional*): The IP address or hostname to check the state of the device (on/off). + diff --git a/source/_components/tellstick.markdown b/source/_components/tellstick.markdown index edca85a85b2..f0474c47575 100644 --- a/source/_components/tellstick.markdown +++ b/source/_components/tellstick.markdown @@ -18,14 +18,6 @@ To get started, add the devices to your `configuration.yaml` file. ```yaml # Example configuration.yaml entry -switch: - platform: tellstick - -sensor: - platform: tellstick - -# All dimmers will be picked up as lights. -light: - platform: tellstick +tellstick: + signal_repetitions: X ``` - diff --git a/source/_components/vera.markdown b/source/_components/vera.markdown index 782ca02cb7d..50167fd0d4a 100644 --- a/source/_components/vera.markdown +++ b/source/_components/vera.markdown @@ -14,8 +14,11 @@ ha_category: Hub The [Vera](http://getvera.com) ecosystem is using Z-Wave for communication between the Vera controller and the devices. -## {% linkable_title Building on top of Vera %} - - - [Vera Sensor](/components/sensor.vera/) - - [Vera Switch](/components/switch.vera/) - - [Vera Light](/components/light.vera/) +```yaml +vera: + vera_controller_url: http://192.168.1.161:3480/ + # Optional to exclude devices - this is a list of vera device ids + exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99] + # Optional to import switches as lights - this is a list of vera device ids + lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87] +``` diff --git a/source/_components/zwave.markdown b/source/_components/zwave.markdown index d4d33d4d3cd..5e1d15f7b18 100644 --- a/source/_components/zwave.markdown +++ b/source/_components/zwave.markdown @@ -108,3 +108,14 @@ automation: ``` The *entity_id* and *scene_id* of all triggered events can be seen in the console output. + +#### {% linkable_title Services %} + +The Z-Wave component exposes two services to help maintain the network. + +| Service | Description | +| ------- | ----------- | +| add_node | | +| remove_node | | +| heal_network | | +| soft_reset | | diff --git a/source/_posts/2016-03-26-embedded-mqtt-broker-uber-yamaha-growl.markdown b/source/_posts/2016-03-26-embedded-mqtt-broker-uber-yamaha-growl.markdown new file mode 100644 index 00000000000..1a325f9a243 --- /dev/null +++ b/source/_posts/2016-03-26-embedded-mqtt-broker-uber-yamaha-growl.markdown @@ -0,0 +1,90 @@ +--- +layout: post +title: "0.16: Embedded MQTT broker, Uber, Yamaha receivers and Growl" +description: "Home Assistant 0.16 has arrived." +date: 2016-03-26 0:10:00 -0700 +date_formatted: "March 26, 2016" +author: Paulus Schoutsen +author_twitter: balloob +comments: true +categories: Release-Notes +--- + +Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: [hbMQTT]. Just add `mqtt:` to your config and a broker is launched and connected with Home Assistant. See the [documentation][embedded server] for more info. + +Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!). + +Rock on. + + + + - Device Tracker - [OwnTracks]: Allow entry into passive zones using iBeacons ([@pavoni]) + - Tellstick: rewrite to [component][Tellstick] to address concurrency issues ([@stefan-jonasson]) + - Z-Wave: add [services][Z-Wave] to heal and soft reset network ([@srcLurker]) + - New component [input_slider] added ([@persandstrom]) + - Light - [Hue]: Option added to ignore unreachable property ([@maddox]) + - Notify: [MessageBird] support added ([@florianholzapfel]) + - HTTP: Failed login attempts are now logged ([@fabaff]) + - Vera: rewrite to [component][Vera] to simplify code and organize for reusability ([@pavoni]) + - Discovery: support for Squeezebox (Logitech media) server added ([@jaharkes]) + - Discovery: fix uPNP discovery crashing some routers ([@jaharkes]) + - Switch: [Wake on LAN] platform added ([@joopert]) + - Services for thermostats, notify and media player will now validate passed in parameters ([@MartinHjelmare]) + - Switch - [Arduino]: support for default state and negate port functionality ([@tilutza]) + - Switch: [PulseAudio loopback] now supported ([@Cinntax]) + - Sensor: [Uber] now supported ([@robbiet480]) + - Notify: [Growl (GNTP)] now supported ([@robbiet480]) + - Media Player: [Yamaha receivers] now supported ([@aoakeson]) + +[hbMQTT]: https://github.com/beerfactory/hbmqtt +[@aoakeson]: https://github.com/aoakeson +[@balloob]: https://github.com/balloob +[@Cinntax]: https://github.com/Cinntax +[@fabaff]: https://github.com/fabaff +[@florianholzapfel]: https://github.com/florianholzapfel +[@jaharkes]: https://github.com/jaharkes +[@joopert]: https://github.com/joopert +[@maddox]: https://github.com/maddox +[@MartinHjelmare]: https://github.com/MartinHjelmare +[@pavoni]: https://github.com/pavoni +[@persandstrom]: https://github.com/persandstrom +[@robbiet480]: https://github.com/robbiet480 +[@srcLurker]: https://github.com/srcLurker +[@stefan-jonasson]: https://github.com/stefan-jonasson +[@tilutza]: https://github.com/tilutza +[embedded server]: /components/mqtt/#use-the-embedded-broker +[Arduino]: /components/switch.arduino/ +[Discovery]: /components/discovery/ +[Growl (GNTP)]: /components/notify.gntp/ +[Hue]: /components/light.hue/ +[input_slider]: /components/input_slider/ +[MessageBird]: /components/notify.message_bird/ +[OwnTracks]: /components/device_tracker.owntracks/ +[PulseAudio loopback]: /components/switch.pulseaudio_loopback/ +[Tellstick]: /components/tellstick/ +[Uber]: /components/sensor.uber/ +[Vera]: /components/vera/ +[Wake on LAN]: /components/switch.wake_on_lan/ +[Z-Wave]: /components/zwave/#services +[Yamaha receivers]: /components/media_player.yamaha/ + +### Breaking changes + - Automation: support for old deprecated config has been removed + + - Tellstick configuration has changed + +```yaml +tellstick: + signal_repetitions: X +``` + +- Vera configuration has changed + +```yaml +vera: + vera_controller_url: http://192.168.1.161:3480/ + # Optional to exclude devices - this is a list of vera device ids + exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99] + # Optional to import switches as lights - this is a list of vera device ids + lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87] +``` diff --git a/source/components/switch.pulseaudio_loopback.html b/source/components/switch.pulseaudio_loopback.html new file mode 100644 index 00000000000..31ef8fc5717 --- /dev/null +++ b/source/components/switch.pulseaudio_loopback.html @@ -0,0 +1 @@ + diff --git a/source/images/supported_brands/ethernet.png b/source/images/supported_brands/ethernet.png new file mode 100644 index 00000000000..6f507b4ac94 Binary files /dev/null and b/source/images/supported_brands/ethernet.png differ diff --git a/source/images/supported_brands/gntp.png b/source/images/supported_brands/gntp.png new file mode 100644 index 00000000000..a0ad0fb1334 Binary files /dev/null and b/source/images/supported_brands/gntp.png differ diff --git a/source/images/supported_brands/message_bird.png b/source/images/supported_brands/message_bird.png new file mode 100644 index 00000000000..1beab0c385c Binary files /dev/null and b/source/images/supported_brands/message_bird.png differ diff --git a/source/images/supported_brands/pulseaudio.png b/source/images/supported_brands/pulseaudio.png new file mode 100644 index 00000000000..f90a8ad76d2 Binary files /dev/null and b/source/images/supported_brands/pulseaudio.png differ diff --git a/source/images/supported_brands/uber.png b/source/images/supported_brands/uber.png new file mode 100755 index 00000000000..7a201cd47d5 Binary files /dev/null and b/source/images/supported_brands/uber.png differ diff --git a/source/images/supported_brands/yamaha.png b/source/images/supported_brands/yamaha.png new file mode 100644 index 00000000000..6ae38e57fed Binary files /dev/null and b/source/images/supported_brands/yamaha.png differ