Just upgraded my hardware to a thin client from a rpi3. All went well, restored , everything good, access to dashboards was fine.
I disconnected and reconnected after moving the server to its final position and then couldn’t get an ip address.
Tried switching it on and off a few times and it would connect for a minute then disconnect again.
Reset ip from the cli thinking I may have set a static IP in ha and was causing some conflict, and all was good again. Left it overnight and everything was still ok.
So this morning after moving it again, same issue, no ip. Same port on switch, tried different cables.
Any ideas?
Don’t think, have control over/know your vital settings, and get familiar with IP home-networking, And your Router, as it have the Master Role in your network, don’t think or hope for miracles
Thank you for such a helpful comment
Try to describe your “issue” in a structured manner.
Have a look in you Router first, if HA is not there ok, i assume you have a monitor so you can access HA-CLI again.
Then provide status of your “findings” in form of copied text or pic
Just hearing your "Swith HA on and OFF few times , and moved your HA 3 times makes people hmmm
Make sure you also turned of rpi3, as you said “conflicts” no 2 same name on the network
Shortly, give people something to go on.
Ideas, yes alot we all have
1 Like
Don’t get touchy - a systematic approach is the most efficient method to solve your problem. Guessing or hoping may not solve the underlying issue. A detailed read of the actual documentation can often uncover settings that are critical to reliable operation, and AI slurp will not cover it. The suggestion offered is a wise one. There is more than one area that may contribute to your frustration, and eating the chocolate elephant one bite at a time is a well trod path to bliss.
Is that faulty? Is the new RJ45 cable firmly clipped in on both ends?
Is the problem with the HomeAssistant server or the device you are attempting to connect to it? The server may be repeatedly crashing, and your network may be fine.
Document all your IP addresses, DNS paths, and how your LAN and internetz connections now happen. What IP Address is static, what is dynamic, what is internal. Where are they allocated from. Hopefully the issue will become self evident if is a networking issue, or even a configuration oversight. As a bonus, your understanding of networking troubleshooting should rise considerably.
What software are you running on your new setup that you weren’t running on your old? Any traces or logs there that might offer clues?
Once we have more clues, the bugs will surface.
