After 6 weeks away, I've come home to all my smarthome tech working fine.
Except #HomeAssistant!
I can get into into its virsh shell, it appears to be updated and running. It is advertising an IP, which I can see on my router, but none of the apps/web will connect to it.
A reboot hasn't fixed it either. Oh well, that's what weekends are for, I guess…
@Edent i'm starting to wonder if there are any (FOSS) alternatives to HA
Well, the "good" news is that other people also have this problem with #HomeAssistant
@Edent Ouch!
Hopefully it'll get sorted quickly.
Doesn't help you much today, but this kind of breakage was part of what motivated me to move from a HAOS/Supervised install to just running the docker container.
I have to update manually, but it's not that much hassle and I get to sit out of updates until I've seen whether anyone else is complaining of breakage
@Edent Is it showing up by mdns name?
@woe2you how would I check that?
@Edent Ping homeassistant.local - possible the apps are hardcoded to hit that rather than the IP?
@woe2you OK, I can get to the #HomeAssistant observer at http://homeassistant.local:4357/ but not the service itself on :8123.
@Edent 6 weeks away and a fun little project for your first weekend back? Bliss.
@neil ah. Well, possession is 9/10th of the law, right?
