-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Add Homecast integration documentation #44341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
9f540ec
bd25ff9
44a850e
95762bb
95e8e6d
0ea88b9
565d6fc
e482e10
bb4c205
a11bbc5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -73,7 +73,7 @@ The `remote` {% term entities %} allow you to learn and send codes with universa | |||||||||||||
|
|
||||||||||||||
| ### Learning commands | ||||||||||||||
|
|
||||||||||||||
| Use `remote.learn_command` to learn IR and RF codes. These codes are grouped by device and stored as commands in the [storage folder](#learned-codes-storage-location). They can be sent with the `remote.send_command` action later. | ||||||||||||||
| Use `remote.learn_command` to learn IR and RF codes. These codes are grouped by device and stored as commands in the [storage folder](#learned-codes-storage-location). They can be sent with the `remote.send_command` action later. A convenient interface to learn, send, and delete codes can be found in web interface under `/developer-tools/service`. | ||||||||||||||
|
|
||||||||||||||
| | Data attribute | Optional | Description | | ||||||||||||||
| | ---------------------- | -------- | ------------------------------------- | | ||||||||||||||
|
|
@@ -428,6 +428,7 @@ The above example creates `switch.philips_tv` and `switch.lg_tv`, which are rela | |||||||||||||
|
|
||||||||||||||
| __IMPORTANT__: Always use unique names for your switches. A good choice is to prefix the name with the area in which the device is located, e.g. Bedroom TV. | ||||||||||||||
|
|
||||||||||||||
| ## Managing codes for remotes | ||||||||||||||
|
Comment on lines
429
to
+431
|
||||||||||||||
| __IMPORTANT__: Always use unique names for your switches. A good choice is to prefix the name with the area in which the device is located, e.g. Bedroom TV. | |
| ## Managing codes for remotes | |
| __IMPORTANT__: Always use unique names for your switches. A good choice is to prefix the name with the area in which the device is located, like Bedroom TV. | |
| ## Managing codes for remotes |
Copilot
AI
Mar 27, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spelling: Managig should be Managing in this heading.
| ### Managig codes with Broadlink Manager | |
| ### Managing codes with Broadlink Manager |
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,104 @@ | ||||||||||
| --- | ||||||||||
| title: Homecast | ||||||||||
| description: Instructions on setting up Homecast within Home Assistant. | ||||||||||
| ha_category: | ||||||||||
|
Comment on lines
+1
to
+4
|
||||||||||
| - Alarm | ||||||||||
| - Binary sensor | ||||||||||
| - Climate | ||||||||||
| - Cover | ||||||||||
| - Fan | ||||||||||
| - Hub | ||||||||||
| - Light | ||||||||||
| - Lock | ||||||||||
| - Sensor | ||||||||||
| - Switch | ||||||||||
| ha_release: "2025.12" | ||||||||||
| ha_iot_class: Cloud Polling | ||||||||||
| ha_config_flow: true | ||||||||||
| ha_domain: homecast | ||||||||||
| ha_platforms: | ||||||||||
| - alarm_control_panel | ||||||||||
| - binary_sensor | ||||||||||
| - climate | ||||||||||
| - cover | ||||||||||
| - fan | ||||||||||
| - light | ||||||||||
| - lock | ||||||||||
| - sensor | ||||||||||
| - switch | ||||||||||
| ha_integration_type: hub | ||||||||||
| ha_codeowners: | ||||||||||
| - '@parob' | ||||||||||
| ha_quality_scale: bronze | ||||||||||
| --- | ||||||||||
|
|
||||||||||
| [Homecast](https://homecast.cloud) bridges Apple HomeKit smart home devices to open standards, enabling remote control, API access, and AI assistant integration. The Homecast Mac or iOS app runs on your home network as a relay between HomeKit and the Homecast cloud. | ||||||||||
|
|
||||||||||
| This integration connects Home Assistant to the Homecast cloud API, exposing your HomeKit devices as native Home Assistant entities. | ||||||||||
|
|
||||||||||
|
Comment on lines
+35
to
+38
|
||||||||||
| [Homecast](https://homecast.cloud) bridges Apple HomeKit smart home devices to open standards, enabling remote control, API access, and AI assistant integration. The Homecast Mac or iOS app runs on your home network as a relay between HomeKit and the Homecast cloud. | |
| This integration connects Home Assistant to the Homecast cloud API, exposing your HomeKit devices as native Home Assistant entities. | |
| The **Homecast** {% term integration %} connects Home Assistant to the Homecast cloud API so you can use your Apple HomeKit smart home devices as native Home Assistant entities. [Homecast](https://homecast.cloud) bridges Apple HomeKit devices to open standards, enabling remote control, API access, and AI assistant integration. The Homecast Mac or iOS app runs on your home network as a relay between HomeKit and the Homecast cloud. |
Copilot
AI
Mar 27, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The My link title should contain the bold breadcrumbs (for example, {% my integrations title="**Settings** > **Devices & services**" %}), and the surrounding text should avoid “click” (prefer “select”). Current step 1 uses **{% my integrations title="Settings > Devices & services" %}** and “click”, which diverges from the convention used across the docs (for example, source/_includes/common-tasks/define_custom_polling.md:7).
Copilot
AI
Mar 27, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This uses the same My link formatting issue as in the Setup steps: the breadcrumbs should be bold inside the My link title (for example, {% my integrations title="**Settings** > **Devices & services**" %}) rather than wrapping the whole tag in **...**.
| If your OAuth token expires, Home Assistant will show a notification prompting you to re-authenticate. Go to **{% my integrations title="Settings > Devices & services" %}** > **Homecast** and follow the re-auth flow. | |
| If your OAuth token expires, Home Assistant will show a notification prompting you to re-authenticate. Go to {% my integrations title="**Settings** > **Devices & services**" %} > **Homecast** and follow the re-auth flow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/developer-tools/serviceis not used elsewhere in the docs, and the UI path is usually referenced via a My link (for example,{% my developer_services title="**Settings** > **Developer tools** > **Actions**" %}insource/_docs/automation/basics.markdown:47). Consider replacing the raw URL/path reference with the My link to avoid drifting UI paths and improve readability.