Do you have Nabu Casa Cloud? If so, can you enable the remote UI and try again? cc @kolossboss
All good being stuck - that’s why we beta test 
I don’t use the cloud service at all - I only access it directly via a duckdns domain.
Yes, I tried duckdns and HA cloud. Always getting back to the start page.
The instructions are a littlebit unclear too.
Do I have to insert my HA address in the white field?
Same experience here
So I upgraded to 92.1 and app works I don’t know if it was related to previous version or home assistant needed to restart.
Now I‘m at home and scan for HA instance works.
Dont no y manuell configuration wont work
I can’t find the option to set the device id anymore…
Is it possible to make an easy way for choosing Home Assistants in the app?
I installed Home Assistant to grandmother’s house and would like to see something like this (mi home app)
1 Like
Fixes for manual entry and other small bugs is in the next build which I just started building a few minutes ago. ETA 1.5-2 hours from this moment.
Hi,
Does the next build also fix the inability to configure an External and Internal URL?
I’m running HAS 0.92.1 and in build 40 i set my nabucasa URL as External and internal IP for Internal and all worked via wifi and cell.
Upgraded to build 42, i got the green checkmarks on the new (and extremely cool) new onboarding screens, but in configure i have only External URL defined and it’s the internal IP address. If i click into it and out of it i get a 400 error (full message is “Response status code was unacceptable: 400”) and from the HASS logs i get:
2019-04-29 01:35:45 WARNING (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid JSON from mobile_app
i get the same error every time i try to edit the Internal or External URL (with either internal or nabucasa URLs).
As a side note: on Wifi using the internal IP it all works fine.
We’re working on new docs to explain more about this, but the quick version is this:
Most people have a base_url set with something like a DuckDNS URL that lets them access their HA from outside of their network. If you don’t have a base_url set than HA automatically gives me http://IP:Port. Some people are starting to rely entirely on the Nabu Casa Cloud for external access now, which is awesome, but I don’t want to remove the external/internal URL functions for those that aren’t. I only ever fill in the external address with whatever your base_url is, never fill the internal address, that’s up to you. External address should be an address that can be accessed from outside of your home. The latest build supports automatically detecting and using the remote UI and cloudhook to communicate, if you have those set up.
Speaking of, big announcement: We finally have the beginning of real documentation for 2.0! PLEASE feel free to submit suggestions and edits by hitting the Edit button at the top of any page or via GitHub. Please make sure the version at the top says next while navigating around to see the 2.0 docs. The 1.0-1.5 docs are the default version (1.0.0).
1 Like
Hi,
I don’t have base_url set, but i do have nabucasa with remote access and webhooks enabled, but they’re not showing up in the app and i can’t define them (keep getting 400).
anything i can do to debug the matter?
if it makes a difference, for some reason i have 2 webhooks showing up with the same phone.
Also, i love the idea of using an internal IP when i’m home, and using the Nabu Casa remote access when out. great feature to keep.
2 Likes
Don’t use the Nabu URLs in the configuration. The app automatically finds the URLs and uses them without you having to do anything. Just leave your external URL as is. The URLs are tried and used in the following order:
- Internal URL if current SSID == previously stored SSID that confirms internal is available
- Cloudhook
- Remote UI (may require turning it on via REST API if available)
- External URL
1 Like
Automatic setting sounds great, but as is, if i’m on my wifi, all works. i turn off wifi, won’t connect (black screen).
It worked fine in build 40.and connecting via web browser to the Nabu Casa with wifi disabled also works fine.
Am i missing anything?
Is your remote UI turned on?
Do you mean the Remote Control feature in the HA Cloud config? If so, yes.
BTW: I’m sure it’s besides the point but also happens in the build 43.
Finally got push notifications working for 2.0b43 
There is some strange behaviour though, when the doorbell is pressed, I send a push notification with the camera stream attached. On the stable app version it shows a preview for the camera stream, on the 2.0 app it doesn’t. When I press and hold the notification the stream shows for both versions so it seems only the preview doesn’t work.
I’m aware camera notifications are broken atm.
1 Like
