Merge branch 'current' into next

This commit is contained in:
Franck Nijhof 2019-12-24 14:35:35 +01:00
commit 8d767a23e6
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
16 changed files with 130 additions and 24 deletions

View File

@ -101,8 +101,8 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 103
current_patch_version: 1
date_released: 2019-12-18
current_patch_version: 4
date_released: 2019-12-22
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

View File

@ -93,7 +93,7 @@ condition:
above: 17
below: 25
# If your sensor value needs to be adjusted
value_template: {% raw %}{{ float(state.state) + 2 }}{% endraw %}
value_template: {% raw %}'{{ float(state.state) + 2 }}'{% endraw %}
```
### State condition

View File

@ -389,11 +389,12 @@ The `entity_id` names will be `light.device_name`, where `device_name` is define
- IKEA Trådfri bulb E14 WS Opal 400lm
- IKEA Trådfri bulb E14 WS Opal 600lm
- IKEA Trådfri Bulb E27 WS clear 950lm
- IKEA Trådfri Bulb E27 WS Opal 980lm
- IKEA Trådfri Bulb E27 WS Opal 1000lm
- IKEA Trådfri Bulb E27 WS & RGB Opal 600lm
- IKEA Trådfri Bulb GU10 W 400lm
- IKEA Trådfri bulb E27 WS clear 806lm
- IKEA Trådfri bulb E27 WS clear 950lm
- IKEA Trådfri bulb E27 WS Opal 980lm
- IKEA Trådfri bulb E27 WS Opal 1000lm
- IKEA Trådfri bulb E27 WS & RGB Opal 600lm
- IKEA Trådfri bulb GU10 W 400lm
- IKEA Trådfri FLOALT LED light panel
- Innr BY-265, BY-245
- OSRAM Classic A60 W clear - LIGHTIFY
@ -479,6 +480,7 @@ The `entity_id` name will be `switch.device_name`, where `device_name` is define
### Verified supported switches
- Innr SP120
- Innr ZB-ONOFFPlug-D0005/SmartThings Smart Plug (2019) (without power measurements)
- Osram Lightify plug
- Osram Outdoor plug
- Heiman siren

View File

@ -199,5 +199,5 @@ image_processing:
- binary_sensor.driveway
action:
- service: image_processing.scan
entity_id: camera.driveway
entity_id: image_processing.doods_camera_driveway
```

View File

@ -78,7 +78,7 @@ Discovery is not yet supported for any robot vacuum models (Dyson 360 Eye). For
To find a devices IP address, you can use your router or `nmap`:
```bash
$ nmap -p 1883 XXX.XXX.XXX.XXX/YY -- open
$ nmap -p 1883 XXX.XXX.XXX.XXX/YY --open
```
Where:
@ -89,7 +89,7 @@ Where:
For example:
```bash
$ nmap -p 1883 192.168.0.0/24 -- open
$ nmap -p 1883 192.168.0.0/24 --open
```
## Vacuum

View File

@ -53,7 +53,7 @@ enable_uart=1
Then (after a reboot): you can setup the sensor using:
```yaml
serial_device: /dev/tty.S0
serial_device: /dev/ttyS0
```
## Calibration

View File

@ -138,7 +138,7 @@ Call the service `recorder.purge` to start a purge task which deletes events and
| PostgreSQL | `postgresql://SERVER_IP/DB_NAME` |
| PostgreSQL | `postgresql://user:password@SERVER_IP/DB_NAME` |
| PostgreSQL (Socket) | `postgresql://@/DB_NAME` |
| MS SQL Server | `mssql+pyodbc://username:password@dsnname` |
| MS SQL Server | `mssql+pyodbc://username:password@SERVER_IP/DB_NAME?charset=utf8;DRIVER={DRIVER};Port=1433;` |
<div class='note'>
@ -247,7 +247,7 @@ A service restart will work as well.
### MS SQL Server
For MS SQL Server you may have to install a few dependencies:
For MS SQL Server you will have to install a few dependencies:
```bash
sudo apt-get install unixodbc-dev
@ -261,3 +261,11 @@ sudo -u homeassistant -H -s
source /srv/homeassistant/bin/activate
pip3 install pyodbc
```
You will also need to install an ODBC Driver. Microsoft ODBC drivers are recommended, however FreeTDS is available for systems that are not supported by Microsoft. Instrucitons for installing the Microsoft ODBC drivers can be found [here](https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server).
<div class='note'>
If you are using Hass.io, FreeTDS is already installed for you. The db_url you need to use is `mssql+pyodbc://username:password@SERVER_IP/DB_NAME?charset=utf8;DRIVER={FreeTDS};Port=1433;`.
</div>

