It appears that my phone updated to 2019.1 yesterday and resulted in my app forcing me to reconfigure my connection. I’m using Nabu Casa, which works fine via the web. When I enter my credentials into the IOS app, I get “Response status code was unacceptable 404.” Any other people having issues with the mobile app? iPhone 7 / IOS 13.2.2 connecting to Hass.io image.
Thanks
I am also getting this error too, very poor hassio !! worked fine yesterday, and as above can login via web browser on iphone fine. need this back up and running.
Put this to the discord group
“Don’t use the nabu url
Setup only works internal so the app can detect nabu and then setup some stuff there it needs”
I’ve got the same, but also on the older version of the app.
The new app won’t accept the Nabu Casa address. It will use the Remote UI perfectly but needs a direct connection to set up. Simplest option is to go through the setup while on the same network as your Home Assistant instance.
I uninstalled the app from my phone and after reinstalling I no longer have notification settings available in settings. Still the same result when trying to log in. Haven’t tried local login yet, will try that later.
I’ve never used Nabu Casa, only trying from local network via ip address. I get past the 2FA and then get the 404 error.
I am receiving the same with local login (as it’s the only option I have).
Is there anything of note in the logs on Home Assistant?
Reconfiguring while on my local network seems to have done the trick! Thank you for the suggestion! Now I’m just trying to get my push notifications working again. The built-in Location Notifications seem to work, but all of my automations no longer work.
Have a look at the migration guide: https://companion.home-assistant.io/en/getting_started/migration
It goes into detail about the necessary cleanup steps from new trackers and sensors.
Thank you.
Do you happen to use a reverse proxy? Maybe with its own authentication?
It seems you need to be on your local network in order to complete the migration. Nice that they pushed such a change while so many of is in the US are traveling for the holiday…
Depends on your setup… on mine I can update/install from anywhere as my HA instance is on the web. The thanksgiving holiday really did not come to mind.
I had this issue (404 - on my home network using duckdns address). I ended up killing the iOS app and starting again and the second time it detected my installation and allowed me to login. Not sure if it was killing the app or connecting to a different wifi AP in my home which did it.
I finally restarted the phone and the server and was able to get past the 404. However, now it’s on the onboarding step and in an endless loop over “Sensors Configured”.
Possibly relevant log entries:
2019-11-27 16:40:37 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mobile_app
2019-11-27 16:40:37 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mobile_app
2019-11-27 16:40:38 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook type: get_config
2019-11-27 16:40:38 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-11-27 16:40:38 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook type: get_zones
2019-11-27 16:40:38 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-11-27 16:40:38 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.mobile_app entity: sensor.average_active_pace_2
2019-11-27 16:40:38 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.mobile_app entity: sensor.distance_2
2019-11-27 16:40:38 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.mobile_app entity: sensor.battery_level_2
2019-11-27 16:40:38 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-11-27 16:40:38 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.mobile_app entity: sensor.floors_descended_2
2019-11-27 16:40:38 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.mobile_app entity: sensor.floors_ascended_2
2019-11-27 16:40:38 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.mobile_app entity: sensor.steps_2
2019-11-27 16:40:38 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-11-27 16:40:38 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-11-27 16:40:38 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-11-27 16:40:38 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
2019-11-27 16:40:38 ERROR (MainThread) [homeassistant.components.mobile_app.webhook] Received invalid webhook payload: required key not provided @ data['unit_of_measurement']. Got None
I ran into this issue too. I also have my HASS instance forwarded (no Nabu Casa) and use SSL. To get the new Home Assistant app to authenticate I disabled SSL in my config, rebooted HASS, connected using the unencrypted local IP that the app discovered, then reenabled SSL and updated the config in the app to point to my DuckDNS address.
I assume there is something about the SSL connection that is not working correctly, the certs are LetsEncrypt so shouldn’t have any issues with being trusted.
Bit of a pain but knocked it all over within a few minutes. The annoying thing will be fixing my housemates login!
If the app actually discovered the local IP then you should check your configuration.yaml file for the base_url: entry and set that to your duckdns address.