Hi,
Thank you very much for the support 
Regarding the alarm name, i’ve looked into this some time ago, and the most extra information that i can manage to retrieve using standard Android API (which in theory should work on all phones) is the application name (or package id) that created the alarm. I will look into it more but i cannot promise anything.
I’m no programmer, so I can be completely looking in the wrong direction.
Is this something you could use?
https://developer.android.com/guide/components/intents-common#ShowAlarms
Indeed an global intent its used by Android to notify when an alarm is created. Unfortunately that intent do not contain all information’s required
This article (android.intent.action.SHOW_ALARMS) suggest it’s possible to ask for a list of alarms, so maybe after the initial trigger that notifies the app that an alarm was created, Ask for the alarm list, maybe there’s more information in that list?
That intent its used to show a native Android activity that will instead the alarms
Sorry, for the late, on HA only have one “Tere_Cel”
as you see , i have both enabled see and mobile tracking, i removed the integration in HA and generated it again, but it only shows me a single entitlement as seen here
tere_cel_wifi is a entity generated by nmap tracker, and on device_tracker.tere_cel is the one that I send for service see that you put away from home
From what i can see only the device tracker (see service) seems to be registered. Also, it seems that device has never been updated? Could you please enable Ariela debug mode, wait few minutes and send me the logs? Thank you.
And of course after an HA update yesterday, it renamed my device from Ariela…
Now instead of android_OnePlus_6 it’s android_OnePlus_OnePlus6_9
No renames or troubles here for 2 phones and a tablet using Ariela
You can manually rename your phone in the Ariela settings if needed.
it’s not the name in Ariela that got changed. It was the name that HA sees FROM Ariela. The name in Ariela was correct. Literally every sensor in HA was changed to this new name.
At this point if you can try to delete Ariela integration from HA, reboot, and from Ariela use force mobile_app. Hopefully HA will re-register the device with old name.
I did. It came back with the new name. I had to manually change every sensor and the device tracker name.
Im having problems with the mjpg streamer, the stream just stops after a while ( typically few hours in ) and i cant really pin down why.
Can you share Ariela logs maybe i could spot something?
How can i do that ?
Enable debug mode from Ariela -> Settings and it will tell you instructions to send those logs. But before sending, enable debug mode wait for the issue to reproduce and then send me the logs
Hi lonut, your app is really very good, runs stable and easy to use. The sensors are a great thing …
One question: Is there a way to display the microphone of the smartphone or tablet as a sensor in HA? You could then use a volume as the trigger for an automation. There are certainly creative ideas what you can do with it so everything.
Thanks for the good app !!!
Can you explain a little bit what means volume of the mic? Do you mean the number of dB at a certain time?
Hello,
Version 1.3.6.4 is out.
What’s new:
Yes, exactly, measuring the volume. HA could then trigger an automation when it reaches a certain level. For example, an alarm is triggered at high volume during the night …
