Home Assistant for iOS 2.0 Beta Testing

[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.

[robbiet480 (Robbie Trencheny)]

I’ve heard this report a few times and seen it once myself, still trying to nail this down.

[robbiet480 (Robbie Trencheny)]

As I mentioned earlier, you now need to always set a sound in your payloads. You can use the sound named default to use the built-in iOS sound.

[robbiet480 (Robbie Trencheny)]

Still working out issues with sensor naming. It’s not the final configuration, that’s for sure.

[robbiet480 (Robbie Trencheny)]

Hoping this was fixed for you with build 40 and will get even better in 41 once we have fallback URL types (see later replies for more info on that).

[robbiet480 (Robbie Trencheny)]

It’s probably a little of this and a little of that.

Current state of themes:

I do what essentially is a hack to piggyback on the frontend WebSocket connection and get themes data out of it. I only use very certain keys from the theme, so double check that your theme has these set:

• sidebar-icon-color for the toolbar icons
• primary-color for the status bar (where the clock and wifi/cellular icons are)
• sidebar-background-color for the toolbar background color.
  • If sidebar-background-color isn’t set, I fall back to using primary-background-color. If that doesn’t work I then fall back again to paper-listbox-background-color.

In build 41, maybe 42, I have implemented my own WebSocket client which should improve this situation a bit.

[robbiet480 (Robbie Trencheny)]

As I just mentioned to @terafin, I use specific keys that some themes may not have, so you need to double check your theme configs.