Reconnect wireless client

The Reconnect wireless client action forces a Wi-Fi client to reconnect to your Omada network. This is useful when a client has a troublesome connection that needs to be reset.

This action does not target an entity. Instead, you select which Omada controller to use and provide the MAC address of the client you want to reconnect.

Using this action from the user interface

If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.

To reconnect a wireless client from an automation or a script:

1. Go to Settings > Automations & scenes.
2. Open an existing automation or script, or select Create automation > Create new automation.
3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
4. In the Then do section, select Add action.
5. From the search box, search for and select TP-Link Omada: Reconnect wireless client.
6. Enter the MAC address of the client you want to reconnect. If you have more than one Omada controller, also select the Omada controller to use.
7. Select Save.

Options in the UI

Using this action in YAML

If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.

In YAML, refer to this action as tplink_omada.reconnect_client. A basic example looks like this:

action: tplink_omada.reconnect_client
data:
  mac: "01:23:45:67:89:AB"

This forces the client with the given MAC address to reconnect to the network.

Options in YAML

Try it yourself

Ready to test this? Open Developer tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.

More examples

Real scenarios where this action shows up in automations and scripts. Copy any example and adapt it to your setup.

Automation: Reconnect a device when it goes unavailable

This automation forces a wireless client to reconnect to your Omada network whenever a device that depends on it becomes unavailable for a few minutes, which can recover a stuck Wi-Fi connection.

• Trigger: the device’s entity stays unavailable for 5 minutes
• Action: TP-Link Omada: Reconnect wireless client
  • MAC address: the client’s MAC address

alias: "Reconnect stuck Wi-Fi device"
triggers:
  - trigger: state
    entity_id: sensor.garage_sensor_signal
    to: "unavailable"
    for:
      minutes: 5
actions:
  - action: tplink_omada.reconnect_client
    data:
      mac: "01:23:45:67:89:AB"

Still stuck?

The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.