I must be doing something wrong. Purchased HA Yellow CM5, 1TB NVMe about a year ago and have not been able to set it up so that I can reliably log in. If I let the device sit without looking in for a week or so, it will lock up and will give me the HA Logo but no login page. I then have to pull the power to reset (in fact I typically have to do this multiple times) before it brings up the login page.
I have only been able to add devices to the HA Yellow but never started any automations as the system is too unreliable
Is this something others have experienced or is it just my install. It has been doing this over multiple HA SW Revisions.
I am impressed that that from the description people have determined that the IP address is changing.
If that is indeed the fact, I would recommend that you assign the IP in the DHCP server which is typically your router. This is sometimes called “reserving” an address
When I log in, I get the HA Logo. It just doesn’t go to the Login Page. So, I can check to see if I set up static IP, I did this a while ago, but that is not my issue (unless there is some quirk that I just am not aware of that DHCP introduces) Would love to be enlightened
By the way, I really appreciate everyone’s response. I didn’t expect such fast response. When this issue happens again, I will provide more details.
If you ever have a problem with HA UI when trying to view it in a browser refresh the browser cache before trying anything else. It may not be the issue but is known to solve many issues with the UI.
Thanks. I had not tried that but when this problem occurs, I see it on my Desktop as well as the HA App on my Android. Maybe the issue is resolved after reserving the IP in my router. If it occurs again I will try this suggestion as well.
Happy (kind of) to see someone else with such a problem.
My HA on Yellow regularly stops responding (everlasting circle). I always kindof assumed this was something wrong with my setup, and didn’t gave it much thought, as I just host z2m on it, which continues to work fine.
My “workaround” is to ssh to the Yellow and restart the HA container, so the Yellow itself is 100% fine.
My containerized main HA instance never showed such symptoms, and that prevented me to move HA to the Yellow.
I’m considering buying a ZBT2 (hoping migration work) and repurposing the yellow.
I have similar problems sometimes and they’re always due to something weird in the networking. I blame my router, which is provided to me by my internet provider. I have noticed that I sometimes cannot reach HA from the app, but then I can get there via browser.
I found that weirdly enough, it is less likely to become unreachable if I connect my HA instance through wifi instead of ethernet. That’s not a recommendation, since for most people it will be opposite.
I personally think that you should use your provider router just as gateway for internet and buy dedicated router(s) to serve for local wifi, dhcp, firewall etc.
This was my opinion from begging and that is how i use it today.
Yeah, makes sense. It just hasn’t been high on my priority list. For most devices, it just works. There are only two or three devices that are troublesome. One of them is the ethernet passthrough to the HAOS virtual machine. But that can be easily circumvented by using wifi instead of ethernet. The other two were giving problems even before I had this router so I am afraid getting another one won’t solve it.
Well you know wifi is backbone of every smart home ha included. I dont see how can you make reliable system without decent infrastructure. Maybe someone will argue different but I don’t think it will work.
I tried different solutions and settle for openwrt with batman for local wifi routers and opnsense as gateway. It is good comination, but it takes a lot of time and effort to set it up.
getting back to my original issue. As I suspected leaving HA running for a 6 days now with the IP Address Reserved in My Router, I am getting the page shown in the picture here. This will stay there indefinitely with browser refreshes. I also tried on Edge and Chrome and cleared Browser Cache. When logging into my router, I see it is still using the same IP Address that I set as reserved.
