This apps looks really promising but I was a bit disappointed when I tried to browse my Lovelace UI and barely half of my cards were rendered. What’s stopping you from just enabling full html rendering? It seems like an impossible task to maintain a specific implementation for every card that is used in lovelace. Even though your update speed is incredible at the moment I hesitate to invest in something that requires updates for every change. If you just manage a generic compatibility with lovelace then I’m on board!
Another topic. The only way to disable the permanent notification seems to be to disable all notifications for the app. I would like to be able to notify in case of alarm but not have the permanent one. That should be possible, right?
The plan is to support at least the official lovelace cards and custom ones to be implemented by number of requests. Indeed its very hard to support all those custom cards, but i believe is doable. Regarding web view mode, Ariela already support this feature, and you can enable it from application settings.
Regarding notifications, you can just only disable the permanent notification group and the icon will not be shown.
Hi, first of all, thanks for the great app. Purchased pro about 10 minutes in, it’s certainly good enough to pay for!
A humble request: I know supporting custom cards is hard, but I would ask if you could prioritize the MonsterCard, which is, I think, essential to keep track of new devices, automations and things of that nature.
Perhaps you could have people vote for the most popular custom cards to help prioritize implementation.
I also appreciate the separate thread for feature updates, following this one can be like drinking from a fire hose.
Although I’m having issues with scanned NFC tags not being reported back to HA. Always seem to have the “unknown” state, any ideas? MacroDroid app on phone has no issues reading the NFC tags in my home.
Also, how does the light sensor work? Seems it’s polling the sensor even if screen is off? Can’t really confirm it but it feels my battery is draining much faster last few days since started using Ariela. I have GPS updates set to 15min / 100m
There is no video yet, but maybe i could do one in the future.
Please send me the logs so i can investigate. Note that its possible that the NFC tags are redirected to another app if its set to be default one which handle NFC tags.
Hi, I have MQTT bluetooth tracking enabled. How would i go about converting/adding the detected BT devices to the known_devices.yaml so that each detected BT device can have its own entity instead of just being listed as [object Object]?
Edit:
it looks like I see a possibility to edit the example template from http://ariela.surodev.com/2019/01/08/bluetooth/ to have something similar to {{ trigger.payload_json.discovered_devices[0].mac = 'aa.bb.cc.dd.ee.ff' }} ?
Haven’t used this for a while but looking at it now it appears to have developed really well!
The one thing that’s missing for me, is being able to change Ariela settings via MQTT. You can do this with zanzito. It means I can turn GPS logging down to minimal when I’m at home, and up to every 5 seconds when I’m approaching a zone (such as work). This can help remove false positives from other automations that rely on my arrival in a zone [mainly notifying my wife that I’ve arrived at work, etc].
It’s a great feature; but not one Ican currently see how to implement in Ariela. Is it something you might consider?
Yes,
Now i am currently working on a 2 way MQTT comunication:
use Home Assistant to sent / receive MQTT data
use build in MQTT client to send / receive data.
Plan is to support almost all features that zanzito has (excepting ones that rely on SMS / Phone functions)
Please let me know if you have any other questions
apply progress theme color for thermostat / light lovelace cards
apply chart color based on the theme selected (sensor lovelace card)
small UI updates in thermostat advanced controls
ui updates in the MQTT sensors screen
fixed device tracker issue when device name ended with “_”
NOTE: PLEASE CHECK IF YOUR DEVICE NAME ENDS WITH “_” IN KNOWN_DEVICES.YAML, AND IF DOES PLEASE REMOVE THAT CHARACTER, ELSE THE DEVICE TRACKER WILL FAIL TO UPDATE. THIS CHANGE WAS INTRODUCED BY HOME ASSISTANT AS DEPRECATED.
A question about Hassio version 0.88, I’ve come across a problem with - I think, the location of the addon of the notifier and was wondering if you knew a fix on this? Error throws out;
Integrations need to be in their own folder. Change notify/fcm-android.py to fcm-android/notify.py. This will stop working soon.
I see this is a new thing to 0.88 and don’t others having this issue?
