mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-07 17:36:50 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
0cb4fe10c4
2
Gemfile
2
Gemfile
@ -11,7 +11,7 @@ group :development do
|
||||
# > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
|
||||
gem 'sassc', '2.1.0'
|
||||
gem 'sass-embedded', '1.81.0'
|
||||
gem 'rubocop', '1.68.0'
|
||||
gem 'rubocop', '1.69.0'
|
||||
gem 'ruby-lsp', '0.22.1'
|
||||
gem 'rackup', '2.2.1'
|
||||
end
|
||||
|
||||
10
Gemfile.lock
10
Gemfile.lock
@ -113,16 +113,16 @@ GEM
|
||||
regexp_parser (2.9.2)
|
||||
rexml (3.3.9)
|
||||
rouge (4.5.1)
|
||||
rubocop (1.68.0)
|
||||
rubocop (1.69.0)
|
||||
json (~> 2.3)
|
||||
language_server-protocol (>= 3.17.0)
|
||||
parallel (~> 1.10)
|
||||
parser (>= 3.3.0.2)
|
||||
rainbow (>= 2.2.2, < 4.0)
|
||||
regexp_parser (>= 2.4, < 3.0)
|
||||
rubocop-ast (>= 1.32.2, < 2.0)
|
||||
rubocop-ast (>= 1.36.1, < 2.0)
|
||||
ruby-progressbar (~> 1.7)
|
||||
unicode-display_width (>= 2.4.0, < 3.0)
|
||||
unicode-display_width (>= 2.4.0, < 4.0)
|
||||
rubocop-ast (1.36.1)
|
||||
parser (>= 3.3.1.0)
|
||||
ruby-lsp (0.22.1)
|
||||
@ -151,7 +151,7 @@ GEM
|
||||
rack-protection (= 4.1.1)
|
||||
rack-session (>= 2.0.0, < 3)
|
||||
tilt (~> 2.0)
|
||||
sorbet-runtime (0.5.11663)
|
||||
sorbet-runtime (0.5.11668)
|
||||
stringex (2.8.6)
|
||||
terminal-table (3.0.2)
|
||||
unicode-display_width (>= 1.1.1, < 3)
|
||||
@ -177,7 +177,7 @@ DEPENDENCIES
|
||||
nokogiri (= 1.16.7)
|
||||
rackup (= 2.2.1)
|
||||
rake (= 13.2.1)
|
||||
rubocop (= 1.68.0)
|
||||
rubocop (= 1.69.0)
|
||||
ruby-lsp (= 0.22.1)
|
||||
sass-embedded (= 1.81.0)
|
||||
sass-globbing (= 1.1.5)
|
||||
|
||||
@ -34,6 +34,11 @@ The **devolo Home Network** {% term integration %} integration allows you to mon
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
{% configuration_basic %}
|
||||
IP address:
|
||||
description: "IP address of your devolo Home Network device. This can be found in the devolo Home Network App on the device dashboard."
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
## Device types
|
||||
|
||||
Currently the following device types within Home Assistant are supported.
|
||||
@ -115,6 +120,19 @@ Since firmware 7.10 also the following device without Wi-Fi can be used as long
|
||||
- Magic 2 DinRail
|
||||
- Magic 2 LAN 1-1
|
||||
- Magic 1 LAN 1-1
|
||||
- Gigabridge
|
||||
|
||||
## Known limitations
|
||||
|
||||
This integration only supports using the API the devolo Home Network App uses. The device website usually offers additional features. However, these features are not available via API and thus cannot be supported until devolo adds them to the API.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Gigabridge
|
||||
|
||||
The devolo Gigabridge is the only device that comes with a default password. However, it seems that in factory default the password works for the device website but not for the API. If you give the device a new password via the website, it is applied to both and the integration starts working. Even using the same password again works.
|
||||
|
||||
## Removal
|
||||
|
||||
This integration follows standard integration removal, no extra steps are required.
|
||||
|
||||
|
||||
@ -16,10 +16,19 @@ ha_platforms:
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The Garages Amsterdam integration uses an API provided by the municipality of Amsterdam, to measure the occupancy of Amsterdam parking garages in the Netherlands. You can track multiple garages by adding the integration multiple times.
|
||||
The **Garages Amsterdam** {% term integration %} uses an API provided by the municipality of Amsterdam, to measure the occupancy of Amsterdam parking garages in the Netherlands. You can track multiple garages by adding the integration multiple times.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
{% configuration_basic %}
|
||||
Garage name:
|
||||
description: The name of the parking garage you want to monitor.
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
## Data updates
|
||||
|
||||
The integration will poll the API of Amsterdam every 10 minutes to update the data in Home Assistant.
|
||||
|
||||
### Sensor
|
||||
|
||||
When you add a parking garage, 4 sensors are created in your configuration by default:
|
||||
@ -36,3 +45,9 @@ Some parking garages don't have long-term parking spaces, in which case the 2 sp
|
||||
### Binary sensor
|
||||
|
||||
Each parking garage also has a binary sensor, which indicates whether there are problems in the data provision from the API. When it indicates `ok` everything is fine. If the state changes to `problem`, the upstream data might not be up to date or reliable and will remain in this state until new data is coming in.
|
||||
|
||||
## Remove integration
|
||||
|
||||
You can remove each parking garage instance by following the default removal process.
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
@ -61,6 +61,7 @@ Your Husqvarna account username/password used for the *Automower® Connect* pho
|
||||
6. Leave this tab open in browser and continue with Home Assistant configuration.
|
||||
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
{% details "I have manually disabled My Home Assistant" %}
|
||||
|
||||
@ -75,32 +76,14 @@ Internal examples: `http://192.168.0.2:8123/auth/external/callback`, `http://hom
|
||||
|
||||
{% enddetails %}
|
||||
|
||||
### Home Assistant
|
||||
|
||||
The My Home Assistant redirect feature needs to be setup to redirect to your Home Assistant installation. See [My FAQ](https://my.home-assistant.io/faq) for additional information.
|
||||
|
||||
1. Add the integration to your Home Assistant installation and test the redirect feature by following below link:
|
||||
[](https://my.home-assistant.io/redirect/config_flow_start/?domain=husqvarna_automower)
|
||||
|
||||
2. Acknowledge prompts to open link, install Husqvarna Automower integration.
|
||||
|
||||
3. Acknowledge prompt to setup application credentials.
|
||||
|
||||
4. Enter the following from the Husqvarna developer tab:
|
||||
|
||||
- A name of the application
|
||||
- Copy and paste the *Application key* into the *OAuth Client ID* field
|
||||
- Copy and paste the *Application secret* into the *OAuth Client Secret* field
|
||||
|
||||
5. Click **Create**
|
||||
|
||||
6. Browser will be redirected to Husqvarna Developer site. Sign in and Authorize the integration to connect with your Husqvarna account
|
||||
|
||||
7. After authorizing the integration the browser will show the My Home Assistant redirect link to link this account. Click on **Link Account**.
|
||||
|
||||
8. Confirm successful connection of mower and assign to an area.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
{% configuration_basic %}
|
||||
Name:
|
||||
description: "Enter the name for the provided credentials. You can choose your favorite name."
|
||||
OAuth Client ID:
|
||||
description: "Enter the Application key from your Husqvarna developer application."
|
||||
OAuth Client Secret:
|
||||
description: "Enter the Application secret from your Husqvarna developer application."
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
@ -234,3 +217,14 @@ data:
|
||||
minutes: 30
|
||||
work_area_id: 123456 ### Work area ID for the "Front lawn" from the example above.
|
||||
```
|
||||
|
||||
## Known limitations
|
||||
|
||||
- The mower can only be started using the `lawn_mower.start_mowing` action during the schedules configured in the Automower Connect App. To start the mower outside the scheduled times, use the `husqvarna_automower.override_schedule` action. In both cases, the battery must be fully charged beforehand.
|
||||
- Stay-out zone handling is not supported for mowers equipped with EPOS technology.
|
||||
|
||||
## Remove integration
|
||||
|
||||
This integration can be removed by following these steps:
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
@ -69,3 +69,9 @@ To use this device tracker, you only need limited privileges. To enhance the sec
|
||||
group add name=homeassistant policy=read,api,test
|
||||
add group=homeassistant name=homeassistant
|
||||
```
|
||||
|
||||
You will be prompted to set a password for the newly created user. Depending on your RouterOS version and configuration, you might need to set a password yourself:
|
||||
|
||||
```bash
|
||||
/user set [find username=homeassistant] password=PASSWORD
|
||||
```
|
||||
|
||||
@ -16,19 +16,26 @@ ha_quality_scale: platinum
|
||||
ha_integration_type: integration
|
||||
---
|
||||
|
||||
The P1 Monitor integration integrates the [P1 Monitor](https://www.ztatz.nl/p1-monitor/)
|
||||
API platform with Home Assistant.
|
||||
The **P1 Monitor** {% term integration %} allows you to gather data from your [P1 Monitor](https://www.ztatz.nl/p1-monitor/) device and use it in Home Assistant.
|
||||
|
||||
P1 Monitor is a platform that allows you to read the data from your smart meter via the serial port (P1), such as your energy consumption, but also that of gas or a water meter.
|
||||
P1 Monitor is a piece of software that can be installed on a Raspberry Pi or other Linux-based system. It reads the data from your smart meter via the serial port (P1), such as your energy consumption, but also that of gas or a water meter.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
{% configuration_basic %}
|
||||
Host:
|
||||
description: The IP address or hostname of your P1 Monitor instance.
|
||||
Port:
|
||||
description: The port number of your P1 Monitor instance. The default port is `80`.
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
## Data updates
|
||||
|
||||
The integration will poll your P1 Monitor instance every 5 seconds to update the data in Home Assistant.
|
||||
|
||||
## Sensors
|
||||
|
||||
The P1 Monitor platform mainly provides sensors that you can use in your
|
||||
[energy dashboard](/energy).
|
||||
|
||||
**Note** that by default, the gas consumption entities are disabled, so if you want to use them, you need to enable them manually.
|
||||
The P1 Monitor platform mainly provides sensors that you can use in your [energy dashboard](/energy).
|
||||
|
||||
### SmartMeter
|
||||
|
||||
@ -40,6 +47,10 @@ Read out what your meter readings are for energy consumption/yield, see what you
|
||||
- Energy Production Low/High (kWh)
|
||||
- Energy Tariff Period (low / high)
|
||||
|
||||
{% note %}
|
||||
By default, the gas consumption entity is disabled. To use it, you need to enable it.
|
||||
{% endnote %}
|
||||
|
||||
### Phases
|
||||
|
||||
See per phase what your voltage, current and power consumption/production is.
|
||||
@ -68,3 +79,9 @@ You can use the rates set in P1 Monitor for your calculations in Home Assistant.
|
||||
- Gas Consumption Price
|
||||
- Energy Consumption Price Low/High
|
||||
- Energy Production Price Low/High
|
||||
|
||||
## Remove integration
|
||||
|
||||
This integration follows standard integration removal, no extra steps are required.
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
@ -364,6 +364,7 @@ The following hubs/NVRs have been tested and confirmed to work with battery-powe
|
||||
- [Reolink Home Hub Pro](https://reolink.com/product/reolink-home-hub-pro/)
|
||||
- [RLN8-410 NVR](https://reolink.com/product/rln8-410/) (only the latest hardware version N7MB01, older versions might receive the required firmware update later)
|
||||
- [RLN16-410 NVR](https://reolink.com/product/rln16-410/) (only the latest hardware version N6MB01, older versions might receive the required firmware update later)
|
||||
- [RLN36 NVR](https://reolink.com/product/rln36/)
|
||||
|
||||
The following battery-powered models have been tested and confirmed to work through the Reolink Home Hub/NVR:
|
||||
|
||||
|
||||
@ -19,7 +19,16 @@ The Swiss public transport integration will give you the next three departure ti
|
||||
|
||||
The [Swiss public transport API](https://transport.opendata.ch/) only allows 1000 requests per 24 hours. The default polling rate is set to `90s`, which is just enough for one connection polling continuously. If more entries are needed, consider [defining a custom polling interval](#defining-a-custom-polling-interval) to reduce the amount of requests.
|
||||
|
||||
The [Stationboard](https://transport.opendata.ch/examples/stationboard.html) website can help to determine the exact name of the start and the end station.
|
||||
{% configuration_basic %}
|
||||
Start station:
|
||||
description: "The departure station for the start of the connection (e.g., 'Zürich HB')"
|
||||
End station:
|
||||
description: "The arrival station for the end of the connection (e.g., 'Geneva')"
|
||||
Via stations:
|
||||
description: "List of up to 5 via stations (e.g., 'Bern, Lausanne')"
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
Use the [Stationboard](https://transport.opendata.ch/examples/stationboard.html) to find exact station names.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -85,3 +94,9 @@ Fetch the connections for a specific instance.
|
||||
## Defining a custom polling interval
|
||||
|
||||
{% include common-tasks/define_custom_polling.md %}
|
||||
|
||||
## Remove integration
|
||||
|
||||
This integration follows standard integration removal, no extra steps are required.
|
||||
|
||||
{% include integrations/remove_device_service.md %}
|
||||
|
||||
@ -22,7 +22,7 @@ Notes:
|
||||
|
||||
- If a unit system is not specified, the {% term integration %} will use the unit system configured on your Home Assistant instance.
|
||||
- **Origin** and **Destination** can be the address or the GPS coordinates of the location. For coordinates, use the following format: `52.5200, 13.4050`. Make sure the coordinates are separated by a comma. They must not include letters. You can also enter an entity id which provides this information in its state, an entity id with latitude and longitude attributes, or zone friendly name (case sensitive).
|
||||
- The `incl_filter`/`excl_filter` allow you to force the {% term integration %} to use a particular route or avoid a particular route in its time travel calculation. These inputs must be an exact match to the street name including casing, spaces, and special characters.
|
||||
- The `incl_filter`/`excl_filter` allow you to force the {% term integration %} to use a particular route or avoid a particular route in its time travel calculation. These inputs must be an exact match to the street name including casing, spaces, and special characters. Use the service [`waze_travel_time.get_travel_times`](#action-waze_travel_timeget_travel_times) to get the exact street names for each route.
|
||||
- When using the `Avoid Toll Roads?`, `Avoid Subscription Roads?` and `Avoid Ferries?` options, be aware that Waze will sometimes still route you over toll roads or ferries if a valid vignette/subscription is assumed. Default behavior is that Waze will route you over roads having subscription options. It is therefor best is to set both `Avoid Toll Roads?` and `Avoid Subscription Roads?` or `Avoid Ferries?` if needed and experiment to ensure the desired outcome.
|
||||
|
||||
## Action `waze_travel_time.get_travel_times`
|
||||
|
||||
@ -6,7 +6,7 @@ date: 2024-11-18 00:00:00
|
||||
date_formatted: "November 18, 2024"
|
||||
author: Missy Quarry
|
||||
comments: true
|
||||
categories: community
|
||||
categories: Community
|
||||
og_image: /images/blog/2024-11-universe/art.jpg
|
||||
---
|
||||
|
||||
|
||||
@ -0,0 +1,67 @@
|
||||
---
|
||||
layout: post
|
||||
title: "Home Assistant Yellow gets CM5 support in HAOS 14"
|
||||
description: "We've tested the CM5 with the Home Assistant Yellow, and it works! But the CM4 is still great!"
|
||||
date: 2024-11-27 00:00:00
|
||||
date_formatted: "November 27, 2024"
|
||||
author: Andy Gill
|
||||
comments: true
|
||||
categories:
|
||||
- HAOS
|
||||
- Hardware
|
||||
og_image: /images/blog/2024-11-cm5/art.jpg
|
||||
---
|
||||
|
||||
<img src='/images/blog/2024-11-cm5/art.jpg' alt="Home Assistant Yellow in all its glory">
|
||||
|
||||
We launched our [Home Assistant Yellow](/yellow/) over two years ago, with the design philosophy that it would grow and extend its capabilities with its users' needs. Need more storage, add an NVMe drive. Need Matter over Thread instead of Zigbee, change the firmware.
|
||||
|
||||
Thanks to Raspberry Pi providing us with an early sample, we have been able to add **Compute Module 5 (CM5) compatibility to the Home Assistant Yellow**, which will be included in Home Assistant OS 14 (along with some [other hardware support](#other-additions-to-haos-14)). This gives current and future users a great option to get more performance if they need it, but we must say that CM4 is still more than enough for most Home Assistant users' needs.
|
||||
|
||||
As part of the Open Home Foundation, we fight for privacy, choice, and sustainability in the smart home. The Yellow achieves all three, and this announcement only improves the choices available and long-term sustainability.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Using Compute Modules
|
||||
|
||||
When designing Yellow to give our users the ability to expand the capabilities of the device we chose Raspberry Pi's Compute Module platform. It allows users to increase the RAM, add eMMC, built-in Bluetooth, or even get more speed 😉 - without having to replace the Yellow - all you need to do is get a new module. This is also great for the repairability of the product over its lifetime.
|
||||
|
||||
Though it was designed for the Compute Module 4 (CM4), we always hoped it would be compatible with its future successors. Over the past couple of months, we've been updating firmware and testing early hardware, and it is indeed compatible. Due to changes on CM5, the installation method is slightly more complex than it was on CM4, which is detailed below.
|
||||
|
||||
## What CM5 could bring
|
||||
|
||||
I must admit, it is fun to play with the latest and greatest hardware (while also finding new uses for the hardware it replaces - old Pi products make great [Wyoming satellites](https://github.com/rhasspy/wyoming-satellite)). In most use cases, such as running automations or connecting an average home's worth of devices, the majority of users will not notice any difference between a Green, CM4, or CM5.
|
||||
|
||||
For certain power user needs CM5 might provide big improvements. Some Pi 5 users have seen nearly [3x improvements](https://www.youtube.com/watch?v=kaVND-M9pkA&t=415s) in ESPHome compilation times; saving a minute or two per device can really add up in big deployments. Another area where CM5 can excel over CM4 is running local speech-to-text processing if you're using [Assist](/voice_control/) fully locally.
|
||||
|
||||
## Installing on CM5
|
||||
|
||||
For the Home Assistant Yellow, we have [two ways to install Home Assistant OS](https://yellow.home-assistant.io/guides/reinstall-os/) onto the Compute Module. One is very easy and quick (using USB 2.0), while the other is more complex (using rpiboot). Unfortunately, due to firmware differences with CM5 it cannot boot off USB 2.0 devices (though the USB 2.0 ports work once the device is booted).
|
||||
|
||||
If you already have a Yellow running Home Assistant OS, upgrading to CM5 can be a drop-in replacement, but in some circumstances it can be more complex,
|
||||
|
||||
- **CM4 Lite (no eMMC) with NVMe storage** - Update to the latest HAOS (version 14.0 or greater - as of writing 14.0 is still pre-release, we recommend you wait for the stable release, but if you want to get the pre-release today either [join the beta channel](https://www.home-assistant.io/common-tasks/os/#running-a-beta-version) or [explicitly install](https://www.home-assistant.io/common-tasks/os/#running-a-specific-version) `14.0.rc2`), power it down, swap the CM4 Lite for a CM5 Lite, and you're good to go.
|
||||
|
||||
- **CM4 with eMMC (regardless if you are using NVMe or not)** - Download a backup of your Home Assistant, power down your system, and install Home Assistant OS on the CM5 using [rpiboot](https://yellow.home-assistant.io/guides/reinstall-os/#:~:text=Option%202%3A%20Reinstall%20Home%20Assistant%20OS%20using%20rpiboot) (the more complex installation method). Once installed restore the backup.
|
||||
|
||||
- **New Yellow with CM5**: You will need to install Home Assistant with [rpiboot](https://yellow.home-assistant.io/guides/reinstall-os/#:~:text=Option%202%3A%20Reinstall%20Home%20Assistant%20OS%20using%20rpiboot) (the more complex installation method).
|
||||
|
||||
For full details on how to set up your Home Assistant Yellow [visit our documentation](https://yellow.home-assistant.io/).
|
||||
|
||||
## CM4 is still great
|
||||
|
||||
If you have, or were looking at getting, a Home Assistant [Green](/green/) or [Yellow](/yellow/) with a CM4, both are more than capable. A third of all Home Assistant users are using Pi 4 class hardware.
|
||||
|
||||
<img src='/images/blog/2024-11-cm5/analytics.png' style='border: 0;box-shadow: none;' alt="In our analytics Pi 4 class hardware is the most used SBC">
|
||||
|
||||
In fact, according to our [opt-in analytics](https://analytics.home-assistant.io/), more people are using Pi 3 hardware than Pi 5 hardware (granted the Pi 5 has only had official support since [February this year](/blog/2024/02/26/home-assistant-os-12-support-for-raspberry-pi-5/)). Home Assistant continues to get updates that improve its speed on all hardware, most recently [faster backups](/blog/2024/02/26/home-assistant-os-12-support-for-raspberry-pi-5/#faster-backups) and [reboots](/blog/2024/03/06/release-20243/#home-assistant-boots-twice-as-fast). This allows people to keep hardware running longer, and in the end that is our goal 🌎.
|
||||
|
||||
CM4 is not only powerful enough for most users, it also has a long life ahead of it. Raspberry Pi has even confirmed that they will **fully support CM4 [until 2034](https://www.raspberrypi.com/products/compute-module-4/?variant=raspberry-pi-cm4001000#:~:text=Obsolescence%20Statement)💪,** and will continue to manufacture them.
|
||||
|
||||
## Other additions to HAOS 14
|
||||
|
||||
On the topic of newly supported hardware, our release of Home Assistant OS 14 will bring support not only for CM5 but also for the Hailo-8 AI accelerator. This is the AI accelerator found in the [Raspberry Pi AI Kit](https://www.raspberrypi.com/documentation/accessories/ai-kit.html) or the even more powerful Raspberry Pi AI HAT+ [released](https://www.raspberrypi.com/news/raspberry-pi-ai-hat/) last month, which is exclusively for the Raspberry Pi 5. For those using a Pi 5 they can now offload AI processing, like object or person detection, to this efficient add-on.
|
||||
|
||||
## Conclusion
|
||||
|
||||
We're incredibly proud that, all this time later, the Home Assistant Yellow continues to be one of the best options for power users. We are excited to see how our users take advantage of CM5, and it's great to see CM4 continue to be a great option with long-term support.
|
||||
@ -79,7 +79,6 @@ frontpage_image: /images/connectzbt1/connectzbt1-cover.jpg
|
||||
<div class="content">
|
||||
<div class="material-card text banner-overlay with-box">
|
||||
<div>
|
||||
<div class="banner-overlay-header">Temporarily unavailable</div>
|
||||
<div class="banner-overlay-content">
|
||||
Home Assistant Connect ZBT-1 (previously known as Home Assistant SkyConnect) is the easiest way to add Zigbee support
|
||||
to your Home Assistant instance.
|
||||
|
||||
BIN
source/images/blog/2024-11-cm5/analytics.png
Normal file
BIN
source/images/blog/2024-11-cm5/analytics.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 41 KiB |
BIN
source/images/blog/2024-11-cm5/art.jpg
Normal file
BIN
source/images/blog/2024-11-cm5/art.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 75 KiB |
@ -29,8 +29,8 @@ Although adding voice to your smart home configuration is exciting, it will requ
|
||||
|
||||
Ready? Now let's get started
|
||||
|
||||
- [I plan to use a local speech-to-text/text-to-speech setup](/voice_source/voice_remote_local_assistant/)
|
||||
- [I plan to use Home Assistant Cloud](/voice_sources/voice_remote_cloud_assistant/) (recommended as it is the simplest)
|
||||
- [I plan to use a local speech-to-text/text-to-speech setup](/voice_control/voice_remote_local_assistant/)
|
||||
- [I plan to use Home Assistant Cloud](/voice_control/voice_remote_cloud_assistant/) (recommended as it is the simplest)
|
||||
|
||||
## Expand and Experiment
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user