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-19 07:17:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Better explain the abilities of Cloud (#37311)

Browse Source 
* Better explain the abilities of Cloud

* Small changes to cloud.markdown

* Update source/_integrations/cloud.markdown

---------

Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
This commit is contained in:
Gord 2025-02-05 12:13:19 +00:00 committed by GitHub
parent 0ece550333
commit f2aef680c2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
source/_integrations/cloud.markdown
View File

@ -5,6 +5,8 @@ ha_release: '0.60'
ha_category:
- Text-to-speech
- Voice
- Backup
- Speech-to-text
ha_iot_class: Cloud Push
ha_codeowners:
- '@home-assistant/cloud'
@ -16,7 +18,7 @@ ha_platforms:
ha_integration_type: system
---
The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa and Google Assistant. [Learn more.](/cloud)
The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa and Google Assistant. It also enables a secure remote connection, speech-to-text, text-to-speech, an offsite backup location, Webhooks support, and better WebRTC. [Learn more.](/cloud)
## Configuration
@ -29,7 +31,7 @@ cloud:
Documentation of further configuration possibilities are located at [NabuCasa](https://www.nabucasa.com/config/)
Once activated, go to the configuration panel in Home Assistant and create an account and log in. If you are not seeing the **Settings** panel, make sure you have the following option enabled in your {% term "`configuration.yaml`" %} file.
Once activated, go to the configuration panel in Home Assistant, create an account, and log in. If you are not seeing the **Settings** panel, make sure you have the following option enabled in your {% term "`configuration.yaml`" %} file.
```yaml
config: