I don’t know if it’s because I’ve gotten a virus and a hacker did something to my HA or just a coincidence but a few days after the virus I stopped being able to access my HA via the external duckdns URL I have set up for it. On my browser it just shows the message Unable to connect to Home Assistant. Retrying in -288 seconds…
On my iPhone it shows a similar message. Rebooting doesn’t fix the issue.
My light switch automations of my Z2M connected devices work, but eg the HASS.Agent app can’t establish a connection to HA and thus the automations relying on it don’t work.
If you can’t see it on the network start at the HA box and look at the screen for info. Is it up and running? If so what ip address does it have etc. You’ve basically said my ha is broke and I don’t know what’s up with no extra information.
And unless you know for a fact you caught a virus or were hacked id not worry about those possibilities… Tbh
either a version from mid 2024 or the latest one. Can’t look it up without HA access.
Hardware: Home Assistant Yellow
connected via ethernet to my router
What do you mean by accessing it via ethernet? Just plugging my HA device to a monitor while it’s plugged in via ethernet? I don’t know how to do that because my HA Yellow doesn’t have a HDMI port and I don’t find information online on how to connect it to a monitor.
I know for a fact I caught one. I opened a sus installer and a few days later there was some extremely suspicious activity on a lot of my online accounts.
I understand and respectfully that’s not how HA works.
Ok so it’s a yellow (see we need the info… Technical info.) we wouldn’t have known you cannot hook to a monitor without that info and it changes how we troubleshoot it
What exactly do you mean by “that’s not how HA works”?
I have the HA Yellow kit that can be plugged into a wall with a Raspberry Pi Compute Module 4: CM4004032 - 4GB RAM - 32GB Storage
I only see the blue network traffic LED blinking. The other ones are off but I’m not sure if it’s because of what off indicates or because I set them to be that way; I have for a fact turned the LEDs off via HA, but I remember them still being turned on at some points. So I have no idea, what’s actually going on here. Neither can I turn them on without HA access
What I mean is nasty traffic on an account doesn’t == someone hacked your box.
Also if someone hacked your box they wouldn’t take it out. They’d leave it running to farm creds without you knowing. So it would be on the network and I do not know of any current virus that can ‘infect’ a ha box is what I meant.
And automatically running to that as a cause leads one to make incorrect assumptions and does you a disservice… Diagnostics and recovery for hack /malware is completely different than network and hardware troubleshooting. (you’re in the latter group right now, this is some kind of hard or config issue.)
Also that link I gave you tells you how to read the leds…
System health LED (yellow)
Home Assistant OS
Pattern
Description
Off
System is in EEPROM firmware or boot loader mode.
Heartbeat
|Home Assistant OS is running.|
Is if you don’t know reboot and watch it boot. The led setting you set won’t take effect until it actually gets to the bootloader. And loads ha and your settings. (read: you should at least see some activity at boot. If not… Well.)
Do you know what ip address it is supposed to have on the net. Does the router see it connected etc?
When booting, I see the red and green LEDs being on, without blinking.
So if I’m understanding you correctly, you’re saying my Homeassistant should show on my local network, despite me having set up an external URL for it.
I’m not sure about the IP address. I seems like my HA Yellow really doesn’t show up in the network, at the moment; when I unplug the Yellow’s ethernet cable and refresh my router’s browser UI page it doesn’t show a change in the number of active devices in the network.
This. We need to know if it’s getting an IP address. On your router console see if you see the box and if so what ip it has. If you can find an IP the you’ll try to ping by IP address.
If that doesn’t work you either have a dead network port or a dead box.
The Yellow troubleshooting documentation explains how to connect a USB cable to gain serial access to the box for console access and troubleshooting at the ha > prompt. I’d recommend following those instructions for additional information and access to the OS.
|Home Assistant OS is running.|