Interestingly, I’ve just had some success. No changes to config.yaml. Went into the (only) actionable notification I have in the app - rearranged the two options, saved, rearranged them back to original order, saved, now it works! Must be some sort of weird caching issue or something, or imports from the old system not being correctly converted for the new app unless edited
Hi all.
Since I use the notifications of the beta version of the app, I don’t receive any attachment (I was used to receive the picture of a camera when someone was ringing the bell).
May I change something in the configuration with the new app?
Thanks a lot in advance for your support.
Hi,
I was using the Beta app for some time now, without any issues.
Recently I wanted to reset it from the beginning and now during connection process I receive the following message:
“The mobile_app component is not loaded. Please add it to your configuration, restart Home Assistant, and try again”
Of course I tried to remove iOS integration and add it back and restart Hassio.
Nothing helps.
The regular app is still working as expected, no issues there.
Any ideas what am I doing wrong?
Thanks in advance.
did you load mobile_app?
Sorry for stupid question.
How do I do that?
I mean I never did anything special before and I’ve been using the beta app for months now.
Surely I miss something here.
Appreciate any help.
Edit. Got it. Sorry again. And thanks!
All good now.
2 Likes
Hi, for some reason the version 62 is crashing upon oppening. It worked fine, but after I had to re-install it it just don’t start. I deleted it and installed several times, but just doesn’t work.
I’m with IOS 12.
https://drive.google.com/file/d/1WpwJ0X-COHsj03ncBkwltJTLyco9j6ld/view?usp=drivesdk
Anyone had the same issue?
Thanks
Hi Bruno, I can’t open your link, but I did submit this bug report recently:
https://github.com/home-assistant/home-assistant-iOS/issues/409
Does this look like your problem?
No it’s diferent.
The APP just crash, before I can do anything. I changed the link on the post above, maybe it works now.
Does anyone has the same issue?
It shouldn’t be IOS related, as I did everything I can remember to solve it.
- Deleted the app
- Rebooted iphone
- Install app again
- Still crashing on starting
PS: IOS is updated. And app worked fine in the past with my current phone. Just now I’m having this issue.
Hi, I don’t know where to put this, but since people using this app are on ios this means users of this app will face this problem very soon. This message is to create awareness for everyone:
iOS 13 makes Home Assistant pretty much unusable. I’m on the third beta now and this has not improved at all. The problem is, when pressing a button it will activate twice in a row. Meaning when your turn on a button it will immediately turn off and vice versa. This is prominent on all ios 13 devices as far as I know and not only in the app, but in Safari as well. At first glance I thought it might be a custom card, but it has the same behaviour with core cards. I have waited until the third beta on purpose, but it seems to me Apple is not going to fix this (I only have this problem with Home Assistant) and thus it makes me think that either Apple will never know about this, either they don’t care as it doesn’t affect other websites or that it is just simply not relevant enough to fix that.
Ofc I might be completely wrong as it is a beta, but usually the second or third beta would be stable enough to run as a daily driver. I really have a bad feeling about this and it would really make the iphone useless for Home Assistant if this persists.
At the same time, tvOS 13 will no longer work with Home Assistant as apparently they have removed a service related to home sharing which Home Assistant relied on.
I am running the public beta on an iPhone 7 and have not had that many issues with the app so far. I have an issue with a button card that toggles an input Boolean but I find a quick double tap will switch it on or off as required. As for all the other buttons they all work as expected.
Hm that is weird, I had some people asking me the same question. I have it with core buttons and button-cards. Though I do not have it with buttons that can not be toggled like scenes.
Weird thing is, if I slightly hold it between a press and a long press they work fine.
Edit: I will try a clean install of iOS 13 in the coming week, it might sounds stupid, but Inhad various ios problems solved by just restoring it. Ofcourse I will keep you guys informed!
BTW I am running iOS13 17A5508m which is the 1st public beta as far as I can tell. Are you running dev or public betas?
I am on iOS13 Public beta 1. ZERO issues such as you describe.
dev beta 3. Hm weird though, I have seen others with the same problem. Must be a dev beta thing then (though most of the time they are pretty much the same). Or it could be some other kind of bug in iOS 13. Will try a fresh install tomorrow.
It could be a device thing. I cannot see my chromecast in the YT app on an iPhone 7 yet a work colleague with an iPhone 8 doesn’t have this issue.
iPhone 8, pubeta, no chromecast on YT, no issue with HA. 
I gess this beta is very beta…
It’s not just you, I’m also on dev b3 and experiencing much of the same problems. Seems to be a problem in WebKit, it’s often registering taps multiple times - which as you’ve experienced destroys the usability of things like buttons.
There are problems with input_selects too, can’t configure the UI (not a problem for me personally since I use yaml mode), and I’ve been getting a bunch of random HA crashes in dev b3 when it’s just in hte background. Some of this stuff was problematic on previous betas but it feels like it’s only gotten worse in dev b3.
I kinda think those still on the first public beta should hold off a bit and not install the second public beta when it comes out if things are working okay for you.
It’s funny you say this, I too am on iOS 13 beta 3 and have the double button press issue too.
And the TVos thing you talked about and I thought I was going crazy because for the life of me I couldn’t get me AppleTV to connect to HA anymore… I hope this is something that can be fixed!