Home Assistant for iOS 2.0 Beta Testing

robbiet480 · April 7, 2019, 8:07am

Known issue I just mentioned about ObjectMapper. Fix will be in next build but it should be ignorable.

TomBrien · April 7, 2019, 8:09am

Yes sorry I missed that post somehow. Thanks again for the great work. Location services still seem to be missing

robbiet480 · April 7, 2019, 8:09am

The location issue was covered in release notes

Will be fixed in 0.91.2 which drops tomorrow morning Pacific Time.

lolouk44 · April 7, 2019, 8:20am

For some reason templated complications aren’t working for me. Though it could be linked to the fact that since 36 (I think) my number of remaining watch sends is stuck at 0
Tried removing sous from both phone and watch to no avail

robbiet480 · April 7, 2019, 8:20am

Okay, so just figured out that one of the new bits of mobile_app wasn’t properly merged into 0.91. It’ll also be in 0.91.2 which as I already said comes out tomorrow morning Pacific Time. Until then, unless you’ve already found success with the app and mobile_app things probably won’t work. Sorry about that y’all, but at least it’s not me with the crashing bug this time

Piggyback · April 7, 2019, 8:24am

Thansk Robbie for all the support! I just upgraded to 39 and rebooted home assistant, but indeed I still get the KeyError: 'rateLimits' Does that mean as you say that depends on 0.91.2 coming out?

Above you mentioned you need to add mobile_app, I am not sure that is always needed, or is it? In the documentation it states : This component is by default enabled, unless you’ve disabled or removed the default_config: line from your configuration.

robbiet480 · April 7, 2019, 8:27am

Yep, 0.91.2.
Documentation is correct.

robbiet480 · April 7, 2019, 8:56am

Oh yeah, if you’re seeing a 404 error specifically, that means mobile_app isn’t loaded. Two options, your choice:

Open the app Settings screen and just leave it there for 2 minutes or so. Assuming you have discovery in your configuration.yaml, mobile_app should automatically be set up, you’ll see lines about it in your HA logs.
Add mobile_app to your configuration.

Dayve67 · April 7, 2019, 11:54am

Ok. Just added mobile_app to my configuration.yaml file. This is what I get:

I’m running HA on FreeNAS in a jail. Do I need to install “PyNaCl==1.3.0” manually?

Edit: Ya that was it. Installed “PyNaCl==1.3.0” manually fixed it. Now I just need to figure out why the app has connection error.

reichley · April 7, 2019, 12:06pm

Still same error in logs (and notification doesn’t fire) when using 0.10 or 0.1 as sound volume for critical alerts. Works only with 1

jwelter · April 7, 2019, 12:12pm

Hi Robbie,

Would these manifest themselves as below? The end result is location tracking doesn’t work as it seems it can’t be received on the HA side.

Received invalid webhook payload: extra keys not allowed @ data['source_type']. Got 'gps'
8:09 AM components/mobile_app/webhook.py (ERROR) - message first occured at 8:07 AM and shows up 8 times
Received invalid webhook payload: extra keys not allowed @ data['source_type']. Got 'bluetooth_le'
8:06 AM components/mobile_app/webhook.py (ERROR)
Received invalid webhook type: get_zones
8:05 AM components/mobile_app/webhook.py (ERROR) - message first occured at 8:03 AM and shows up 7 times

reichley · April 7, 2019, 1:39pm

I believed he fixed the extra options errors with this PR to be released in HA 0.91.2
mobile_app fixes

ha_steve · April 7, 2019, 3:15pm

Is / will there be a way to sync actions and actionable push notifications across ios devices? I haev the beta installed on an iPhone and iPad, and it appears I need to set the notifications and actions up on both?

krissen · April 7, 2019, 6:21pm

notify.mobile_app_shinydevice working well now, on build 39.

robbiet480 · April 8, 2019, 2:37am

That PR fixed the update location issues but sadly it’s a total of 4 PRs for mobile_app going into 0.91.2.

Argo · April 8, 2019, 5:22am

Hi
Got 404 issue couple of times during the day. Right after that I tap “ok”,”done” and everything works.

I am on 91.0, using remote UI

robbiet480 · April 8, 2019, 5:55am

That’s because of the missing get_zones call which was supposed to be in 0.91 but got missed during the cherry pick. Will be in 0.91.2 which leads me to my next post…

robbiet480 · April 8, 2019, 5:56am

0.91.2 is delayed to tomorrow Pacific time, sorry everyone! Got another build coming up tonight though with more bug fixes and the return of all the sensors, except this time via mobile_app!

roflcoopter · April 8, 2019, 5:56am

I keep getting “Token is expired” and “An SSL error has occured”.
I’m not using cloud remote UI, but it doesnt seem to work without it, am i forced to use the cloud remote UI?

robbiet480 · April 8, 2019, 5:57am

No, of course you aren’t required to use the remote UI URL.

Token is expired means the token legitimately is expired, or at least the app thinks it should be. As for the SSL error, is this a new thing you only started experiencing in 2.0?