Hello,
Ariela 1.4.7 is out.
What’s new:
Really loving the quick launch. Any plans to allow grouping and/or ordering?
Yep, that is on my TODO list. 
Ariela installed 20 minutes ago. Discovered quick launch 5 minutes later. Then, try to order items and came here to ask how to.
Right now I cannot live without quick launch anymore… 
I am very glad you like the feature
Now I have an Ariela related problem:
Logger: homeassistant.loader
Source: loader.py:786
First occurred: 21:58:29 (1 occurrences)
Last logged: 21:58:29
No ‘version’ key in the manifest file for custom integration ‘fcm-android’. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of ‘fcm-android’
Tried to add version key to manifest.json (like I did to some other custom ones) but fcm-android refuses to cooperate 
Any ideas?
Best, JR
The fcm-android was discontinued and no longer supported. Instead, you can use the build-in notify service.
Sorry but no clue here
Removing fcm-notify from custom_components results in an error…Sorry forgot to remove from configuration.yaml 
Noticed also that Ariela speech (mic) no longer provides answers- related? No config/devices have changed - that was not true: MQTT broker changed and also device name
So all good again and awaiting for new enhancements
Best, JR
Hi @Ionut , fellow builders
Just a few weeks ago I found out about Home Assistant and now I am deep inside the rabbithole! Thank you for all your contributions!
I’m trying to hook up my Fossil (Wear OS) smartwatch to the system so I can access the switches/automations via the watch. Next i’d like to access the NFC function of the watch to ‘scan’ tags to start an automation.
I ran into a problem installing the APK on the Fossil Watch.
Any input from your side?
Have sort of a strange issue. I updated Ariela to the latest version however it would not start but just crash instead. No Google services on my device which is likely the reason.
So I downgraded to the previous version which works fine. But since I did that, very few of the MDI icons work. Most are just blank, and a few show wrong icons (usually brooms for some reason).
Is there an icon cache or something I can delete to fix this?
Thanks!
I wanted to try Ariela, but everytime I try to setup the built in MQTT and press “Check Connection” Ariela crashes, is there anything I can do about this?
Seems that Google changed the app watch policies. What does this mean exactly? It means that watch apps need to be distributed separately and not inside an application. I am working on this to make it work.
Could you please enable Ariela debug mode and send me the logs? Thank you.
[quote=“RobinKuiper, post:3009, topic:67519, full:true”]
I wanted to try Ariela, but everytime I try to setup the built in MQTT and press “Check Connection” Ariela crashes, is there anything I can do about this?
[/quote]Could you please enable Ariela debug mode and send me the logs? Thank you.
Hmm… If it helps, you might want to take a look at xDrip+ - Somehow the Play Store app on the watch will happily install the WearOS app for xDrip if xDrip is present on the phone, despite the app not actually being IN the Play Store in any way, shape, or form. GitHub - NightscoutFoundation/xDrip: Nightscout version of xDrip+
Like the person you were replying to, I’m seeing a compatibility error for Ariela on my TicWatch Pro 3
Thank you very much. I will take a look.
Thank you for this really helpful and smooth dashboard experience!
Do you plan on supporting the Grid card soon?
Hello,
I swapped IP addresses and now my default server cannot be deleted. I am currently on the new server and it states “The active server cant be deleted. Switch to another server to do this action.”
When I try to swap to the new server it says “This server is already active.”
My mobile app sensors havent updated in days because of this.
Hi.
Something I can’t get an answer from Ariela. The message comes by itself, but there is no reaction to pressing the button. When you click, a notification should come out… Please help me figure it out.
Triggers have been created in automations:
- alias: TEST TRIGGER1
trigger:
- platform: state
entity_id: input_boolean.test
to: "on"
action:
- service: persistent_notification.create
data:
message: "Test message sended"
title: "Test"
- service: notify.mobile_app_galaxy_a3_2017
data:
message: "Test message"
data:
actions:
- action: open_door
title: Open door
- alias: TEST RESPONSE
trigger:
- event_data:
action: open_door
event_type: ariela_notification_clicked
platform: event
action:
- service: persistent_notification.create
data:
message: "Clicked Open door on android"
title: "Test"
Yes, i have in plan adding that card.
That’s very strange. Did you figure it out the problem in the end?
Is the notification seen on the remote device?
yes, it is visible, but there is no reaction to pressing the button
I’ve been using the Pro app for a while, but a recent install on a new device (Pixel 5a) was a challenge. It sees like the client certificate selection process isn’t updated for recent Android security filesystem access limitations? I can’t navigate to the root of the emulated SD card, instead I’m stuck in the app’s container only.
I managed to use adb to put the p12 file in the right place, and chmod it to make it readable to the app’s UID. That got things working, but I’d hope for an easier solution.
Relatedly, have you considered making the client cert work with the “web UI” options in Ariela (I’ve confirmed it doesn’t work now). As the skew between Ariela native cards and the web UI grows, I find myself using the web UI more. There are a number of long-standing requests for the default mobile clients to offer certificate auth, with dupes as recent as today. Unfortunately it appears that this is a feature the core team is uninterested in offering. Since this is already a feature of Ariela, it seems there’s another opportunity here for differentiation.