Actions and triggers
Actions
Add these to an action group, a schedule or a trigger. They are under Device Actions in the UniFi Health section of the action list.
| Action | What it does |
|---|---|
| Restart Access Point | Tells the controller to restart the access point you choose. Devices on it drop off for a minute or two and reconnect. |
| Locate Access Point (flash LED) | Makes the access point’s light flash so you can pick it out, which helps when several look the same. |
| Stop Locating Access Point | Stops the flashing. |
| Set Access Point Transmit Power | Sets one band (2.4, 5 or 6 GHz) on the access point you choose to Auto, Low, Medium, High, or Custom with a figure in dBm. The access point restarts that radio, so its devices reconnect within a minute or two. The plugin reads the setting back and says in the Event Log whether the controller kept it. A band you have switched off is left off. |
| Refresh UniFi Data Now | Checks the controller straight away rather than waiting for the next check. |
These four access point actions change something on the controller, so the account the plugin signs in with must be allowed to manage devices. The Event Log says whether each one was sent, and gives the controller’s reply if it was turned away.
Send Status Request on an access point or a UniFi WiFi Client also checks the controller straight away.
A Geofence Switch answers Indigo’s standard Turn On, Turn Off and Toggle, which is how Apple Home switches it. It only changes its own state.
Triggers
To use one, create a new trigger, set its type to UniFi Health, and choose the event. Then add whatever you want to happen.
| Trigger | When it runs |
|---|---|
| An Access Point Rebooted | Once, when the plugin sees an access point has restarted. |
| The UniFi Controller Became Unreachable | At each check while the controller device shows Unreachable. A controller that was Connected only turns Unreachable after three checks in a row get no answer. |
| Config Audit Found an Issue (wrong setting / over-powered AP) | Once, when the settings check finds a problem on an access point that it had not found before. It does not run again while the problem stays, or when the plugin restarts. A busy channel is left to the next trigger. |
| An AP Band Went Over the Utilisation Threshold | Once, when a band on an access point has been busier than the Utilisation warning threshold setting, on average, over the last 15 minutes. It can run again once that average has dropped 10 points below the threshold. |
| WLAN Subsystem Health Not OK | At each check while UniFi’s own verdict on your Wi-Fi is anything other than ok. |
| A Tracked Client Arrived (presence became home) | When a UniFi WiFi Client device changes from away to home. |
| A Tracked Client Left (presence became away) | When a UniFi WiFi Client device changes from home to away. |
| A Client Dropped Below the Satisfaction Threshold | At each check while a UniFi WiFi Client device is connected with a satisfaction score below the Satisfaction warning threshold setting. |
These triggers do not say which device caused them. Where that matters, use one of Indigo’s own device state triggers instead, which you can point at a single device — for example a trigger on an access point’s Device State, or on a client’s Presence (home/away) becoming away. The Event Log names the access point and the problem each time one of the two settings check triggers runs.
Other useful device state triggers
Every state on the Your devices page can be used in an Indigo device state trigger. A few that are handy:
- an access point’s device turning off, which happens once it has been away for longer than the AP offline grace setting
- the controller’s APs Needing Firmware Update going above zero
- an access point’s Uplink Below Capability becoming true
- the controller’s WAN/Internet Status changing from ok
Raising or lowering an access point’s power
More power is not always better. On 2.4 GHz, a loud access point makes devices cling to it when a nearer one would serve them better, and it adds to the noise every other access point has to work through. The settings check flags 2.4GHz TX power High for that reason.
Raise it when a device that cannot move has a weak signal from the nearest access point. Remember that this only makes the access point louder: a small device such as a smart plug still sends back at its own fixed power, so the link the other way does not improve. Check the device’s own signal reading afterwards, and put the band back to Auto if nothing changed.