mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-09 18:36:51 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
b433992208
@ -18,7 +18,7 @@ GEM
|
||||
sass (>= 3.3.0, < 3.5)
|
||||
compass-import-once (1.0.5)
|
||||
sass (>= 3.2, < 3.5)
|
||||
concurrent-ruby (1.1.9)
|
||||
concurrent-ruby (1.1.10)
|
||||
em-websocket (0.5.3)
|
||||
eventmachine (>= 0.12.9)
|
||||
http_parser.rb (~> 0)
|
||||
|
||||
@ -107,8 +107,8 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 2022
|
||||
current_minor_version: 03
|
||||
current_patch_version: 5
|
||||
date_released: 2022-03-15
|
||||
current_patch_version: 6
|
||||
date_released: 2022-03-21
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -75,6 +75,22 @@ The variables action allows you to set/override variables that will be accessibl
|
||||
|
||||
{% endraw %}
|
||||
|
||||
Variables can be templated.
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
- alias: "Set a templated variable"
|
||||
variables:
|
||||
blind_state_message: "The blind is {{ states('cover.blind') }}."
|
||||
- alias: "Notify about the state of the blind"
|
||||
service: notify.mobile_app_iphone
|
||||
data:
|
||||
message: "{{ blind_state_message }}"
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
### Scope of Variables
|
||||
|
||||
Variables have local scope. This means that if a variable is changed in a nested sequence block, that change will not be visible in an outer sequence block.
|
||||
|
||||
@ -8,13 +8,13 @@
|
||||
<li><a href='https://demo.home-assistant.io'>Try the online demo</a></li>
|
||||
<li><a class="twitter-follow-button" href="https://twitter.com/Home_Assistant">Follow Home Assistant on Twitter</a></li>
|
||||
<li><div class="fb-like" data-href="https://www.facebook.com/homeassistantio/" data-layout="standard" data-action="like" data-size="small" data-show-faces="true" data-share="false"></div></li>
|
||||
<li>
|
||||
<!-- <li>
|
||||
Subscribe to the Home Assistant Newsletter
|
||||
<form action="https://services.home-assistant.io/newsletter/signup" method="post" target="_blank">
|
||||
<input type="email" id="email" name="email" placeholder="Email address" required >
|
||||
<input type="submit" value="Subscribe">
|
||||
</form>
|
||||
</li>
|
||||
</li> -->
|
||||
</ul>
|
||||
</section>
|
||||
<div id="fb-root"></div>
|
||||
|
||||
@ -16,7 +16,7 @@ We will need a few things to get started with installing Home Assistant. Links b
|
||||
- [Power Supply for Raspberry Pi 4](https://amzn.to/2ReZ2Vq) or [Power Supply for Raspberry Pi 3](https://amzn.to/2R8yG7h)
|
||||
- [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.
|
||||
- SD Card reader. This is already part of most laptops, but you can purchase a [standalone USB adapter](https://amzn.to/2WWxntY) if you don't have one. The brand doesn't matter, just pick the cheapest.
|
||||
- Ethernet cable. Home Assistant can work with Wi-Fi, but an Ethernet connection is more reliable and highly recommended.
|
||||
- [Ethernet cable](https://amzn.com/dp/B00N2VISLW). Required for installation. After installation, Home Assistant can work with Wi-Fi, but an Ethernet connection is more reliable and highly recommended.
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@ -11,13 +11,12 @@ ha_domain: group
|
||||
|
||||
The group binary_sensor platform lets you combine multiple binary_sensors into one entity. This integration presents itself as a single binary sensor in the UI. This allows the UI to use the text and icon of the type of sensor you are grouping. The sensor doesn't know what device class it should be, so this should be set to match the device class of the items in the group.
|
||||
|
||||
## Group behavior
|
||||
|
||||
By default when any member of a group is `on` then the group will also be `on`. If you set the `all` option to `true` though, this behavior is inverted and all members of the group have to be `on` for the group to turn on as well.
|
||||
## Configuration
|
||||
|
||||
To enable this platform in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
- platform: group
|
||||
name: Patio Doors
|
||||
@ -50,3 +49,18 @@ device_class:
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
## Group behavior
|
||||
|
||||
Group behavior differs depending on if the `all` option is `false` (the default) or `true`.
|
||||
If `all` is `false`(the default):
|
||||
- Group state is `unavailable` if all group members are `unavailable`
|
||||
- Otherwise, group state is `unknown` if all group members are `unknown`
|
||||
- Otherwise, group state is `on` if at least one group member is `on`
|
||||
- Otherwise, group state is `off`
|
||||
|
||||
If `all` is `true`:
|
||||
- Group state is `unavailable` if all group members are `unavailable`
|
||||
- Otherwise, group state is `unknown` if at least one group member is `unknown` or `unavailable`
|
||||
- Otherwise, group state is `off` if at least one group member is `off`
|
||||
- Otherwise, group state is `on`
|
||||
|
||||
@ -8,7 +8,7 @@ ha_iot_class: Configurable
|
||||
ha_domain: mqtt
|
||||
---
|
||||
|
||||
The `mqtt` camera platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Every time a message under the `topic` in the configuration is received, the image displayed in Home Assistant will also be updated.
|
||||
The `mqtt` camera platform allows you to integrate the content of an image file sent through MQTT into Home Assistant as a camera. Every time a message under the `topic` in the configuration is received, the image displayed in Home Assistant will also be updated. Messages received on `topic` should contain the full contents of an image file, for example, a JPEG image, without any additional encoding or metadata.
|
||||
|
||||
This can be used with an application or a service capable of sending images through MQTT.
|
||||
|
||||
@ -23,6 +23,12 @@ camera:
|
||||
topic: zanzito/shared_locations/my-device
|
||||
```
|
||||
|
||||
The sample configuration above can be tested by publishing an image to the topic from the console:
|
||||
|
||||
```shell
|
||||
mosquitto_pub -h <mqtt_broker> -t zanzito/shared_locations/my-device -f <camera_imaga.jpg>
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
availability:
|
||||
description: A list of MQTT topics subscribed to receive availability (online/offline) updates. Must not be used together with `availability_topic`.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: CPU Speed
|
||||
description: Instructions on how to integrate CPU speed within Home Assistant.
|
||||
logo: cpu.png
|
||||
ha_category:
|
||||
- System Monitor
|
||||
ha_release: pre 0.7
|
||||
|
||||
@ -16,17 +16,17 @@ ha_codeowners:
|
||||
- '@javicalle'
|
||||
---
|
||||
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](http://www.rflink.nl/blog2/download), for example, the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink Gateway is an Arduino Mega firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](https://www.rflink.nl/download.php), for example, the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink Gateway is an Arduino Mega firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
The 433 MHz spectrum is used by many manufacturers mostly using their own protocol/standard and includes devices like: light switches, blinds, weather stations, alarms and various other sensors.
|
||||
|
||||
RFLink Gateway supports a number of RF frequencies, using a wide range of low-cost hardware. [Their website](http://www.rflink.nl/blog2/) provides details for various RF transmitters, receivers and transceiver modules for 433MHz, 868MHz and 2.4 GHz.
|
||||
RFLink Gateway supports a number of RF frequencies, using a wide range of low-cost hardware. [Their website](https://www.rflink.nl) provides details for various RF transmitters, receivers and transceiver modules for 433MHz, 868MHz and 2.4 GHz.
|
||||
|
||||
<div class='note'>
|
||||
Note: Versions later than R44 add support for Ikea Ansluta, Philips Living Colors Gen1 and MySensors devices.
|
||||
</div>
|
||||
|
||||
A complete list of devices supported by RFLink can be found [here](http://www.rflink.nl/blog2/devlist).
|
||||
A complete list of devices supported by RFLink can be found [here](https://www.rflink.nl/devlist.php).
|
||||
|
||||
This integration is tested with the following hardware/software:
|
||||
|
||||
@ -69,7 +69,7 @@ tcp_keepalive_idle_timer:
|
||||
description: Time in seconds to wait since last data packet was seen before a TCP KEEPALIVE is sent. Value of 0 will disable this feature.
|
||||
required: false
|
||||
default: 3600
|
||||
type: integer
|
||||
type: integer
|
||||
{% endconfiguration %}
|
||||
|
||||
### Full example
|
||||
@ -160,7 +160,7 @@ Even though a lot of devices are supported by RFLink, not all have been tested/i
|
||||
|
||||
### Device Incorrectly Identified
|
||||
|
||||
If you find a device is recognized differently, with different protocols or the ON OFF is swapped or detected as two ON commands, it can be overcome with the RFLink 'RF Signal Learning' mechanism from RFLink Rev 46 (11 March 2017). [Link to further detail.](http://www.rflink.nl/blog2/faq#RFFind)
|
||||
If you find a device is recognized differently, with different protocols or the ON OFF is swapped or detected as two ON commands, it can be overcome with the RFLink 'RF Signal Learning' mechanism from RFLink Rev 46 (11 March 2017). [Link to further detail.](https://www.rflink.nl/faq.php#RFFind)
|
||||
|
||||
### Technical Overview
|
||||
|
||||
|
||||
@ -89,6 +89,7 @@ media_content_type: channel
|
||||
#### Selecting a source
|
||||
|
||||
It's possible to switch between the 2 sources `TV` and `HDMI`.
|
||||
Some older models also expose the installed applications through the WebSocket, in which case the source list is adjusted accordingly.
|
||||
|
||||
### Known issues and restrictions
|
||||
|
||||
|
||||
@ -62,3 +62,7 @@ Note: This does not affect the auto off timer.
|
||||
| ------------- | --------- | -------------------------------------------------------------------------------------- | -------------------------- |
|
||||
| `entity_id` | Yes | Name of the entity id associated with the integration, used for permission validation | switch.switcher_kis_boiler |
|
||||
| `timer_minutes` | Yes | Integer containing timer minutes (valid range 1 to 150) | 90 |
|
||||
|
||||
## Notes
|
||||
|
||||
If Home Assistant and your Switcher are not on the same network, you need to create a firewall rule, which allows a connection on port 20002 with the UDP protocol from Switcher to your Home Assistant and port 9957 with the TCP protocol from Home Assistant to your Switcher.
|
||||
|
||||
@ -22,9 +22,16 @@ The Tailscale integration integrates the [Tailscale](https://www.tailscale.com)
|
||||
with Home Assistant; giving you the possibility to monitor and automate on
|
||||
the state of the devices in your Tailscale VPN network (Tailnet).
|
||||
|
||||
Please, note that this integration integrates with data from the Tailscale API,
|
||||
it is not a Tailscale client itself, and thus add Home Assistant to your
|
||||
Tailscale VPN network.
|
||||
<div class="note">
|
||||
|
||||
This integration **DOES NOT** make your Home Assistant accessible via
|
||||
Tailscale VPN remotely!
|
||||
|
||||
If you want to access your Home Assistant instance remotely, you will
|
||||
need to install Tailscale itself on your own. For instructions on how to do
|
||||
this, please consult the [Tailscale documentation](https://tailscale.com/kb/).
|
||||
|
||||
</div>
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -16,6 +16,8 @@ ha_platforms:
|
||||
<div class='note warning'>
|
||||
|
||||
This integration is deprecated and will be removed in Home Assistant Core 2022.5.
|
||||
|
||||
Similar functionality is available using the [Version integration](/integrations/version/).
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -206,7 +206,7 @@ custom_quirks_path:
|
||||
|
||||
ZHA component has the ability to automatically download and perform OTA (Over-The-Air) firmware updates of Zigbee devices if the OTA firmware provider source URL for updates is available. OTA firmware updating is set to disabled (`false`) in the configuration by default.
|
||||
|
||||
Online OTA providers for firmware updates are currently only available for IKEA, LEDVANCE and SALUS devices. Support for OTA updates from other manufacturers could be supported in the future, if they publish their firmware images publicly.
|
||||
Online OTA providers for firmware updates are currently only available for IKEA, LEDVANCE/OSRAM, and SALUS/Computime devices. Support for OTA updates from other manufacturers could be supported in the future if they publish their firmware images publicly.
|
||||
|
||||
To enable OTA firmware updates for the ZHA integration you need to add the following configuration to your `configuration.yaml` and restart Home Assistant:
|
||||
|
||||
@ -215,8 +215,8 @@ zha:
|
||||
zigpy_config:
|
||||
ota:
|
||||
ikea_provider: true # Auto update Trådfri devices
|
||||
ledvance_provider: true # Auto update LEDVANCE devices
|
||||
salus_provider: true # Auto update SALUS devices
|
||||
ledvance_provider: true # Auto update LEDVANCE/OSRAM devices
|
||||
salus_provider: true # Auto update SALUS/Computime devices
|
||||
#otau_directory: /path/to/your/ota/folder # Utilize .ota files to update everything else
|
||||
```
|
||||
|
||||
|
||||
@ -53,6 +53,7 @@ Enjoy the release!
|
||||
- [Release 2022.3.3 - March 7](#release-202233---march-7)
|
||||
- [Release 2022.3.4 - March 11](#release-202234---march-11)
|
||||
- [Release 2022.3.5 - March 15](#release-202235---march-15)
|
||||
- [Release 2022.3.6 - March 21](#release-202236---march-21)
|
||||
- [Need help? Join the community!](#need-help-join-the-community)
|
||||
- [Breaking Changes](#breaking-changes)
|
||||
- [Updates for custom integration developers](#updates-for-custom-integration-developers)
|
||||
@ -552,6 +553,54 @@ The following integrations are now available via the Home Assistant UI:
|
||||
[shelly docs]: /integrations/shelly/
|
||||
[somfy_mylink docs]: /integrations/somfy_mylink/
|
||||
|
||||
## Release 2022.3.6 - March 21
|
||||
|
||||
- Fix TypeError in SamsungTV ([@epenet] - [#68235]) ([samsungtv docs])
|
||||
- Fix lyric climate ([@nprez83] - [#67018]) ([lyric docs])
|
||||
- Fix finding matrix room that is already joined ([@antlarr] - [#67967]) ([matrix docs])
|
||||
- Respect disable_new_entities for new device_tracker entities ([@mib1185] - [#68148]) ([device_tracker docs])
|
||||
- Add missing await [velbus] ([@cdce8p] - [#68153]) ([velbus docs])
|
||||
- Fix point by adding authlib constraint ([@cdce8p] - [#68176]) ([point docs])
|
||||
- Update opensensemap-api to 0.2.0 ([@frenck] - [#68193]) ([opensensemap docs])
|
||||
- Bump renault-api to 0.1.10 ([@epenet] - [#68260]) ([renault docs])
|
||||
- Hue integration: update errors that should be supressed ([@marcelveldt] - [#68337]) ([hue docs])
|
||||
- Filter IPv6 addreses from enphase_envoy discovery ([@bdraco] - [#68362]) ([enphase_envoy docs])
|
||||
- Handle Hue discovery errors ([@balloob] - [#68392]) ([hue docs])
|
||||
- Fix tplink color temp conversion ([@bdraco] - [#68484]) ([tplink docs])
|
||||
|
||||
[#67018]: https://github.com/home-assistant/core/pull/67018
|
||||
[#67967]: https://github.com/home-assistant/core/pull/67967
|
||||
[#68148]: https://github.com/home-assistant/core/pull/68148
|
||||
[#68153]: https://github.com/home-assistant/core/pull/68153
|
||||
[#68176]: https://github.com/home-assistant/core/pull/68176
|
||||
[#68193]: https://github.com/home-assistant/core/pull/68193
|
||||
[#68235]: https://github.com/home-assistant/core/pull/68235
|
||||
[#68260]: https://github.com/home-assistant/core/pull/68260
|
||||
[#68337]: https://github.com/home-assistant/core/pull/68337
|
||||
[#68362]: https://github.com/home-assistant/core/pull/68362
|
||||
[#68392]: https://github.com/home-assistant/core/pull/68392
|
||||
[#68484]: https://github.com/home-assistant/core/pull/68484
|
||||
[@antlarr]: https://github.com/antlarr
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@cdce8p]: https://github.com/cdce8p
|
||||
[@epenet]: https://github.com/epenet
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@marcelveldt]: https://github.com/marcelveldt
|
||||
[@mib1185]: https://github.com/mib1185
|
||||
[@nprez83]: https://github.com/nprez83
|
||||
[device_tracker docs]: /integrations/device_tracker/
|
||||
[enphase_envoy docs]: /integrations/enphase_envoy/
|
||||
[hue docs]: /integrations/hue/
|
||||
[lyric docs]: /integrations/lyric/
|
||||
[matrix docs]: /integrations/matrix/
|
||||
[opensensemap docs]: /integrations/opensensemap/
|
||||
[point docs]: /integrations/point/
|
||||
[renault docs]: /integrations/renault/
|
||||
[samsungtv docs]: /integrations/samsungtv/
|
||||
[tplink docs]: /integrations/tplink/
|
||||
[velbus docs]: /integrations/velbus/
|
||||
|
||||
## Need help? Join the community!
|
||||
|
||||
Home Assistant has a great community of users who are all more than willing
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user