View File

@ -40,6 +40,7 @@ The following OID examples pull the current MAC Address table from a router. Thi
| OPNSense | 19.1 | `1.3.6.1.2.1.4.22.1.2` |
| pfSense | 2.2.4 | `1.3.6.1.2.1.4.22.1.2` |
| Ruckus | ZoneDirector 9.13.3 | `1.3.6.1.4.1.25053.1.2.2.1.1.3.1.1.1.6` |
| TP-Link | Archer VR1600v | `1.3.6.1.2.1.3.1.1.2.16.1` |
| TP-Link | Archer VR2600v | `1.3.6.1.2.1.3.1.1.2.19.1` |
| TP-Link | Archer VR600 | `1.3.6.1.2.1.3.1.1.2` |
| Ubiquiti | Edgerouter Lite v1.9.0 | `1.3.6.1.2.1.4.22.1.2` |

View File

@ -7,7 +7,7 @@ ha_release: 0.101
ha_iot_class: Local Polling
---
The `solarlog` integration uses the open JSON interface on Solar-Log PV monitoring systems to allow you to get details from your Solar-Log device and integrate these into your Home Assistant installation.
The `solarlog` integration uses the open JSON interface on [Solar-Log PV monitoring systems](https://www.solar-log.com/) to allow you to get details from your Solar-Log device and integrate these into your Home Assistant installation.
Before being able to use the integration, you have to activate the open JSON interface on your Solar-Log device. This can be activated from the Configuration | System | Access control menu of your Solar-Log device.
When activating the interface, a red warning triangle with security information and risks is displayed.

View File

@ -273,7 +273,7 @@ That means that Home Assistant is not getting any response from your Xiaomi gate
- You should generate the key again using an Android Phone or alternatively an emulator such as [bluestacks](https://www.bluestacks.com). In some instances, there is an issue with keys being generated using the iOS application.
- You need to make sure to have multicast support on your network. If you are running Home Assistant in a virtual machine (like Proxmox), try `echo 0 >/sys/class/net/vmbr0/bridge/multicast_snooping` on the host and restart the service or reboot the host.
- If the required library "PyXiaomiGateway" cannot be installed you will need to install some missing system dependencies `python3-dev`, `libssl-dev`, `libffi-dev` manually (e.g., `$ sudo apt-get install python3-dev libssl-dev libffi-dev`).
- If your gateway's MAC address starts with `04:CF:8C`, there is a good chance that the required port `9898` is closed on your gateway (you can check it with the Nmap utility, using the command `sudo nmap -sU {gateway_ip} -p 9898`). To fix that issue, you need to do these steps:
- If your gateway's MAC address starts with `04:CF:8C` or `7C:49:EB`, there is a good chance that the required port `9898` is closed on your gateway (you can check it with the Nmap utility, using the command `sudo nmap -sU {gateway_ip} -p 9898`). To fix that issue, you need to do these steps:
- Find a specific screw bit (like a fork) to open the gateway case.
- Find a USB-UART cable/module and connect it to your computer.
- Solder 3 wires - RX, TX and GND like [here](https://cs5-3.4pda.to/14176168/IMG_20181020_201150.jpg).

View File

@ -56,7 +56,7 @@ aspect_ratio:
type: string
entity:
required: false
description: Entity to use for `state_image`.
description: Entity to use for `state_image` and `state_filter`.
type: string
show_state:
required: false
@ -320,6 +320,7 @@ Specify different [CSS filters](https://developer.mozilla.org/en-US/docs/Web/CSS
state_filter:
"on": brightness(110%) saturate(1.2)
"off": brightness(50%) hue-rotate(45deg)
entity: switch.decorative_lights
```
## Examples

View File

@ -280,6 +280,60 @@ All services for use in Home Assistant are moved to their integration naming spa
[tank_utility docs]: /integrations/tank_utility/
[zwave docs]: /integrations/zwave/
## Release 0.103.2 - December 19
- Fix dependency installation recursinog ([@balloob])
## Release 0.103.3 - December 20
- Fix update port and api key on deconz discovery config entry u… ([@frenck] - [#30088]) ([deconz docs])
- Patch rachio ([@omriasta] - [#30031]) ([rachio docs])
- Fix failure in transform method ([@depl0y] - [#30023]) ([dsmr_reader docs])
- Fix homekit handling of 0 light brightness and fan speed ([@fuzzie360] - [#29962]) ([homekit docs])
- Bump starlingbank to 3.2 ([@springstan] - [#30098]) ([starlingbank docs])
- Bump ring to 0.2.5 ([@balloob] - [#30103]) ([ring docs])
[#29962]: https://github.com/home-assistant/home-assistant/pull/29962
[#30023]: https://github.com/home-assistant/home-assistant/pull/30023
[#30031]: https://github.com/home-assistant/home-assistant/pull/30031
[#30088]: https://github.com/home-assistant/home-assistant/pull/30088
[#30098]: https://github.com/home-assistant/home-assistant/pull/30098
[#30103]: https://github.com/home-assistant/home-assistant/pull/30103
[@balloob]: https://github.com/balloob
[@depl0y]: https://github.com/depl0y
[@frenck]: https://github.com/frenck
[@fuzzie360]: https://github.com/fuzzie360
[@omriasta]: https://github.com/omriasta
[@springstan]: https://github.com/springstan
[deconz docs]: /integrations/deconz/
[dsmr_reader docs]: /integrations/dsmr_reader/
[homekit docs]: /integrations/homekit/
[rachio docs]: /integrations/rachio/
[ring docs]: /integrations/ring/
[starlingbank docs]: /integrations/starlingbank/
## Release 0.103.4 - December 22
- Remove requirement from entity integration ([@balloob] - [#30113]) ([doods docs]) ([image_processing docs]) ([seven_segments docs]) ([tensorflow docs])
- Move imports into setup function in homekit __init__.py ([@springstan] - [#30137]) ([homekit docs])
- Fix deconz SSDP updating Hassio discovery ([@frenck] - [#30153]) ([deconz docs])
- Allow battery value of 0 as well as make sure to not create a battery tracker if one already exist ([@Kane610] - [#30155]) ([deconz docs])
[#30113]: https://github.com/home-assistant/home-assistant/pull/30113
[#30137]: https://github.com/home-assistant/home-assistant/pull/30137
[#30153]: https://github.com/home-assistant/home-assistant/pull/30153
[#30155]: https://github.com/home-assistant/home-assistant/pull/30155
[@Kane610]: https://github.com/Kane610
[@balloob]: https://github.com/balloob
[@frenck]: https://github.com/frenck
[@springstan]: https://github.com/springstan
[deconz docs]: /integrations/deconz/
[doods docs]: /integrations/doods/
[homekit docs]: /integrations/homekit/
[image_processing docs]: /integrations/image_processing/
[seven_segments docs]: /integrations/seven_segments/
[tensorflow docs]: /integrations/tensorflow/
## If you need help...
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e).

View File

@ -0,0 +1,42 @@
---
layout: post
title: "Celebrate the holidays with open standards"
description: "A lot of news dropped around open standards. Time for a quick round up."
date: 2019-12-20 0:43:02
date_formatted: "December 20, 2019"
author: Paulus Schoutsen
author_twitter: balloob
comments: true
categories: Technology
---
It's been a busy week with a lot of announcements around IoT standards, so I thought I would do a quick round up of them, and how it might impact Home Assistant users.
## New IoT standard announced
As it's been a while, the industry has announced yet a new effort to create a new IoT standard called [Project Connected Home over IP](https://www.connectedhomeip.com/). I think that there are a few interesting bits to this standard:
The standard will be royalty-free. This is big, as it means that it will be easy for companies to build products. Take, for example, Homekit, which is a great IP-based local standard. Homekit has strict licensing and royalties, which prevented it from widespread adoption.
The new standard specification will be written in conjunction with building an open source implementation of the standard. Once it's all finished, we'll be able to integrate this implementation into Home Assistant.
Finally, Apple, Google and Amazon are seriously involved, even contributing their own IoT standards to help bootstrap this specification. This significantly increases the odds of them also integrating it into their products. Since their products are everywhere, it means that more companies might incorporate the standard and it can get widespread adoption.
But don't hold your breath. Developing a standard takes time. They aim for a draft to be released at the end of 2020. And that's just the specification. Not any of the devices built with it. If (and that's a big IF) everything works out, expect this standard to get into your home in 2022.
<!--more-->
## Z-Wave to become an open standard
Silicon Labs and the Z-Wave Alliance have announced plans to [open up Z-Wave](https://news.silabs.com/2019-12-19-Silicon-Labs-and-Z-Wave-Alliance-Expand-Smart-Home-Ecosystem-by-Opening-Z-Wave-to-Silicon-and-Stack-Suppliers) in the second half of 2020. Among other things, this allows other companies to create Z-Wave radios, which could result in wider adoption and cheaper devices.
## Open Source HomeKit Accessory Development Kit
As part of the Connected Home over IP announcement, Apple has released an [open source version](https://github.com/apple/HomeKitADK) of their Accessory Development Kit (ADK). The ADK allows devices to be controlled by HomeKit controllers like Home Assistant (and ok, iOS devices). The spec was already open and Home Assistant implements it via the [Homekit integration](/integrations/homekit/). Opening up the ADK still helps because it gives a reference implementation to see how the spec should work.
## Bonus: deCONZ hass.io add-on gets Ingress support
It's not really related, but a little. deCONZ is Zigbee controller software that works with the Conbee Zigbee stick. It's a platinum Home Assistant integration and we've been working with [Phoscon](https://phoscon.de), the company behind deCONZ and Conbee, to add Ingress support to the Hass.io add-on.
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Wait... did I just release the deCONZ add-on 4.0 for <a href="https://twitter.com/home_assistant?ref_src=twsrc%5Etfw">@home_assistant</a> with Ingress support? 🎉<br><br>Thanks to <a href="https://twitter.com/phosconde?ref_src=twsrc%5Etfw">@phosconde</a> for solving the last issues in deCONZ 2.05.72, that allows for this awesomeness! <a href="https://t.co/t9aVNdLJEg">pic.twitter.com/t9aVNdLJEg</a></p>&mdash; Franck Nijhof (@Frenck) <a href="https://twitter.com/Frenck/status/1207770759273353231?ref_src=twsrc%5Etfw">December 19, 2019</a>
</blockquote>

View File

@ -5,6 +5,4 @@ description: "Landing page for Home Assistant Android app."
<link rel='redirect_uri' href='homeassistant://auth-callback'>
Nothing to see yet :)
<script>/*document.location.href = '/docs/ecosystem/ios';*/</script>
<script>document.location.href = 'https://companion.home-assistant.io/';</script>

View File

@ -33,7 +33,7 @@ Follow this guide if you want to get started with Home Assistant easily or if yo
### Suggested hardware
We will need a few things to get started with installing Home Assistant. The Raspberry Pi 3 Model B+ is a good, affordable starting point for your home automation journey. Links below lead to Amazon US. If you're not in the US, you should be able to find these items in web stores in your country.
We will need a few things to get started with installing Home Assistant. The Raspberry Pi 4 Model B is a good, affordable starting point for your home automation journey. Links below lead to Amazon US. If you're not in the US, you should be able to find these items in web stores in your country.
- [Raspberry Pi 4 Model B (2GB)](https://amzn.to/2XULT2z) + [Power Supply](https://www.raspberrypi.org/help/faqs/#powerReqs) (at least 2.5A)
- [Micro SD Card](https://amzn.to/2X0Z2di). Ideally get one that is [Application Class 2](https://www.sdcard.org/developers/overview/application/index.html) as they handle small I/O much more consistently than cards not optimized to host applications. A 32 GB or bigger card is recommended.
@ -42,7 +42,7 @@ We will need a few things to get started with installing Home Assistant. The Ras
### Software requirements
- Download the HassOS image for [your device](/hassio/installation/)
- Download and extract the HassOS image for [your device](/hassio/installation/)
- Download [balenaEtcher] to write the image to an SD card
[balenaEtcher]: https://www.balena.io/etcher

View File

@ -4,4 +4,4 @@ description: "Landing page for Home Assistant iOS app."
---
<link rel='redirect_uri' href='homeassistant://auth-callback'>
<script>document.location.href = '/docs/ecosystem/ios';</script>
<script>document.location.href = 'https://companion.home-assistant.io/';</script>