Home Assistant for iOS 2.0 Beta Testing

DavidFW1960 · April 17, 2019, 8:02am

you need to create a notification group. Here is what I use:

notify:
  - platform: group
    name: David iOS Notify
    services:
      - service: mobile_app_davids_iphone
        data:
          data:
            push:
              sound:
                name: default
      - service: mobile_app_davids_ipad
        data:
          data:
            push:
              sound:
                name: default

Then I can send notifications to notify.david_ios_notify
(it also fixes the sound back to defaults again)

johntdyer · April 17, 2019, 1:45pm

I am unable to get push notifications working on the beta. I am using build 40 against 0.91.2. I have tried the following:

Remove all mobile apps in “integration” and then restart hass. Then reset phone via app and re-log in.
“import push configuration from server”
Changing the name of the app and doing the above
Crying a bit

At this point I dont even see the device listed as an available target to notify, and when I try the old name I get an error related to rateLimits

2019-04-17 09:47:54 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.139992112233104] 'rateLimits'
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api/commands.py", line 122, in handle_call_service
    connection.context(msg))
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/core.py", line 1138, in async_call
    self._execute_service(handler, service_call))
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/core.py", line 1160, in _execute_service
    await handler.func(service_call)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/notify/__init__.py", line 117, in async_notify_message
    await notify_service.async_send_message(**kwargs)
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/ios/notify.py", line 103, in send_message
    log_rate_limits(self.hass, target, req.json())
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/ios/notify.py", line 23, in log_rate_limits
    rate_limits = resp["rateLimits"]
KeyError: 'rateLimits'

Here is my config in the app as it stands now

Nothing seems to work via the new app… Any suggestions ?

kolossboss · April 17, 2019, 3:56pm

Ok nice, this works for me, too. Little bit complicated in my opion…

But why is to old notify.ios not working anymore?

Edit: Ok I think its because the notify ios target

Argo · April 17, 2019, 3:57pm

Good day. I thought that it would be great to have taptic engine working on toggling for example. Is it hard to do?

TravelinMax · April 17, 2019, 4:46pm

This was fixed in 91.3

jimz011 · April 17, 2019, 5:31pm

I am guessing it will be hard as the app is basically a webviewer. You just present your lovelace setup through the app (or states ui). I think the only way to make this possible is to have a fully native app (something like hassapp, Hassapp: An alternative iOS app to empower your HA)

It would be cool though, but to me it sounds like impossible.

Piggyback · April 17, 2019, 9:16pm

See my post above. Had this issue too.

robbiet480 · April 18, 2019, 2:47am

Hi all,

I’m back again. Had the worst food poisoning of my life. Hit me on Friday morning and I didn’t fully recover until Tuesday afternoon. Glad to be back to work on the app. Working on getting the things that were supposed to be in 0.91.4 into 0.92 now. Build 41 still requires them, so no new builds until new Home Assistant version is out.

Thanks

TravelinMax · April 18, 2019, 2:59am

Where’s that tip jar? We can help you feel better! fryshutupandtakemymoney

Seriously though I’m glad you’re feeling better. I have been meaning to ask you to please not kill yourself working on this beta. Don’t forget to eat and sleep and rest when you’re sick!

robbiet480 · April 18, 2019, 7:34am

Yeah that would be pretty hard to implement…

Thanks for the idea @Argo, it was really awesome and easy to do!

The iOS side of the equation will be in build 41 but it will only start working if and when the above linked PR is merged and a new frontend build is released.

Argo · April 18, 2019, 8:12am

You are just awesome
Thank you

jimz011 · April 18, 2019, 8:15am

Ooh that is pretty cool. Didn’t think it would be possible. Great work.

robbiet480 · April 20, 2019, 9:21am

0.92 was delayed a week as some of you know which has given me plenty of extra time to squash more bugs and flesh things out. Here’s a sliver of what to look forward to in the next beta:

