mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 15:26:59 +00:00
Merge branch 'current' into rc
This commit is contained in:
Franck Nijhof
commit
85b2b2669a
@ -25,11 +25,11 @@ GEM
|
||||
http_parser.rb (~> 0.6.0)
|
||||
eventmachine (1.2.7)
|
||||
eventmachine (1.2.7-x64-mingw32)
|
||||
ffi (1.13.0)
|
||||
ffi (1.13.0-x64-mingw32)
|
||||
ffi (1.13.1)
|
||||
ffi (1.13.1-x64-mingw32)
|
||||
forwardable-extended (2.6.0)
|
||||
http_parser.rb (0.6.0)
|
||||
i18n (1.8.2)
|
||||
i18n (1.8.3)
|
||||
concurrent-ruby (~> 1.0)
|
||||
jekyll (4.1.0)
|
||||
addressable (~> 2.4)
|
||||
@ -88,7 +88,7 @@ GEM
|
||||
rb-inotify (0.10.1)
|
||||
ffi (~> 1.0)
|
||||
rexml (3.2.4)
|
||||
rouge (3.19.0)
|
||||
rouge (3.20.0)
|
||||
ruby-enum (0.8.0)
|
||||
i18n
|
||||
ruby2_keywords (0.0.2)
|
||||
|
||||
12
package-lock.json
generated
12
package-lock.json
generated
@ -2289,9 +2289,9 @@
|
||||
}
|
||||
},
|
||||
"remark-stringify": {
|
||||
"version": "8.0.0",
|
||||
"resolved": "https://registry.npmjs.org/remark-stringify/-/remark-stringify-8.0.0.tgz",
|
||||
"integrity": "sha512-cABVYVloFH+2ZI5bdqzoOmemcz/ZuhQSH6W6ZNYnLojAUUn3xtX7u+6BpnYp35qHoGr2NFBsERV14t4vCIeW8w==",
|
||||
"version": "8.1.0",
|
||||
"resolved": "https://registry.npmjs.org/remark-stringify/-/remark-stringify-8.1.0.tgz",
|
||||
"integrity": "sha512-FSPZv1ds76oAZjurhhuV5qXSUSoz6QRPuwYK38S41sLHwg4oB7ejnmZshj7qwjgYLf93kdz6BOX9j5aidNE7rA==",
|
||||
"dev": true,
|
||||
"requires": {
|
||||
"ccount": "^1.0.0",
|
||||
@ -2495,9 +2495,9 @@
|
||||
}
|
||||
},
|
||||
"stringify-entities": {
|
||||
"version": "3.0.0",
|
||||
"resolved": "https://registry.npmjs.org/stringify-entities/-/stringify-entities-3.0.0.tgz",
|
||||
"integrity": "sha512-h7NJJIssprqlyjHT2eQt2W1F+MCcNmwPGlKb0bWEdET/3N44QN3QbUF/ueKCgAssyKRZ3Br9rQ7FcXjHr0qLHw==",
|
||||
"version": "3.0.1",
|
||||
"resolved": "https://registry.npmjs.org/stringify-entities/-/stringify-entities-3.0.1.tgz",
|
||||
"integrity": "sha512-Lsk3ISA2++eJYqBMPKcr/8eby1I6L0gP0NlxF8Zja6c05yr/yCYyb2c9PwXjd08Ib3If1vn1rbs1H5ZtVuOfvQ==",
|
||||
"dev": true,
|
||||
"requires": {
|
||||
"character-entities-html4": "^1.0.0",
|
||||
|
||||
@ -9,7 +9,7 @@
|
||||
"remark-lint": "^7.0.0",
|
||||
"remark-lint-fenced-code-flag": "^2.0.0",
|
||||
"remark-lint-no-shell-dollars": "^2.0.1",
|
||||
"remark-stringify": "^8.0.0",
|
||||
"remark-stringify": "^8.1.0",
|
||||
"textlint": "^11.6.3",
|
||||
"textlint-rule-common-misspellings": "^1.0.1",
|
||||
"textlint-rule-terminology": "^2.1.4"
|
||||
|
||||
@ -54,23 +54,16 @@ Before proceeding, make sure you have shared out a drive for Docker to mount to.
|
||||
<https://docs.docker.com/docker-for-windows/troubleshoot/#verify-domain-user-has-permissions-for-shared-drives-volumes>
|
||||
|
||||
```powershell
|
||||
docker run --init -d --name="home-assistant" -e "TZ=America/Los_Angeles" -v /PATH_TO_YOUR_CONFIG:/config --net=host homeassistant/home-assistant:stable
|
||||
docker run --init -d --name="home-assistant" -e "TZ=America/Los_Angeles" -v /PATH_TO_YOUR_CONFIG:/config -p 8123:8123 homeassistant/home-assistant:stable
|
||||
```
|
||||
|
||||
It’s easier to understand the trick when put into practice. Here we would like to mount a current working directory (something like `C:\Users\<your login name>\homeassistant` make sure this exists first) into the `homeassistant/home-assistant:stable` image at the `/config` location in the container. We would do that as so:
|
||||
|
||||
```powershell
|
||||
docker run --init -d --name="home-assistant" -e "TZ=America/Los_Angeles" -v //c/Users/<your login name>/homeassistant:/config --net=host homeassistant/home-assistant:stable
|
||||
docker run --init -d --name="home-assistant" -e "TZ=America/Los_Angeles" -v //c/Users/<your login name>/homeassistant:/config -p 8123:8123 homeassistant/home-assistant:stable
|
||||
```
|
||||
|
||||
When running Home Assistant in Docker on Windows, you may have some difficulty getting ports to map for routing (since the `--net=host` switch actually applies to the hypervisor's network interface). To get around this, you will need to add port proxy ipv4 rules to your local Windows machine, like so (Replacing '192.168.1.10' with whatever your Windows IP is, and '10.0.50.2' with whatever your Docker container's IP is):
|
||||
|
||||
```bash
|
||||
netsh interface portproxy add v4tov4 listenaddress=192.168.1.10 listenport=8123 connectaddress=10.0.50.2 connectport=8123
|
||||
netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=8123 connectaddress=10.0.50.2 connectport=8123
|
||||
```
|
||||
|
||||
This will let you access your Home Assistant portal from `http://localhost:8123`, and if you forward port 8123 on your router to your machine IP, the traffic will be forwarded on through to the Docker container.
|
||||
Host networking is not supported on Windows so we have to forward the port 8123. This will let you access your Home Assistant portal from `http://localhost:8123`, and if you forward port 8123 on your router to your machine IP, the traffic will be forwarded on through to the Docker container.
|
||||
|
||||
### Synology NAS
|
||||
|
||||
|
||||
@ -1457,3 +1457,45 @@ The configuration parameters will have to be added to the `zwcfg` file. Replace
|
||||
</Value>
|
||||
</CommandClass>
|
||||
```
|
||||
|
||||
### Jasco 2 Button Remote (37792/ZW5307)
|
||||
|
||||
<!-- from https://products.z-wavealliance.org/products/2930/ -->
|
||||
|
||||
Once you've added the remote to your Z-Wave network, you'll need to update your `zwcfg_*.xml` file with the below XML data. Stop Home Assistant and open your `zwcfg_*.xml` file (located in your configuration folder). Find the remote's device section and then its corresponding `CommandClass` section with id="91". Replace the entire CommandClass section with the below XML data. Save the file and restart Home Assistant.
|
||||
|
||||
```xml
|
||||
<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0">
|
||||
<Instance index="1" />
|
||||
<Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
|
||||
<Value type="int" genre="system" instance="1" index="1" label="Button One" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
|
||||
<Value type="int" genre="system" instance="1" index="2" label="Button Two" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
|
||||
</CommandClass>
|
||||
```
|
||||
|
||||
Below is a table of the action/scenes for the Jasco remote:
|
||||
|
||||
**Action**|**scene\_id**|**scene\_data**
|
||||
:-----:|:-----:|:-----:
|
||||
Button one single tap|1|0
|
||||
Button one double tap|1|3
|
||||
Button one triple tap|1|4
|
||||
Button two single tap|2|0
|
||||
Button two double tap|2|3
|
||||
Button two triple tap|2|4
|
||||
|
||||
Example Event:
|
||||
|
||||
```yaml
|
||||
- alias: JascoButton1
|
||||
trigger:
|
||||
- event_type: zwave.scene_activated
|
||||
platform: event
|
||||
event_data:
|
||||
node_id: 2
|
||||
scene_id: 1
|
||||
scene_data: 0
|
||||
action:
|
||||
- service: switch.toggle
|
||||
entity_id: switch.office_fan
|
||||
```
|
||||
|
||||
@ -188,7 +188,7 @@ To fix the problem, you need to follow these steps:
|
||||
- Remove the device from Broadlink App
|
||||
- Factory reset the device
|
||||
- Add the device to your local network using the app
|
||||
- Do not set up a cloud (not now, not ever)
|
||||
- Do not set up a cloud (not now, not ever). This means that you don't have to complete the setup in the app, configure only the Wi-Fi and don't add the Broadlink device to the app
|
||||
- Specify the correct device type in the configuration file
|
||||
|
||||
Example 1: Set up the new RM Mini 3 using remote platform
|
||||
|
||||
@ -126,6 +126,7 @@ For example: for model `UN55NU7100`, the `UN55` would mean it's an LED, North Am
|
||||
- U6300
|
||||
- RU7100
|
||||
- RU7172
|
||||
- Q90RATXZT
|
||||
|
||||
#### Models tested but not yet working
|
||||
|
||||
|
||||
@ -43,7 +43,7 @@ For UniFi OS a local-only user needs to be created. A user who uses the Ubiquiti
|
||||
|
||||
### Conflicts with MQTT
|
||||
|
||||
The UniFi controller can either be a dedicated hardware device (UniFi's cloud key), or as software any Linux system. If you run the UniFi controller on the same operating system as Home Assistant there may be conflicts in ports if you have the MQTT integration as well.
|
||||
The UniFi controller can either be a dedicated hardware device (UniFi's cloud key), or as software on any Linux system. If you run the UniFi controller on the same operating system as Home Assistant there may be conflicts in ports if you have the MQTT integration as well.
|
||||
|
||||
It is recommended that you run the UniFi controller in a dedicated virtual machine to avoid that situation.
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ Before calling one of these services, make sure your vacuum platform supports it
|
||||
|
||||
#### Service `vacuum.turn_on`
|
||||
|
||||
Start a new cleaning task. For the Xiaomi Vacuum and Neato use `vacuum.start` instead.
|
||||
Start a new cleaning task. For the Xiaomi Vacuum, Roomba, and Neato use `vacuum.start` instead.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
@ -35,7 +35,7 @@ Start a new cleaning task. For the Xiaomi Vacuum and Neato use `vacuum.start` in
|
||||
|
||||
#### Service `vacuum.turn_off`
|
||||
|
||||
Stop the current cleaning task and return to the dock. For the Xiaomi Vacuum and Neato use `vacuum.stop` instead.
|
||||
Stop the current cleaning task and return to the dock. For the Xiaomi Vacuum, Roomba, and Neato use `vacuum.stop` instead.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|---------------------------|----------|-------------------------------------------------------|
|
||||
|
||||
@ -216,7 +216,7 @@ The following table shows the units of measurement for each attribute:
|
||||
|
||||
## Retrieving the Access Token
|
||||
|
||||
### Xiaomi Home app (Xiaomi Aqara Gateway, android?)
|
||||
### Xiaomi Home app (Xiaomi Aqara Gateway, Android & iOS)
|
||||
|
||||
1. Install the Xiaomi Home app.
|
||||
2. Sign In/make an account.
|
||||
@ -224,9 +224,10 @@ The following table shows the units of measurement for each attribute:
|
||||
4. Select your Gateway in Xiaomi Home app.
|
||||
5. Then the 3 dots at the top right of the screen.
|
||||
6. Then click on about.
|
||||
7. Tap the version number (Plug-in version 2.77.1 as of January 2020) at the bottom of the screen repeatedly.
|
||||
8. You should now see 2 extra options listed in English, this means you enabled developer mode. [if not, try all steps again!].
|
||||
9. Under "Hub info" there is quite some text in JSON format, this includes the "token" that you need.
|
||||
7. Tap the version number (Plug-in version 2.77.1 as of January 2020, iOS has a white space instead of version number) at the bottom of the screen repeatedly.
|
||||
8. You should now see 2 extra options listed in English (iOS still in Chinese), this means you enabled developer mode. [if not, try all steps again!].
|
||||
9. Android: under "Hub info" there is quite some text in JSON format, this includes the "token" that you need.
|
||||
iOS: Most options are still in Chinese, you need the fourth item from the top.
|
||||
|
||||
Note: If you have multiple devices needing a token, e.g., Xiaomi Mi Robot Vacuum and a Xiaomi IR Remote, the above method may not work. The Xiaomi Home app will display a token, though it isn't the correct one. The alternative method using "Mi Home v5.4.49" will provide the correct token.
|
||||
|
||||
|
||||
@ -12,12 +12,6 @@ ha_domain: websocket_api
|
||||
|
||||
The `websocket_api` integration set up a WebSocket API and allows one to interact with a Home Assistant instance that is running headless. This integration depends on the [`http` component](/integrations/http/).
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
It is HIGHLY recommended that you set the `api_password`, especially if you are planning to expose your installation to the internet.
|
||||
|
||||
</div>
|
||||
|
||||
## Configuration
|
||||
|
||||
```yaml
|
||||
|
||||
@ -100,11 +100,11 @@ a new pop-up asking for a radio type. In the pop-up:
|
||||
|
||||
| Radio Type | Zigbee Radio Hardware |
|
||||
| ------------- | ------------- |
|
||||
| `ezsp` | EmberZNet based radios, HUSBZB-1, Telegesis ETRX357USB*** (using EmberZNet firmware) |
|
||||
| `deconz` | dresden elektronik ConBee and RaspBee based radios with deCONZ Zigbee firmware |
|
||||
| `xbee` | Digi XBee Series 2, 2C and 3 based radios with XBee Zigbee firmware |
|
||||
| `ti_cc` | Texas Instruments CC253x/CC26x2/CC13x2 based radios with Z-Stack firmware |
|
||||
| `zigate` | ZiGate USB-TTL, PiZiGate, and WiFi based Zigbee radios with ZiGate firmware |
|
||||
| `ezsp` | Silicon Labs EmberZNet protocol (ex; Elelabs, HUSBZB-1, Telegesis) |
|
||||
| `deconz` | dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II |
|
||||
| `ti_cc` | Texas Instruments Z-Stack ZNP protocol (ex: CC253x, CC26x2, CC13x2) |
|
||||
| `zigate` | ZiGate Serial protocol: PiZiGate, ZiGate USB-TTL, ZiGate WiFi |
|
||||
| `xbee` | Digi XBee ZB Coordinator Firmware protocol (Digi XBee Series 2, 2C, 3) |
|
||||
|
||||
- Submit
|
||||
|
||||
|
||||
@ -66,7 +66,9 @@ Toggle entity using a service:
|
||||
```yaml
|
||||
type: picture
|
||||
image: /local/light.png
|
||||
service: light.toggle
|
||||
service_data:
|
||||
entity_id: light.ceiling_lights
|
||||
tap_action:
|
||||
action: call-service
|
||||
service: light.toggle
|
||||
service_data:
|
||||
entity_id: light.ceiling_lights
|
||||
```
|
||||
|
||||
@ -823,6 +823,28 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[todoist docs]: /integrations/todoist/
|
||||
[zeroconf docs]: /integrations/zeroconf/
|
||||
|
||||
## Release 0.110.5 - June 5
|
||||
|
||||
- Add partial mobile app sensor validation ([#36433] - [@balloob])
|
||||
- Fix iOS app crashing on None values in Zeroconf service info ([#36490] - [@frenck])
|
||||
- Update myq for latest api changes ([#36469] - [@bdraco])
|
||||
|
||||
[#36433]: https://github.com/home-assistant/core/pull/36433
|
||||
[#36490]: https://github.com/home-assistant/core/pull/36490
|
||||
[#36469]: https://github.com/home-assistant/core/pull/36469
|
||||
|
||||
## Release 0.110.6 - June 8
|
||||
|
||||
- Fix mobile_app registering/update sensor values with an unknown state. Will unblock iOS app (#36566 - [@frenck])
|
||||
|
||||
[#36566]: https://github.com/home-assistant/core/pull/36566
|
||||
|
||||
## Release 0.110.7 - June 9
|
||||
|
||||
- Fix mobile_app missing state in sensor registration ([#36604] - [@frenck])
|
||||
|
||||
[#36604]: https://github.com/home-assistant/core/pull/36604
|
||||
|
||||
## All changes
|
||||
|
||||
<details>
|
||||
|
||||
@ -5,7 +5,7 @@ date: 2020-05-25 00:00:00
|
||||
date_formatted: "May 25, 2020"
|
||||
author: Franck Nijhof
|
||||
author_twitter: frenck
|
||||
categories: Announcements, Organization
|
||||
categories: Announcements Organization
|
||||
---
|
||||
|
||||
On January 21st, 2017, Home Assistant [announced](/blog/2017/01/21/home-assistant-governance/)
|
||||
|
||||
@ -107,23 +107,23 @@ If you would like to test next release before anyone else, you can install the b
|
||||
|
||||
[balenaEtcher]: https://www.balena.io/etcher
|
||||
[hassos-network]: https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md
|
||||
[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_rpi0-w-4.8.img.gz
|
||||
[pi1]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_rpi-4.8.img.gz
|
||||
[pi2]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_rpi2-4.8.img.gz
|
||||
[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_rpi3-4.8.img.gz
|
||||
[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_rpi3-64-4.8.img.gz
|
||||
[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_rpi4-4.8.img.gz
|
||||
[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_rpi4-64-4.8.img.gz
|
||||
[tinker]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_tinker-4.8.img.gz
|
||||
[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_odroid-c2-4.8.img.gz
|
||||
[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_odroid-n2-4.8.img.gz
|
||||
[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_odroid-xu4-4.8.img.gz
|
||||
[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_intel-nuc-4.8.img.gz
|
||||
[vmdk]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_ova-4.8.vmdk.gz
|
||||
[vhdx]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_ova-4.8.vhdx.gz
|
||||
[vdi]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_ova-4.8.vdi.gz
|
||||
[qcow2]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_ova-4.8.qcow2.gz
|
||||
[Virtual Appliance]: https://github.com/home-assistant/operating-system/releases/download/4.8/hassos_ova-4.8.ova
|
||||
[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi0-w-4.10.img.gz
|
||||
[pi1]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi-4.10.img.gz
|
||||
[pi2]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi2-4.10.img.gz
|
||||
[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi3-4.10.img.gz
|
||||
[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi3-64-4.10.img.gz
|
||||
[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi4-4.10.img.gz
|
||||
[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi4-64-4.10.img.gz
|
||||
[tinker]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_tinker-4.10.img.gz
|
||||
[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_odroid-c2-4.10.img.gz
|
||||
[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_odroid-n2-4.10.img.gz
|
||||
[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_odroid-xu4-4.10.img.gz
|
||||
[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_intel-nuc-4.10.img.gz
|
||||
[vmdk]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_ova-4.10.vmdk.gz
|
||||
[vhdx]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_ova-4.10.vhdx.gz
|
||||
[vdi]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_ova-4.10.vdi.gz
|
||||
[qcow2]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_ova-4.10.qcow2.gz
|
||||
[Virtual Appliance]: https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_ova-4.10.ova
|
||||
[local]: http://homeassistant.local:8123
|
||||
[samba]: /addons/samba/
|
||||
[ssh]: /addons/ssh/
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
layout: null
|
||||
layout: none
|
||||
---
|
||||
{% assign recent_release_post = site.categories['Release-Notes'].first %}{
|
||||
"current_version": "{{ site.current_major_version }}.{{ site.current_minor_version }}.{{ site.current_patch_version }}",
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user