mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-21 08:16:53 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
dd8fedf8e4
@ -84,7 +84,7 @@ GEM
|
||||
rack-protection (2.0.8.1)
|
||||
rack
|
||||
rake (13.0.1)
|
||||
rb-fsevent (0.10.3)
|
||||
rb-fsevent (0.10.4)
|
||||
rb-inotify (0.10.1)
|
||||
ffi (~> 1.0)
|
||||
rexml (3.2.4)
|
||||
|
||||
@ -101,8 +101,8 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 109
|
||||
current_patch_version: 1
|
||||
date_released: 2020-04-30
|
||||
current_patch_version: 2
|
||||
date_released: 2020-05-01
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -8,6 +8,8 @@ redirect_from: /getting-started/installation-docker/
|
||||
|
||||
These below instructions are for an installation of Home Assistant Core running in your own Docker environment, which you manage yourself.
|
||||
|
||||
Note that Docker command line option `--net=host` or the compose file equivalent `network_mode: host` must be used to put put Home Assistant on the host's network, otherwise certain functionality - including mDNS and UPnP - will break. The `-p` command line option or the compose file equivalent `ports:` is not compatible with host networking mode and must not be used.
|
||||
|
||||
For an installation of Home Assistant Supervised, which includes Home Assistant's add-on ecosystem, see the instructions for installing [Home Assistant Supervised on a generic Linux host](/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host/).
|
||||
|
||||
</div>
|
||||
@ -38,13 +40,11 @@ docker run --init -d --name="home-assistant" -e "TZ=America/New_York" -v /home/p
|
||||
|
||||
When using `docker-ce` (or `boot2docker`) on macOS, you are unable to map the local timezone to your Docker container ([Docker issue](https://github.com/docker/for-mac/issues/44)). Instead of `-v /etc/localtime:/etc/localtime:ro`, just pass in the timezone environment variable when you launch the container, e.g, `-e "TZ=America/Los_Angeles"`. Replace "America/Los_Angeles" with [your timezone](http://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
|
||||
|
||||
If you wish to browse directly to `http://localhost:8123` from your macOS host, meaning forward ports directly to the container, replace the `--net=host` switch with `-p 8123:8123`. More detail can be found in [the Docker forums](https://forums.docker.com/t/should-docker-run-net-host-work/14215/10).
|
||||
|
||||
```bash
|
||||
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
|
||||
```
|
||||
|
||||
Alternatively, `docker-compose` works with any recent release of `docker-ce` on macOS. Note that (further down this page) we provide an example `docker-compose.yml` however it differs from the `docker run` example above. To make the .yml directives match, you would need to make _two_ changes: first add the equivalent `ports:` directive, then _remove_ the `network_mode: host` section. This is because `Port mapping is incompatible with network_mode: host:`. More details can be found at [Docker networking documentation](https://docs.docker.com/network/). Note also the `/dev/tty*` device name used by your Arduino etc. devices will differ from the Linux example, so the compose `mount:` may require updates.
|
||||
Alternatively, `docker-compose` works with any recent release of Docker CE on macOS. Note the `/dev/tty*` device name used by your Arduino etc. devices will differ from the Linux example, so the compose `mount:` may require updates.
|
||||
|
||||
### Windows
|
||||
|
||||
|
||||
@ -64,11 +64,15 @@ media_player:
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
### Cast devices and Home Assistant on different subnets
|
||||
### Docker and Cast devices and Home Assistant on different subnets
|
||||
|
||||
Cast devices can only be discovered and connected to if they are on the same subnet as Home Assistant. If this is not the case, it's necessary to:
|
||||
Cast devices can only be discovered and connected to if they are on the same subnet as Home Assistant.
|
||||
|
||||
When running Home Assistant Core in a [Docker container](/docs/installation/docker/), the command line option `--net=host` or the compose file equivalent `network_mode: host` must be used to put it on the host's network, otherwise the Home Assistant Core will not be able to connect to any Cast device.
|
||||
|
||||
Setups with cast devices on a different subnet than Home Assistant are not recommended and not supported.
|
||||
|
||||
If this is not possible, it's necessary to:
|
||||
|
||||
- Enable mDNS forwarding between the subnets.
|
||||
- Enable source NAT to make requests from Home Assistant to the Chromecast appear to come from the same subnet as the Chromecast.
|
||||
|
||||
Setups with cast devices on a different subnet than Home Assistant are not recommended and not supported.
|
||||
|
||||
@ -15,7 +15,6 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
|
||||
* [Bluesound speakers](/integrations/bluesound)
|
||||
* [Bose Soundtouch speakers](/integrations/soundtouch)
|
||||
* [Denon network receivers](/integrations/denonavr/)
|
||||
* [DirecTV receivers](/integrations/directv)
|
||||
* [DLNA DMR enabled devices](/integrations/dlna_dmr)
|
||||
* [Enigma2 media player](/integrations/enigma2)
|
||||
* [Frontier Silicon internet radios](/integrations/frontier_silicon)
|
||||
@ -25,7 +24,6 @@ Home Assistant can discover and automatically configure [zeroconf](https://en.wi
|
||||
* [NETGEAR routers](/integrations/netgear)
|
||||
* [Panasonic Viera](/integrations/panasonic_viera)
|
||||
* [Philips Hue](/integrations/hue)
|
||||
* [Roku media player](/integrations/roku#media-player)
|
||||
* [SABnzbd downloader](/integrations/sabnzbd)
|
||||
* [Samsung SyncThru Printer](/integrations/syncthru)
|
||||
* [Sonos speakers](/integrations/sonos)
|
||||
@ -74,7 +72,6 @@ Valid values for ignore are:
|
||||
* `bluesound`: Bluesound speakers
|
||||
* `bose_soundtouch`: Bose Soundtouch speakers
|
||||
* `denonavr`: Denon network receivers
|
||||
* `directv`: DirecTV receivers
|
||||
* `enigma2`: Enigma2 media players
|
||||
* `frontier_silicon`: Frontier Silicon internet radios
|
||||
* `harmony`: Logitech Harmony Hub
|
||||
@ -85,7 +82,6 @@ Valid values for ignore are:
|
||||
* `openhome`: Linn / Openhome
|
||||
* `panasonic_viera`: Panasonic Viera
|
||||
* `philips_hue`: Philips Hue
|
||||
* `roku`: Roku media player
|
||||
* `sabnzbd`: SABnzbd downloader
|
||||
* `samsung_printer`: Samsung SyncThru Printer
|
||||
* `sonos`: Sonos speakers
|
||||
@ -102,17 +98,17 @@ Valid values for enable are:
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### UPnP
|
||||
### mDNS and UPnP
|
||||
|
||||
Home Assistant must be on the same network as the devices for UPnP discovery to work.
|
||||
If running Home Assistant in a [Docker container](/docs/installation/docker/) use switch `--net=host` to put it on the host's network.
|
||||
When running Home Assistant Core in a [Docker container](/docs/installation/docker/) command line option `--net=host` or the compose file equivalent `network_mode: host` must be used to put it on the host's network, otherwise mDNS and UPnP will not work.
|
||||
|
||||
### Windows
|
||||
|
||||
#### 64-bit Python
|
||||
There is currently a <a href='https://bitbucket.org/al45tair/netifaces/issues/17/dll-fails-to-load-windows-81-64bit'>known issue</a> with running this integration on a 64-bit version of Python and Windows.
|
||||
|
||||
### could not install dependency netdisco
|
||||
### Could not install dependency netdisco
|
||||
|
||||
If you see `Not initializing discovery because could not install dependency netdisco==0.6.1` in the logs, you will need to install the `python3-dev` or `python3-devel` package on your system manually (eg. `sudo apt-get install python3-dev` or `sudo dnf -y install python3-devel`). On the next restart of Home Assistant, the discovery should work. If you still get an error, check if you have a compiler (`gcc`) available on your system.
|
||||
|
||||
|
||||
@ -3,7 +3,6 @@ title: Linksys Smart Wi-Fi
|
||||
description: Instructions on how to integrate Linksys Smart Wi-Fi Router into Home Assistant.
|
||||
ha_category:
|
||||
- Presence Detection
|
||||
logo: linksys.png
|
||||
ha_release: 0.48
|
||||
ha_domain: linksys_smart
|
||||
---
|
||||
|
||||
@ -37,6 +37,10 @@ All configuration options are offered from the front end. Enter what UniFi integ
|
||||
|
||||
The UniFi controller allows you to create multiple users on it besides the main administrator. If all you want to use is the device tracker then it is recommended that you create a limited user that has `read-only` permissions for the UniFi device tracker. If you want blocking of network access or POE control as well you would need to have 'admin' permissions.
|
||||
|
||||
### UniFi OS
|
||||
|
||||
For UniFi OS a local-only user needs to be created. A user who uses the Ubiquiti cloud will not work. You can do this in the manage users section on the UniFi OS dashboard. Make sure to give it the right permissions for the functions you want to use.
|
||||
|
||||
### 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.
|
||||
|
||||
@ -401,6 +401,53 @@ Pushetta has been offline since September 2019 and the Yahoo Weather API has bee
|
||||
[toon docs]: /integrations/toon/
|
||||
[webostv docs]: /integrations/webostv/
|
||||
|
||||
## Release 0.109.2 - May 1
|
||||
|
||||
- Don't attempt to set Vizio is_volume_muted property if Vizio API doesn't provide muted state ([@raman325] - [#34782]) ([vizio docs])
|
||||
- Bump brother to 0.1.14 ([@bieniu] - [#34930]) ([brother docs])
|
||||
- Fix MQTT debug info for same topic ([@emontnemery] - [#34952]) ([mqtt docs])
|
||||
- Fix preservation of homekit fan speed on toggle ([@bdraco] - [#34971])
|
||||
- Fix restoring isy994 brightness with no previous state ([@bdraco] - [#34972]) ([isy994 docs])
|
||||
- Support num_repeats for roku remote ([@ctalkington] - [#34981]) ([roku docs])
|
||||
- Support num_repeats for directv remote ([@ctalkington] - [#34982]) ([directv docs]) ([directv docs])
|
||||
- UniFi - Disconnected clients wrongfully marked as wired not created ([@Kane610] - [#34986]) ([unifi docs])
|
||||
- Log the rachio webhook url ([@bdraco] - [#34992]) ([rachio docs])
|
||||
- Add allow extra to totalconnect config schema ([@austinmroczek] - [#34993]) ([totalconnect docs])
|
||||
- Fix roomba not reporting error ([@shenxn] - [#34996]) ([roomba docs])
|
||||
- Lint roomba ([@balloob] - [#35000]) ([roomba docs])
|
||||
|
||||
[#34782]: https://github.com/home-assistant/core/pull/34782
|
||||
[#34930]: https://github.com/home-assistant/core/pull/34930
|
||||
[#34952]: https://github.com/home-assistant/core/pull/34952
|
||||
[#34971]: https://github.com/home-assistant/core/pull/34971
|
||||
[#34972]: https://github.com/home-assistant/core/pull/34972
|
||||
[#34981]: https://github.com/home-assistant/core/pull/34981
|
||||
[#34982]: https://github.com/home-assistant/core/pull/34982
|
||||
[#34986]: https://github.com/home-assistant/core/pull/34986
|
||||
[#34992]: https://github.com/home-assistant/core/pull/34992
|
||||
[#34993]: https://github.com/home-assistant/core/pull/34993
|
||||
[#34996]: https://github.com/home-assistant/core/pull/34996
|
||||
[#35000]: https://github.com/home-assistant/core/pull/35000
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@austinmroczek]: https://github.com/austinmroczek
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bieniu]: https://github.com/bieniu
|
||||
[@ctalkington]: https://github.com/ctalkington
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@raman325]: https://github.com/raman325
|
||||
[@shenxn]: https://github.com/shenxn
|
||||
[brother docs]: /integrations/brother/
|
||||
[directv docs]: /integrations/directv/
|
||||
[isy994 docs]: /integrations/isy994/
|
||||
[mqtt docs]: /integrations/mqtt/
|
||||
[rachio docs]: /integrations/rachio/
|
||||
[roku docs]: /integrations/roku/
|
||||
[roomba docs]: /integrations/roomba/
|
||||
[totalconnect docs]: /integrations/totalconnect/
|
||||
[unifi docs]: /integrations/unifi/
|
||||
[vizio docs]: /integrations/vizio/
|
||||
|
||||
## All changes
|
||||
|
||||
<details>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user