That PR fixed the update location issues but sadly it’s a total of 4 PRs for mobile_app going into 0.91.2.
Hi
Got 404 issue couple of times during the day. Right after that I tap “ok”,”done” and everything works.
I am on 91.0, using remote UI
That’s because of the missing get_zones call which was supposed to be in 0.91 but got missed during the cherry pick. Will be in 0.91.2 which leads me to my next post…
0.91.2 is delayed to tomorrow Pacific time, sorry everyone! Got another build coming up tonight though with more bug fixes and the return of all the sensors, except this time via mobile_app!
1 Like
I keep getting “Token is expired” and “An SSL error has occured”.
I’m not using cloud remote UI, but it doesnt seem to work without it, am i forced to use the cloud remote UI?
No, of course you aren’t required to use the remote UI URL.
Token is expired means the token legitimately is expired, or at least the app thinks it should be. As for the SSL error, is this a new thing you only started experiencing in 2.0?
Yes, I still have 1.5 installed and that one works fine.
If i turn on cloud UI it works instantly, but not when its disabled.
App is pointing to my own URL
Y’all wanna know my dedication to you? I just took like 3 years off of the life of my MacBook Pro by cutting a new release of the app to add sensors while simultaneously cutting the release of 0.91.2. It’s on PyPi now and Docker builds are underway. Have at it
7 Likes
Fine. Just wanted you to know. Thank you.
How to get process list in my rpi as you are having
It would be great to have in my rpi.
Can you please share your config.
Thanks in adv.
I was hoping if we can get like this feature in our rpi,
Sorry if you feel it wrongly.
0.91.2 is out on PyPi and Docker Hub. I strongly suggest everyone Reset your app if you are still experiencing issues.
Build 40 was uploaded to Apple about 20 minutes ago so it’ll be processing for another 1.5 hours or so. I’m going to bed. More fun tomorrow!
No sadly, not as far as I know.
When I create a Shortcut with input_boolean_turn_on with only 1 entity, it turns on all input_boolean entities. Am I doing something wrong?
I cleared all settings, reinstalled the app, removed all references to the mobile_app component (refresh tokens etc) and restarted Home Assistant, still get the error.
The exact error is:
An SSL error has occured and a secure connection to the server cannot be made
However it works fine in the old app and in a Safari. It seems really keen on trying to use the remote UI aswell even tho i specify my domain
The SSL error occurs when Cloud is enabled but remote control is disabled. Right now when the app gets set up it will always try to use the remote UI webhook. I consider this a bug btw…
3 Likes
I’m noticing a few things:
- Registration of the app does not use the “Device ID” set in the app config in any way?
- I’m getting several entries for my device “iPhone” in
.storage/core.device_registry, and HA complaints about duplicate device names (code ref). Resetting the app or logging in again seems to add another entry each time. - I’m getting a “notify.mobile_app_iphone” service, but with a simple payload
{"message":"message"}i’m getting an error in HA ([homeassistant.components.mobile_app.notify] Internal server error, please try again later: That is not a valid FCM token) - None of the entries seem to have a push_token or push_url configured?
Am I missing something in my config? I’m running build 40 / HA 0.91.2
Ok, so I’m running 0.91.2 and 2.0 build 40. Critical alerts are working (that alone is worth my patreon contribution), so thank you @robbiet480 !
I’ve got a couple of questions:
-
Can’t really grasp how to get this whole apple watch complications thing working (a how-to would be nice)
-
I can’t seem to get the “new” data (Pedometer data) (it is authorised)