Driver Type
Categories
- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Networking
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
Driver Type
Categories
- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Networking
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
Pushover Notifications
By: David Bowdler
Updated: July 28, 2026
Version: 0.4
Pushover Notifications
Two-way Pushover on RTI. Send rich push notifications to your phone, tablet or desktop from any macro — with a per-message alert sound, priority and optional link — and turn incoming Pushover messages into RTI events. No hardware, just a free Pushover account.
Key Features
- Send from any macro: fire a notification when an alarm trips, a door opens or a scene starts, with a title, message and five priority levels including emergency (requires acknowledgement).
- Per-message sound: choose the alert sound per notification — arm/disarm as one chime, an alarm as a siren — or set a default sound for everything.
- Targeted delivery: address your user or group key, choose from up to ten named recipients, or send to a single named device.
- Tappable link: attach a URL — a camera snapshot or a dashboard — shown as a link in the notification.
- Emergency alerts: priority-2 notifications repeat until acknowledged, with a configurable retry interval and expiry.
- Receive (optional): turn incoming Pushover messages into RTI events — a message of “event5” fires event5, anything else fires New Message — so a message on your phone can trigger any macro, scene or activity.
- Rock-solid connection: the receive channel holds a Pushover Open Client connection with a keep-alive watchdog that automatically reconnects a dropped or stalled socket.
- Web Object dashboard: on-screen status plus a test-send button, on any panel.
- Diagnostics: a built-in telnet debug console for commissioning.
Requirements
- A free Pushover account (pushover.net) — an Application API Token and your User or Group Key.
- An RTI processor with internet access (Pushover is a cloud service).
- The Pushover app on your phone, tablet or desktop to receive notifications.
How It Works
Create a free Pushover account, copy your User Key and create an Application for its API Token, then paste both into the driver. Wire the Notify functions into macros to send notifications — each can carry its own sound, target device, priority or link. To trigger RTI from your phone, turn on the optional Receive channel: any message you send back becomes an RTI event, so a Pushover message can start any macro, scene or activity. A keep-alive watchdog keeps the receive connection up for the long haul.
Pushover Notifications Driver
Version 0.4
Send push notifications from RTI to your phone, and (optionally) turn incoming Pushover messages into RTI events. Requires a free/one-time Pushover account (pushover.net).
1. Sending notifications (RTI to phone)
1. At pushover.net create an Application and copy its API Token.
2. Copy your User Key (or a Delivery Group key) from the Pushover dashboard.
3. In Driver Properties, Pushover Account: paste the Application API Token and the User or Group Key. Optionally pick a default Sound.
4. Add more people in Additional Recipients (Name + Key) if you want to address them individually.
5. Emergency Alerts: for Priority 2 (Emergency) messages you can set how often Pushover re-alerts (Retry Interval, min 30s) and when it gives up (Expire After, max 10800s / 3 hours).
2. Receiving messages (phone to RTI) - optional
This is the part most other drivers struggle to keep alive. This driver holds the connection open with a keep-alive watchdog that automatically reconnects a dropped or stalled socket.
1. In Driver Properties, Receive: tick Enable Receive.
2. Enter the Email and Password you log into pushover.net with.
3. If your account uses two-factor login, enter a current One-Time Code once (only needed at the first connect).
4. Give this processor a unique Device Name (letters, numbers, _ and - only).
On first connect the driver registers a virtual Pushover device on your account. Any message you send to that device arrives as an RTI event. A message whose text is exactly event1 ... event20 fires the matching Inbound event, so you can trigger macros from a Pushover message. Any other message fires New Message Received and fills the Last Message variables.
Functions (wire to macros)
Notify(Title, Message) - send to the default recipient.
Notify (with priority)- same, plus a Priority (-2 to 2; 2 is emergency).
Notify Recipient(Recipient, Title, Message) - send to a chosen recipient slot.
Notify Recipient (with priority)- recipient plus priority.
Notify (with sound)(Title, Message, Sound) - pick a per-message sound (e.g. Arm/Disarm = Gamelan). Sound set to (Use driver default) falls back to the Default Sound in Driver Properties.
Notify (with priority + sound)(Title, Message, Priority, Sound) - per-message sound at a chosen priority, e.g. Alarm going off = Siren at Emergency.
Notify Recipient (with sound)(Recipient, Title, Message, Sound) - per-message sound to a chosen recipient.
Notify (with sound + device)(Title, Message, Sound, Device) - also target one named Pushover device (e.g. Office). Device left blank falls back to the Target Device in Driver Properties.
Notify (with link)(Title, Message, Link URL, Link Title) - adds a tappable link to the notification (e.g. a camera snapshot or dashboard URL).
Send Test Notification- quick check.
Receive - Start / Stop / Reconnect- control the inbound channel.
Print Status- dump status to TraceView / debug console.
Events
Receive Connected / Disconnected; New Message Received; Inbound event1 ... event20; Send Succeeded / Failed; Trial Warning; Trial Expired.
Variables
Send: Send Ready, Last Send Status, Last Send Time.
Receive: Receive Connected, Receive Status, Last Message, Last Message Title, Last Message Time, Last Inbound Event.
Driver: Driver Version, Licence Status, Trial Time Remaining.
Web dashboard
With Enable Web Interface ticked, bind a Web Object to http://(processor-ip):9066/ to see status and send notifications from a panel. The port is configurable.
Licence
The driver runs for a 120-minute trial without a key. A per-processor Licence Key unlocks it permanently. The MAC the key is tied to is shown in the MAC For Key variable and the debug console (mac command).
Diagnostics
Telnet the processor on port 12531 for a live console (status, test, send, recv, licence). Set the port to 0 to disable.
Support
Smart Home Programming - smarthomeprogramming.com.au
This driver is licensed per RTI processor. A built-in 120-minute free trial runs on every processor with no key, so you can fully evaluate it before buying.
When the trial ends the driver stops sending commands — two-way feedback keeps working — until a licence key is entered. Each key is tied to the processor’s MAC address, shown in the driver’s licence status variables and via the debug console.
Buy a per-processor licence from the Smart Home Programming store; your key is generated for the MAC you provide and delivered by email.