Hi All,
I just got HA green and have it connected to UDR7. I see the device in the device topology and know that it has a valid IP. I was able to ping it successfully from another pc on the network. But I am not able to find the device with the HA app or connect to it from the browser using the IP address.
I checked the network settings and mDNS is enabled and nothing blocking or filtering traffic.
Not sure how to proceed further.
Are you using the port? 8123?
yes. I tried using that port. it says it cannot connect to the server.
Can you show a screenshot? What browser(s)? attach the screen capture using the graphic icon located just to the right of the coding block (< / >).
Did you install SSL certificates?
I have tried safari and Firefox on my MacBook Air and chrome on another pc. On the Macbook it says that safari cannot connect to the server.
Where is the :8123?
I tried using 8123 port but it shows the same message. HA companion app on my iPhone keeps searching for the device on the network but cannot find it. I tried reinstalling HA app on iPhone, blocking location access but still cannot connect.
How are you over riding the browsers for https versus http ? You normally have to setup an exception for that address and port in the browser for using http
No VLANs, segregation, privacy settings, guest or IoT network/WiFi?
Not aimed at the original thread starter but a general comment:
Seeing a few Green connectivity threads. Is there a bigger issue with design and integration during installation, a documentation quality issue, or just a reflection of user inexperience?
Even in a complex network setting, it shouldn’t be this hard to get going. Error checks, default settings, return codes with comprehensive logging should all contribute to better user experience, and effective troubleshooting.
Does the specifics of the Green need a little love? Is a specific FAQ needed?
I think the HAOS/HA core could use a better notification standard for when DNS issues arise.
It is not just the Green that are subject to this issue and the Green or HAOS/HA Core is not even the culprit, it is usually the ISP, the router or the DNS server that cause the issue, but HA could still implement some triggers to send a notification when it happens.
Standard procedure would be to attach a monitor,mouse and keyboard, and go on from there
The DNS issue often just have HAOS running in circles sadly with no sign that it is DNS that is the culprit.
Nope. Default VLAN. No privacy setting or firewall. There are no guest networks. There is only one wifi network on the router.
1 Like
nairsunils
“Default VLAN”
Uh oh! Ain’t such an animal. Here be dragons.
DNS? It’s always DNS™…
Is this relevant? Do you have the battery installed?
I tried to connect HA green to a monitor. The system information shows IPv4 address for end0 as no address. When I type core info command it indicates IP address as 172.xx.xx.x
Port shows 8123.
I am not sure how to proceed.
I did not have the battery installed and got a low voltage message on the console. I installed the batter and set the dns as per the following link. But after a short while I got the low voltage message again. I will have to check the battery again.
A 172.x temporary IP Address indicates you are still having issues with network access to the internet.
Go back and check your DHCP settings on your router and preallocate a static IP address for your green that you can consistently use to access it.
Close down everything and switch it off, and power it back on again. Router first, and then the green after the router lights indicate successful internet connectivity.
Wait a few minutes for everything to stabilise.
Tell us what IP address your router is, and the IP Address you have allocated for your green.
Are you connecting your green via WiFi or Ethernet?
What devices do you have plugged into your green?