jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-28 11:47:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2023-08-04 15:58:12 +02:00
commit 948de4c7a2
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
12 changed files with 142 additions and 104 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Gemfile.lock
View File

@ -1,7 +1,7 @@
GEM
remote: https://rubygems.org/
specs:
addressable (2.8.4)
addressable (2.8.5)
public_suffix (>= 2.0.2, < 6.0)
chunky_png (1.4.0)
colorator (1.1.0)

4
_config.yml
View File

@ -110,8 +110,8 @@ social:
# Home Assistant release details
current_major_version: 2023
current_minor_version: 8
current_patch_version: 0
date_released: 2023-08-02
current_patch_version: 1
date_released: 2023-08-04
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

9
source/_data/glossary.yml
View File

@ -76,6 +76,15 @@
such as on or off.
link: /integrations/binary_sensor
- term: Blueprint
definition: >-
A blueprint is a script or automation configuration with certain parts marked as configurable. This allows users to create multiple scripts or automations based on the same blueprint, with each having its own configuration-specific settings. Blueprints are shared by the community on the [blueprints exchange](https://community.home-assistant.io/c/blueprints-exchange/53) in the forum.
link: /docs/blueprint/
excerpt: >-
A blueprint is a script or automation configuration with certain parts marked as configurable. This allows users to create multiple scripts or automations based on the same blueprint, with each having its own configuration-specific settings.
aliases:
- blueprints
- term: Component
definition: >-
Better known as: Integrations. Integrations used to be known as components.

3
source/_includes/integrations/config_flow.md
View File

@ -3,8 +3,7 @@
## Configuration
Adding {{ name }} to your Home Assistant instance can be done via the user
interface, by using this My button:
To add the **{{ name }}** integration to your Home Assistant instance, use this My button:
{% my config_flow_start badge domain=domain %}

2
source/_integrations/alexa.smart_home.markdown
View File

@ -229,7 +229,7 @@ Alexa needs to link your Amazon account to your Home Assistant account. Therefor
- Find the skill you just created, click `Edit` link in the `Actions` column.
- Click `ACCOUNT LINKING` in the left navigation bar of build page
- Do not turn on the "Allow users to link their account to your skill from within your application or website" switch. This will require a Redirect URI, which won't work.
- Input all information required. Assuming your Home Assistant can be accessed by `https://[YOUR HOME ASSISTANT URL]`
- Input all information required. Assuming your Home Assistant can be accessed by `https://[YOUR HOME ASSISTANT URL]`. Alexa account linking does not work with a non-standard port. You must use port 443. Use your firewall to forward, if needed. Using a `:1234` or a similar port number will not work.
- `Authorization URI`: `https://[YOUR HOME ASSISTANT URL]/auth/authorize`
- `Access Token URI`: `https://[YOUR HOME ASSISTANT URL]/auth/token`
- Note: you must use a valid/trusted SSL Certificate for account linking to work

2
source/_integrations/broadlink.markdown
View File

@ -157,7 +157,7 @@ When the LED blinks for the first time, press the button you want to learn. Then
#### Learned codes storage location
The learned codes are stored in `/configuration/.storage/` or `/config/.storage/` in a JSON file called `broadlink_remote_MACADDRESS_codes`. You can open this file with a text editor and copy the codes to set up [custom IR/RF switches](#setting-up-custom-irrf-switches) or to send them as [base64 codes](#sending-a-base64-code), but beware: the files in the .storage folder _should never be edited manually_.
The learned codes are stored in `/config/.storage/` in a JSON file called `broadlink_remote_MACADDRESS_codes`. You can open this file with a text editor and copy the codes to set up [custom IR/RF switches](#setting-up-custom-irrf-switches) or to send them as [base64 codes](#sending-a-base64-code), but beware: the files in the .storage folder _should never be edited manually_.
### Sending commands

78
source/_integrations/discovery.markdown
View File

@ -1,78 +0,0 @@
---
title: Discovery
description: Instructions on how to setup Home Assistant to discover new devices with the Discovery integration.
ha_category:
- Other
ha_release: 0.7
ha_quality_scale: internal
ha_domain: discovery
ha_codeowners:
- '@home-assistant/core'
ha_integration_type: system
---
This is the legacy discovery integration for Home Assistant. It's use is no longer recommended. Use the [SSDP](/integrations/ssdp/), [Zeroconf](/integrations/zeroconf/) and [USB](/integrations/usb/) integrations instead.
This integration is limited to detect:
- [Bluesound speakers](/integrations/bluesound)
- [Bose Soundtouch speakers](/integrations/soundtouch)
- [Enigma2 media player](/integrations/enigma2)
- [SABnzbd downloader](/integrations/sabnzbd)
- [Yamaha media player](/integrations/yamaha)
To load this integration, add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
discovery:
ignore:
- yamaha
- logitech_mediaserver
```
{% configuration discovery %}
ignore:
description: A list of platforms that never will be automatically configured by `discovery`.
required: false
type: list
enable:
description: A list of platforms not enabled by default that `discovery` should discover.
required: false
type: list
{% endconfiguration %}
Valid values for ignore are:
- `bluesound`: Bluesound speakers
- `bose_soundtouch`: Bose Soundtouch speakers
- `enigma2`: Enigma2 media players
- `lg_smart_device`: LG Soundbars
- `sabnzbd`: SABnzbd downloader
- `yamaha`: Yamaha media player
## Troubleshooting
### mDNS and UPnP
Home Assistant should be on the same network as the devices for mDNS and UPnP discovery to work.
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.
If mDNS is still not working:
- Make sure there are no firewall rules blocking mDNS traffic. mDNS relies on sending and receiving UDP multicast packets on port 5353.
- mDNS traffic may not be forwarded correctly between the wired and wireless interfaces of a Wi-Fi AP or router.
#### mDNS forwarding
If it's not possible to have Home Assistant and the devices on the same network, mDNS forwarding may allow mDNS discovery between networks.
mDNS forwarding is a configurable option in some routers. It can also be called mDNS reflector or mDNS repeater, depending on the manufacturer.
### Windows
#### 64-bit Python
There is currently a <a href='https://web.archive.org/web/20200623234241/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
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.

2
source/_integrations/enigma2.markdown
View File

@ -17,7 +17,7 @@ The `enigma2` platform allows you to control a Linux based set-top box which is
[OpenWebif](https://github.com/E2OpenPlugins/e2openplugin-OpenWebif) is an open source web interface for Enigma2 based set-top boxes.
To manually add a set-top box to your installation, add the following to your `configuration.yaml` file:
To add a set-top box to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry

2
source/_integrations/nest.markdown
View File

@ -47,7 +47,7 @@ The Nest Smart Device Management (SDM) API **requires a US$5 fee**. Before buyin
## Configuration
Adding Nest to your Home Assistant instance can be done via the user interface, by using this My Button:
To add the **Nest** integration to your Home Assistant, use this My Button:
{% my config_flow_start badge domain=page.ha_domain %}
![Screenshot of Setup prompt](/images/integrations/nest/setup_prompt.png)

2
source/_integrations/panasonic_viera.markdown
View File

@ -118,7 +118,7 @@ Some of the known valid key values are:
- `back`
- `power`
The list with all known valid keys can be found [here](https://github.com/florianholzapfel/panasonic-viera/blob/521cefadc8e1543514ce41d3d49e9218d1c2302d/panasonic_viera/__init__.py#L35). Additionally, you can also send custom commands, such as `"NRC_HOME-ONOFF"` (which is the same as `home`). Two further undocumented commands are `"NRC_CHG_HDMI1-ONOFF"` and `"NRC_CHG_HDMI1-ONOFF"` for selecting HDMI inputs.
The list with all known valid keys can be found [here](https://github.com/florianholzapfel/panasonic-viera/blob/521cefadc8e1543514ce41d3d49e9218d1c2302d/panasonic_viera/__init__.py#L35). Additionally, you can also send custom commands, such as `"NRC_HOME-ONOFF"` (which is the same as `home`). Further undocumented commands are `"NRC_HDMI1-ONOFF"`, `"NRC_HDMI2-ONOFF"`, `"NRC_HDMI3-ONOFF"` and `"NRC_HDMI4-ONOFF"` for selecting HDMI inputs and `"NRC_NETFLIX-ONOFF"`, `"NRC_APPS-ONOFF"`, "`NRC_MYAPP-ONOFF`" for apps.
### Currently known supported models

18
source/_integrations/yamaha.markdown
View File

@ -32,7 +32,8 @@ To add a Yamaha Network Receiver to your installation, add the following to your
media_player:
- platform: yamaha
```
You **must** enable network standby on your receiver, or else startup of Home Assistant will hang if you
have your receiver switched off.
{% configuration %}
name:
description: Name of the device. This overrides the default name (often model number) that is returned by the device.
@ -60,21 +61,6 @@ zone_names:
type: list
{% endconfiguration %}
### Discovery notes
- If the `discovery` integration is enabled, all units on the network
will be discovered using UPnP.
- For receivers that support more than one zone, Home Assistant will
add one media player per zone supported by the player, named "$name
Zone 2" and "$name Zone 3".
- If you specify `host` manually, you **must** enable network standby
on your receiver, or else startup of Home Assistant will hang if you
have your receiver switched off.
- In some cases, auto-discovery fails due to a known bug in the
receiver's firmware. It is possible to manually specify the
receiver's IP address or via its hostname (if it is discoverable by
your DNS) then.
### Supported operations
- Media players created by Yamaha support powering on/off, mute,

122
source/_posts/2023-08-02-release-20238.markdown
View File

@ -338,6 +338,128 @@ The following integrations are now available via the Home Assistant UI:
[OpenSky]: /integrations/opensky
[Zodiac]: /integrations/zodiac
## Release 2023.8.1 - August 4
- Raise PlatformNotReady on initial OwnTone connection failure ([@uvjustin] - [#97257])
- Add overkiz battery sensor level medium ([@matthieume] - [#97472])
- Fix ZHA `turn_on` issues with `transition=0`, improve tests ([@TheJulianJES] - [#97539])
- Bump pyDuotecno to 2023.8.1 ([@Cereal2nd] - [#97583])
- Bump Cryptography to 41.0.3 for a second security fix ([@blastoise186] - [#97611])
- Waqi State unknown if value is string ([@joostlek] - [#97617])
- Bump dbus-fast to 1.90.1 ([@bdraco] - [#97619])
- Bump python-roborock to 0.31.1 ([@Lash-L] - [#97632])
- Bump intents to 2023.8.2 ([@synesthesiam] - [#97636])
- Add device naming to Yeelight ([@joostlek] - [#97639])
- Fix typo in tplink OUI ([@bdraco] - [#97644])
- Revert "Add device naming to Yeelight" ([@joostlek] - [#97647])
- Enable the `PRESET_MODE` `FanEntityFeature` for VeSync air purifiers ([@DuckyCrayfish] - [#97657])
- Fix tplink child plug state reporting ([@bdraco] - [#97658])
- Fix date and timestamp device class in Command Line Sensor ([@gjohansson-ST] - [#97663])
- Bump zeroconf to 0.72.3 ([@bdraco] - [#97668])
- Bump pyatv to 0.13.3 ([@bdraco] - [#97670])
- Fix color mode attribute for both official and non-official Hue lights ([@marcelveldt] - [#97683])
- Fix UniFi image platform not loading when passphrase is missing from WLAN ([@Kane610] - [#97684])
- Fix Kostal_Plenticore SELECT entities using device_info correctly ([@N3rdix] - [#97690])
- Fix freebox enumerate raid disks ([@cyr-ius] - [#97696])
- Fix allow_name_translation logic ([@amitfin] - [#97701])
- Fix NWS twice_daily forecast day/night detection ([@karwosts] - [#97703])
- Bump opower to 0.0.19 ([@tronikos] - [#97706])
- Fix detection of client WAN access rule in AVM Fritz!Box Tools ([@mib1185] - [#97708])
- Fix unloading KNX integration without sensors ([@farmio] - [#97720])
- Update zigpy to 0.56.3 ([@cdce8p] - [#97480])
- Bump zigpy to 0.56.4 ([@TheJulianJES] - [#97722])
- Fix keymitt_ble RuntimeWarning ([@cdce8p] - [#97729])
- Bump zeroconf to 0.74.0 ([@bdraco] - [#97745])
- Avoid calling the http access logging when logging is disabled in emulated_hue ([@bdraco] - [#97750])
- Bump opower to 0.0.20 ([@tronikos] - [#97752])
- Bump pyduotecno to 2023.8.3 ([@Cereal2nd] - [#97759])
- Add has entity name to Solarlog ([@joostlek] - [#97764])
- Fix WAQI being zero ([@joostlek] - [#97767])
[#97257]: https://github.com/home-assistant/core/pull/97257
[#97472]: https://github.com/home-assistant/core/pull/97472
[#97480]: https://github.com/home-assistant/core/pull/97480
[#97539]: https://github.com/home-assistant/core/pull/97539
[#97583]: https://github.com/home-assistant/core/pull/97583
[#97609]: https://github.com/home-assistant/core/pull/97609
[#97611]: https://github.com/home-assistant/core/pull/97611
[#97617]: https://github.com/home-assistant/core/pull/97617
[#97619]: https://github.com/home-assistant/core/pull/97619
[#97632]: https://github.com/home-assistant/core/pull/97632
[#97636]: https://github.com/home-assistant/core/pull/97636
[#97639]: https://github.com/home-assistant/core/pull/97639
[#97644]: https://github.com/home-assistant/core/pull/97644
[#97647]: https://github.com/home-assistant/core/pull/97647
[#97657]: https://github.com/home-assistant/core/pull/97657
[#97658]: https://github.com/home-assistant/core/pull/97658
[#97663]: https://github.com/home-assistant/core/pull/97663
[#97668]: https://github.com/home-assistant/core/pull/97668
[#97670]: https://github.com/home-assistant/core/pull/97670
[#97683]: https://github.com/home-assistant/core/pull/97683
[#97684]: https://github.com/home-assistant/core/pull/97684
[#97690]: https://github.com/home-assistant/core/pull/97690
[#97696]: https://github.com/home-assistant/core/pull/97696
[#97701]: https://github.com/home-assistant/core/pull/97701
[#97703]: https://github.com/home-assistant/core/pull/97703
[#97706]: https://github.com/home-assistant/core/pull/97706
[#97708]: https://github.com/home-assistant/core/pull/97708
[#97720]: https://github.com/home-assistant/core/pull/97720
[#97722]: https://github.com/home-assistant/core/pull/97722
[#97729]: https://github.com/home-assistant/core/pull/97729
[#97745]: https://github.com/home-assistant/core/pull/97745
[#97750]: https://github.com/home-assistant/core/pull/97750
[#97752]: https://github.com/home-assistant/core/pull/97752
[#97759]: https://github.com/home-assistant/core/pull/97759
[#97764]: https://github.com/home-assistant/core/pull/97764
[#97767]: https://github.com/home-assistant/core/pull/97767
[@Cereal2nd]: https://github.com/Cereal2nd
[@DuckyCrayfish]: https://github.com/DuckyCrayfish
[@Kane610]: https://github.com/Kane610
[@Lash-L]: https://github.com/Lash-L
[@N3rdix]: https://github.com/N3rdix
[@TheJulianJES]: https://github.com/TheJulianJES
[@amitfin]: https://github.com/amitfin
[@bdraco]: https://github.com/bdraco
[@blastoise186]: https://github.com/blastoise186
[@cdce8p]: https://github.com/cdce8p
[@cyr-ius]: https://github.com/cyr-ius
[@farmio]: https://github.com/farmio
[@frenck]: https://github.com/frenck
[@gjohansson-ST]: https://github.com/gjohansson-ST
[@joostlek]: https://github.com/joostlek
[@karwosts]: https://github.com/karwosts
[@marcelveldt]: https://github.com/marcelveldt
[@matthieume]: https://github.com/matthieume
[@mib1185]: https://github.com/mib1185
[@synesthesiam]: https://github.com/synesthesiam
[@tronikos]: https://github.com/tronikos
[@uvjustin]: https://github.com/uvjustin
[apple_tv docs]: /integrations/apple_tv/
[bluetooth docs]: /integrations/bluetooth/
[command_line docs]: /integrations/command_line/
[conversation docs]: /integrations/conversation/
[duotecno docs]: /integrations/duotecno/
[emulated_hue docs]: /integrations/emulated_hue/
[forked_daapd docs]: /integrations/forked_daapd/
[freebox docs]: /integrations/freebox/
[fritz docs]: /integrations/fritz/
[hue docs]: /integrations/hue/
[keymitt_ble docs]: /integrations/keymitt_ble/
[knx docs]: /integrations/knx/
[kostal_plenticore docs]: /integrations/kostal_plenticore/
[nws docs]: /integrations/nws/
[opower docs]: /integrations/opower/
[overkiz docs]: /integrations/overkiz/
[roborock docs]: /integrations/roborock/
[solarlog docs]: /integrations/solarlog/
[tplink docs]: /integrations/tplink/
[unifi docs]: /integrations/unifi/
[vesync docs]: /integrations/vesync/
[waqi docs]: /integrations/waqi/
[yeelight docs]: /integrations/yeelight/
[zeroconf docs]: /integrations/zeroconf/
[zha docs]: /integrations/zha/
## Need help? Join the community!
Home Assistant has a great community of users who are all more than willing