thank you for the hard work !
Build is with Apple now, probably another hour or so until release.
Just deployed a server side fix for this, let me know if you are having issues.
Well, Apple made me a liar I guess. Build 39 is out. Go crazy brazy.
Yes, aware that the error about ObjectMapper keeps popping up, it should be ignorable for now.
I seem to be getting a connection error whenever opening the app without it already open in the background.
Known issue I just mentioned about ObjectMapper. Fix will be in next build but it should be ignorable.
Yes sorry I missed that post somehow. Thanks again for the great work. Location services still seem to be missing
The location issue was covered in release notes
Will be fixed in 0.91.2 which drops tomorrow morning Pacific Time.
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
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
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.
Yep, 0.91.2.
Documentation is correct.
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 yourconfiguration.yaml
,mobile_app
should automatically be set up, you’ll see lines about it in your HA logs. - Add
mobile_app
to your configuration.
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.
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
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
I believed he fixed the extra options errors with this PR to be released in HA 0.91.2
mobile_app fixes
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?
notify.mobile_app_shinydevice
working well now, on build 39.