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: June 27, 2026
Version: 0.2
Pushover Notifications
Get RTI talking to your phone. Send Pushover push notifications from any macro — an alarm tripped, a door opened, a scene started — straight to your phone, tablet or desktop, with a title, a priority level and an optional sound. Optionally turn it around: incoming Pushover messages become RTI events, so a message on your phone can trigger any macro, scene or activity.
Key Features
- Send from any macro: title, message and an optional alert sound, to your phone, tablet or desktop.
- Five priority levels: from silent through to emergency notifications that require acknowledgement.
- Up to ten recipients: a default user or group key plus ten named recipients you can address individually.
- Two-way (optional): incoming Pushover messages fire RTI events — a message of event1 to event20 fires that event; anything else fires a New Message event and fills the Last Message variables.
- Self-healing receive channel: a keep-alive watchdog automatically reconnects a dropped or stalled connection, so it stays up for the long haul.
- Web Object dashboard: status and a test-send button on a panel.
- Debug console: telnet diagnostics for setup and support.
Requirements
- A free Pushover account (pushover.net) with an Application API Token and User/Group Key.
- An RTI processor with internet access (Pushover is a cloud service).
- For the optional receive channel: your pushover.net account login (email + password).
How It Works
Sending uses Pushover's Message API over HTTPS. Receiving uses Pushover's Open Client API: the driver registers a virtual device on your account and holds a connection that pushes new messages to RTI in real time, with an automatic-reconnect watchdog for reliability. Wire the Notify functions to macros to send, and the inbound event triggers to macros to act on messages received.
Pushover Notifications Driver
Version 0.2
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.
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.
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 runs on a free 120-minute trial. Permanent use needs a per-processor licence key, generated against the RTI processor's MAC address (shown in the driver's MAC For Key variable). One key covers all use on that processor. Purchase from the link below.