Android actionable notifications

Tags: #<Tag:0x00007f47fd36d638>


installed and working! Nice and very rapid work!

Now just got to get the Assist app to support lovelace somehow. Seems to only show groups :frowning:

Yeah i had to uninstall the store version. I used apkinstaller to then install the downloaded .apk


Hi there. Fairly new to Home Assistant, so apologies if I’m overlooking something obvious.

I fall at the first hurdle using the Home Assist fork app. I’m using Hassio with a username/password for initial authentication. The app only has URL and password fields. When I try to connect, the app reports invalid password. I assume that has something to do with the lack of a username field.

Any suggestions?



@ronschaeffer sounds like you are using the new auth system. I haven’t tried it out yet so I can’t comment on it too much. This program uses the Rest API and Websockets, which as of now rely on a legacy api password. In your configuration.yaml file under the the http: section you should have a base_url and an api_password. This api_password is what is needed, so add it in if it isn’t there. This shouldn’t affect how you currently log in.

  # Secrets are defined in the file secrets.yaml
  api_password: !secret http_password
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url:
  base_url: !secret dns_url
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem


Thanks. That was indeed the problem.

Now to play around with notifications…


All set up and working now with the HANotify APK. I tried first with your fork of the Home Assist app, but it did not generate a fcm-android-registrations.conf file.

After success with HANotify, I tried again with the Home Assist fork. This time, the APK installation ended with the error “App not installed”. This occurred both with and without HANotify also installed.

Is anyone using this to launch an Android app from the notification. If so, which method are you using to trigger the app launch after receiving the callback on the HA server.

@Crewski Thanks for your great work on this. It’s exactly what I need for a smart doorbell project.


Glad at least one is working!

If you want to try the HomeAssist app again, go ahead an uninstall whatever version of HomeAssist that may be there. Then install my version from the links given. Go to settings where it says Push Notifications. Try to toggle it a few times…ending with it being checked.

When you uncheck it, there will be a toast message that’ll either say “Registration not found” or “Push notification subscriber unregistered”. When you toggle it back on you should see a toast that says “Push notification subscriber registered”.


I can’t actually (re)install the HANotify version of Home Assist from the Drive link anymore. Attempting to install it results in an “App Not Installed” error at the end of the Package Installer wizard. Installation did work the first time around (when notifications didn’t work) but hasn’t worked since I uninstalled it. No other version of Home Assist is installed.

Pixel 2 XL
Android 9.0.0



I get the same thing, Not Installed. Although you did get it to install once, It never would install for me. I have every external sources options on my phone enabled.


I tried again this morning to install the forked version of HomeAssist, and for not obvious reason, it worked this time. I did power cycle my phone prior to attempting the install, but I’d also tried that a couple of times yesterday when the install failed. Notifications are now working with HomeAssist.

@Crewski Do you plan to continue to develop HANotify on its own or only the HomeAssist fork? Thanks again. Fantastic work.


Ha…first rule of IT, turn it off and turn it back on!

I’d like to make a more complete app with notifications, widgets, and location tracking, but can’t decide if I should just use the web UI of home assistant or try to develop a websocket version similar to HomeAssist.

I am very curious what the project below will yield. Chances are this guy is way better at this stuff than I am.


I’m totally fine with an app that just takes care of the actionable notifications, and does nothing else.
If I want to have more functionality I can install another app.


I agree with that. I like it when an app is aimed at doing one thing and doing that thing really well. Building some fancy stuff around it might just bring some bugs along.


It Will be good to have an app for home assistant that have themes, widgets , notifications, tracker, Will be awasome


If the firebase key can be configured without recompiling the apk, i would say you should put it in the Play store & see if you can get this as a standard component.

I have been looking since the begining to have actionable notifications withouting opening HA to the outside world (using VPN).


I am struggling to get the right config working, can you check what I am doing wrongly?

  - service:
      message: '{{ }} - {{now().strftime("%H:%M:%S")}}'
      title: De-Activated
        icon https://xxxxx
        color #08B80D
        tag yyyy


I like this project very much but don’t like the fact using Google … is there a way using this without cloud services and Google ?


@elRadix what kind of errors are you getting in your log? The first thing I notice is that icon, color, and tag do not have a colon after them (not sure if its just a typo or not). Should be

  - service:
      message: '{{ }} - {{now().strftime("%H:%M:%S")}}'
      title: De-Activated
        icon: https://xxxxx
        color: #08B80D
        tag: yyyy

If that doesn’t work, maybe try wrapping things in double quotes " instead of single quotes '. I don’t know what the difference is in yaml though.

@thundergreen The notification is sent via Firebase, which is google. I’m sure you can accomplish the same thing via other push notification platforms, but I never looked into that as I’m comfortable with using google. The “actionable” part doesn’t involve Google at all because it is sent back as a POST request.


Thanks for your work on this.
I have installed the HANotify.apk on my phone without issues, is properly registered and is running.
I installed on my ver 75.1 without issues. No errors when restarting Hass.
But when I try to send a simple notification eg:

  • service:
    message: Garage Door notification

I get the following error:

2018-09-20 10:06:22 ERROR (SyncWorker_19) [custom_components.notify.fcm-android] Error sending message. Response 400: Bad Request:
NoneType: None

Any ideas?
thanks so much for this work.

Update: After about 5 minutes it started to work without errors. Weird, but thanks again for you work.


@fantangelo That’s odd. My first thought was that the fcm_android_registrations.conf file wasn’t created or there wasn’t anything in it…but that doesn’t explain why all the sudden it would start working.


i have 2 devices (unnamed device and unnamed device_2), how i can send notifications to specific device? (i.e., to unnamed device_2 only)?