I’ve tried typing out my Ip address given to me right from the device I’m running HA on (mini pc), and tried the homeassistant.local in browser, but neither work. However on my phone with the IOS app, which shows the same IP address as on the monitor connected to the mini pc, it works fine. Any ideas?
Are you using https when you should be using http (or vice-versa)?
Have you included the port number?
e.g.
http://192.168.1.120:8123
When entering the IP I don’t use either http or https…but I’ll check that out
None of that worked.
How did you install HA because in most cases the machine that has HA doesn’t have a browser.
Also, some browsers automatically might switch to httpS
Installed via USB drive, x64 if I remember correctly it’s been a while.
Yes, didn’t work 
Settings → System → repairs → 3dots in upper right corner → System information
What does that show ?
System Information
| version | core-2024.9.1 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.12.4 |
| os_name | Linux |
| os_version | 6.6.46-haos |
| arch | x86_64 |
| timezone | America/Winnipeg |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 1.33.0 |
| Stage | running |
| Available Repositories | 1466 |
| Downloaded Repositories | 13 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | September 16, 2024 at 7:00 PM |
| relayer_connected | true |
| relayer_region | us-east-1 |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | true |
| google_enabled | false |
| remote_server | us-east-1-11.ui.nabu.casa |
| certificate_status | ready |
| instance_id | b63da9d52061448e99967305b86d2746 |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 13.1 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2024.09.1 |
| agent_version | 1.6.0 |
| docker_version | 26.1.4 |
| disk_total | 116.7 GB |
| disk_used | 8.2 GB |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | |
| board | generic-x86-64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Advanced SSH & Web Terminal (18.0.0), Studio Code Server (5.15.0), Node-RED (18.0.4), Docker Wyze Bridge (2.9.12), File editor (5.8.0) |
Dashboards
| dashboards | 5 |
|---|---|
| resources | 8 |
| views | 4 |
| mode | storage |
Recorder
| oldest_recorder_run | September 14, 2024 at 8:10 PM |
|---|---|
| current_recorder_run | September 15, 2024 at 7:56 AM |
| estimated_db_size | 21.21 MiB |
| database_engine | sqlite |
| database_version | 3.45.3 |
Can you ping the ip address from the computer you try to browse on ?
Forgive me for asking but, how do you do that? If you mean using the IP address shown on my device ( I have a monitor hooked up to it) then yes I’ve tried that. Using http and https, nothing works
Wow so the issue was is that my PC was connected via WiFi, and ha was plugged into a router. When I plugged PC into same router…. Boom… it popped up!!
1 Like
Wow so the issue was is that my PC was connected via WiFi, and ha was plugged into a router. When I plugged PC into same router…. Boom… it popped up!!
glad you got it… you maybe able to connect to your HA when you are on your wifi as you mention but the network design needs to be reviewed for your case