Cannot connect to host 172.30.32.1:8123

Configuration
1

I’ve been struggling with a bizarre problem for the last month or so. Through trial and error I narrowed it down to the ZHA entry in core.config_entities (in config/.storage).

The symptoms:

A. Supervisor log filled with errors:

22-10-23 00:35:24 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config: Cannot connect to host 172.30.32.1:8123 ssl:False [Connect call failed (‘172.30.32.1’, 8123)]

B. Cannot connect to web GUI.

C. There’s a small window at startup when I can connect to the web GUI

I can ssh using the add-on and deleting the ZHA entry from core.config_entities and rebooting makes the problem go away.

Only issue is that I use zigbee devices.

Any ideas on where to go from here?

2

Is this the internal IP address of your Home Assistant?

Try to share a bit more info… How is your HA instalation? Any change in the system from when this started? A new device? Some change in your settings?

3

Some more info:

  • Home Assistant 2022.10.5
  • Supervisor 2022.10.0
  • Operating System 9.2
  • Frontend 20221010.0 - latest
  • Running on an Intel NUC
  • Using the Nortek Zigbee/Zwave Stick with the latest firmware (manually updated)
  • Problem starting happening a while ago and unfortunately I can’t remember exactly when
  • IP 172.30.32.1 is not the IP of my home assistant instance. Appears to be the IP of the gateway but I don’t have my head around the architecture (I can ssh to port 22222 and run ha network info)
  • These are the lines in the core.config_entries file that, once removed, resolve the issue:
      {                                                                                                   
        "entry_id": "8ae31bffb18af4e702e0909217ec27f5",                                                   
        "version": 3,                                                                                     
        "domain": "zha",                                                                                  
        "title": "HubZ Smart Home Controller - HubZ ZigBee Com Port",                                     
        "data": {                                                                                         
          "device": {                                                                                     
            "path": "/dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_4150051D-if01-port0",  
            "baudrate": 57600,                                                                            
            "flow_control": "software"                                                                    
          },                                                                                              
          "radio_type": "ezsp"                                                                            
        },                                                                                                
        "options": {},                                                                                    
        "pref_disable_new_entities": false,                                                              
        "pref_disable_polling": false,                                                                   
        "source": "usb",                                                                                 
        "unique_id": "10C4:8A2A_4150051D_Silicon Labs_HubZ Smart Home Controller - HubZ ZigBee Com Port",
        "disabled_by": null                                                                              
      },
4

Anyone experiencing a similar problems or have any clues? I’m willing to roll up my sleeves to figure this out because essentially it kills ZHA for me.

5

From CLI, what is the command:

ip a

telling? :thinking:

6

SSH to port 22 and running ip a with ZHA disabled or enabled:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
20: eth0@if21: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP 
    link/ether 02:42:ac:1e:21:01 brd ff:ff:ff:ff:ff:ff
    inet 172.30.33.1/23 brd 172.30.33.255 scope global eth0
       valid_lft forever preferred_lft forever

Also looks like sometimes the errors are slightly different:

22-10-28 23:24:23 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:

A bit more info:

I suspect it’s the ip address of one of the docker containers. I went through them all but none of the IPs match.

Should there be a docker image and running container for ZHA?

7

I’ve started having the same symptoms. Started having the issue after upgrading to 2022.11 and adding a zigbee device (aqara magic cube).

8

In my case it all came down to the hardware I was using. I was using the Nortek GoControl QuickStick Combo Model HUSBZB-1 (Z-Wave & Zigbee Ember 3581 USB Adapter). I switched to the Sonoff dongle for zigbee and kept the Nortek for ZWave and the problems are all gone !

9

Interesting as I am also using the same Nortek stick, possible compatibility issue between it and ZHA? I’ve got a mostly z-wave setup so disabling ZHA isn’t terrible as a short term solution. Maybe I just need to upgrade to dedicated adapters.

10

Aha ! Finally - someone else with the same hardware and symptoms ! I wasted way too much time troubleshooting this and the cost of the Sonoff is well worth the time savings.

11

I do have the same problem with the sonoff stick. Did anyone solve the problem?

12

I have the same error in my home assistant log

23-04-09 21:26:17 ERROR (MainThread) [supervisor.homeassistant.api] Error on call https://172.30.32.1:8123/api/config: [Errno 104] Connection reset by peer
23-04-09 21:27:44 ERROR (MainThread) [supervisor.homeassistant.api] Error on call https://172.30.32.1:8123/api/config: [Errno 104] Connection reset by peer

my home assistant running on a raspberrypi3 with ZHA and a zigate USB to connect with ZigBee devices

the ip address 172.30.32.1 is the docker HA core ip:
ha core info return :

arch: aarch64
audio_input: null
audio_output: null
boot: true
image: ghcr.io/home-assistant/raspberrypi3-64-homeassistant
ip_address: 172.30.32.1
machine: raspberrypi3-64
port: 8123
ssl: true
update_available: true
version: 2023.4.1
version_latest: 2023.4.2
watchdog: true
13

Dearss,

I have the same error 1 week ago:

23-11-06 23:03:00 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:63950 ssl:default [Connect call failed ('172.30.32.1', 63950)]

I have hassio installation, but I don’t understand how I can solve the problem. This issue results in continuous restart sof node red. Anyone can helps me?.

Thanks,

Jose