as per top - these commands aren’t running
In Home Assistant, there are integrations and Add-ons. ZHA is an integration.
Yes, you may be able to take advantage of it (assuming nothing else in your system uses MQTT) but it means migrating your entire network of Zigbee devices from Zigbee2MQTT to ZHA (a non-trivial procedure).
Are you familiar with the process of upgrading Home Assistant Core? It’s not too different from installing it. If the following installation instructions seem too complicated then that’s what you’ll face each month (or whenever you choose to upgrade). That’s why I suggested you consider re-installing with Home Assistant OS.
Okay, so that ZHA integration is not the direction i want to take just yet - but looks like some plan “B”.
Now, i’ve been telnetin my broker’s address on various ports:
[[email protected]][/h/chmurix]$ telnet 192.168.1.69 8081
Trying 192.168.1.69…
telnet: Unable to connect to remote host: Connection refused
[[email protected]][/h/chmurix]$ telnet 192.168.1.69 8080
Trying 192.168.1.69…
telnet: Unable to connect to remote host: Connection refused
[[email protected]][/h/chmurix]$ telnet 192.168.1.69 1883
Trying 192.168.1.69…
telnet: Unable to connect to remote host: Connection refused
[[email protected]][/h/chmurix]$ telnet 192.168.1.69 8123
Trying 192.168.1.69…
Connected to 192.168.1.69.
Escape character is ‘^]’.
^CConnection closed by foreign host.
The 8123 is HA’s front end - would there are a way to maybe check what other ports might be open on this IP? I am assuming some inadvertent configuration change there.
I ma not familiar with that process - however i am able to set new HAOS instance by myself, hook into network, give static IP LAN etc. And that is definitely sound of the future for me - however - I’d like to look for any means to restore this instance here.
The HA core version i am using is 2025.1.3 - can you tell me if and how can i downgrade to any previous one?
Helo again,
one more hint i found was the Cloudflare Zero Trust certificate which has expired for me on 2nd of Feb - the day after my issue hit.
I am not sure if this can affect this set up - as after all - mqqt and HA are working locally, right?
Still, CF was incorporated on my set up to allow login and connection from Internet to my box - is anyone having and idea if that expiry could affect the broker set up?
hey everyone,
i’ve run “netstat -tulpn | grep LISTEN” and got:
tcp 0 0 127.0.0.1:20241 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:1883 0.0.0.0:* LISTEN -
tcp 0 0 192.168.1.69:33315 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8123 0.0.0.0:* LISTEN -
tcp 0 0 192.168.1.69:40191 0.0.0.0:* LISTEN -
tcp 0 0 192.168.1.69:40000 0.0.0.0:* LISTEN
No 8081 on 192.168.1.69 - i this looks like potential cause of the issue.
Can you guys advise how i can go about opening that port on this IP ?
This is useful — at least you know Mosquitto is running (listening on port 1883) but Zigbee2mqtt (Z2M) appears to be missing, or at least its web console is. Running systemctl status will list everything it manages as a “.service” so if you see it in that list try restarting with systemctl restart zigbeename.service. If not, you need to figure out where Z2M is installed to start it manually and, while you’re there, check its logs for errors. The docs suggest /opt/zigbee2mqtt which is a good place to start looking.
Hey peterxian - thanks for input.
So i ran systemctl status and got below output:
systemctl status
● no.i
State: running
Units: 263 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 0 units
Since: Thu 2025-02-13 10:13:40 CET; 9h ago
systemd: 257.2-2-arch
CGroup: /
├─init.scope
│ └─1 /sbin/init
├─system.slice
│ ├─NetworkManager.service
│ │ └─325 /usr/bin/NetworkManager --no-daemon
│ ├─cloudflared.service
│ │ └─475 /usr/bin/cloudflared --no-autoupdate tunnel run --token eyJhIjoiNDQ2YTk3ZDUyMDNmNmJjMjYwZD>
│ ├─cronie.service
│ │ └─381 /usr/sbin/crond -n
│ ├─dbus-broker.service
│ │ ├─315 /usr/bin/dbus-broker-launch --scope system --audit
│ │ └─322 dbus-broker --log 4 --controller 9 --machine-id da7ad1d8b196401199e1d212d88b092b --max-byt>
│ ├─home-assistant.service
│ │ └─586 /var/lib/hass/.venv/bin/python /var/lib/hass/.venv/bin/hass --config /var/lib/hass/ --log->
│ ├─mosquitto.service
│ │ └─422 /usr/bin/mosquitto -c /etc/mosquitto/mosquitto.conf
│ ├─nginx.service
│ │ ├─429 “nginx: master process /usr/bin/nginx”
│ │ ├─431 “nginx: worker process”
│ │ └─432 “nginx: worker process”
│ ├─polkit.service
│ │ └─867 /usr/lib/polkit-1/polkitd --no-debug --log-level=notice
│ ├─sshd.service
│ │ └─365 “sshd: /usr/bin/sshd -D [listener] 0 of 10-100 startups”
│ ├─system-getty.slice
│ │ └─[email protected]
│ │ └─383 /sbin/agetty -o “-- \u” --noreset --noclear - linux
│ ├─systemd-journald.service
│ │ └─235 /usr/lib/systemd/systemd-journald
│ ├─systemd-logind.service
│ │ └─328 /usr/lib/systemd/systemd-logind
│ ├─systemd-udevd.service
│ │ └─udev
│ │ └─276 /usr/lib/systemd/systemd-udevd
│ └─zigbee2mqtt.service
│ └─93863 node index.js
└─user.slice
└─user-1000.slice
├─session-19.scope
│ ├─80819 “sshd-session: chmurix [priv]”
│ ├─80844 “sshd-session: chmurix@pts/0”
│ └─80846 -bash
├─session-22.scope
│ ├─86966 “sshd-session: chmurix [priv]”
│ ├─86976 “sshd-session: chmurix@pts/1”
│ ├─86978 -bash
│ ├─93873 systemctl status
│ └─93874 less
└─[email protected]
└─init.scope
├─80831 /usr/lib/systemd/systemd --user
└─80836 “(sd-pam)”
lines 1-60/60 (END)
● no.i
State: running
Units: 263 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 0 units
Since: Thu 2025-02-13 10:13:40 CET; 9h ago
systemd: 257.2-2-arch
CGroup: /
├─init.scope
│ └─1 /sbin/init
├─system.slice
│ ├─NetworkManager.service
│ │ └─325 /usr/bin/NetworkManager --no-daemon
│ ├─cloudflared.service
│ │ └─475 /usr/bin/cloudflared --no-autoupdate tunnel run --token e>
│ ├─cronie.service
│ │ └─381 /usr/sbin/crond -n
│ ├─dbus-broker.service
│ │ ├─315 /usr/bin/dbus-broker-launch --scope system --audit
│ │ └─322 dbus-broker --log 4 --controller 9 --machine-id da7ad1d8b>
│ ├─home-assistant.service
│ │ └─586 /var/lib/hass/.venv/bin/python /var/lib/hass/.venv/bin/ha>
lines 1-22/60 39%…skipping…
● no.i
State: running
Units: 263 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 0 units
Since: Thu 2025-02-13 10:13:40 CET; 9h ago
systemd: 257.2-2-arch
CGroup: /
├─init.scope
│ └─1 /sbin/init
├─system.slice
│ ├─NetworkManager.service
│ │ └─325 /usr/bin/NetworkManager --no-daemon
│ ├─cloudflared.service
│ │ └─475 /usr/bin/cloudflared --no-autoupdate tunnel run --token eyJhIjoiNDQ2YTk3ZDUyMDNmNmJjMjYwZDY3OTk2MDJhNWJiZDAiLCJ0IjoiZmRiMTJhY2MtNWU5ZC00OTMxLTg2YjctYzE4NDcwOTMwN2Q0IiwicyI6IlkyUXpaakkzTWpFdFptRTFaQzAwTkdJeExXSTFNVGt0TTJOak1UTXhORE5pWVdFMSJ9
│ ├─cronie.service
│ │ └─381 /usr/sbin/crond -n
│ ├─dbus-broker.service
│ │ ├─315 /usr/bin/dbus-broker-launch --scope system --audit
│ │ └─322 dbus-broker --log 4 --controller 9 --machine-id da7ad1d8b196401199e1d212d88b092b --max-bytes 536870912 --max-fds 4096 --max-matches 131072 --audit
│ ├─home-assistant.service
│ │ └─586 /var/lib/hass/.venv/bin/python /var/lib/hass/.venv/bin/hass --config /var/lib/hass/ --log-file /var/log/hass/home-assistant.log --log-rotate-days 1
│ ├─mosquitto.service
│ │ └─422 /usr/bin/mosquitto -c /etc/mosquitto/mosquitto.conf
│ ├─nginx.service
│ │ ├─429 “nginx: master process /usr/bin/nginx”
│ │ ├─431 “nginx: worker process”
│ │ └─432 “nginx: worker process”
│ ├─polkit.service
│ │ └─867 /usr/lib/polkit-1/polkitd --no-debug --log-level=notice
│ ├─sshd.service
│ │ └─365 “sshd: /usr/bin/sshd -D [listener] 0 of 10-100 startups”
│ ├─system-getty.slice
│ │ └─[email protected]
│ │ └─383 /sbin/agetty -o “-- \u” --noreset --noclear - linux
│ ├─systemd-journald.service
│ │ └─235 /usr/lib/systemd/systemd-journald
│ ├─systemd-logind.service
│ │ └─328 /usr/lib/systemd/systemd-logind
│ ├─systemd-udevd.service
│ │ └─udev
│ │ └─276 /usr/lib/systemd/systemd-udevd
│ └─zigbee2mqtt.service
│ └─93863 node index.js
└─user.slice
└─user-1000.slice
├─session-19.scope
│ ├─80819 “sshd-session: chmurix [priv]”
│ ├─80844 “sshd-session: chmurix@pts/0”
│ └─80846 -bash
├─session-22.scope
│ ├─86966 “sshd-session: chmurix [priv]”
│ ├─86976 “sshd-session: chmurix@pts/1”
│ ├─86978 -bash
│ ├─93873 systemctl status
│ └─93874 less
└─[email protected]
└─init.scope
├─80831 /usr/lib/systemd/systemd --user
└─80836 “(sd-pam)”
I’ve ran systemctl restart zigbee2mqtt.service command and received below output:
No i’ve ran netstat -tulpn | grep LISTEN again and got:
tcp 0 0 0.0.0.0:8123 0.0.0.0:* LISTEN 586/python
tcp 0 0 127.0.0.1:1883 0.0.0.0:* LISTEN 422/mosquitto
tcp 0 0 192.168.1.69:34659 0.0.0.0:* LISTEN 586/python
tcp 0 0 127.0.0.1:20241 0.0.0.0:* LISTEN 475/cloudflared
tcp 0 0 192.168.1.69:40000 0.0.0.0:* LISTEN 586/python
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 429/nginx: master p
tcp 0 0 192.168.1.69:45471 0.0.0.0:* LISTEN 586/python
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 365/sshd: /usr/bin/
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 429/nginx: master p
[[email protected]][/h/chmurix]$
No change whatsoever tough - would you happen to have any more ideas?
If Z2M isn’t starting, you’ll need to find where its log files are and use them, along with the startup troubleshooting link I posted earlier, to fix whatever is wrong with it.
right, as far as start up troubleshooting perhaps below output makes any sense:
[[email protected]][/h/chmurix]$ sudo systemctl start zigbee2mqtt
[sudo] password for chmurix:
[[email protected]][/h/chmurix]$ systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/usr/lib/systemd/system/zigbee2mqtt.service; enabled; preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2025-02-13 20:12:18 CET; 56ms ago
Invocation: 412dacb709064e6ca6247995567fcca7
Process: 4229 ExecStart=node index.js (code=exited, status=1/FAILURE)
Main PID: 4229 (code=exited, status=1/FAILURE)
Mem peak: 100.5M
CPU: 8.157s
[[email protected]][/h/chmurix]$
hey, for any one following this - the effort has been dropped from my end - i am moving (already moved) to HAOS - already installed it on box, and replaced in network - also been able to copy&paste most of my front end.
The dongle kept the connections so that was huge surprise but a welcomed one.
Also - the back up from HA Core did not work for HAOS in my case.
Currently, i have all critical component moved to new box almost seamlessly - but still a LOT of manual rebuild of helpers and automations await.
Thanks guys - and rhqq sucks.