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-18 23:06:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2023-10-03 20:32:54 +02:00
commit 5b2ea315c5
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
32 changed files with 151 additions and 61 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Gemfile.lock
View File

@ -114,7 +114,7 @@ GEM
concurrent-ruby (~> 1.0)
tzinfo-data (1.2023.3)
tzinfo (>= 1.0.0)
unicode-display_width (2.4.2)
unicode-display_width (2.5.0)
webrick (1.8.1)
PLATFORMS

2
sass/custom/_paulus.scss
View File

@ -934,6 +934,8 @@ code {
a.my {
img {
border: 0px;
border-radius: 0;
box-shadow: none;
}
}

8
source/_docs/locked_out.md
View File

@ -1,12 +1,12 @@
---
title: "I'm Locked Out!"
title: "I'm locked out!"
description: "Options for regaining access"
---
The sections below deal with recovering from a situation where you are not able to sign in,
or need to recover your data.
## Forgot Password
## Forgot password
### Home Assistant (including Supervised)
@ -30,7 +30,9 @@ Use this procedure if you know the username, and you can access the [Home Assist
- If you are using a Home Assistant Green, refer to the following procedure:
- [Using the terminal](https://green.home-assistant.io/guides/use-terminal/)
2. Once you have opened the Home Assistant command line, enter the following command:
`auth reset --username existing_user --password new_password`
- Note: `existing_user` is a placeholder. Replace it with your user name.
- Note: `new_password` is a placeholder. Replace it with your new password.
- **Command**: `auth reset --username existing_user --password new_password`
3. You can now log in to Home Assistant using this new password.
#### To reset a user's password, via the container command line

3
source/_includes/common-tasks/backups.md
View File

@ -85,12 +85,13 @@ You can use a backup during the onboarding process to restore your configuration
- This procedure assumes you have already completed the [installation](/installation/) procedure on your target device and are now viewing the welcome screen as part of the [onboarding](/getting-started/onboarding/).
- The login credentials of the device from which you made the backup.
- If you migrate the installation to a new device, make sure the new device has more storage capacity than the existing device.
- **Required storage capacity**: If you migrate the installation to a new device, make sure the new device has more storage capacity than the existing device.
- Before migrating, on the old system, check how much storage you used.
- Go to **{% my system_health title="Settings > System > Repairs -> ... -> System Information" %}**, and under **Home Assistant Supervisor**, look at the **Disk used** value.
- The target device must have more free space than the source device.
- If your target device is a Home Assistant Yellow, note that it is the size of the eMMC that is relevant.
- The restore process mainly uses the eMMC, not the NVMe.
- The size of the backup file is no indication of the size of your installation. To know the size of your installation, you need to check the **Disk used** value mentioned above.
- If you are migrating to a new device:
- You do not need to transfer the backup to a USB or SD card to bring it to your device.
- You will be able to upload the backup file from the device you are accessing the onboarding from.

4
source/_integrations/fan.mqtt.markdown
View File

@ -223,12 +223,12 @@ payload_oscillation_on:
type: string
default: oscillate_on
payload_reset_percentage:
description: A special payload that resets the `percentage` state attribute to `None` when received at the `percentage_state_topic`.
description: A special payload that resets the `percentage` state attribute to `unknown` when received at the `percentage_state_topic`.
required: false
type: string
default: 'None'
payload_reset_preset_mode:
description: A special payload that resets the `preset_mode` state attribute to `None` when received at the `preset_mode_state_topic`.
description: A special payload that resets the `preset_mode` state attribute to `unknown` when received at the `preset_mode_state_topic`.
required: false
type: string
default: 'None'

2
source/_integrations/flume.markdown
View File

@ -19,7 +19,7 @@ ha_platforms:
ha_integration_type: integration
---
The `flume` sensor will show you the current [flume](https://portal.flumewater.com) status for the given Device ID.
The Flume integration will show you the current [Flume](https://flumewater.com/) status for the given Device ID.
Flume monitors the real-time status of your home water meter. Allowing the end-user to detect small leaks, gain real-time information on household water consumption, set water goals and budgets, and receive push notifications when suspicious water activities occur.

2
source/_integrations/generic.markdown
View File

@ -63,7 +63,7 @@ In this section, you find some real-life examples of how to use this camera plat
- Still Image URL: `https://www.yr.no/en/content/1-72837/meteogram.svg`
Instructions on how to locate the SVG for your location are available at [developer.yr.no](https://developer.yr.no/doc/guides/deprecating-old-widgets/)
Instructions on how to locate the SVG for your location are available at [developer.yr.no](https://developer.yr.no/doc/guides/available-widgets/)
### Local image

5
source/_integrations/google_mail.markdown
View File

@ -122,3 +122,8 @@ data:
- "example4@gmail.com"
from: "example@gmail.com"
```
### Video Tutorial
This video tutorial explains how to set up Gmail in Home Assistant and how you can create a dashboard and automations to send e-mail and toggle your out-of-office notice.
<lite-youtube videoid="IHKliqSFZvM" videotitle="How To send e-mail PERFECTLY using Gmail in Home Assistant - Tutorial" posterquality="maxresdefault"></lite-youtube>

2
source/_integrations/heos.markdown
View File

@ -15,7 +15,7 @@ ha_platforms:
ha_integration_type: integration
---
The HEOS integration adds support for [HEOS](https://www.denon.com/en-gb/shop/amplifiersmrs/heosavr) capable products, such as speakers, amps, and receivers (Denon and Marantz) into Home Assistant. Features currently include:
The HEOS integration adds support for [HEOS](https://www.denon.com/en-gb/category/heos/) capable products, such as speakers, amps, and receivers (Denon and Marantz) into Home Assistant. Features currently include:
- Each device is represented as a media player entity
- View the currently playing media

4
source/_integrations/humidifier.mqtt.markdown
View File

@ -215,12 +215,12 @@ payload_on:
type: string
default: "ON"
payload_reset_humidity:
description: A special payload that resets the `target_humidity` state attribute to `None` when received at the `target_humidity_state_topic`.
description: A special payload that resets the `target_humidity` state attribute to an `unknown` state when received at the `target_humidity_state_topic`. When received at `current_humidity_topic` it will reset the current humidity state.
required: false
type: string
default: 'None'
payload_reset_mode:
description: A special payload that resets the `mode` state attribute to `None` when received at the `mode_state_topic`. When received at `current_humidity_topic` it will reset the current humidity state.
description: A special payload that resets the `mode` state attribute to an `unknown` state when received at the `mode_state_topic`.
required: false
type: string
default: 'None'

22
source/_integrations/imap.markdown
View File

@ -20,17 +20,27 @@ The IMAP integration is observing your [IMAP server](https://en.wikipedia.org/wi
### Gmail with App Password
If you’re going to use Gmail, you need to create an [App Password](https://support.google.com/mail/answer/185833).
If you’re going to use Gmail, 2-step verification must be enabled on your Gmail account. Once it is enabled, you need to create an [App Password](https://support.google.com/mail/answer/185833).
1. Go to your [Google Account](https://myaccount.google.com/)
2. Select **Security**
3. Under “Signing in to Google” select **App Passwords**
4. Sign in to your Account, and create a new App Password for Gmail.
5. Then you can setup the intergation as below:
3. Under “How you sign into Google” select **2-Step Verification**.
4. Sign in to your Account.
5. At the bottom of the 2-Step Verification page, click **App Passwords**.
6. Give your app a name that makes sense to you (Home Assistant IMAP, for example).
7. Click **Create**, then make a note of your 16-character app password for safekeeping (remove the spaces when you save it).
8. Click **Done**.
9. Add the IMAP Integration to your Home Assistant instance using the My button above. Enter the following information as needed:
- Username: Your Gmail email login
- Password: your 16-character app password (without the spaces)
- Server: `imap.gmail.com`
- Port: `993`
- Username: Your full email address
- Password: The new app password
10. Click **Submit**.
11. Assign your integration to an "Area" if desired, then click **Finish**.
Congratulations, you now have a sensor that counts the number of unread e-mails in your Gmail account. From here you can create additional sensors based upon the data that comes through the event bus when there's a new message detected.
### Configuring IMAP Searches

2
source/_integrations/keba.markdown
View File

@ -19,7 +19,7 @@ ha_platforms:
ha_integration_type: integration
---
The `keba` integrates your Keba charging station/BMW Wallbox into your Home Assistant instance using the UDP Smart Home Interface ([manual](https://www.keba.com/web/downloads/e-mobility/KeContact_P20_P30_UDP_ProgrGuide_en.pdf)). The fetching interval to the charging station is set to 5 seconds, same as in the official mobile app. In order to use the integration, enable the UDP Smart Home Interface by adjusting the DIP switches within the charging station according to the [installation manual](https://www.keba.com/file/downloads/e-mobility/KeContact_KCP20_30_ih_en.pdf).
The `keba` integrates your Keba charging station/BMW Wallbox into your Home Assistant instance using the UDP Smart Home Interface ([manual](https://www.ifix-solar.shop/wp-content/uploads/shop/Dokumente/KEBA/KeContact_P20_P30_UDP_ProgrGuide_en.pdf)). The fetching interval to the charging station is set to 5 seconds, same as in the official mobile app. In order to use the integration, enable the UDP Smart Home Interface by adjusting the DIP switches within the charging station according to the [installation manual](https://www.keba.com/file/downloads/e-mobility/KeContact_KCP20_30_ih_en.pdf).
This integration provides the following platforms:

8
source/_integrations/knx.markdown
View File

@ -823,6 +823,8 @@ The KNX cover platform is used as an interface to KNX covers.
Unlike most KNX devices, Home Assistant defines 0% as closed and 100% as fully open in regards to covers. The corresponding value inversion is done internally by the KNX integration.
Home Assistant will, by default, `close` a cover by moving it in the `DOWN` direction in the KNX nomenclature, and `open` a cover by moving it in the `UP` direction.
</div>
To use your KNX covers in your installation, add the following lines to your top level [KNX Integration](/integrations/knx) configuration key in `configuration.yaml`:
@ -852,7 +854,7 @@ move_long_address:
required: false
type: [string, list]
move_short_address:
description: KNX group address for moving the cover stepwise up or down. Used by some covers also as the means to stop the cover, if no dedicated `stop_address` exists on the actuator. *DPT 1*
description: KNX group address for moving the cover stepwise up or down. Used by some covers also as the means to stop the cover. Stepwise moves are only mapped to tilt angle functions in Home Assistant, as no stepwise move of cover position is generally supported by the architecture. If tilt angle is not supported, prefer the use of a `stop_address`. *DPT 1*
required: false
type: [string, list]
stop_address:
@ -886,12 +888,12 @@ travelling_time_up:
default: 25
type: integer
invert_updown:
description: Set this to `true` to invert the binary up/down commands from/to your KNX actuator. Default is 0 for UP; 1 for DOWN.
description: Set this to `true` to invert the up/down commands from/to your KNX actuator. Default is to consider `UP` (0) as opening of a cover and `DOWN` (1) as closing of a cover.
required: false
default: false
type: boolean
invert_position:
description: Set this to `true` if your actuator reports fully closed position as 0% in KNX.
description: Set this to `true` if your actuator reports fully down position as 0% in KNX.
required: false
default: false
type: boolean

2
source/_integrations/locative.md
View File

@ -8,7 +8,7 @@ ha_iot_class: Cloud Push
ha_domain: locative
---
This platform allows you to detect presence using [Locative](https://www.locative.io/). Locative is an open source app for [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location.
This platform allows you to detect presence using [Locative](https://www.locative.app/). Locative is an open source app for [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location.
Install on your smartphone:

5
source/_integrations/lyric.markdown
View File

@ -22,12 +22,13 @@ The Honeywell Lyric integration integrates the Lyric thermostat platform into Ho
## Setup
To set up this integration, you first **must** set up a developer account with Honeywell:
To set up this integration, you first **must** set up a developer account with Honeywell using the same email address as your Resideo account:
1. Go to the [developer site](https://developer.honeywellhome.com) and register with an account.
2. Next, create a [new app](https://developer.honeywellhome.com/user/me/apps/add) via the `My Apps` section.
1. App Name: You can use any name here, but it must not contain special characters.
2. Callback URL: `https://my.home-assistant.io/redirect/oauth`
3. The app will be approved automatically. To view the **Consumer Key** and **Consumer Secret** values, select the name of the app. Copy the values, you will need them later.
{% details "I have manually disabled My Home Assistant" %}
@ -46,7 +47,7 @@ You can then add the integration in the frontend via the steps below.
{% include integrations/config_flow.md %}
The integration configuration will ask for the *Client ID* and *Client Secret* created above. See [Application Credentials](/integrations/application_credentials) for more details.
The integration configuration will ask for the **Client ID** and **Client Secret**, which correspond to the **Consumer** values in the app you created above. See [Application Credentials](/integrations/application_credentials) for more details.
## Sensors

2
source/_integrations/modbus.markdown
View File

@ -24,7 +24,7 @@ ha_integration_type: integration
[modbus](http://www.modbus.org/) is a communication protocol to control PLCs (Programmable Logic Controller) and RTUs (Remote Terminal Unit).
The integration adheres strictly to the [protocol specification](https://modbus.org/docs/modbus_Application_Protocol_V1_1b3.pdf) using [pymodbus](https://github.com/pymodbus-dev/pymodbus) for the actual protocol implmentation.
The integration adheres strictly to the [protocol specification](https://www.modbus.org/docs/Modbus_Application_Protocol_V1_1b3.pdf) using [pymodbus](https://github.com/pymodbus-dev/pymodbus) for the actual protocol implmentation.
The modbus integration supports all devices adhering to the modbus standard. The communication to the device/devices can be serial (rs-485), TCP, or UDP connections. The modbus integration allows multiple communication channels e.g. a serial port connection combined with one or more TCP connections.

2
source/_integrations/mvglive.markdown
View File

@ -27,7 +27,7 @@ sensor:
{% configuration %}
station:
description: Name of the stop or station. Visit [the MVG live web site](https://www.mvg-live.de/ims/dfiStaticAuswahl.svc) to find valid names. Be aware, that not all data of interest might be available (i.e., bus departure-times in Haar).
description: Name of the stop or station. Visit [the MVG live web site](https://www.mvg.de/meinhalt.html) to find valid names. Be aware, that not all data of interest might be available (i.e., bus departure-times in Haar).
required: true
type: string
destinations:

2
source/_integrations/nest.markdown
View File

@ -466,6 +466,8 @@ Once you have completed the above steps, you can continue through the flow to re
## Troubleshooting
- *No access to partner information* "Information could not be retrieved" error message during the setup wizard means that the Google Account used is not able to access the Home. Please ensure that you have successfully migrated your Nest Account to a Google Account using the Google Nest App. Additionally, if your home has multiple members, please note that the individual who initially set up the home must complete the migration of their Nest Account to a Google Account before you can establish a connection with Home Assistant.
- You can manage devices and permissions granted to Home Assistant in the Nest [Partner Connections Manager](https://nestservices.google.com/partnerconnections). Restart Home Assistant to make new devices available. See the [SDM API Troubleshooting](https://developers.google.com/nest/device-access/authorize#modify_account_permissions) documentation for more details.
- *Error 400: invalid_request* plus a message about not complying with *Google's OAuth Policy for keeping accounts secure* is shown when using *App Auth* or *Desktop Auth* or *OOB Auth* which has been [deprecated](https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html) by Google. Follow the steps in the previous section to upgrade Home Assistant and restore access.

2
source/_integrations/number.mqtt.markdown
View File

@ -167,7 +167,7 @@ optimistic:
type: boolean
default: "`true` if no `state_topic` defined, else `false`."
payload_reset:
description: A special payload that resets the state to `None` when received on the `state_topic`.
description: A special payload that resets the state to `unknown` when received on the `state_topic`.
required: false
type: string
default: '"None"'

2
source/_integrations/pilight.markdown
View File

@ -152,7 +152,7 @@ binary_sensor:
This `pilight` sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g., _uuid_) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight Home Assistant hub has to be set up.
To use your sensor via pilight, make sure it is [supported](https://wiki.pilight.org/protocols) and add the following to your `configuration.yaml` file:
To use your sensor via pilight, make sure it is [supported](https://manual.pilight.org/protocols/index.html) and add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry

2
source/_integrations/plugwise.markdown
View File

@ -29,7 +29,7 @@ ha_integration_type: hub
---
This enables [Plugwise](https://www.plugwise.com) integrations with a central Smile gateway to be integrated. This integration talks locally to your **Smile** interface, and you will need its password and IP address.
The platform supports [Anna](https://www.plugwise.com/en_US/products/anna), [Adam (zonecontrol)](https://www.plugwise.com/en_US/zonecontrol), [P1](https://www.plugwise.com/en_US/products/smile-p1) Smile products and the [Stretch](https://www.plugwise.com/nl_NL/het-systeem) products. See below list for more details.
The platform supports [Anna](https://www.plugwise.com/en_US/products/anna), [Adam (zonecontrol)](https://www.plugwise.com/en_US/zonecontrol), [P1](https://www.plugwise.com/en_US/products/smile-p1) Smile products and the Stretch products (not in sale). See below list for more details.
Platforms available - depending on your Smile and setup include:

4
source/_integrations/select.markdown
View File

@ -17,8 +17,8 @@ a limited set of selectable options for the entity.
## Services
The select entity exposes additional to control the entity in, for example,
automation or scripts. These service can be created via the UI, but are
The select entity exposes additional services to control the entity in, for example,
automation or scripts. These services can be created via the UI, but are
also available in YAML (for which examples are provided below).
### Service `select.select_first`

14
source/_integrations/shelly.markdown
View File

@ -262,16 +262,16 @@ The firmware limits the transition time to 5 seconds.
The integration offers device services which can be triggered by a configuration button.
### OTA update
### OTA firmware update
Trigger device OTA firmware update.
#### Buttons
#### Update entities
- OTA Update
- triggers the OTA update process for latest stable version
- OTA Update Beta (_disabled by default_)
- triggers the OTA update process for latest beta version
- Firmware update
- triggers the OTA firmware update process to the latest stable version
- Beta firmware update (_disabled by default_)
- triggers the OTA firmware update process to the latest beta version
### Reboot
@ -324,5 +324,5 @@ Please check from the device Web UI that the configured server is reachable.
- Only supports firmware 0.8 and later for generation 2 devices
- Generation 1 "Shelly 4Pro" and "Shelly Sense" are not supported (devices based on old CoAP v1 protocol)
- Before set up, battery-powered devices must be woken up by pressing the button on the device.
- OTA update service does not support battery-powered devices
- For battery-powered devices, the `update` platform entities only inform about the availability of firmware updates but are not able to trigger the update process.
- Frequency sensors for generation 2 energy monitoring devices are supported by firmware 1.0.0 beta 6 or later.

13
source/_integrations/upb.markdown
View File

@ -230,3 +230,16 @@ kitchen_fade_on:
## Notes
- A UPB device does not always report its current state. For example, if you call `upb.light_fade_start` and then, a few seconds later, call `upb.light_fade_stop`, the selected UPB device will not report its new brightness level. However, if you then call `homeassistant.update_entity` it will make the UPB device report its current state to Home Assistant.
- Alterations to your UPB configuration with UpStart must be re-exported. The exported UPE file must have the same filename in the Home Assistant `config` directory.
## Debugging
Debug logs are often required to solve an issue. To enable UPB debug logs add the following to your `configuration.yaml` file in your Home Assistant `config` directory:
```yaml
logger:
logs:
upb_lib: debug
homeassistant.components.upb: debug
```
After updating your configuration file, restart Home Assistant. The debug logs will be in the file `homeassistant.log` in the `config` directory.

2
source/_integrations/vallox.markdown
View File

@ -40,7 +40,7 @@ For convenient switching of ventilation profiles in the GUI, just click on the `
The four standard Vallox profiles are supported:
- `At Home`
- `Home`
- `Away`
- `Boost`
- `Fireplace`

2
source/_integrations/volvooncall.markdown
View File

@ -18,7 +18,7 @@ ha_integration_type: integration
ha_config_flow: true
---
The `volvooncall` integration offers integration with the [Volvo On Call](https://www.volvocars.com/intl/why-volvo/human-innovation/future-of-driving/connectivity/volvo-on-call) cloud service and offers presence detection as well as sensors such as odometer and fuel level.
The `volvooncall` integration offers integration with the [Volvo Cars App](https://www.volvocars.com/intl/v/volvo-cars-app) (former Volvo On Call) cloud service and offers presence detection as well as sensors such as odometer and fuel level.
{% include integrations/config_flow.md %}

2
source/_integrations/webostv.markdown
View File

@ -24,7 +24,7 @@ The `webostv` platform allows you to control a [LG](https://www.lg.com/) webOS S
There is currently support for the following device types within Home Assistant:
- [Media Player](/integrations/media_player/)
- [Notifications](/integrations/notification/)
- [Notifications](/integrations/notify/)
To begin with enable *LG Connect Apps* feature in *Network* settings of the TV.

4
source/_integrations/zha.markdown
View File

@ -108,7 +108,7 @@ Some other Zigbee coordinator hardware may not support a firmware that is capabl
- Silicon Labs EmberZNet based radios using legacy hardware using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy)
- [ITead Sonoff ZBBridge](https://itead.cc/product/sonoff-zbbridge/) (Note! [WiFi-based bridges are not recommended for ZHA with EZSP radios](https://github.com/home-assistant/home-assistant.io/issues/17170). Also, this first has to be flashed with [Tasmota firmware and Silabs EmberZNet NCP EZSP UART Host firmware to use as Serial-to-IP adapter](https://www.digiblur.com/2020/07/how-to-use-sonoff-zigbee-bridge-with.html))
- [Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee Ember 3581 USB Adapter)](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) (Note! Not a must but recommend [upgrade the EmberZNet NCP application firmware](https://github.com/walthowd/husbzb-firmware))
- [Bitron Video/Smabit BV AV2010/10 USB-Stick](https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/) with Silicon Labs Ember 3587
- [Bitron Video/Smabit BV AV2010/10 USB-Stick](https://manuals.smabit.eu/len/av2010_10.html) with Silicon Labs Ember 3587
- Telegesis ETRX357USB/ETRX357USB-LR/ETRX357USB-LRS+8M (Note! These first have to be [flashed with other EmberZNet firmware](https://github.com/walthowd/husbzb-firmware))
- Texas Instruments based radios using legacy hardware (via the [zigpy-znp](https://github.com/zigpy/zigpy-znp) library for zigpy)
- [CC2538 USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/information/supported_adapters) (no longer recommended as only got deprecated old end-of-life firmware)
@ -195,7 +195,7 @@ Some devices can be auto-discovered, which can simplify the ZHA setup process. T
| ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | ------------------------------ |
| [ITead SONOFF Zigbee 3.0 USB Dongle Plus V2 Model "ZBDongle-E" (EFR32MG21 variant)](https://itead.cc/product/zigbee-3-0-usb-dongle/) | USB | 1A86:55D4 |
| [ITead SONOFF Zigbee 3.0 USB Dongle Plus Model "ZBDongle-P" (CC2652P variant)](https://itead.cc/product/sonoff-zigbee-3-0-usb-dongle-plus/) | USB | 10C4:EA60 |
| [Bitron Video/SMaBiT BV AV2010/10](https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/) | USB | 10C4:8B34 |
| [Bitron Video/SMaBiT BV AV2010/10](https://manuals.smabit.eu/len/av2010_10.html) | USB | 10C4:8B34 |
| [ConBee II](https://phoscon.de/conbee2) | USB | 1CF1:0030 |
| [Nortek HUSBZB-1](https://www.nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) | USB | 10C4:8A2A |
| [slae.sh CC2652RB development stick](https://slae.sh/projects/cc2652/) | USB | 10C4:EA60 |

9
source/_posts/2023-09-17-home-assistant-green-your-entry-to-home-assistant.markdown
View File

@ -25,11 +25,10 @@ Home Assistant Green contains everything you need for Home Assistant in one box.
Home Assistant Green alongside Home Assistant Yellow and Home Assistant Blue
</p>
On the inside, Home Assistant Green runs on a powerful 1.8 GHz quad-core CPU. Memory and storage are amply provided with 4 GB of RAM and 32 GB of eMMC, more than enough to keep you running Home Assistant on the device for a long time. When your smart home grows, you can use <a href="/skyconnect">Home Assistant SkyConnect</a> to add Zigbee and Matter support or one of many third-party USB devices available to expand Home Assistant Green with other smart standards like Z-Wave or Bluetooth.
On the inside, Home Assistant Green runs on a powerful 1.8&nbsp;GHz quad-core CPU. Memory and storage are amply provided with 4&nbsp;GB of RAM and 32&nbsp;GB of eMMC, more than enough to keep you running Home Assistant on the device for a long time. Connecting to your existing smart home platforms lets you instantly use your devices that communicate over Zigbee, Matter, or other smart standards. And when your smart home grows, you can use <a href="/skyconnect">Home Assistant SkyConnect</a> to add Zigbee and Thread radios (Thread support under development) or one of many third-party USB devices available to expand Home Assistant Green with other smart standards like Z-Wave or Bluetooth.
On the outside, Home Assistant Green has a stunning translucent enclosure design revealing the hub's inner hardware. Unlike some other smart home devices, it looks great in your home decor. The bottom of the case also functions as the hub's heat sink and is made of a solid piece of black, anodized aluminum. And, of course, this case features [the new Home Assistant logo][logo-blog] on top as a nice subtle mosaic pattern.
<p class='img'>
<img src="/images/blog/2023-09-ha10/green-specs.jpeg" alt="Home Assistant Green has 1.8 GHz quad-code CPU, 4 GB of RAM and 32 GB of eMMC storage.">
Home Assistant Green specifications
@ -43,11 +42,9 @@ For more information about Home Assistant Green, [visit our product page](/green
<br>
To celebrate [the 10th anniversary of Home Assistant][10ha-blog], we are making an anniversary batch of 1000 Home Assistant Green hubs available for sale via our partner Seeed Studio. You can order your Home Assistant Green right now:
To celebrate [the 10th anniversary of Home Assistant][10ha-blog], we made an anniversary batch of 1000 Home Assistant Green hubs available. This batch has sold out, but Home Assistant Green will become widely available through our existing distributor network starting in November. You can pre-order your Home Assistant Green at our product page:
<a href="https://www.seeedstudio.com/Home-Assistant-Green-p-5792.html" class="btn">Order at Seeed Studio</a>
If this anniversary batch sells out before you can get one, don't worry! At the end of October, the Home Assistant Green will become widely available through our existing distributor network. Keep an eye on the <a href="/green">Home Assistant Green</a> website for availability!
<a href="/green" class="btn">Home Assistant Green</a>
[logo-blog]: /blog/2023/09/17/a-refreshed-logo-for-home-assistant/
[10ha-blog]: /blog/2023/09/17/10-years-home-assistant/

6
source/_posts/2023-09-22-philips-hue-force-users-upload-data-to-cloud.markdown
View File

@ -1,5 +1,5 @@
---
title: "Philips Hue will force users to upload their data to Hue cloud"
title: "[Update Oct 2: data sharing to become optional] Philips Hue will force users to upload their data to Hue cloud"
description: "To control your lights you soon need to create an account and share your data with the Hue cloud."
date: 2023-09-22 0:0:00
date_formatted: "September 22, 2023"
@ -10,6 +10,10 @@ categories: Public-Service-Announcement
og_image: /images/blog/2023-09-hue-upload-user-data-cloud/social.png
---
**Update Oct 2:** In a [conversation with The Verge](https://www.theverge.com/2023/9/28/23892761/philips-hue-app-account-changes), Philips Hue has announced that they will update their privacy policy to require users to consent to share their usage data with Philips Hue.
_Original Post_
Today’s story is about Philips Hue by Signify. They will soon start forcing accounts on all users and upload user data to their cloud. For now, Signify says you’ll still be able to control your Hue lights locally as you’re currently used to, but we don’t know if this may change in the future. The privacy policy allows them to store the data and share it with partners.
Last week I wrote how toying with the first Philips Hue hub and their local API led me to [start Home Assistant back in 2013](/blog/2023/09/17/10-years-home-assistant/). They have played an important role in my smart home and they were a role model for [our Open Home vision](/blog/2021/12/23/the-open-home/). Sure, they are expensive but they work reliably, have a local API, can be used completely offline, and you don’t have to share your data with the cloud.

4
source/developers/cla_sign.html
View File

@ -437,7 +437,7 @@ description: "The Home Assistant contributor license agreement (CLA) signature p
if (codeCheck && codeCheck.length > 0) {
$.ajax({
type: "POST",
url: "https://cla.home-assistant.io/github/exchange",
url: "https://service-hub-bots.home-assistant.io/cla-sign/authorize",
data: JSON.stringify({"code": codeCheck}),
contentType: "application/json",
}).done(function(data){
@ -446,7 +446,7 @@ description: "The Home Assistant contributor license agreement (CLA) signature p
var clean_uri = uri.substring(0, uri.indexOf("?"));
window.history.replaceState({}, document.title, clean_uri);
}
localStorage.setItem("gh_token", data.token);
localStorage.setItem("gh_token", data.access_token);
fill_fields();
});
} else if (localStorage.getItem("gh_token") != null) {

67
source/green/index.html
View File

@ -1008,10 +1008,8 @@ frontpage_image: /images/frontpage/green-frontpage.png
Expand compatibility as your home expands.
</h3>
<p>
You can add Home Assistant SkyConnect* for Zigbee and
Matter-over-Thread, set up Home Assistant Cloud for voice
assistants, and integrate third-party USB accessories to support
other smart standards such as Z-Wave.
You can add Home Assistant SkyConnect to connect Zigbee and Thread* devices, set up Home Assistant Cloud for voice assistants, and integrate third-party USB accessories to support other smart standards, such as Z-Wave or Bluetooth.
<br>*Thread support is currently under development.
</p>
<a
href="/skyconnect"
@ -2195,11 +2193,10 @@ frontpage_image: /images/frontpage/green-frontpage.png
></a>
<div class="faq-container margin-bottom-small">
<p class="main-paragraph-w">
No, Home Assistant Green works out of the box, but it does not
have a Zigbee radio.<br /><br />If you want to use a Zigbee and/or
Matter-over-Thread network, Home Assistant SkyConnect can provide
that.
If you want to connect Home Assistant Green to the hub of your existing smart home system that uses Zigbee or Thread to communicate, you can do so out-of-the-box for most popular brands. This will be the easiest way to connect your existing Zigbee or Matter devices and does not require a Home Assistant SkyConnect.
</p>
<p>You need a Home Assistant SkyConnect if you want to connect Zigbee or Thread* devices directly to Home Assistant Green.</p>
<p>* Thread support is currently under development.</p>
</div>
</div>
<div class="faq-wrapper">
@ -2327,6 +2324,24 @@ frontpage_image: /images/frontpage/green-frontpage.png
</div>
</a>
<a
href="https://shop.everythingsmart.io/en-de/products/home-assistant-green"
target="_blank"
>
<div class="distributor">
<div>
<div>🇬🇧</div>
<div>Everything Smart Technology</div>
<div>Located in the United Kingdom</div>
</div>
<svg width="24" height="24" viewBox="0 0 24 24">
<path
d="M8.59,16.58L13.17,12L8.59,7.41L10,6L16,12L10,18L8.59,16.58Z"
/>
</svg>
</div>
</a>
<a
href="https://en.m.nu/controllers-smart-hubs/home-assistant-green"
target="_blank"
@ -2381,6 +2396,42 @@ frontpage_image: /images/frontpage/green-frontpage.png
</div>
</a>
<a
href="https://smarterhome.sk/controllers/home-assistant-green-smart-home-hub-1490.html"
target="_blank"
>
<div class="distributor">
<div>
<div>🇸🇰</div>
<div>SmarterHOME</div>
<div>Located in Slovakia</div>
</div>
<svg width="24" height="24" viewBox="0 0 24 24">
<path
d="M8.59,16.58L13.17,12L8.59,7.41L10,6L16,12L10,18L8.59,16.58Z"
/>
</svg>
</div>
</a>
<a
href="https://shop.swiss-domotique.ch/smarthome-hub/2295-nabu-casa-home-assistant-green.html"
target="_blank"
>
<div class="distributor">
<div>
<div>🇨🇭</div>
<div>Swiss-Domotique</div>
<div>Located in Switzerland</div>
</div>
<svg width="24" height="24" viewBox="0 0 24 24">
<path
d="M8.59,16.58L13.17,12L8.59,7.41L10,6L16,12L10,18L8.59,16.58Z"
/>
</svg>
</div>
</a>
</div>
</div>
</div>