Skip to content

Entities and Actions

dkwolf1 edited this page Nov 11, 2026 · 2 revisions

Entities and Actions

Entity availability depends on model, firmware, reported data, and whether optional entities are enabled.

Device trackers

Deco trackers

One tracker is created for each discovered Deco node. Attributes can include model, hardware and firmware versions, online state, connection type, BSSIDs, backhaul information, signal data, and parent Deco information.

Client trackers

One tracker is created for each known client. Attributes can include:

  • MAC and IP address
  • connection type and network interface
  • current upload and download rate
  • connected Deco name and identifier
  • last activity

When a client disconnects, its last descriptive attributes are retained while upload and download rates return to zero.

Sensors

Depending on available data, the integration creates:

  • total and per-Deco upload/download rates
  • connected client count
  • IP address
  • 2.4 GHz and 5 GHz BSSID
  • backhaul type, speed, and maximum speed
  • CPU usage, raw and smoothed
  • memory usage, raw and smoothed
  • mobile data usage on supported cellular Deco firmware
  • Deco and client coordinator response times
  • last successful update timestamps
  • client timeout count and query mode
  • last Deco and client errors

Most technical sensors appear in the device's Diagnostics section.

Binary sensors

  • Deco online
  • Internet online
  • Main WiFi status (disabled by default)
  • Guest WiFi status
  • IoT WiFi status

WiFi sensors are read-only. Changing WiFi state is not supported because local write endpoints are unreliable across models and firmware versions.

Controls

  • switch.deco_polling - pause or resume polling for one config entry
  • select.polling_interval - select 10, 30, 60, or 120 seconds
  • button.refresh_deco_status - refresh nodes and topology immediately

Entity IDs can differ when Home Assistant resolves naming conflicts. Use the entity registry instead of assuming an exact entity ID.

Since v3.15.0, polling switches use entry-specific unique IDs. The legacy registry entry is migrated for its owning entry so its entity ID is retained.

Actions

Pause and resume polling

action: tplink_deco.pause_polling
action: tplink_deco.resume_polling

Reboot Deco nodes

action: tplink_deco.reboot_deco
data:
  device_id:
    - 0123456789abcdef0123456789abcdef

Select actual Deco devices, not client devices.

Download the Deco system log

action: tplink_deco.download_system_log
data:
  config_entry_id: 01JABCDEF0123456789ABCDEFG
  filename: deco.log
  log_level: WARNING
response_variable: system_log

Files are saved under:

<config>/tplink_deco_logs

config_entry_id is optional when exactly one TP-Link Deco entry is loaded and required when multiple entries are loaded. A filename cannot contain a directory path.

In Developer tools > Actions, select tplink_deco.download_system_log and use the form to choose the entry. The YAML above is a script/automation action; omit response_variable in the interactive action editor. The response contains path and line_count.

Omitting filename uses deco-<timestamp>.log. An existing file with the same name is overwritten. This action downloads the router log; it is not the redacted Home Assistant diagnostics download.

The action is unavailable on legacy encrypted sessions such as the currently documented Deco S7 firmware. Router system logs are not automatically redacted; inspect them before sharing.

Automatic syslog forwarding

Forwarding is configured in the integration options, not through a new sensor or download action. It is disabled by default and supports UDP or TCP. The first successful download establishes a starting position without sending old history. See Syslog for setup, limits and tests.

Clone this wiki locally