I hope I’ve put this in the right category as it probably falls under more than one.
Recently I’ve been having problems with automations not working properly and devices dropping on and offline in Home Assistant. After doing some digging around in the network settings I found Docker has IP 172.30.232.1, home assistant OS has IP 172.30.32.1, the host IP is 192.168.0.2xx and one showing as “Lo” of 127.0.0.1 which I know is loopback.
Could someone advise if this seems right? To me, this doesn’t seem right as I can’t see how they all talk to each other let alone how port forwarding entries can work with several different IP’s and I also don’t understand why it would be using loopback either. Shouldn’t they all be using the host IP?
I’ve tried looking for network config for them all but have only found the main host network config in the UI. I spent hours in the file editor seeing if I could find anything to give a clue about these IP’s
I run Home Assistant via Vbox on a designated mini Windows 10 PC. Docker Machine has never been installed so am a little confused as to why it’s showing in HA so wonder if this could be the cause of my issues.
Any help or suggestions from those of you more experienced gratefully received
No. HAOS is a docker container. I am a strong advocate of HAOS bare-metal because it makes little sense to complicate your installation with unnecessary containers or virtualization. But, HAOS core and all add-ons are in docker containers, so this is why you see a docker IP address. The beauty of bare-metal is that you never have to worry about the configuration and management of Docker. Ignore the 172.30.x.x IP addresses.
For the automations, look at the traces to see why they aren’t finishing.
For dropping on and offline, you need to be more specific. How are you determining if a device is on or offline?
Just for curiosity, so how VM installation fits into this picture? Is it HAOS installation running not on bare metal but as VM or is it Supervised running as VM…
You’ll have to forgive my ignorance, but whilst I’m pretty proficient in general computing and networking etc, I only started getting involved with HA in January, so appreciate the clarification about docker.
The automations aren’t even running most of the time and I know there is nothing wrong with the config as when I run them manually they work as expected. I’ll try briefly explain - I have a number of Hikvision camera’s connected to a DVR. I’ve installed and setup the Hikvision addon in HA along with all the required port forwarding and the camera feed to HA has always been spot on with no issues as I have them permanently displayed on a display along with other stuff like my solar panel info etc. But I have 1 automation to display a camera full screen when it detects motion and another automation for when another camera detects motion to turn on an outside light. As I say, when run manually they fulfill the intended action. Upon investigating the Hikvision logs within HA, they are not picking up motion events from the cameras, which is why and from a place of ignorance I wondered if it could be down to all these different IP’s and port forwarding. I’ve spent hours tweaking the config and the port forwarding but every time I’ve managed to get motion events to show within the HA Hikvision addon and automations to fire as expected it very quickly stops working again.
My router generally has around 41 clients with all my smart lights and devices etc. The PC running the HA server is connected via LAN as is my Hikvision DVR.
I don’t think I explained the problem very well in my initial post, I was trying to keep it as short and sweet as possible, but you’ll see a far better explanation in my reply just now to Steve.
When doing my research online before setting up HA, I was aware that it works best installed directly on a linux system or similar, but was too nervous to attempt to change as I have no experience with those OS’s. I’ve installed fresh versions of Windows loads of times which has sometimes been challenging (more so with older windows versions) setting up devices with right drivers etc when I pretty much know Windows inside and out I just thought I had no chance with an OS I know nothing about.
Mind you, me saying it’s installed on a mini PC, it was very old and gave up the ghost a few weeks back. I still run HA on a designated PC but it’s a HP all in one where everything is integrated in to the screen - purely as it’s touchscreen so ideal for HA. Can Linux still be installed?
You can install Linux, but the touchscreen probably won’t work.
Home Assistant is basically a server with a web based UI. Home Assistant is expected to be running 24/7. You manage it from any web browser on your network.
Many people do use the Raspberry Pi, and the Orange and Green use similar hardware. But if you are serious about exxperiencing this rabbit hole, you should run Home Assistant on a micro PC like the Intel NUC.
The easiest installation is HAOS on bare metal. HAOS is the operating system. It runs with a minimalistic Linux operating system but you never need to know Linux. Everything is done in the UI on your web browser.
If your router is one provided by the ISP, then you could be on the fuzzy limit of the router’s capability. The symptoms would be clients will go offline at random and new clients have a problem connecting. The primary limiting factor is the amount of RAM in the router to hold the routing table.
I’m with Virgin Media for my broadband, but have never liked their hubs as a router so have always just used them in modem mode with TP Link routers. I’ve got an AX20 at the moment which I believe has 256mb RAM. I do keep an eye on the router performance and it seems to be okay.
