Home Assistant for iOS 2.0 Beta Testing

jwelter · April 8, 2019, 5:50pm

I’m seeing the same.

It seems the device_tracker is being registered using a GUID versus the Device ID name set in the app name.

device_tracker.c1c4bad229e2466bb5ddd7816baea934

Corresponds to my phone. It tracks correctly.

The GUI integrations page correctly lists my iPhone and using the Device ID set in the app as the name. But all the related sensors do no contain the GUID or the device ID; so if multiple phones being tracked these sensors overlap with a _2, _3, etc. They all get listed for each phone being tracked.
Notifications seem to show up correctly as mobile_app_<<device_ID_set_in_app>> and seem to work fine. Restart after adding for this to work.

TomBrien · April 8, 2019, 6:52pm

Same here on all three counts except I note that the _beta given at the end of the Device ID in the app is not used, possibly just using the device name set in iOS?

sgruby · April 8, 2019, 7:37pm

I have notifications working for the mobile_app prefix, but like others, don’t see the _beta at the end of the device ID. In addition, my notifications aren’t vibrating or playing a sound (if I turn that on). If I use the ios target, i.e. notify.ios_scotts_iphone_beta (as opposed to notify.mobile_app_scott_s_iphone), I get the sound.

From the event log for the mobile app notify:

{
  "gcm.message_id" : "1554752096289754",
  "aps" : {
    "alert" : {
      "body" : "Mobile app notify"
    },
    "mutable-content" : 1
  },
  "google.c.a.e" : "1"
}

iOS notify:

{
  "aps" : {
    "alert" : "iOS notify",
    "sound" : "default",
    "mutable-content" : 1
  }
}

Looks to me like the sound parameter isn’t being sent in the aps payload.

jjlawren · April 8, 2019, 10:01pm

Definitely makes sense to add back iBeacon exit events somehow. Just need to consider the best way so that it works well for both single beacons and blanketed zones.

TravelinMax · April 9, 2019, 2:58am

Does 0.91.2 or build 40 trigger a reboot of HA? Mine just restarted out of the blue and I can’t think of why. The new sensors from 40 showed though, so that’s nice lol

jwelter · April 9, 2019, 5:12am

What are you seeing in the integration tab? See mine below as all entries seem to have a overlapping friendly name and report duplicate info

@robbiet480 any ideas on this? Also not picking up device id in the app so perhaps related?

Angarok · April 9, 2019, 6:24am

Does anyone else have really choppy scrolling with build 40?

raxpa · April 9, 2019, 7:24am

Same for me no sound

TomBrien · April 9, 2019, 8:01am

Yep they all show a friendly name of Last Update Trigger. If I look on the dev-state and look at the history it seems that all six sensors (I have sensor.activity and sensor.last_update_trigger in addition to the ones you show) contain the same information and it looks like a merge of all the data I would expect across those sensors. For example sensor.battery changes from Background Fetch to Charging to Automotive then to Walking.

@robbiet480 I also see the sensors as sensor.battery, sensor.bssid etc not sensor.device_ID_battery, is this expected? It will presumably get confusing with multiple mobile_apps connections. Cheers again for the huge amount of work

TomBrien · April 9, 2019, 8:01am

I did the very first time I opened the app. I just closed it completely and reopened and it has be fine since.

lolouk44 · April 9, 2019, 9:52am

just a quick one if anyone can help.
This doesn’t seem to work very well anymore since 0.38:

  trigger:
    - platform: event
      event_type: ios.action_fired
      event_data:
        actionName: DISARM_ALARM

should I replace ios.action_fired with mobile_app.action_fired?
(I’m upgrading to 0.40 as we speak but at work now so can’t test)

VirtualL · April 9, 2019, 10:17am

FIX for my problem 3 days before: " can’t make auth with any iOS app including this beta , while using Nginx proxy server"
After trying every config and debug for this problem for 3 days without finding anything on the web.
Fix the Errors deal with iOS app 1.5 and iOS 2.0 BETA

error while looking up redirect_uri Home Assistant iOS - Home Assistant
error while looking up redirect_uri Home Assistant iOS beta authentication - Home Assistant

I found this config is working: (NGINX config for Home Assistant)
(Running HASS via Docker on Unraid server + NGINX reverse proxy)

## Version 2018/12/05 - Changelog: https://github.com/linuxserver/docker-letsencrypt/commits/master/root/defaults/default

