- Home
- Integrations by brand
- Pushover
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
Section titled “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 |
| Write the message and choose the recipient accounts | Pushover action | Prepare a Pushover notification |
| Send the notification on a KNX event | Scenario with a KNX trigger | Create a KNX trigger |
| Find out why no notification arrives | Action, scenario and provider account | Diagnose missing notifications |
Step-by-step commissioning
Section titled “Step-by-step commissioning”- On pushover.net, 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.
- Declare the account in Other → Pushover, then review it with Edit.
- Create the Pushover action: Name, one or more accounts in Pushover account and Notification text.
- Add the action to a scenario, with a KNX trigger if sending starts from the bus, then save the scenario.
- 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 gives the order of the checks.
Good to know
Section titled “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.