HA LG Manager

Home Assistant custom integration for managing LG webOS TVs during network migrations and ongoing office operations.

What it does

• Discovers LG TVs over SSDP on the local network.
• Optionally reads a firewall/export CSV as extra discovery input.
• Optionally reads live Meraki client data from the Dashboard API.
• Reconciles discovered TVs against Home Assistant webostv config entries.
• Exposes Home Assistant entities for summary, per-TV reconciliation state, and manual refresh.
• Keeps live office state out of the repository by using optional local hints in /config.

Current scope

This first version focuses on discovery and reconciliation:

• one integration config entry
• one refresh button
• one discovery sweep button
• one summary sensor
• one sensor per configured LG TV

The integration does not modify Home Assistant .storage. It can inspect current wake-related automations and scripts and can trigger those existing entities during a discovery sweep.

Installation

HACS custom repository

1. Add this repository as a HACS custom integration repository.
2. Install HA LG Manager.
3. Restart Home Assistant.
4. Add the integration from Settings -> Devices & Services.

Manual install

Copy custom_components/lg_tv_manager into /config/custom_components/lg_tv_manager.

Local files

The integration can use local, non-public operator data in /config, but it no longer requires inventory to function.

• Optional inventory file: default /config/lg_tv_manager.yaml
• Optional firewall CSV: configured in the integration options
• Optional Meraki API URL and API key: configured in the integration UI and stored privately in Home Assistant config storage

See examples/lg_tv_manager.example.yaml for the public-safe inventory format.

Inventory model

Each TV entry can define optional hints:

• canonical room title
• expected Home Assistant entity ID
• name hints for matching
• expected source
• optional wake automation aliases

No IPs, MACs, or office-specific live data need to be committed. Meraki can act as the main candidate source while inventory remains an optional enhancement layer.

Meraki support

If you use Cisco Meraki for client visibility, you can provide:

• a full clients API URL, for example https://api.meraki.com/api/v1/networks/<network_id>/clients?timespan=86400&perPage=1000
• an API key in the integration options

The API key is intended to be stored in Home Assistant's config entry storage, not in this repository.

For mostly-off TVs, use a longer timespan than one day. A 24 hour window can miss devices that still appear in the Meraki dashboard client view but have not been seen recently.

Discovery sweep

The integration provides an LG TV Manager Discovery Sweep button entity.

When pressed, it:

1. builds wake targets from all current Meraki-discovered LG-like candidates
2. sends Home Assistant WOL packets for those candidates when MAC and broadcast information are available
3. optionally triggers known wake automation/script aliases from the optional inventory when Enable legacy wake automation/script aliases is turned on
4. waits briefly
5. refreshes live discovery and reconciliation

This is intended for cases where most TVs are normally off and Meraki acts as the candidate source while SSDP/webOS provides the live identity after wake.

By default, the sweep does not depend on manually maintained wake automations.

Live configuration inspection

The integration already inspects current live Home Assistant webostv config entries. It also reads:

• /config/automations.yaml
• /config/scripts.yaml

to surface current wake-related configuration on the summary and per-TV diagnostic entities.