So tested a bit more:
Notifications also work with only auth token, but some notification parameters did not work for me:
target: did not work, I set name in app, but no luck calling it with target parameter. fcm_android_registrations.conf missing?
Under data I was able to trigger automations with actions, but adding color, image and icon did nothing for my notifications.
In general I hope to get actionable pop-up notifications, and I think the default icon for notifications should be Home Assistant logo and not the current exclamation mark. In the current layout actions is also hidden in default view so you do not see the actions without opening the notification.
And I hope we can dismiss the permanent notification with server address in the future.
Overall I think the app has come a long way in a short time!
I updated latest version from store, but app insta-crash when I enter auto token.
Hey @lonut sorry been away tried the latest apk link u provided but duckdns doesn’t work for me same error as before.
Thank you for the suggestions / bug report. I will take a look into it
An update fixing this issue will be posted today.
I will investigate the issue.
Thank you guys for testing the application it really helps me improving it.
Hello,
Version 1.1.1 is posted to Google Play
What’s new:
- use just one FCM script for both pro and free apps
- the device name is saved now in the config
- fixed crashed reported by yrune
Do not forget to replace the FCM script with the new one:
https://github.com/MCrissDev/HANotify and also enable firebase push notifications again in the Ariela app in order to work properly.
Rocklobster please let me know if the new version works as expected.
Wanted to give it a shot but I cant connect to hassbian on a PI 3B. Not with discovery nor with manual settings.
Server not found… Connection failed. Please ckeck IP /URL…
I have a spare PI 3B which I set up with Hass.io a while back for some tests and there I have no problem. It works flawless.
No idea…
Can you give me more details about the server like: version, is http/https, Ariela app version? Also, if i send you a debug version of the application will you willing to try again?
Hello all,
In order to have the lovelace configuration retrieved, HANotify component will have to be installed. Is this ok for you?
Thank you,
Ionut
No problem for me, actually I like a hotify component
Great then 
Lovelace and device tracker support will be added in few days.
What other functions would you guys like to see in the application?
I really like your enthusiasm, I think this project will be a big success. Thumbs up!
Server is up to date, home assistant 0.79.3
App version says 1.1 - it was the last posted by you as I dont use Google atm.
And I use https (on the Pi without problems its http)
I will do some further tests this weekend. I did not have a lot of time and thought maybe somebody else had this problem.
If the problem persists I will get back to you, of course I’ll help with debugging.
groups that have a view in the frontend as view and groups that dont have a view not 
and it would be very helpfull if i could change the charactersize from the widgets somehow, because the size they are now i can only have 4 characters in a name with a 1x2 widget.
and the widgets dont stay up to date 
Can confirm that target parameter now works for me, good job !
Also you can target directly like in the screenshot posted.
Tested color and image but they still do not work, but my time testing was limited.
Another ting is timestamp for notifications, should be in the status field like normal notifications.
Thank you for your work!
Hey @Ionut
based on your post Android actionable notifications I tried your app and managed to log in internally and externally. However I get a message Failed to enable Firebase notifications for this device. Please check that HANotify component is installed on Home Assistant server.
I installed your version of fcm-android.py under \config\custom_components\notify. And I did reboot afterwards.
If I enable notify for android in configuration.yaml (like in code below), verifying configuraiton hangs in HA Web as well as notify.android is not available in Services (after reboot).
notify:
- name: android
platform: fcm-android
But for example notify for pushover does work without any problems. It shows in Services, sends notifications etc.
Some more information: I am running latest version of HA on Synology Docker and am using Synologys Nginx for Reverse Proxy. HA is on default 8123 port, but from outside to nginx I have 443 (Let’s Encrypt certificate). I still use legacy_api_password.
Thanks for your help.
I noticed too. Opening the app will bring the widget back to updated value
yeah, but if i need to open the app every time then the widgets have no value
when i need to open an app i can create any dashboard i like and it will be up to date immediatly.
Hey @Ionut ,
Just wanted to say great work on the app thus far , it’s great to see your enthusiasm for this!!
I unfortunately am also not able to log in with error server connection failed , I’m using the latest apk you posted on here. Im using hassio with https://xxxx.duckdns.org
Happy to send you any logs or anything to help debug etc, just let me know!
Ok, please let me know if anything wrong.
" it would be very helpfull if i could change the charactersize from the widgets somehow, because the size " → what do you mean by this?
Thank you for the feedback i will investigate the not up to date widgets.
Thank you for the feedback, i will going to look into it.
From Ariela, is the Firebase setting enabled successfully?
I will investigate the issue. Thank you.
Also here is a demo of Lovelace UI enabled. Note that HANotify component must be installed.
Download: http://surodev.com/ariela/app-ariela-release.apk
What i think i can do is for user to allow selecting the font size. Unfortunately textview widgets in Android cannot auto resize its text. Do you think that could work?