mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-25 10:17:23 +00:00
Merge branch 'current' into rc
This commit is contained in:
Franck Nijhof
commit
e8215b775a
@ -26,7 +26,7 @@ GEM
|
||||
eventmachine (1.2.7-x64-mingw32)
|
||||
ffi (1.16.2)
|
||||
forwardable-extended (2.6.0)
|
||||
google-protobuf (3.24.3)
|
||||
google-protobuf (3.24.4)
|
||||
http_parser.rb (0.8.0)
|
||||
i18n (1.14.1)
|
||||
concurrent-ruby (~> 1.0)
|
||||
|
||||
@ -25,18 +25,6 @@ type:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
### Example
|
||||
|
||||
Alternatively, the position of the card can be configured using YAML with the `view_layout` option:
|
||||
|
||||
```yaml
|
||||
type: entities
|
||||
entities:
|
||||
- media_player.lounge_room
|
||||
view_layout:
|
||||
position: sidebar
|
||||
```
|
||||
|
||||
## Cards config:
|
||||
|
||||
{% configuration %}
|
||||
@ -45,3 +33,17 @@ view_layout.position:
|
||||
description: "The position of the card, `main` or `sidebar`"
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
### Example
|
||||
|
||||
The position of the card is configured using YAML with the `view_layout` option:
|
||||
|
||||
```yaml
|
||||
type: sidebar
|
||||
cards:
|
||||
- type: entities
|
||||
entities:
|
||||
- media_player.lounge_room
|
||||
view_layout:
|
||||
position: sidebar
|
||||
```
|
||||
|
||||
@ -0,0 +1,4 @@
|
||||
{% capture name %}{{ include.name | default: page.title }}{% endcapture %}
|
||||
{% capture domain %}{{ include.domain | default: page.ha_domain }}{% endcapture %}
|
||||
|
||||
**Building block integration**: The {{ name | downcase }} integration cannot be directly used. You cannot create your own {{ domain }} entities using this integration. This integration is a building block for other integrations to use, enabling them to create {{ domain }} entities for you.
|
||||
@ -229,10 +229,18 @@ 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]`. 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.
|
||||
- Input all information required. Assuming your Home Assistant can be accessed by `https://[YOUR HOME ASSISTANT URL]`. For Alexa account linking, by default, the standard port 443 is used. Use your firewall to forward this, if needed:
|
||||
- `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
|
||||
|
||||
It is also possible to use a different port by appending `:1443` or a similar port number, make sure your firewall is forwarding the correct port:
|
||||
- `Authorization URI`: `https://[YOUR HOME ASSISTANT URL]:1443/auth/authorize`
|
||||
- `Access Token URI`: `https://[YOUR HOME ASSISTANT URL]:1433/auth/token`
|
||||
|
||||
<div class="note">
|
||||
Note: you must use a valid/trusted SSL certificate for account linking to work. Self signed certificates will not work, but you can use a free Let's Encrypt certificate.
|
||||
</div>
|
||||
|
||||
- `Client ID`:
|
||||
- `https://pitangui.amazon.com/` if you are in US
|
||||
- `https://layla.amazon.com/` if you are in EU
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "RFLink Binary Sensor"
|
||||
description: "Instructions on how to integrate RFLink binary sensors into Home Assistant."
|
||||
logo: rflink.png
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: BSB-Lan
|
||||
description: Instructions on how to integrate BSBLan device into Home Assistant.
|
||||
logo: bsblan.png
|
||||
ha_category:
|
||||
- Climate
|
||||
ha_release: '0.110'
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "RFLink Cover"
|
||||
description: "Instructions on how to integrate RFLink Somfy RTS and KAKU ASUN-650 covers into Home Assistant."
|
||||
logo: rflink.png
|
||||
ha_category:
|
||||
- Cover
|
||||
ha_iot_class: Assumed State
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: DSMR Slimme Meter
|
||||
description: Instructions on how to integrate DSMR Smartmeter within Home Assistant.
|
||||
logo: netbeheernederland.jpg
|
||||
ha_category:
|
||||
- Energy
|
||||
ha_release: 0.34
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: EnOcean
|
||||
description: Connect EnOcean devices to Home Assistant
|
||||
logo: enocean.png
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
- Hub
|
||||
|
||||
@ -18,11 +18,11 @@ The EufyLife integration allows you to integrate Eufy smart scales with Home Ass
|
||||
|
||||
## Supported devices
|
||||
|
||||
- [Smart Scale (T9140)](https://www.eufy.com/products/t9140)
|
||||
- [Smart Scale C1 (T9146)](https://www.eufy.com/products/t9146)
|
||||
- [Smart Scale P1 (T9147)](https://www.eufy.com/products/t9147)
|
||||
- [Smart Scale P2 (T9148)](https://www.eufy.com/products/t9148)
|
||||
- [Smart Scale P2 Pro (T9149)](https://www.eufy.com/products/t9149111)
|
||||
- [Smart Scale (T9140)](https://support.eufy.com/s/product/a085g000000Nm5FAAS/smart-scale(t9140))
|
||||
- [Smart Scale C1 (T9146)](https://us.eufy.com/products/t9146)
|
||||
- [Smart Scale P1 (T9147)](https://us.eufy.com/products/t9147)
|
||||
- [Smart Scale P2 (T9148)](https://us.eufy.com/products/t9148)
|
||||
- [Smart Scale P2 Pro (T9149)](https://us.eufy.com/products/t9149111)
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "RFLink Light"
|
||||
description: "Instructions on how to integrate RFLink lights into Home Assistant."
|
||||
logo: rflink.png
|
||||
ha_category:
|
||||
- Light
|
||||
ha_iot_class: Assumed State
|
||||
|
||||
@ -6,7 +6,6 @@ ha_category:
|
||||
- DIY
|
||||
- Sensor
|
||||
- Switch
|
||||
logo: numato.png
|
||||
ha_release: '0.110'
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: numato
|
||||
|
||||
@ -273,6 +273,7 @@ Then power up the camera while pointing it at the QR code. It takes about a minu
|
||||
- Setting a static IP address for Reolink cameras/NVRs in your router is advisable to prevent (temporal) connectivity issues when the IP address changes.
|
||||
- Do not set a static IP in the Reolink device itself, but leave the **Connection Type** on **DHCP** under **Settings** > **Network** > **Network Information** > **Set Up**. If you set it to **static** on the Reolink device itself, this is known to cause incorrect DHCP requests on the network. The incorrect DHCP request causes Home Assistant to use the wrong IP address for the camera, resulting in connection issues. The issue originates from the Reolink firmware, which keeps sending DCHP requests even when you set a static IP address in the Reolink device.
|
||||
- Reolink cameras can support a limited amount of simultaneous connections. Therefore using third-party software like Frigate, Blue Iris, or Scrypted, or using the ONVIF integration at the same time can cause the camera to drop connections. This results in short unavailabilities of the Reolink entities in Home Assistant. Especially when the connections are coming from the same device (IP) where Home Assistant is running, the Reolink cameras can get confused, dropping one connection in favor of the other originating from the same host IP. If you experience disconnections/unavailabilities of the entities, please first temporarily shut down the other connections (like Frigate) to diagnose if that is the problem. If that is indeed the problem, you could try moving the third-party software to a different host (IP address) since that is known to solve the problem most of the time. You could also try switching the protocol to FLV on Home Assistant and/or the third-party software, as that is known to be less resource-intensive on the camera.
|
||||
- If the integration and the browser can't connect to the camera even after you enable the HTTP/HTTPS ports, try to create a new user on the camera; that fixes the problem in some cases.
|
||||
|
||||
### Reducing latency of motion events
|
||||
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "RFLink Sensor"
|
||||
description: "Instructions on how to integrate RFLink sensors into Home Assistant."
|
||||
logo: rflink.png
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_iot_class: Local Push
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: "RFLink Switch"
|
||||
description: "Instructions on how to integrate RFLink switches into Home Assistant."
|
||||
logo: rflink.png
|
||||
ha_category:
|
||||
- Switch
|
||||
ha_iot_class: Assumed State
|
||||
|
||||
@ -1,6 +1,5 @@
|
||||
---
|
||||
title: Wiffi
|
||||
logo: wiffi.png
|
||||
description: Support for WIFFI devices from stall.biz, e.g., Weatherman, Rainyman, ...
|
||||
ha_category:
|
||||
- DIY
|
||||
|
||||
@ -2325,7 +2325,7 @@ frontpage_image: /images/frontpage/green-frontpage.png
|
||||
</a>
|
||||
|
||||
<a
|
||||
href="https://shop.everythingsmart.io/en-de/products/home-assistant-green"
|
||||
href="https://shop.everythingsmart.io/products/home-assistant-green"
|
||||
target="_blank"
|
||||
>
|
||||
<div class="distributor">
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user