Home Assistant for iOS 2.0 Beta Testing

[DavidFW1960 (David)]

I had a nightmare with this a day ago. If you rename the entity id you end up with dupes…

Yeah nice eh!

So I went scorched earth as when I added back stuff I ended up getting _5 and _6 lol…
I think this is because of 0.91.2 and 40 changes.

Anyway, I wrote a new scorched earth procedure for mobile app:

1. Reset Mobile App and force Close
2. Delete iOS Tokens (Login)
3. Stop Home Assistant
4. Delete mobile_app
5. Edit core.config_entries
   Delete all mobile_app, iphone, ipad entries
6. Edit core.device_registry
   Search for and delete iPhone & iPad entries
7. Edit core.entity_registry
   Search for and delete iPhone & iPad entries (Probably none)
   Search for and delete all mobile_app entries
8. Edit core.restore_state
   Search for and delete iPhone & iPad entries (Probably none)
9. Restart Home Assistant
10. Load App and auth
11. Force-close app and open
12. Check in settings mobile_app tick
13. Goto notifications import push settings (probably don’t need to)
14. Send one-shot to server from app
15. Restart Home Assistant again
16. Should have integration and notification settings now
17. Get Device ID’s from core.device_registry and setup in customize.yaml
18. Delete known_devices.yaml and restart home assistant
19. Push a one-shot again to make new known_devices
    Fix Lovelace ID’s

I am also not using ios: as I don’t care about actionable notifications. (and I only use the new beta 2 app)

[akkaria (Adam)]

Mine too is very choppy. Even just scrolling through the settings page.

[glassbase]

You will have both notify.ios_xxxxx and notify.mobile_app_xxxxx as beta app transitions to mobile_app platform. Eventually notify.ios_xxxxx will be gone (is what my understanding is when reading this thread).

ios service uses the Device ID configured in HA app. mobile_app uses the Apple Settings - General - About - Name.

(You may not have notify.ios_xxxxx if you reset the app since updating to new beta version. And / or if you don’t have discovery: enabled or ios: component enabled)

[DavidFW1960 (David)]

No the iOS ones are gone.

[glassbase]

Yes. I read above (can’t find the comment now) that if you registered the app with HA and did not reset the app, you will have both notify services. But if you reset HA and updated app to v40 or 38 (I think), you will only get notify.mobile_app

Again, I cannot find the comment above that stated that. But I know I read it the other day.

EDIT - sorry the above was mentioned in TestFlight release notes.

[glassbase]

How do we get both ios and mobile_app to initialize? Or can we not when using mobile_app? I want to use ios actionable notification but iOS component not even shown in app anymore. I only show Mobile App component loaded in app settings? The others are not shown (iOS, location, and something else).

[ha_steve]

@jimz011

Btw did you check all your entities? Probably there are new device trackers with an ID that has a bunch of letters/numbers. I posted this a bit earlier. I have completely new device tracker entities since version 39. I’d look there first. I found it by accident as it were the only device trackers that had the correct zone where I was yesterday

Sure… but this can’t be the “correct” way, no? It should be using the name of the device?

[VirtualL]

First. It’s was only the location.
After endless trying to make it work.

Added back the webshocket and its worked!

[Flipso (Fli)]

… i only wanted to say that i really appreciate your hard work and love your 2.0 beta!

[jwelter (John Welter)]

The “trash can” in the integrations for mobile devices seems to wipe most of the manual steps you do.

I used this and everything was automagically cleaned up after a re-start which it tells you is required

[Dayve67 (Dave)]

@akkaria

Mine too is very choppy. Even just scrolling through the settings page.

Ya same here. I thought it was my animated weather card causing it until I went to the settings page and it was the same.

[Steven_Rollason]

There is an issue with the 2.0 Beta when using the Compact Custom Header. It looks like the app hides the toolbar (Settings, Refresh, etc.) until it detects a swipe down but it seems to do this by detecting a scroll event. Since CCH reduces the overall height of the page, it seems to stop this working unless there are enough cards on a view that the page is scrollable.
I have mentioned this on the CCH thread, but I would think that a better better method of showing/hiding the toolbar is probably needed rather than relying on page scrolling.

[jimz011 (Jim)]

@Steven_Rollason it isn’t the custom header that does this, it is the app itself. In the latest beta patch notes (version 40 or maybe even 39) it is said that when you are on a page with insufficient cards you could simply shake the phone to get the toolbar back.

For some reason though the swipe action seems to work fine for me on some pages and some not since the last update even on pages with only a single card.

Shake to get the toolbar works fine though.

[lolouk44]

My logs are littered with errors like this:

2019-04-10 08:23:57 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_battery
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_bssid
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_connection_type
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_ssid
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_activity
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_last_update_trigger
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_battery
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_bssid
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_connection_type
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_ssid
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_activity
2019-04-10 08:23:58 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Refusing to update non-registered sensor: 1228e0af7c469b...922aad983fe3c25427c9b44a8_last_update_trigger

Any pointers?

[TomBrien (Tom)]

Looks like your it’s trying to update sensors with the form sensor.UUID_battery etc. currently the sensors are just sensor.battery. Are you running the latest beta and 0.91.2?

Just a guess but you could follow the pointers above to delete the offending entities:

@jwelter

The “trash can” in the integrations for mobile devices seems to wipe most of the manual steps you do.

I used this and everything was automagically cleaned up after a re-start which it tells you is required

Then carry these out to get them back:

@DavidFW1960

9. Restart Home Assistant
10. Load App and auth
11. Force-close app and open
12. Check in settings mobile_app tick
13. Goto notifications import push settings (probably don’t need to)
14. Send one-shot to server from app
15. Restart Home Assistant again
16. Should have integration and notification settings now

[lolouk44]

thanks, it was the version, I was still on 0.91.0. Somehow my HA update available notification didn’t work for 0.91.1, 0.91.2 nor 0.91.3 which I just installed and it’s now looking ok

[DavidFW1960 (David)]

I have just found even after a restart they can be persistent little buggers.

[robbiet480 (Robbie Trencheny)]

You now need to specify the push sound always in your payloads. This is so that silent notifications can now be sent.

[robbiet480 (Robbie Trencheny)]

Nothing relating to the app or mobile_app if there are random reboots…

[robbiet480 (Robbie Trencheny)]

Fixed in 0.91.3 as I’m guessing you know by now.