Ariela - Home Assistant Android Client

GoSpursGoNL · June 10, 2019, 6:04pm

Ah thanks, quotes to be put around the various elements, my bad! (in your example an extra comma is needed after the message-line by the way.

hassmon · June 10, 2019, 9:38pm

i had both notify.mobile_app_xxx and notify.android working. however, the notifications seem to only work sporadically. i would get the messages instantaneously for a while then the next one won’t come in for hours. then i get a flood of notifications all show up at the same time… any reason for that?

also, i did not see this mentioned in the thread. i kept getting this warning in home-assistant.log on restart:

2019-06-10 21:08:06 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved Traceback (most recent call last): File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 357, in _async_add_entity raise HomeAssistantError(msg) homeassistant.exceptions.HomeAssistantError: Entity id already exists: device_tracker.my_phone. Platform mobile_app does not generate unique IDs

i have cleared out the entity registry files in .storage and rebuilt home-assistant_v2.db several times. I made sure there was only one client registration from Ariela, yet that message kept coming back after a while. I’m still getting the notifications despite of that warning, however, i’m not sure if it contributes to the random delays in receiving those notifications…

Ionut · June 11, 2019, 3:58am

Mostly depends on your network connection and google servers. With what kind of connection the issue is happening: wifi / 4g or both?

I will investigate this. Thank you for reporting it.

GoSpursGoNL · June 11, 2019, 5:56am

I notice the same thing, have the feeling it has more to do with battery management. If the app is open or if the phone screen has only been off for a short moment, then the notification appears immediately. But if I then send another one a couple of minutes later, nothing happens. But when I then reactivate the phone’s screen, it appears right away.

Ionut · June 11, 2019, 6:08am

Hello all,

Version 1.3.3.8 is out. What’s new:

NEW: added option to vibrate when toggling switches, buttons etc
NEW: added option to vibrate when clicking on widgets
updated Russian localization
fixed device tracker issue loading even if disabled
fixed issue where user can’t enter sensors screen if MQTT is not enabled
added information dialog when forcing mobile_app on device

bschatzow · June 11, 2019, 12:22pm

Today after updating on two devices my configuration file was lost. Had to reconfigure. No big deal, but should not happen. Also on one device I was away from my home network and there is no way to configure external access is I don’t have the local access setup.

Ionut · June 11, 2019, 12:39pm

That’s very strange. Regarding local access setup, just put your wifi name from home, and your external IP address and will work just fine

jo-me · June 11, 2019, 1:57pm

Hi,

two questions:

are you planning to support horizontal/vertical stacks properly? Right now, the layout is completely different than the web view due to the fact that (especially horizontal) stacks are not treated as layout elements but rather some sort of slider view. The apps “no. of column” setting is working agains the layout mechanism that lovelace provides.
This prevents me from using the native UI in Ariela which I’d prefer to the webview because my old Kinde Fire HD does not run stable with the web view.
I recently moved HA from HTTP to HTTPS using a self-signed certificate (HA is not exposed to the internet). I managed to set the certs up so that Chrome & Firefox are happy and don’t show any SSL warnings. For that I imported the root ca certificate to the trusted root certificate list. On Android, I also imported the root CA which eliminates the warnings on Android’s Chrome and other apps as well. However, despite this new trusted root, Ariela still shows a warning on every app start :

Can this be prevented? Not sure what an app has to do in order to look at the system’s credential storage… I’m kind of irritated that it does not work out of the box for all apps.

Thanks,
Jochen

bschatzow · June 11, 2019, 1:58pm

As soon as I got home Ariela logged in on my home even though when I wasn’t connected it asked me to set it up. This is why I thought the configuration was gone. Maybe duckdns was down and this caused the external issue. All working now. I do have questions on sending notifications based on location. Should I post the questions here or email you?

hassmon · June 11, 2019, 2:28pm

i was on 4g with relatively good signal and stable connection. i did notice the messages came in better when i vpn back to home network or connect to a wifi. so it could have something to do with my mobile connection… i will have to test a bit more…

is there any practical difference between the mobile client notification and firebase notification? for general usage they appear to provide the exact same functionalities while mobile client notification requires almost no setup?

Thank you. this “entity id already exists” warning doesn’t seem to be breaking anything but i’m at a lost as of what was being put in the config to trigger it in the first place. admittedly, i don’t have a good grasp on how Ariela registers itself with HA. i’m afraid if/when i logout/reset the mobile client or press the “force register” button by accident i will have no choice but to reconfigure all the mobile client entities from scratch again…

DobriyS · June 11, 2019, 2:28pm

I’m sorry, I don’t know which branch to ask. Notifications stopped working after the last HA update and the last Ariela update. If I manual trigger my automation with notification I get the following error:

Error Log

Error while executing automation automation.completed_torrent. Unknown error for call_service at pos 1:
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/automation/init.py”, line 391, in action
await script_obj.async_run(variables, context)
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 131, in async_run
await self._handle_action(action, variables, context)
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 210, in _handle_action
action, variables, context)
File “/usr/src/homeassistant/homeassistant/helpers/script.py”, line 299, in _async_call_service
context=context
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 89, in async_call_from_config
domain, service_name, service_data, blocking=blocking, context=context)
File “/usr/src/homeassistant/homeassistant/core.py”, line 1150, in async_call
self._execute_service(handler, service_call))
File “/usr/src/homeassistant/homeassistant/core.py”, line 1172, in _execute_service
await handler.func(service_call)
File “/usr/src/homeassistant/homeassistant/components/notify/init.py”, line 112, in async_notify_message
await notify_service.async_send_message(**kwargs)
File “/usr/src/homeassistant/homeassistant/components/mobile_app/notify.py”, line 119, in async_send_message
result = await response.json()
File “/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py”, line 1027, in json
headers=self.headers)
aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: ’

