# Do I need Supporter Perks For Google Home And Alexa?
Source: https://help.homeway.io/frequently-asked-questions/google-home-and-alexa/do-i-need-supporter-perks-for-google-home-and-alexa



Yes, you need Homeway Supporter Perks to enable Google Home and Alexa. [All new users get a free, no-obligation 30-day trial of Supporter Perks](https://homeway.io/supporter?source=help_google_alexa_perks_required), giving you time to try Homeway and see if it works for you!

Homeway establishes a secure, private connection between your Home Assistant server and Google Home or Alexa cloud services. This enables communication between Home Assistant and services without exposing Home Assistant to the public internet.

However, Google Home and Alexa place a heavy workload on our services, which is why we require users to support Homeway with Supporter Perks to use them.


# Delete Your Account
Source: https://help.homeway.io/help-docs/account-help/delete-your-homeway-account



We are sad to see you go, but your privacy and security are important to us. We make it easy to delete your account whenever you want.

You can delete your account by doing the following:

1. Go to your [Homeway Account](https://homeway.io/account?source=help_delete_account) page.
2. Hit the "Delete Account" button.
3. Press yes to confirm you want to delete your account.

<Warning>
  Deleting your account is permanent. But you're always welcome to join again anytime!
</Warning>

<Tip>
  If you have a Supporter Perks subscription, it will be automatically canceled when you delete your account.
</Tip>


# One-Time Supporter Perks Payment
Source: https://help.homeway.io/help-docs/account-help/one-time-supporter-perks-payment



**Homeway currently doesn't support a one-time payment for Supporter Perks.** Our service costs us funds to run each month, and we use the Supporter Perks income to cover the hosting and development costs.

However, a good alternative might be to purchase a year's worth of Supporter Perks and then cancel immediately. You will then get Supporter Perks for the entire year you paid for, but you will not be automatically charged the following year. You can repeat this process on demand as often as you like!

If you have any questions, contact us via our support system!


# Reset Your Password
Source: https://help.homeway.io/help-docs/account-help/reset-your-password

test description

Forgot or need to change your password? 😖

No problem! Resetting your password is easy:

1. [Use this link](https://homeway.io/resetpassword?source=help_password_reset) to send yourself a password recovery email.
2. Open the email and click the link.
3. Set a new password!

<Warning>
  Resetting your password will disable two-factor authentication for your account. Be sure
</Warning>


# Save 30% With Yearly Billing
Source: https://help.homeway.io/help-docs/account-help/save-30-with-yearly-billing



**Who doesn't like saving money?**

You can save 30% of your Supporter Perks just by upgrading to yearly billing. Each time Homeway makes a transaction, we have to pay a fee, and 12 transactions a year add up! Making one transaction a year saves us money, and we pass it on to you!

Switching to yearly payments is easy:

1. Go to the [Homeway Supporter](https://homeway.io/supporter?source=help_yearly) website.
2. Log in to your account.
3. Select the "Upgrade To Yearly" button.

Enjoy your savings!


# Cancel Supporter Perks
Source: https://help.homeway.io/help-docs/account/supporter-perks/cancel-supporter-perks



We make it easy; you can cancel your Supporter Perks subscription anytime.

To cancel, simply:

1. Go to the [Homeway Supporter](https://homeway.io/supporter) website.
2. Log in to your account.
3. Click the "Cancel Your Support"

Your Supporter Perks will continue for the time you paid for. You can cancel while in trial and still get the remaining trial length for free!

We are always sad to see you go, but you're welcome back anytime! 🥰


# Get Supporter Perks
Source: https://help.homeway.io/help-docs/account/supporter-perks/get-supporter-perks



Homeway is 100% community-supported. Your support goes directly to hosting costs, development, and community outreach.

When you support Homeway, you get awesome Supporter Perks! Supporter Perks: unlimited, unthrottled remote access, Alexa and Google Home support, advanced Sage AI features, and more!

[**Learn More About Supporter Perks Now!**](https://homeway.io/supporter)


# Upgrade Your Supporter Perks
Source: https://help.homeway.io/help-docs/account/supporter-perks/upgrade-your-supporter-perks



Level up your Supporter Perks with Elite Perks, which include life-like Sage AI voices, 10x Sage AI limits, and more!

Get your Elite Perks now\...

1. Go to the [Homeway Supporter](https://homeway.io/supporter) page.
2. Log in to your account.
3. Select the "Upgrade To Elite" button.

Enjoy your perks! 🚀


# Get Addon Logs
Source: https://help.homeway.io/help-docs/addon/home-assistant-addons/get-addon-logs



Accessing your Homeway logs is helpful for debugging support issues.

If your Homeway add-on is installed via the Home Assistant web portal, you can access your logs there.

1. Open your Home Assistant website.
2. Click "Settings" in the main menu at the bottom left.
3. Click "System" in the settings list.
4. Click "Logs" in the system settings list.
5. At the top right, there's a drop-down text that defaults to "Home Assistant Core". Click the drop-down text and select "Homeway"
6. Click the download "arrow" icon toward the top right.
7. Send the log file via support by dragging it into the chat window.


# Link Your Addon
Source: https://help.homeway.io/help-docs/addon/link-your-addon



There are several ways to link your add-on; choose the best option for your install type.

### **If you installed the Homeway add-on using the Home Assistant add-on system:**

1. Open Home Assistant in your browser.
2. Go to the Home Assistant settings.
3. Select Add-ons
4. Select Homeway
5. Select the text that says "OPEN WEB UI"
6. Follow the guide!

### **If you installed the Homeway standalone add-on:**

1. SSH into the device running the Homeway standalone addon.
2. Enter the following command:
   1. `cat ./.homeway-addon/logs/homeway.log`
3. In the log output, you will find a link to [homeway.io](http://homeway.io) that completes the linking process.

### **If you installed the Homeway standalone Docker container:**

1. Use the Docker logs to find your link URL. The link URL will always appear at the top of the logs when the container starts.

That's it! If you need help, let us know via our chat system!


# Fix Addon Permission Issues
Source: https://help.homeway.io/help-docs/addon/standalone-addons/fix-addon-permission-issues



The standalone Homeway add-on requires a long-lived Home Assistant access token to communicate with Home Assistant. Add-on authentication is required for Homeway features such as Google Assistant and Alexa Assistants.

Here's how to update your long-lived authentication token:

**If you use the CLI standalone Homeway add-on:**

1. SSH into the device running the Homeway add-on.
2. Go to the Homeway plugin folder:
   1. `cd ~/homeway`
3. Run the install script:
   1. `./install`
4. The installer will locate your add-on and guide you through setting up the long-lived access token.
5. Done 🥳

**If you use the Docker standalone Homeway add-on:**

1. Create a new long-lived access token in Home Assistant:
   1. Go to your Home Assistant dashboard.
   2. Click your user name and image in the bottom right corner to open the account UI.
   3. Select the "Security" tab at the top of the webpage.
   4. Scroll to the bottom of the header "Long-lived access tokens"
   5. Click "Create Token"
   6. Give the token any name you want.
   7. Copy the access token.
2. Update the Docker Compose file:
   1. Open your Docker Compose file and paste the new access token into the `HOME_ASSISTANT_ACCESS_TOKEN` field.
   2. Restart the Docker container.
      1. `docker compose restart`


# Get Addon Logs
Source: https://help.homeway.io/help-docs/addon/standalone-addons/get-addon-logs



Accessing your Homeway logs is helpful for debugging support issues. Follow the guide below that matches your Homeway add-on type.

### **Standalone Linux CLI Add-on**

If your Homeway install was done via the Linux CLI installer, you can find your logs by doing the following:

1. SSH into the device running the Homeway plugin.
2. cd into the logs folder cd \~/.homeway-addon/logs
3. Download the most recent log file, labeled "homeway.log"
4. Send the log file via support by dragging it into the chat window.

If you're having trouble downloading the file via SSH, use an SFTP UI client like FileZilla.

### **Homeway Standalone Docker Container or Docker Compose**

If your Homeway plugin is running in the Homeway Docker Container or via Docker Compose, do the following:

1. Find the Docker container's mapped data folder.
   1. This folder mapping is either part of the Docker command-line run option or defined in your Docker-Compose file.
2. In the data folder, open the logs folder
3. Download the most recent log file, labeled "homeway.log"
4. Send the log file via support by dragging it into the chat window.

If you're having trouble downloading the file via SSH, use an SFTP UI client like FileZilla.


# Updating The Standalone Add-On
Source: https://help.homeway.io/help-docs/addon/standalone-addons/updating-the-standalone-add-on



Updating the Homeway standalone add-on is easy - even easier than installing it!

The [Homeway standalone add-on](https://homeway.io/support?source=help_standalone_update) can be used if your Home Assistant doesn't have built-in add-on support. It enables the full power of Homeway on any Home Assistant setup!

To update the Homeway standalone add-on:

1. SSH into the device running the Homeway standalone add-on.
2. Enter `cd ~` to ensure you're in the home directory.
3. Enter `./update-homeway.sh` to run the update script in your home directory.
4. Wait for the script to finish the update.
5. Done!

The update script will automatically pull the code and run the proper update scripts. It's just that easy!

If you get stuck or need help, [contact our support team](https://homeway.io/support)!


# Unbind Your Addon
Source: https://help.homeway.io/help-docs/addon/unbind-your-addon



Work in progress...

Please contact our support team for help unbinding.


# Introduction
Source: https://help.homeway.io/help-docs/getting-started/introduction



<div>
  <h1>
    Homeway Help Center
  </h1>

  <p>
    Search for help or explore the sidebar to get started.
  </p>

  <div>
    <div>
      <div>
        <svg>
          <path />
        </svg>
      </div>

      <span>Search for help...</span>

      <div>
        <span>⌘K</span>
      </div>
    </div>
  </div>
</div>


# Quickstart
Source: https://help.homeway.io/help-docs/getting-started/quickstart



Homeway is the easiest way to enable private, secure remote access to Home Assistant. And don't forget our other awesome features like Sage AI, WebRTC Camera Streaming, Cloud MCP Home Assistant server, and more.

[Click here to follow our step-by-step setup guide for any Home Assistant installation.](https://homeway.io/getstarted?source=help_quick_start)


# Accessing The Home Assistant Configuration YAML File
Source: https://help.homeway.io/help-docs/home-assistant/accessing-home-assistant-config-configuration-yaml-file



The configuration.yaml file in Home Assistant is the core configuration file. You might need to edit it occasionally to change fundamental Home Assistant features that can't be configured in the Home Assistant UI.

Here's how to access the Home Assistant configuration.yml file for editing:

### Option 1 - Use VS Code Server Add-on

This is the easiest and preferred way to edit configuration.yml if your Home Assistant supports add-ons.

1. Open the Home Assistant dashboard
2. Go to the settings menu.
3. Select Add-ons
4. Select "Add-on Store"
5. Find the add-on called "Studio Code Server"
6. Install the addon, and start it.
7. Select "Open in Web UI"
8. Select "configuration.yaml" in the Explorer list.
9. Make any edits needed.
10. Save the configuration.yml file.
11. Restart Home Assistant for the change to be applied.

### Option 2 - **Use SSH To Edit The Config**

Use this option if your Home Assistant server doesn't support add-ons and you know how to SSH into it.

1. SSH into the device running Home Assistant.
2. Look for the Home Assistant config file; it could be in a few places.
   1. /home/homeassistant/.homeassistant/configuration.yaml
   2. \~/.homeassistant/configuration.yaml
3. Use a command-line text editor, such as nano, to edit the file.
4. Restart Home Assistant for the change to be applied.


# Enable X-Forwarded-For Support in Home Assistant
Source: https://help.homeway.io/help-docs/home-assistant/enable-x-forwarded-for-header-http-config-trusted-proxies



Enabling support for the `X-Forwarded-For` header in Home Assistant allows Homeway and other proxy servers to give Home Assistant the user's IP address when making requests. This allows Home Assistant to know the user's actual IP address, not the IP address of the server proxying the web requests.

Knowing the real user's IP address is helpful for many Home Assistant features, such as WebRTC peer-to-peer connection negotiation, IP banning for failed login attempts, and more.

<Tip>
  If you're using the Homeway add-on in Home Assistant, it will configure this automatically!
</Tip>

If you're using the standalone Homeway add-on or another proxy server, such as DuckDNS or nginx, you need to manually configure the proxy settings in Home Assistant's config. yaml file.

1. [Get access to the Home Assistant configuration.yaml file.](/help-docs/home-assistant/accessing-home-assistant-config-configuration-yaml-file)
2. Find the IP address of your Homeway standalone add-on or other proxy server.
3. Add the following configuration to the bottom of the Home Assistant configuration.yml file.

```yaml theme={null}
http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.32.0/23 # This allows add-ons running in HA access
    - 192.168.1.15   # This allows a reverse proxy on your home LAN access
```

**Be sure to update the example IP address** `192.168.1.15`  with the IP address of your Home Assistant standalone add-on or other proxy server. Your IP address might start with `192.168.` `10.0.` .

Restart Home Assistant, and you're all set!


# Control Devices Exposed To Assistants
Source: https://help.homeway.io/help-docs/home-assistant/google-home-and-alexa/control-devices-exposed-to-assistants



Controlling the Home Assistant devices and entities exposed to Google Home or Alexa from Homeway is simple.

Go to the [Assistant Device Control](https://homeway.io/assistantdevicecontrol?source=helpdesk) page and select or unselect which devices you want to expose!

<Tip>
  Note that due to Google Home and Alexa restrictions, it might take 10 minutes to a few hours for the exposure changes to be reflected in your Google Home app.
</Tip>


# Google Home Integration
Source: https://help.homeway.io/help-docs/home-assistant/google-home-and-alexa/google-home-integration



Setting up a Google Home integration with your Home Assistant is very easy using Homeway. Homeway handles all the complexity and security for you, keeping things simple and secure!

Even better, Homeway's global server network enables an extremely low-latency connection between Google Home and Home Assistant, so your voice commands will be instant!

### To set up Google Home, do the following:

1. Set up the [Homeway add-on](https://homeway.io/getstarted?source=help_google_home) if you haven't yet.
2. Open the Google Home App on your phone.
3. Tap your user profile icon at the top right.
4. Tap "Home Settings"
5. Tap the "Works With Google" card.
6. Search for "Homeway"
7. Follow the Homeway guide to log in, select the devices you want Google Home to control, and create a secure connection.

That's it! You now have a secure connection between Google Home and your Home Assistant. You can always control which Home Assistant devices and entities Google Home has access to on the [Assistant Device Control](https://homeway.io/assistantdevicecontrol?source=help_google_home) page on Homeway.io.


# Amazon Alexa Integration
Source: https://help.homeway.io/help-docs/home-assistant/google-home-and-alexa/google-home-integration-copied-1



Setting up an Alexa integration with your Home Assistant is very easy using Homeway. Homeway handles all the complexity and security for you, keeping things simple and secure!

Even better, Homeway's global server network provides extremely low latency between Alexa and Home Assistant, so your voice commands will be instant!

### To set up Alexa, do the following:

1. Set up the [Homeway add-on](https://homeway.io/getstarted?source=help_alexa) if you haven't yet.
2. Open the Alexa App on your phone.
3. Tap the three-line menu icon at the bottom of the screen.
4. Tap "Skills & Games"
5. Search for "Homeway"
6. Select the search result and tap the "Enable" button.
7. Follow the Homeway guide to log in, select the devices you want Alexa to control, and create a secure connection.

That's it! You now have a secure connection between Amazon Alexa and your Home Assistant. You can always control which Home Assistant devices and entities Alexa has access to on the [Assistant Device Control](https://homeway.io/assistantdevicecontrol?source=help_alexa) page on Homeway.io.


# Manual Setup Guide
Source: https://help.homeway.io/help-docs/home-assistant/google-home-and-alexa/manual-setup-guide



[Homeway](https://homeway.io/?source=helpdesk_assistant_manual_setup) can connect [Amazon Alexa](https://homeway.io/alexa?source=helpdesk_assistant_manual_setup) or [Google Assistant](https://homeway.io/googleassistant?source=helpdesk_assistant_manual_setup) to your Home Assistant server to provide voice control of your home.

In 98% of cases, the Homeway add-on can instantly and automatically set up Amazon Alexa or Google Assistant. But in a few rare cases, the add-on can't access the Home Assistant configuration file, so it needs to be done manually.

But don't worry; the manual assistant setup process is easy and fast! Here's how:

1. [Get Access To Your Home Assistant Config File](/help-docs/home-assistant/accessing-home-assistant-config-configuration-yaml-file)
2. Add the following lines to the bottom of the Home Assistant config file:

```yaml theme={null}
# Added By Homeway to enable Alexa support.
alexa:
  smart_home:

# Added By Homeway to enable Google Assistant support.
google_assistant:
  project_id: homewayio
  service_account:
    private_key: "nokey"
    client_email: "support@homeway.io"
```

**Restart Home Assistant to reload the config,** and you're done! You can now use the Alexa or Google Home app to link Homeway.

If you need any help, contact our [support team](https://homeway.io/support).


# Home Assistant App Secure Remote Access
Source: https://help.homeway.io/help-docs/home-assistant/home-assistant-app/home-assistant-app-secure-remote-access



Setting up remote access for the official Home Assistant iOS and Android apps is super easy and free with Homeway!

To set up your Home Assistant app, grab your phone and head to the Homeway app setup website. We recommend opening the app website on your phone so it's easier to copy and paste the required setup content.

[https://homeway.io/app](https://homeway.io/app)


# Claude Connector for Home Assistant
Source: https://help.homeway.io/help-docs/home-assistant/remote-mcp/claude-connector



[Homeway provides a free Claude Connector for Home Assistant](https://homeway.io/mcp?source=help_mcp_claude). It's secure and private by default and is extremely easy to set up. Homeway has a [Privacy Commitment](https://help.homeway.io/privacy) to protect your data.

Setting up the Homeway Claude Connector will make your Home Assistant available to Claude wherever you are, no matter where you are, on your phone, desktop, or away from home.

### Set up Your Home Assistant Claude Connector

1. Open the Claude desktop app on Windows, Mac, or Linux.
2. Click your name in the bottom left to open the profile menu, then select Settings.
3. In the Settings menu, select Connectors.
4. Press the "Add custom connector" button at the bottom.
5. Enter any name you wish.
6. Use the following URL for the "Remote MCP server URL."
   1. [https://homeway.io/api/mcp](https://homeway.io/api/mcp)
7. Leave all of the other settings at their defaults.
8. Press the "Add" button.
9. Log in to Homeway.
10. Done!

Be sure to check out Homeway's other awesome Home Assistant cloud tools like [free remote access](https://homeway.io/?source=help_mcp_claude), [Sage AI](https://homeway.io/sage-ai?source=help_mcp_claude), [Google and Alexa support](https://homeway.io/?source=help_mcp_claude), and more!


# Free Remote MCP for Home Assistant
Source: https://help.homeway.io/help-docs/home-assistant/remote-mcp/free-remote-mcp-server



## Intro

[Homeway's free remote MCP server for Home Assistant](https://homeway.io/mcp?source=help_mcp_getstarted) allows any AI assistant or agent to fully integrate with your Home Assistant. Your AI assistant will be able to access live status information about your home, control any device in your home, send commands, and more.

## Ease Of Use

Homeway's cloud AI MCP server is easy to set up. [Simply install our Home Assistant App](https://homeway.io/getstarted?source=help_mcp_install_app), log in to the MCP server, and you're done. It's private and secure by default and accessible to any AI.

## Security

Homeway's MCP granular control allows you to enable/disable access to any MCP function, ensuring the model has no access to it. This allows you to make your home read-only or allow the AI access to only a subset of controls. The granular control permissions are enforced by Homeway's servers, so there's no way for the AI to get around them.

## Privacy

The cloud MCP server is built on Homeway's worldwide secure and private server infrastructure. Homeway sticks to a strict [Privacy Commitment; you can read more about it here.](https://help.homeway.io/privacy)

## Get Started

[Click here to set up your Home Assistant](https://homeway.io/getstarted?source=help_mcp_get_started) or choose a client below for a full step-by-step guide.

## AI Setup Guides

### Claude

1. Open the Claude app and navigate to **Customize** > **Connectors**.
2. Click the "Add" or "+" button and select **Add Connector**.
3. Enter the MCP server URL: `https://homeway.io/api/mcp`.
4. Click Connect after saving, then follow the on-screen prompts to complete OAuth sign-in and authorization.

### ChatGPT

1. Open ChatGPT and go to **Settings** > **Apps** > **Advanced Settings**.
2. Turn on **Developer Mode**.
3. Click **Create App**.
4. Enter the MCP server URL: `https://homeway.io/api/mcp`
5. Save the configuration and follow the prompts to complete OAuth sign-in and authorization.

### Google Gemini

The Homeway MCP server will work everywhere in Gemini, but it must be set up in the desktop app or website.

1. Open the Gemini desktop app or website in your browser.
2. Click the settings gear icon and then select "Connected Apps"
3. Scroll to the bottom and select "Add a custom app"
4. Enter the MCP server URL: `https://octoeverywhere.com/api/mcp`
5. Click Next
6. Approve the permissions

<Tip>
  Sometimes the Gemini Custom App setup will fail, saying something about a linked account being required. Simply retry a few times, and the error will resolve itself.
</Tip>

### Claude Code

1. Run the following command in your terminal:

```text theme={null}
claude mcp add --transport http homeway https://homeway.io/api/mcp
```

2. In your Claude Code session, run `/mcp` and follow the prompts to complete the OAuth authorization flow.
3. To use a Bearer Token instead, add the `--header` flag:

```text theme={null}
claude mcp add --transport http homeway https://homeway.io/api/mcp --header "Authorization: Bearer YOUR_TOKEN_HERE"
```

### Cursor

1. Open Cursor and go to **Cursor Settings**.
2. In the left sidebar, select **Tools & MCP**, then click **Add Custom MCP**.
3. Edit the `.cursor/mcp.json` file and add the following content:

```text theme={null}
{
  "mcpServers": {
    "homeway": {
      "url": "https://homeway.io/api/mcp"
    }
  }
}
```

4. Save the configuration, then reopen **Tools & MCP**.
5. Find Homeway in the installed MCP services list, click **Connect**, and complete OAuth sign-in and authorization in your browser.
6. To use a Bearer Token, add the `headers` field to the configuration instead:

```text theme={null}
{
  "mcpServers": {
    "homeway": {
      "url": "https://homeway.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```

### VS Code

1. Create or edit the `.vscode/mcp.json` file in your workspace and add the following content:

```text theme={null}
{
 "servers": {
    "homeway": {
      "type": "http",
      "url": "https://homeway.io/api/mcp"
    }
  }
}
```

2. You can also open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P), run **Add Server**, choose **HTTP (HTTP or Server-Sent Events)**, enter the MCP server URL `https://homeway.io/api/mcp` and an ID, then choose whether to apply it to the workspace or globally.
3. Save the configuration and follow the prompts to complete OAuth sign-in and authorization in your browser.
4. To use a Bearer Token, add the `headers` field to the configuration instead:

```text theme={null}
{
  "servers": {
    "homeway": {
      "type": "http",
      "url": "https://homeway.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```

### Codex

**Via the Codex App**

1. Open the Codex App and go to **Settings > MCP Servers**.
2. Click **Add Server**.
3. Select **Streamable HTTP**.
4. Enter the MCP server URL: `https://homeway.io/api/mcp`
5. Click **Authenticate** after saving, then follow the on-screen prompts to complete OAuth sign-in and authorization.

**Via the CLI**

1. Run the following command in your terminal:

```text theme={null}
codex mcp add homeway --url https://homeway.io/api/mcp
```

2. You will be automatically prompted to complete OAuth sign-in and authorization in your browser.

### TRAE

1. Open TRAE and go to **Settings**.
2. In the left sidebar, select **MCP**, then click **Add > Add Manually**.
3. Add the following configuration:

```text theme={null}
{
  "mcpServers": {
    "homeway": {
      "url": "https://homeway.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
```


# Gemini Custom App for Home Assistant
Source: https://help.homeway.io/help-docs/home-assistant/remote-mcp/google-gemini-custom-app



[Homeway provides a free Gemini Custom App for Home Assistant](https://homeway.io/mcp?source=help_mcp_gemini). It's secure and private by default and is extremely easy to set up. Homeway has a [Privacy Commitment](https://help.homeway.io/privacy) to protect your data.

Setting up the Homeway Gemini Custom App will make your Home Assistant available to Gemini wherever you are, no matter where you are, on your phone, desktop, or away from home.

### Set up Your Home Assistant Gemini Custom App

The Homeway Gemini Custom App must be set up in the desktop app or desktop web browser, but will work on all platforms Gemini supports.

1. Open the Gemini desktop app or website in your browser.
2. Click the settings gear icon and then select "Connected Apps"
3. Scroll to the bottom and select "Add a custom app"
4. Enter the MCP server URL: `https://octoeverywhere.com/api/mcp`
5. Click Next
6. Approve the permissions

<Tip>
  Sometimes the Gemini Custom App setup will fail, saying something about a linked account being required. Simply retry a few times, and the error will resolve itself.
</Tip>

Be sure to check out Homeway's other awesome Home Assistant cloud tools like [free remote access](https://homeway.io/?source=help_mcp_gemini), [Sage AI](https://homeway.io/sage-ai?source=help_mcp_gemini), [Google and Alexa support](https://homeway.io/?source=help_mcp_gemini), and more!


# ChatGPT Plugin for Home Assistant
Source: https://help.homeway.io/help-docs/home-assistant/remote-mcp/openai-chatgpt-plugin



[Homeway provides a free ChatGPT Plugin for Home Assistant](https://homeway.io/mcp?source=help_mcp_chatgpt). It's secure and private by default and is extremely easy to set up. Homeway has a [Privacy Commitment](https://help.homeway.io/privacy) to protect your data.

Setting up the Homeway ChatGPT Plugin will make your Home Assistant available to ChatGPT wherever you are, no matter where you are, on your phone, desktop, or away from home.

### Set up Your Home Assistant ChatGPT Plugin

1. Open ChatGPT and go to **Settings** > **Apps** > **Advanced Settings**.
2. Turn on **Developer Mode**.
3. Click **Create App**.
4. Enter the MCP server URL: `https://homeway.io/api/mcp`
5. Save the configuration and follow the prompts to complete OAuth sign-in and authorization.

Be sure to check out Homeway's other awesome Home Assistant cloud tools like [free remote access](https://homeway.io/?source=help_mcp_chatgpt), [Sage AI](https://homeway.io/sage-ai?source=help_mcp_chatgpt), [Google and Alexa support](https://homeway.io/?source=help_mcp_chatgpt), and more!


# General Setup Guide
Source: https://help.homeway.io/help-docs/home-assistant/remote-mcp/setup-guide



[Homeway provides a free cloud MCP server for Home Assistant](https://homeway.io/mcp?source=help_mcp_claude), usable by any AI assistant or agent that supports MCP. It's secure and private by default, and is extremely easy to set up. Homeway has a [Privacy Commitment](https://help.homeway.io/privacy) to protect your data.

<Tip>
  [Check out all of our remote MCP server features here!](https://homeway.io/mcp?source=help_mcp_features)
</Tip>

Homeway's remote MCP server works with any AI assistant or agent that supports remote MCP HTTP servers and OAuth authentication. We designed our server to be as compatible as possible.

[We have custom guides for the top AI clients like ChatGPT, Claude, and Gemini here.](/help-docs/home-assistant/remote-mcp/free-remote-mcp-server)

### Set up Your Home Assistant Remote MCP

1. Go to the MCP server configuration/settings in your AI tool or agent.
2. Use the following URL as the remote MCP server URL.
   1. [https://homeway.io/api/mcp](https://homeway.io/api/mcp)
3. If needed, select an HTTP transport and OAuth authentication.
   1. Note that no other OAuth authentication details are required; the client will automatically discover them.
4. Add the MCP server.
5. Use the authentication flow to log in to your Homeway account.
6. Done!

Be sure to check out Homeway's other awesome Home Assistant cloud tools like [free remote access](https://homeway.io/?source=help_mcp_general), [Sage AI](https://homeway.io/sage-ai?source=help_mcp_general), [Google and Alexa support](https://homeway.io/?source=help_mcp_general), and more!


# VS Code MCP for Home Assistant
Source: https://help.homeway.io/help-docs/home-assistant/remote-mcp/vs-code



[Homeway provides a free cloud MCP server for Home Assistant](https://homeway.io/mcp?source=help_mcp_vscode), usable by any AI assistant or agent that supports MCP. It's secure and private by default, and is extremely easy to set up. Homeway has a [Privacy Commitment](https://help.homeway.io/privacy) to protect your data.

Setting up your Home Assistant MCP server integration in Visual Studio Code lets you query your home's state and interact with it directly from VS Code.

### Set up Your Home Assistant MCP VS Code Server

1. Open Visual Studio Code
2. Click on the search bar at the top, enter `> mcp:add server`
3. Select the HTTP transport.
4. Enter the following URL and press Enter.
   1. [https://homeway.io/api/mcp](https://homeway.io/api/mcp)
5. Name your Home Assistant MCP server whatever you wish, then press enter.
6. Select to add the MCP server to the Global space.
7. VS Code will show you the MCP json config file and then will prompt you to authenticate the MCP server with Homeway.
8. Select "Allow" on the authentication prompt.
9. Select "Open" on the external website prompt.
10. Log in to Homeway
11. Done!

Be sure to check out Homeway's other awesome Home Assistant cloud tools like [free remote access](https://homeway.io/?source=help_mcp_claude), [Sage AI](https://homeway.io/sage-ai?source=help_mcp_claude), [Google and Alexa support](https://homeway.io/?source=help_mcp_claude), and more!


# Sage AI Wyoming Setup
Source: https://help.homeway.io/help-docs/home-assistant/sage-ai-wyoming-setup



Usually, the Sage AI setup is as easy as clicking the Add button on a discovered service. But sometimes, Home Assistant fails to find the Sage protocol integration, or it might have been ignored in the past.

Here's how to manually set up your Sage Home Assistant Integration:

1. Go to your Home Assistant dashboard.
2. Go to the Home Assistant settings.
3. Select "Devices & Services" in the settings list.
4. On the "Integration" tab (the default view), click the "Add Integration" button at the bottom right of the screen.
5. Search for "Wyoming Protocol" and select the icon with the buffalo.
6. In the "Host" text box:
   1. If your Homeway add-on is running in Home Assistant's add-on system, enter "127.0.0.1".
   2. If your Home Assistant add-on is standalone or a Docker container, enter the device's IP address running the add-on.
7. In the "Port" text box, enter "11027"
8. Select "Submit" and the Wyoming integration should find the Sage service. Follow the guide to finish the integration setup.

Once the integration is ready, set up your Home Assistant Assist or Voice! [Here's a complete guide.](https://blog.homeway.io/homeway-sage-free-private-intelligent-chatgpt-for-home-assistant-assist-voice/)


# Free WebRTC For Home Assistant
Source: https://help.homeway.io/help-docs/home-assistant/web-rtc/free-webrtc-for-home-assistant-stun-and-turn



Homeway is proud to offer free WebRTC servers for all Home Assistant users. We offer free access to both our STUN and TURN servers, which are two protocols WebRTC uses to establish secure streaming connections remotely. For full details, [see our announcement blog](https://blog.homeway.io/free-webrtc-video-streaming-for-home-assistant/).

<Tip>
  WebRTC is end-to-end encrypted; Homeway never has access to your video and audio stream.
</Tip>

### WebRTC Setup In Home Assistant

**The easiest way to set up WebRTC in Home Assistant is with our free Homeway add-on.** It takes about 20 seconds to install and automatically configures Home Assistant to use our free WebRTC servers.

You can also manually configure WebRTC for Home Assistant in your configuration.yaml file. [Here's our guide on how to do that.](/help-docs/home-assistant/web-rtc/webrtc-camera-streaming-manual-configuation)

### Free WebRTC STUN Servers For Home Assistant

STUN is a lightweight protocol used by WebRTC to help open ports and find your public IP address. Homeway is proud to offer **free and unlimited** access to our STUN servers to the entire Home Assistant community!

**Homeway's Free WebRTC STUN Servers:**

* `stun:webrtc.homeway.io:443`
* `stun:webrtc.homeway.io:80`
* `stun:webrtc.homeway.io:53`

### Free WebRTC TURN Servers For Home Assistant

TURN is a relay protocol that WebRTC uses as a fallback if it can't establish a direct connection. Turn servers require much more bandwidth and are thus more expensive to operate, but we offer everyone limited free use.

Since TURN servers are open to the public internet, anonymous use must be limited to prevent abuse. We offer even higher limits to users with free Homeway accounts, since those accounts can generate TURN username and authentication credentials.

**Homeway's Free WebRTC STUN Servers:**

* `turn:webrtc.homeway.io:443?transport=udp`
* `turn:webrtc.homeway.io:3478?transport=tcp`
* `turns:webrtc.homeway.io:443?transport=tcp`

Enjoy free access to our Homeway WebRTC server and consider joining our amazing community of Home Assistance users!

[Learn more about Homeway.](https://homeway.io/?source=help_webrtc_free)


# Manual Configuration
Source: https://help.homeway.io/help-docs/home-assistant/web-rtc/webrtc-camera-streaming-manual-configuation



<Tip>
  If you're using the Homeway add-on for Home Assistant, there's no configuration needed! The add-on will automatically configure Home Assistant to use Homeway's WebRTC servers.
</Tip>

If you are using the standalone Homeway add-on for Home Assistant, your add-on might not have access to the Home Assistant YAML configuration file, which is needed to enable WebRTC camera streaming. But you can easily manually add the required WebRTC configuration!

### Get Access To The Home Assistant Configuration File

[Follow this guide to get access to the configuration.yaml file.](/help-docs/home-assistant/accessing-home-assistant-config-configuration-yaml-file)

### Find Your Unique WebRTC Username and Credential

WebRTC TURN servers require authentication to use them, so you must get your Homeway WebRTC username and credentials. The username and credentials can be found in two places.

1. The Homeway Add-On Logs
   1. Access the add-on logs via the log file or the Docker log viewer (if running in Docker) and search for webrtc. You will find a printout that shows your username and credentials.
2. The Homeway Config File
   1. Access your Homeway configuration file `homeway.conf` and look for the WebRTC section. This section will list your username, credentials, and the current Homeway WebRTC servers.

### Update the Home Assistant Configuration For WebRTC

Once you have access to the Home Assistant YAML configuration  file and have your Homeway username and secret, add this block to your Home Assistant configuration.

```yaml theme={null}
web_rtc:
  ice_servers:
    - url:
        - "stun:stun.cloudflare.com:3478"
        - "stun:stun.cloudflare.com:53"
        - "stun:webrtc.homeway.io:443"
    - url:
        - "turn:webrtc.homeway.io:443?transport=udp"
        - "turn:webrtc.homeway.io:3478?transport=udp"
        - "turn:webrtc.homeway.io:3478?transport=tcp"
        - "turn:webrtc.homeway.io:80?transport=tcp"
        - "turns:webrtc.homeway.io:443?transport=tcp"
        - "turns:webrtc.homeway.io:5349?transport=tcp"
      username: "<your Homeway username>"
      credential: "<your Homeway credential>"
```

Be sure to update your username and credentials, restart Home Assistant, and you're good to go!


# Welcome
Source: https://help.homeway.io/knowledge-base/welcome



Welcome to the Homeway knowledge base. Unlike the [help docs](/help-docs/getting-started/introduction), the intention is to build a collection of facts that search engines or LLM agents can easily index and use to provide answers.

**We recommend using the search feature or our AI chatbot to find what you're looking for.**

Happy Exploring!


# Homeway's Commitment to Privacy
Source: https://help.homeway.io/privacy



Secure Home Assistant remote access is useless without strong data privacy. Our goal at Homeway is to empower the Home Assistant community with free, secure, and private remote access. We can't do that without a strong commitment to data privacy.

<Check>
  Our privacy commitment is simple. **We don't store or sell any of your Home Assistant data.** All remote access data is tunneled through our services and then deleted.
</Check>

Information **we do not store** includes:

* Home Assistant website information.
* Home Assistant home state information.
* Your Home Assistant credentials.
* Your Home Assistant logged-in session data.
* Any other private Home Assistant data.

To operate the service, we need to store data like your login email and password. We purposefully collect only the minimum amount of information to establish and secure your account.

We store your account information as securely as possible. For details, read our [Security Page.](https://help.homeway.io/security)

For full privacy details, please read our [Privacy Policy](https://homeway.io/privacy?source=help_privacy). If you have any questions, concerns, or feedback, please [contact us.](https://homeway.io/support?source=help_privacy)

### Ready to get started?

[Create your free Homeway account now.](https://homeway.io/getstarted?source=help_privacy)


# Homeway's Commitment To Security
Source: https://help.homeway.io/security



We are committed to building Homeway with the strongest possible security.

We make Homeway for the Home Assistant community, and our only goal is to provide a fantastic, private, and secure remote access solution. Security is the first consideration for every new feature; if we can't build it securely, we don't.

<Check>
  **Homeway never sells or stores your Home Assistant information.** This includes any data tunneled through our servers for remote access; once it's been relayed, it's deleted. Read our [<u>Privacy Commitment.</u>](https://help.homeway.io/privacy)
</Check>

This page covers the security that protects your Home Assistant remote access. We are a community-driven project; if you have any questions, concerns, or clarifications, don't hesitate to [contact us directly.](https://homeway.io/support?source=help_security)

## **Overview**

Let's start with a quick overview of the security model behind Homeway. After that, we will do a deep dive into each component and detail as much information as possible.

### **👩 Accounts**

Security starts with your account. We encourage users to set strong passwords when creating accounts. We offer Google and Apple as 3rd-party login providers, leveraging their account security measures as the first line of defense. Adding another layer of security, Homeway will require an emailed code challenge for any login from a new IP address. Finally, we optionally offer a code-based 2-factor login challenge that can be enabled on any account.

### **💻 Servers**

Next, server security. When your browser communicates with our services, it uses the latest web security standard, TLS 1.3. This is the same tech used by your bank, government websites, and online retailers. Our SSL certificates are minted by Let's Encrypt from a bot running on each server. [We have achieved an A+ security rating with our server and SSL configuration.](https://www.ssllabs.com/ssltest/analyze.html?d=sfo.homeway.io) The certificates are created and used per server and never leave the servers. We strive to stay up to date on the latest web server security best practices. For example, we use just-in-time access, require [HSTS](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security) and HSTS preloading, and bug bounty programs, just to name a few. For a full list, see the details below.

### **🏠 Add-on For Home Assistant**

Moving on to our Home Assistant add-on. Our Homeway add-on connects to our worldwide server network via the same TLS connection your web browser uses. This connection is established using a secure WebSocket from the add-on, meaning no port forwarding or mapping is required. Your home router, Home Assistant server, and device **are not** exposed to the public internet in any way.

As part of the WebSocket handshake, we take security even further. The add-on generates a random challenge and sends it to the server. The server must sign and return the challenge with its private key, allowing the add-on to verify the signature with the public key. If the challenge fails, the add-on will not connect to the server. While this has some redundancy with the TSL WebSocket connection, if a bad actor were able to generate a valid [homeway.io](http://homeway.io) certificate or gain control of the homeway domain, the bad actor wouldn't have the server's private key, so add-ons won't connect.

### **🚀 End-To-End Remote Access**

Finally, the end-to-end picture. We use multiple layers of security to provide the best possible protection. First, when your browser makes a request to our Homeway servers, the server verifies that you're logged in and that your session credentials are valid. Thus, your user account strength is the first security layer for all remote access. Next, the request is tunneled from our servers to our add-on. Our add-on makes requests to Home Assistant the same way your browser would if the browser were on your local network. The second layer of security is the Home Assistant user login system.

***Homeway does not store any information on our servers, including your password or any of your logged-in user session information from Home Assistant.*** Meaning that even if someone had your Homeway user information and logged in to your Homeway account, they would still need to log in to your Home Assistant server to access it.

### **🥰 Summary**

Our remote access solution elegantly provides robust security while offering incredible convenience. Our service has been built with the community's feedback and hundreds of engineering hours. We are incredibly proud of what we have made, but there's always room for improvement. If you have any ideas, concerns, or feedback on how we could improve, please contact us directly; we would love to hear from you.

### 🚀 Ready To Get Started?

[Create your free Homeway account now](https://homeway.io/getstarted?source=help_security) and install our Home Assistant app!

## **🪸 Deep Dives**

The deep dives on each technical section of our server are coming soon. It took a lot of effort just to write this much! 🙌