Home Assistant Push Notifications

Send Home Assistant sensor events and automation alerts to your phone
with Signalgrid and a reusable REST command.

Send Home Assistant automation alerts

Use Home Assistant automations to send Signalgrid push notifications for door sensors, temperature changes, power events, and completed tasks. The built-in RESTful Command integration sends the request directly, with no custom integration or extra add-on.

Prerequisites

  • A Home Assistant installation with access to configuration.yaml and secrets.yaml.
  • A Signalgrid account with an iPhone, Android device, or web client registered to receive notifications.
  • Your Signalgrid client key and a channel token. Use the channel token rather than the channel name.
  • Outbound HTTPS access to https://api.signalgrid.co.

Add the REST command

Add the following to configuration.yaml. If a rest_command: section already exists, add signalgrid_push beneath it instead of creating a second top-level section.

YAML
rest_command: signalgrid_push: url: "https://api.signalgrid.co/v1/push" method: POST content_type: "application/x-www-form-urlencoded" payload: !secret signalgrid_push_payload

Store the request template in secrets.yaml

Add this entry to secrets.yaml and replace the credential placeholders. The entire payload is kept in the secrets file, while the automation supplies only the notification details.

YAML
signalgrid_push_payload: >- {{ { 'client_key': 'YOUR_CLIENT_KEY', 'channel': 'YOUR_CHANNEL_TOKEN', 'title': title | default('Home Assistant'), 'body': message | default('Your automation has triggered.'), 'type': notification_type | default('INFO'), 'critical': 'true' if (critical | default(false) | bool) else 'false' } | urlencode }}

The urlencode filter encodes the dictionary as form data, including punctuation and line breaks in your messages. Check the configuration and restart Home Assistant to load the new REST command. Keep your secrets file private.

Send a test notification

Open Developer tools → Actions, switch to YAML mode and run this action:

YAML
action: rest_command.signalgrid_push data: title: "Home Assistant test" message: "Your Home Assistant notification has arrived." notification_type: "INFO" critical: false

Confirm the notification arrives in the selected Signalgrid channel. Once the manual action works, reuse the same action in your automations.

Create a sensor automation

Create a new automation, open its YAML editor and use the following example. Replace binary_sensor.front_door with your own entity. This example assumes off means closed and on means open.

YAML
alias: Signalgrid - front door alert triggers: - trigger: state entity_id: binary_sensor.front_door from: "off" to: "on" actions: - action: rest_command.signalgrid_push data: title: "Front door opened" message: "The front door opened at {{ now().strftime('%H:%M') }}." notification_type: "WARN" critical: false mode: single

The trigger reacts to a closed-to-open transition. For another use case, replace the trigger with your sensor or automation event and keep the rest_command.signalgrid_push action.

Notification fields

Action data
Meaning
title
Short notification heading.
message
Notification body; templates can include sensor values and timestamps.
notification_type
INFO, WARN, SUCCESS or CRIT.
critical
Boolean true or false; defaults to false.

Send critical alerts

For urgent incidents, set critical to true and type to CRIT. These are separate settings: the visual notification type alone does not enable critical delivery. Critical notifications require a Single or Teams subscription and the appropriate device permissions. See Critical Notifications for iOS Critical Alerts and Android notification settings. Keep routine results non-critical.

For a critical automation action, set notification_type: CRIT and critical: true in its data. This controls the Signalgrid notification; it does not require a Home Assistant Companion app notification payload.

Troubleshooting

  • The action is unavailable: verify YAML indentation, the secrets entry and the REST command name, then check the configuration and restart.
  • The API rejects the request: check the credentials in secrets.yaml and use the channel token rather than its name.
  • Manual test works but automation does not: inspect the automation trace, entity state and trigger conditions.
  • Too many alerts: use a state transition, a duration condition or other filtering appropriate to the sensor.
  • No mobile sound: check Signalgrid device permissions and critical-notification settings.

Official documentation