If i try to run through call services notify.mobile_app_mi8 {“message”:“test”} getting the following error:

Error Log

0, message='Attempt to decode JSON with unexpected mimetype: ’
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py”, line 121, in handle_call_service
connection.context(msg))
File “/usr/src/homeassistant/homeassistant/core.py”, line 1150, in async_call
self._execute_service(handler, service_call))
File “/usr/src/homeassistant/homeassistant/core.py”, line 1172, in _execute_service
await handler.func(service_call)
File “/usr/src/homeassistant/homeassistant/components/notify/init.py”, line 112, in async_notify_message
await notify_service.async_send_message(**kwargs)
File “/usr/src/homeassistant/homeassistant/components/mobile_app/notify.py”, line 119, in async_send_message
result = await response.json()
File “/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py”, line 1027, in json
headers=self.headers)
aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: ’

Before updates all work fine. Something wrong with custom notify android? Or with my hands and inability to read docs?)))

Ionut · June 11, 2019, 3:10pm

Can you share some screenshots via email on how its showing in Ariela and how its showing in Home Assistant web ui?

I think i have a solution for this. Let me see what i can do about it.

You can ask here, maybe questions / answers can help others.

HANotify i do not plan to support or add new features. Only mobile_app notification will get updates. And of course mobile_app notifications do not require setup

Try to re-register the Ariela with mobile_app and tell me if works.

hassmon · June 11, 2019, 3:54pm

perhaps there’s an obvious button i missed, but…

if i go to settings->ui and turn on web ui… is there any way to switch back? as far i can tell once switched Ariela will act just like a single page web browser. there’s no way to access Ariela app’s “native” menu and settings again?

Ionut · June 11, 2019, 4:20pm

Just swipe right from the left margin to display Ariela menu.

hassmon · June 11, 2019, 5:03pm

ah. i knew it had to be something simple… i have full screen gesture setup so swipe from left or right edge of the phone is the same as hitting “back” button. So in my case i had to treat Ariela menu as a hidden “hamburger” menu and swipe from top edge of left side.

Thank you!

Viggen · June 11, 2019, 11:15pm

I have recently started using Ariela app and I noticed a new error in hassio logs:

Log Details (ERROR)
Wed Jun 12 2019 00:08:54 GMT+0100 (British Summer Time)
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 357, in _async_add_entity
    raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: device_tracker.pixel_3. Platform mobile_app does not generate unique IDs

Not sure if I got that right, but is it trying to create the same entity twice?

IKROWNI · June 12, 2019, 12:20am

Are you using any other device tracker with that name already?

Ionut · June 12, 2019, 5:56am

Hello,

New feature for Ariela: camera streaming

Ionut · June 12, 2019, 6:36am

Hello all,

Version 1.3.3.9 is out.
What’s new:

NEW: support for camera streaming
update Russian localization
updated German localization
fixed incorrect cover icon when device_class is garage
small UI changes
fixed device tracker crash

bschatzow · June 12, 2019, 1:05pm

The following is some of my automation.
configuration.yaml
mobile_app
automations.yaml

alias: ‘Leave Gym notification’
trigger:
platform: zone
event: leave
zone: zone.gym
entity_id: device_tracker.bill_pixel_xl
action:
service: notify.mobile_app_pixel_xl
data:
message: ‘Bill has left the gym’
alias: ‘Arrive at Gym notification’
trigger:
platform: zone
event: enter
zone: zone.gym
entity_id: device_tracker.google_pixel_xl
action:
service: notify.mobile_app_pixel_xl
data:
message: ‘Bill is at the gym’
alias: ‘Arrived Home notification’
trigger:
platform: zone
event: enter
zone: zone.home
entity_id: device_tracker.google_pixel_xl
action:
service: notify.mobile_app_pixel_xl
data:
message: ‘Bill is home’

I never get a notification when I either leave or enter a zone.