Ariela - Home Assistant Android Client

You can do that from Ariela → Settings ->Server Connection → Home Assistant Servers

Please share Ariela logs regarding this so i can investigate. Thank you.

About voice recognition- investigated changes in Ariela after Speech recognizer introduction and found that

was not behaving like before or I can not understand what has changed- not working anymore. But no big deal- implemented the new and more elegant approach:

#Demo to ask and play back energy price via Ariela
automation:
#Electricity price
  - alias: 'Electricity price'
    trigger:
      platform: state
      entity_id: sensor.voicecommand
      to: 'keyphrase'
    action:
      service: mqtt.publish
      data_template:
        payload_template: Current energy price with all taxes is now {%- set hour =  states.sensor.tund.state | int -%} 
         {{  states.sensor.nordpool.attributes.NPS[hour].Price | round(1) |replace('.', ',') }} cents per kilowatt-hour
        topic: homeassistant/tts/android_MyPhone_tts/tts

sensor:
#Voice Recognizer
  - platform: mqtt
    state_topic:  "homeassistant/sensor/android_MyPhone_tts/attributes"
    name: voicecommand
    value_template: "{{ value_json.state }}"
    expire_after: 4

So far so good- thanks for Your support :slight_smile:
Best, Reps

1 Like

Holy f.? What is going on there? Ariela used 24 Gb so far. And I don’t use any of the sensors or so.

Actually used 2 GB :stuck_out_tongue: Let me check what’s going on, can you share Ariela logs by any chance?

I just had a genereal feature idea:

Add an amp meter to ariela that shows if the charging rate for a wall mounted tablet is sustainable.

This could give an early indicator if the charger one just installed in the wall is sufficient to keep the tablet running :wink:

That is a great idea, unfortunately i don’t know a way to retrieve the current charging amps.What can it be done at most is check if the battery is charging, and if its not getting higher enough (meaning there is more consumption then its charging) means you need a better charger :smiley:

1 Like

Hi, i have a new question :|, i have ariela installed on two phones (both are huawei) but, on one the phone close ariela after a while of not in in use, (i configured the batt options on the phone, and put in ariela config the autostart , etc etc) but still are closing, (on the other phone same settings don’t happen, well my problem is, that ariela device tracker still in “Home” when the app are closed, and if i going out of home the status don’t change, maybe can use the availability_sensor on a automation and force not_home, but i think it’s possible to you put a configuration on the app, that if the device tracker don’t communicate to the server after a while put the state on away???

What happen on each priority setting on device tracker?

You can find the device tracker documentation here: Device Tracker – Ariela

You may want to enable the background running in Ariela too if you want better stability

Hello all,
Version 1.3.6.1 is out.
What’s new:

  • NEW: motion detection sensor when using MJPEG streaming
  • NEW: added enable flash option when using MJPEG streaming
  • fixed issue when scroll to refresh option can’t be disabled
  • display lovelace title if available instead of “Dashboard”
  • improved MJPEG stream capabilities
  • fixed device tracker wifi issue when the default home wifi is not assigned to home zone

Actually have background running enabled, but it’s a phone problem still closing the app, so if the app is closed and my wife don’t notice, i prefer home assistant set “not home” that device

Well then maybe a automation can be created to achieve this.
Example:

  1. enable Ariela availability sensor(its the once which tells HA the last time Ariela and HA communicated)
  2. create automation / script which: when last time communication provided by the availability sensor is more then 5 minutes, set the device tracker to away.
    Does this have any sense?

actually tried that, but when ariela are closed or withouth net connection, home assitant on the log show “The see service is not supported for this entity device”, (i have enabled see service on ariela config), and when the app are working , i can update to away with the see service

Well, see service and mobile app service will create 2 different tracker enties so be sure you update the one which is assigned to see service.

I have activated mobile app and see, device trackers on the app, but on my integration in HA only appear 1 device tracker for my phone

Can you tell me which one is showing in HA?

Hello,
Version 1.3.6.3 is out.
What’s new:

  • disable HANotify firebase notifications in mobile_app is supported
  • show thermostat Lovelace card update in realtime
  • improved badges rendering when running on tablets
  • enable Lovelace UI by default when the first run
  • added setting option to disable mobile_app push notifications for a device
  • rearrange notification settings
  • fixed weather card image issue loading
  • updated google libraries
  • small other fixes

Under Device Tracker->WiFi & Zones, whenever I enter a new wifi name and zone, they never seem to set whenever I go back to the setting

I could replicate the issue. Next Ariela version will have this fixed.

Hi Ionut, great app (have the registered version in our household)
A thing we started to use is the alarm sensor. So much potential with it, and running into limitations already :slight_smile:

I’ve created morning automations based on the alarm time (and the phone wich is configured to take the correct room): Open rolleshutters, slowly start music, sound alarm, sound another alarm if the garage door hasn’t opend in time (Kids need to leave on time for school with bike),…

This works great, but now they are also sometimes using their phone alarm for other stuff… You can already imagine what happens in the house :slight_smile:

Would it be possible to read also the alarm name with Ariela? If that’s possible, we can use that name to see if it’s an alarm for HA or not. It doesn’t need to get transferred to HA itself, could make a filter option in Ariela that it only take alarms into account that start with HA_ (or something)