-
-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android HomeAssistant app will not connect locally over WiFi to install Matter device. #4877
Comments
please provide the error you get in teh app logs when you see the pop-up, the logs were requested as part of the issue template which appears to be below everything you wrote. Please make sure to fill out the template completely as well. |
Sorry. I hope this is what you need... Home Assistant Android app version(s): 2024.10.3-full Android version(s): 14 Device model(s): Google Pixel 6A Home Assistant version: Last working Home Assistant release (if known): Description of problem, include YAML if issue is related to notifications: Companion App Logs: Screenshot or video of problem: Additional information: |
error -2 is a host look up error, may be having an issue with your local DNS https://developer.android.com/reference/android/webkit/WebViewClient#ERROR_HOST_LOOKUP this is not an error the app can solve, what is your networking setup like? that may help narrow down the issue you can also just use the IP directly if the local host name does not work out in your network |
Found the problem. Matter enabled devices need the HA App to be connected to the same network as the Matter device. You either need your HA ecosystem to be LAN (WiFi) only (mine was not), or if you want secured access via DuckDNS for remote acceess, you then need to setup a temporary reverse proxy using the NGINX addon. Once configured, your phone can connect over WiFi to the HA server which then allows you to add the Matter enabled device. Once the devices is added, I was able to disable NGINX and go back my secured access over DuckDNS when then allowed me to access HA from my phone over the carrier's data network and securely from a web browser. Bit of a pain in the neck, but with some instructions from K Peyanski, it seems to have worked. |
As a new Home Assistant user, I have a web interface that is working well using the local IP URL https://10.0.0.11:8123/ which defaults to non-secure mode.
My local connection problem is stopping me adding a Nest thermostat (Gen 1) via Matter. HA requires the Nest to be fully installed through Google Home (to view the Matter QR code), and then added to the configuration via HA app running on Android ver 14.
HA app connects to HA server (running in a ProxMox virtual environment 8.2.4) when connecting over wireless data through DuckDNS, but I cannot make it connect to HA server properly when switching to WiFi.
When the phone is WiFi, the phone can successfully ping the local IP address (10.0.0.11) and can ping server name homeassistant.local returning the local IP address (10.0.0.11)
In the HA App:
Home assistant URL set to https://xxxx.duckdns.org:8123/ (again - worked well on the carrier's data plan)
Home network WiFi SSID to the on-premises network SSID
Internal connection tried multiple ways to no avail:
http://homeassistant.local:8123/
Refreshing the internal connection returns "There was an error loading Home Assistant, please review the connection settings and try again...
Also, with the above setup, I can only connect when I turn off WiFi on the phone and connect using DuckDNS. i.e. When on WiFi, the app will only let me in the the settings which I've been trying various internal connection settings.
If important, the environment is in a Shaw/Rogers (Canada) environment that uses an ARRIS router/modem Model TG4482A (not in bridged mode). Also running Bitdefender security software on the remote PC (works fine), and on the phone.
Any suggestions would be greatly appreciated.
Home Assistant Android app version(s):
Android version(s):
Device model(s):
Home Assistant version:
Last working Home Assistant release (if known):
Description of problem, include YAML if issue is related to notifications:
Companion App Logs:
Screenshot or video of problem:
Additional information:
The text was updated successfully, but these errors were encountered: