---
title: "Pushover KNX integration: notifications with Link’nX"
description: "Send Pushover notifications from Link’nX scenarios and KNX events: accounts, message text, recipients and diagnosis of missing notifications."
canonical: https://wiki.can-nx.com/en/integrations/pushover/
language: en
---

# Pushover KNX integration: notifications with Link’nX

Link’nX sends Pushover notifications from the installation’s scenarios. A KNX event or another trigger starts the scenario, whose action sends a text to one or more declared Pushover accounts. This page sums up the steps, from declaring the account to diagnosing a missing notification.

## What the Pushover integration does

| Need | Where to configure it | Guide |
| --- | --- | --- |
| Save a recipient account with its user key and API key | **Other → Pushover** | [Declare a Pushover account](https://wiki.can-nx.com/en/guides/link-pushover-device/) |
| Write the message and choose the recipient accounts | **Pushover** action | [Prepare a Pushover notification](https://wiki.can-nx.com/en/guides/link-pushover-action/) |
| Send the notification on a KNX event | Scenario with a **KNX** trigger | [Create a KNX trigger](https://wiki.can-nx.com/en/guides/link-trigger-knx/) |
| Find out why no notification arrives | Action, scenario and provider account | [Diagnose missing notifications](https://wiki.can-nx.com/en/guides/link-pushover-action/) |

## Step-by-step commissioning

1. [On pushover.net](https://wiki.can-nx.com/en/guides/link-pushover-device/), note the account’s user key and create the application that provides the API key. If the Pushover entry is missing, check the context and options with [Link’nX navigation](https://wiki.can-nx.com/en/guides/link-navigation/).
2. [Declare the account](https://wiki.can-nx.com/en/guides/link-pushover-device/) in **Other → Pushover**, then review it with **Edit**.
3. [Create the Pushover action](https://wiki.can-nx.com/en/guides/link-pushover-action/): **Name**, one or more accounts in **Pushover account** and **Notification text**.
4. Add the action to a scenario, with a [KNX trigger](https://wiki.can-nx.com/en/guides/link-trigger-knx/) if sending starts from the bus, then [save the scenario](https://wiki.can-nx.com/en/guides/link-scenario-save/).
5. Trigger a test and check that the notification is received in the recipient’s Pushover app.

If nothing arrives, the “Troubleshooting” section of the [Pushover action guide](https://wiki.can-nx.com/en/guides/link-pushover-action/) gives the order of the checks.

## Good to know

- **User key** and **API key** are both required and are not interchangeable. The Link’nX form does not create a provider account.
- An action can target several accounts, or all of them with **Select all**. Always fill in the text: the form accepts an empty text, which is not a usable notification.
- The action offers no emergency priority, repetition until acknowledgment, sound, attachment or choice of a particular phone within an account.
- The Pushover declaration has no KNX gateway table: the link with the bus goes through the scenario’s trigger.
- Saving the account or the action sends nothing and does not prove that Pushover accepts the keys.

To build triggers, conditions and actions, see [Scenarios and commands](https://wiki.can-nx.com/en/usages/automatismes/).

## All Pushover guides

### Devices and integrations

- [Send a Pushover notification from a Link’nX scenario](https://wiki.can-nx.com/en/guides/link-pushover-action/)
- [Declare a Pushover account in Link’nX: user key and API key](https://wiki.can-nx.com/en/guides/link-pushover-device/)