Repository navigation
FAQ
Use username admin and the Deco owner account password. A manager account does not work with the local web API.
Yes, but use a separate manager account for daily app access. Logging in as the owner can invalidate Home Assistant's local session.
Use the exact address that opens the main Deco web interface. Include the scheme. When HTTPS uses a self-signed certificate, disable certificate verification in the integration form.
Traffic remains encrypted, but Home Assistant no longer verifies that the certificate was issued by a trusted authority. This is commonly necessary for self-signed certificates on local routers. Only connect to the expected local Deco address on a trusted network.
No. WiFi status is read-only because local write endpoints are not reliable across models and firmware versions.
Home Assistant can combine devices that share the same MAC address. Disable Link client trackers to devices by MAC address if you want Deco client trackers kept separate.
Home Assistant disables some diagnostic or optional entities by default. Open the device's entity list and enable the entity manually. Main WiFi status is intentionally disabled by default.
It is created only when supported cellular Deco firmware exposes the required endpoint.
The integration normally queries clients per Deco node. It can use a bounded global fallback when all per-node requests fail and periodically probes per-node mode again.
Increase the polling interval. If device_list affects wireless backhaul, increase the separate Deco status interval or set it to 0, then use Refresh Deco status only when needed.
No. It stops scheduled updates while keeping entities and the session loaded. Resume polling with the switch or tplink_deco.resume_polling.
Under <config>/tplink_deco_logs. The router log is not automatically redacted.
Yes, since v3.15.0. Enable forwarding in the entry's integration options and configure the receiver host, port and UDP/TCP protocol. It is off by default. See Syslog.
No. Each poll forwards at most the newest 1,000 new lines and skips older excess lines. UDP delivery is best effort; TCP retries can duplicate partially delivered data. Use manual download when you need the full log currently retained by the router.
No. Use a trusted local receiver and inspect output before sharing. Raw logs can contain authentication-related protocol data, not just network identifiers.
The first successful download records the current position without sending old history. Wait for a subsequent poll and confirm new router log events exist. Check the exact receiver port and protocol as well as firewall/VPN restrictions.
The fix was merged after beta.2. Install stable v3.15.0 or newer and restart Home Assistant. Historical warnings may remain visible; compare their timestamps.
That strongly suggests a firmware-side client database or API problem. Reboot the mesh, check for firmware updates, and contact TP-Link when both interfaces remain incorrect.
Normal updates should preserve unique IDs. Always back up Home Assistant before major updates. Report duplicate or renamed entities with entity-registry details and diagnostics.
Follow Diagnostics-and-Bug-Reports. Include evidence from the current release rather than logs from an old local copy.