Device Integrations

Home Assistant TV and Wearable Integrations: LG webOS, Roku and Fitbit

Set up LG webOS and Roku TVs in Home Assistant, learn why webOS TVs need Wake on LAN, and check the current status of Fitbit before you start.

On this page
  1. LG webOS TVs
  2. Roku
  3. Fitbit

TVs and wearables are some of the more fun Home Assistant integrations, but each has its quirks. LG webOS and Roku are local integrations. Fitbit is different: its data goes through the cloud, and its setup has changed recently.

LG webOS TVs

Connect the TV

  1. On the TV, turn on the LG Connect Apps setting in the network options. The menu name varies by model and webOS version.
  2. In Home Assistant, go to Settings > Devices & services > Add integration and select LG webOS TV. Home Assistant usually discovers the TV on its own. If it doesn’t appear, enter the TV’s IP address.
  3. Accept the pairing prompt on the TV screen. The TV needs to be on for this step.

The integration connects to the TV over its local network, on port 3000, or port 3001 for SSL.

Turn the TV on from automations

A webOS TV’s network interface sleeps when the TV is off. Once the TV is off, Home Assistant can’t reach it, so it can’t turn the TV back on by itself. You need a separate power-on method:

  • Turn on Turn on via Wi-Fi or Mobile TV On in the TV’s settings. The name varies by model.
  • Set up Wake on LAN for the TV, and use the webOS turn on device trigger in your automations.

Wake on LAN is generally more reliable over Ethernet than over Wi-Fi.

Community members report that calling wake_on_lan.send_magic_packet directly in your turn-on automation works more reliably than using a Wake on LAN button entity. Test it with your own TV, because results vary.

What you can control

  • A media player entity, with volume, source, channel and playback controls
  • On-screen notifications
  • Actions such as webostv.button, webostv.command and webostv.select_sound_output

Browsing the TV’s media from Home Assistant wasn’t supported in the GitHub issues we reviewed, so check the current integration page before you rely on it.

For deeper controls, such as picture settings, pointer input or push-based state updates, a community project called ha-lg-webos-tv builds on a separate library. It’s a custom integration, so treat it as an add-on choice.

Updating webOS

Install software updates from the TV’s own settings menu. The Home Assistant integration doesn’t take the place of that.

Roku

Roku’s core integration talks to the Roku over its External Control Protocol (ECP) on TCP port 8060. Discovery uses SSDP.

  1. On the Roku, go to Settings > System > Advanced system settings and open Control by mobile apps. Set the network access option to allow control. Menu names vary by model.
  2. In Home Assistant, go to Settings > Devices & services > Add integration and select Roku. If auto-discovery fails, enter the Roku’s IP address.

No Roku account login is needed. The integration adds a media player entity and a remote entity. Use remote.send_command with ECP keys such as Home, Select, Up and Back.

Roku TVs can power on over the network if Fast TV start is enabled. Roku streaming sticks don’t have a true off state, so the integration can’t fully power them down.

Fitbit

Check the current setup first

Fitbit’s integration is in transition. Google has been moving Fitbit accounts and data to Google Health, and older setup routes may no longer work. Home Assistant has added a Google Health integration in recent releases. Check the current integration page in Home Assistant before you start, because the older steps below may not apply to your account.

Legacy steps

If your Home Assistant still offers the older Fitbit integration, the setup uses Fitbit’s Web API:

  1. Create a “Personal” app at dev.fitbit.com.
  2. Add the app’s client ID and secret under Application Credentials in Home Assistant.
  3. Add the Fitbit integration and sign in with your Fitbit account.

Reports indicate that Google has turned off the legacy API, which can return a 410 Gone error. If you see that error, switch to the Google Health integration.

What Fitbit data gives you

  • The legacy integration exposes steps, resting heart rate, sleep, activity minutes and device battery. The newer integration’s metrics may differ, so check its page.
  • Fitbit data isn’t real time. Devices sync on a schedule, so don’t build second-by-second automations on it.
  • The legacy API limited requests to about 150 per hour per user. Keep polling intervals modest.

Wear OS companion app

A companion app on a Wear OS watch can expose heart rate and steps directly to Home Assistant. Check the app’s documentation for setup, because it doesn’t depend on Fitbit’s sync schedule.

How Fitbit connects

Fitbit trackers don’t connect to Home Assistant on their own. Data reaches Home Assistant through Fitbit’s or Google’s cloud services, or through a phone app that shares it.

For how integrations, devices and entities fit together, see adding and managing devices in Home Assistant. If you’re also connecting a garage door or other appliances, connecting appliances to Home Assistant covers those.

The complete guide to device integrations

Adding and Managing Devices in Home Assistant: Integrations and Device Classes
Read the guide

Keep exploring

Guides from other topics

All topics →