search

kinu-garage / hut_10sqft

Computer setup tools for my own environment, and public discussion place holder.
2 stars 1 forks source link

HASS not functioning after the IP address of the host changed #1089

Closed 130s closed 1 month ago

130s commented 1 month ago

Reported in https://github.com/kinu-garage/hut_10sqft/issues/1087#issuecomment-2362077248

  1. [x] HASS: nabu.casa URL wasn't accessible --> Later it went through, w/o me doing anything.
  2. [ ] HASS: Lots of sensors are marked as "unavailable".
    • [ ] ZWaveJS

      Failed to connect: Cannot connect to host localhost:3123 ssl:default [Multiple exceptions: [Errno 111] Connect call failed ('::1', 3123, 0, 0), [Errno 111] Connect call failed ('127.0.0.1', 3123)]

    • [ ] garage-2 opener
    • [ ] light stand office
    • Lots of others
  3. [ ] HASS: Almost/All automations haven't been triggered, or triggered but devices are not doing the jobs.
130s commented 1 month ago

On Z-Wave JS page on Lovelace, I see this. Must be related:

Failed setup, will retry: Failed to connect: Cannot connect to host localhost:%PORT_ZWAVEJS% ssl:default [Multiple exceptions: [Errno 111] Connect call failed ('::1', %PORT_ZWAVEJS%, 0, 0), [Errno 111] Connect call failed ('127.0.0.1', %PORT_ZWAVEJS%)]

Z-Wave JS: Failed setup, will retry
Failed to connect: Cannot connect to host localhost:%PORT_ZWAVEJS% ssl:default [Multiple exceptions: [Errno 111] Connect call failed ('::1', %PORT_ZWAVEJS%, 0, 0), [Errno 111] Connect call failed ('127.0.0.1', %PORT_ZWAVEJS%)]
130s commented 1 month ago

Similar to Z-Wave, Zigbee also failing, although this is more physical issue.

HubZ Smart Home Controller - HubZ ZigBee Com Port
Failed setup, will retry: [Errno 2] could not open port /dev/ttyUSB1: [Errno 2] No such file or directory: '/dev/ttyUSB1'

But I do see it.

$ ls -lath /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 1 Sep 19 13:06 /dev/ttyUSB1
130s commented 1 month ago

Both errors on Z-Wave JS and HubZ went away after restarting HASS server (docker-compose). I still see many devices showing "unavailable" though...

130s commented 1 month ago

I'm not sure if many Z-Wave devices turned to unavailable status is due to a bad Z-wave route though, I triggered a rebuild for Z-Wave network route.

130s commented 1 month ago

I'm not sure if many Z-Wave devices turned to unavailable status is due to a bad Z-wave route though, I triggered a rebuild for Z-Wave network route.

Interestingly, I see devices slowly but surely become available, and I can tell those closer to the Zwave hub are dissipatingly becoming available than those further.

Meanwhile very less or even zero zigbee devices are responding.

130s commented 1 month ago

Samsung TV is operatable but status doesn't reflect on Lovelace.

130s commented 1 month ago

I drafted the post below (following horizontal line) but before that, I stopped HASS, unplugged the Zwave-Zigbee hub USB cable then replugged to another USB port on rpi-4, then started HASS. I see most of the devices recognized, and functional.

ZHA visual

Before recovery

2024-09-20-15-35-33_zigbee-visualization

Post recovery

I do see more green (good connection, I think) nodes than pre-recovery. I do NOT know what caused this. zha-visualization_after-recovered_2024-09-20-1638-54 In hindsight, a post community.home-assistant.io#528654 says a bad node in the network could block other nodes' functionality. IDK that's the case with me this time though.

Draft written to be posted on HASS community.

I have 26 of Z-Wave devices, 44 of Zigbee devices as of today integrated with my Home Assistant server. A few days ago, the following issues started happening:

Q-1. What should I look at? Q-2. I'm so dependent on HASS so want to recover asap.

As you see in the detail below, I tested older HASS software AND the backup config, but I can't recover the status.

Environment

Things I did before the issue started

Things I did in a hope to resolve the issue but don't seem to work