Send a Pushover notification from a Link’nX scenario

A Pushover action in Link’nX sends a notification text to one or more declared Pushover accounts. Added to a scenario, for example with a KNX trigger, it alerts the recipients in the Pushover app when an event occurs on the installation.

Intended for the administrator or installer. First declare the Pushover account or accounts in the right project and the right gateway. Saving the action does not trigger sending: launching the scenario is what requests it.

Create the Pushover action

1. Open Actions → Add, then choose Pushover.
2. Fill in Name, required, for example Fictitious information.
3. In Pushover account, select at least one declared account. You can select several or use Select all. Review the recipients before saving.
4. In Notification text, write the message, for example Demonstration event, a fictitious text to adapt. The form accepts an empty text, but a notification without text is not usable: always enter an explicit message.
5. Click the floppy disk at the bottom right, wait for Success!, then find the action in the list.

The form offers no emergency priority, no repetition until acknowledgment, no sound, no attachment and no choice of a particular phone within an account. Nor does it document a variable format for inserting a dynamic value into the text. For any of these needs, or for a specific delivery delay, have the available path confirmed by support rather than guessing a syntax.

Send the notification from a scenario

1. Add the action to the appropriate scenario.
2. Configure the scenario’s triggering as needed. To start from a bus event, use a KNX trigger: the Pushover declaration has no KNX gateway table for the text.
3. Save the scenario. Its authorized launch requests that the text be sent to the selected accounts.

Edit the action or stop sending

To edit or duplicate the action, follow the action editor, then check Name, the accounts and the text. Deleting the configuration does not recall a message already received. To prevent future sending, adjust the automation concerned following its guide rather than deleting the keys at random.

Check the result

Success! confirms that the action is saved. To check sending, cause the planned triggering during an authorized test, then check delivery in each recipient’s Pushover app. Neither saving nor the end of the scenario counts as a delivery receipt.

Troubleshooting

If no notification arrives:

1. Check the project, the gateway and the action used by the scenario.
2. Check that at least one Pushover account is selected and that Notification text contains the intended message.
3. Check that the action and the scenario have been saved and that the expected triggering actually took place. An action that is not used in any scenario sends nothing: the linked scenarios check shows where it is used.
4. With the person responsible for the installation, check the provider account and the receipt of notifications in the Pushover app. A save in Link’nX does not prove that the keys are accepted.

If only one destination is missing among several, note which named account is concerned and the tests already carried out.

Contact support

If these points have already been checked, write to support@can-nx.com with the Link’nX context, the name of the action, the time of the test, the symptom, the account concerned and the checks already done. Do not attach the user key, the API key or sensitive private text.

French labels: Compte Pushover, Tout sélectionner, Texte de la notification, Nom, Actions and Ajouter.