Push notification sound management entirely in app. Import and delete sounds without having to use iTunes. iTunes remains supported though.
Utilize Apple’s system sounds for push notifications. This adds 296 new sounds to the library. This might not make it to the App Store if Apple doesn’t like it.
Previously mentioned Haptic Feedback support
RIP toolbar. App now has pull to refresh and settings can be opened via a new button in the HA front end
Fix for actionable notifications importing

Plenty more where that came from. Expect to see a build in the next few days, probably when the next 0.92 beta hits or on release day at worst.

ajoyce · April 20, 2019, 3:59pm

This is fantastic Robbie, great work. Quite pleased to hear the toolbar is dead as the buttons never seemed to render properly with my custom themes!

Thanks also for confirming that 0.92 is coming a week late - I wondered what had happened to this week’s slice of goodness!

DavidFW1960 · April 21, 2019, 2:45am

What happened is the punishing release schedule didn’t leave enough time for proper testing and adding new stuff so they are moving to a 3 week cycle.

ajoyce · April 21, 2019, 7:56am

Good, makes sense

Piggyback · April 21, 2019, 10:02am

Hi,
I noticed that with this IOS HA, sensors for battery level and battery state are not updated. Is that right? Not that it is hugely important , but was just wondering. Likely as this version has one tick for mobile component loaded?

Again, not important, just wondering.

kolossboss · April 21, 2019, 3:15pm

Hi,

thanks for the great work.
The old “notify.ios” Service is not working anymore.
I converted all notifies to the now mobile.app component. But it looks like, sending a camera pic/stream is not working. So I leave my camera notification the old style, but I get an error message. Whats the problem?

- id: '1514543372312'
  alias: 'Notify: Garagentür vorne wurde geöffnet bei Abwesenheit'
  trigger:
  - entity_id: binary_sensor.door_window_sensor_158d0001aad1df
    from: 'off'
    platform: state
    to: 'on'
  condition:
  - condition: state
    entity_id: group.all_devices
    state: not_home
  action:
  - data:
      data:
        attachment:
          content-type: jpeg
        entity_id: camera.kamera_einfahrt_onvif
        push:
          category: camera
      message: Bewegung am Carport
    service: notify.ios

Error Log:

Error while executing automation automation.notify_garagentur_vorne_wurde_geoffnet_bei_abwesenheit. Unknown error for call_service at pos 1: 
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/automation/__init__.py", line 380, in action
    await script_obj.async_run(variables, context)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/script.py", line 131, in async_run
    await self._handle_action(action, variables, context)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/script.py", line 210, in _handle_action
    action, variables, context)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/script.py", line 299, in _async_call_service
    context=context
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/service.py", line 88, in async_call_from_config
    domain, service_name, service_data, blocking=blocking, context=context)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1138, in async_call
    self._execute_service(handler, service_call))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 1160, in _execute_service
    await handler.func(service_call)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/notify/__init__.py", line 117, in async_notify_message
    await notify_service.async_send_message(**kwargs)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/ios/notify.py", line 103, in send_message
    log_rate_limits(self.hass, target, req.json())
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/ios/notify.py", line 23, in log_rate_limits
    rate_limits = resp["rateLimits"]
KeyError: 'rateLimits'

TomBrien · April 21, 2019, 4:07pm

Hi @kolossboss, a couple of things jump out at me, you’re not actually specifying a target for the notification and you have an indentation error. Try changing the action part to the below, replacing notify.ios_DEVICE_ID_HERE with the service you find in the drop down on Services page of the dev tools. I’ve never sent picture content personally but I have basically adjusted your code to match the example found here.

  action:
    service: notify.ios_DEVICE_ID_HERE
    data:
      data:
        attachment:
          content-type: jpeg
        entity_id: camera.kamera_einfahrt_onvif
        push:
          category: camera
      message: Bewegung am Carport

kolossboss · April 21, 2019, 4:54pm

Hi thanks for reply.

Notify.ios should send notifications to all ios devices. It works like that for nearly a year.