################################################################################
#### PORT 80  
################################################################################
# listening on port 80 disabled by default, remove the "#" signs to enable
#redirect all traffic to https
server {
	listen 80 default_server;
	listen [::]:80;
	server_name _;
	return 301 https://$host$request_uri;
}
################################################################################
# main server block
################################################################################
server {
	listen 443 ssl http2 default_server;
	listen [::]:443 ssl http2 default_server;

	root /config/www;
	index index.html index.htm index.php;

	server_name _;

	# all ssl related config moved to ssl.conf
	include /config/nginx/ssl.conf;
    
	client_max_body_size 0;

	location / {
		try_files $uri $uri/ /index.html /index.php?$args =404;
	}

	location ~ \.php$ {
		fastcgi_split_path_info ^(.+\.php)(/.+)$;
		fastcgi_pass 127.0.0.1:9000;
		fastcgi_index index.php;
		include /etc/nginx/fastcgi_params;
	}	
}	

###############################################################
### SUBDOMAIN 1 - Home-Assitant
###############################################################
server {
	listen 443 ssl http2;
	listen [::]:443 ssl http2;
	server_name hass.MYDOMAIN.COM;

    ssl_certificate /config/keys/letsencrypt/fullchain.pem;
    ssl_certificate_key /config/keys/letsencrypt/privkey.pem;

    ssl_dhparam /config/nginx/dhparams.pem;

    # These shouldn't need to be changed
    add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
    ssl on;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4";
    ssl_prefer_server_ciphers on;
    ssl_session_cache shared:SSL:50m;

    proxy_buffering off;

    location / {
        proxy_pass http://LOCAL_HASS_IP:8123;
        proxy_set_header Host $host;
        proxy_redirect http:// https://;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Upgrade $http_upgrade;
	    proxy_set_header Connection "upgrade";

		resolver 127.0.0.11 valid=30s; 
        proxy_buffering               off;
        proxy_ssl_verify              off;
    }


    location /api/websocket {
        resolver 127.0.0.11 valid=30s;
        proxy_pass http://LOCAL_HASS_IP:8123;
        proxy_set_header Host $host;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }	
}

Hope its will help to someone!

Joshfindit · April 9, 2019, 1:31pm

As of b40 and 0.91.2, I now have iOS notifications working on my iPad (12.1).

Thank you! Will test as time goes on.

Joshfindit · April 9, 2019, 1:34pm

iOS interface bug:

When “Automatically hide toolbar” is off, the dev tools can’t be clicked as they are always under the toolbar.

terafin · April 9, 2019, 4:24pm

As a couple people have pointed out, themes are almost working, but not quite there! Screenshot attached - but is this something we need to fix with the theme itself, or is this the new HA app not honoring them? (note: the production version of the app looks way worse related to blue, so it definitely got better!)

jimz011 · April 9, 2019, 5:06pm

What is wrong with theming? Works perfectly fine to my knowledge, even with the 1.5.1 app.

terafin · April 9, 2019, 5:18pm

Thanks! - Looks awesome Are you able to share the theme to confirm this is a theme issue vs software? As above - I just pulled a few themes from the theme gallery here, it’s possible (probable?) that I need to update them!

Cheers,

jimz011 · April 9, 2019, 5:32pm

github.com

jimz011/old-reference-files/blob/master/themes.yaml

slate:
    # Main colors
    primary-color: '#555555'
    accent-color: '#555555'
    dark-primary-color: 'var(--accent-color)'
    light-primary-color: 'var(--accent-color)'
    # Text colors
    primary-text-color: '#FFFFFF'
    text-primary-color: 'var(--primary-text-color)'
    secondary-text-color: '#b58e31'
    disabled-text-color: '#777777'
    label-badge-border-color: 'green'
    # Sidebar
    sidebar-icon-color: '#777777'
    # Background colors
    primary-background-color: '#222222'
    secondary-background-color: '#222222'
    divider-color: 'rgba(0, 0, 0, .12)'
    table-row-background-color: '#292929'
    table-row-alternative-background-color: '#292929'

This file has been truncated. show original

Though, it only works if you start HA with it. It won’t work if you change themes via the user interface. So if you want to setup themes per user, make sure the headers have the same color across all themes.

fillwe · April 9, 2019, 5:41pm

Been getting this error every time I start the app since the latest build, need to click ok and done every time no problem connecting after that until next restart of app. Anyone else? Also it has gotten really laggy, tried reinstall but hasn’t helped

TomBrien · April 9, 2019, 5:47pm

Should be fixed by upgrading HA to 0.91.2.