Skip to content
Android actionable notifications for Home Assistant and Ariela client
Branch: master
Clone or download
Latest commit 9d28266 Apr 26, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information. Update Apr 26, 2019 Create Apr 26, 2019 Add compatibility dismiss with HA template Mar 25, 2019
manifest.json Update manifest.json Apr 26, 2019

Ariela Client Home Assistant Notify

Android actionable notifications for Home Assistant + Ariela ( This code is based from


1.1. Copy the file into your /custom_components/notify/ folder (create it if you don't already have it) (use this step only if you are using Home Assistant version lower then 0.88)

1.2 If you are using Home Assistant version 0.88 or newer, Copy the file into your /custom_components/fcm-android/ and rename the script to

Attention: if you are using Home Assistant version 0.92 or higher, please create a empty file called (or download the one attached in this repository) in the folder where you placed Also attach the manifest.json to the same folder as the is.

  1. In your configuration.yaml file, add the following to initialize the components:
  - name: android
    platform: fcm-android
  1. Reboot Home Assistant.
  2. Enter Ariela application, go to settings and enable Firebase notifications


Sending the notification

The android actionable notifications are set up the same as the html5 notifications. The following parameters can be sent:


Parameter Required Description
message Required Body of the notification
title Optional Title for the notification, default value: Home Assistant
target Optional Target notification to be delivered to one specific device
data Optional Extra parameters for the notification

Parameters for the data section of the notification. Everything here is optional.

Parameter Description
color A hex color such as #FF0000, default value is a blue
message_type 'notification' or 'data', defaults to 'data'. This is the type of FCM that is sent. Notification has higher priority, but can't include actions or be dismissed by Home Assistant.
tag Must be an integer. Tag is the 'id' of the notifications. Sending a new notification to the same tag will overwrite the current notifcation instead of creating a separate one.
dismiss true or false, requires a tag parameter. If true, the notification will be dismissed.
actions Array of ojects (up to 3) with an 'action' and 'title'. The title will be the button text on the notification, the action is what is sent back in the callback
image A URL of an image to send. The image overwrites the BigTextStyle so longer texts will be truncated. The image will also be smaller if actions are included
icon A URL of an icon to use for the notification. Only on >= SDK 26. Careful to choose icon with tranparent background to follow Android guidelines.

In order to send a "regular" notification without actions, all you have to do is not include them in the call to the service, such as below.

- service:
    message: Anne has arrived home

This will send a simple push notification without any action buttons.

If you want to include some actions, something like this will work:

- service:
    message: Anne has arrived home
        - action: open
          title: Open Home Assistant
        - action: open_door
          title: Open door 

This will have two buttons, one that says "Open Door" and one that says "Open Home Assistant". The action for each button ("open" or "open_door" in this example) will be returned in the callback.

Handling the callback

The callback is pushed to the event bus. It can be accessed via fcm_android_notications.clicked. The "action" of the button that was pressed is included in the event_data. So an automation would looks something like:

  - event_data:
      action: open_door
    event_type: fcm_android_notifications.clicked
    platform: event
  condition: []
  - data:
      entity_id: light.front_door
    service: light.turn_on

How it works

When you clicked register on the app, it sends a firebase token back to Home Assistant. That token is saved into the fcm-android-registrations.conf file. This token is what is used to identify what devices to send the notification to. If the notifications involve actions, the token for the device is included in the callback. Before the callback is processed, the token is checked against the fcm-android-registrations.conf file for validity.

You can’t perform that action at this time.