All Zigbee2MQTT devices have gone unavailable

Configuration Zigbee
1

Hello,

For some reason all of my zigbee2mqtt devices have gone unavailable in the MQTT integration. Not sure why, haven’t knowingly changed anything.

I can see and operate all my devices within the zigbee2mqtt addon (operate switches and so on) but they are unavailable within the MQTT integration.

I am using:
SLZB-06 => Zigbee2MQTT => EMQX => MQTT integration.

Everything looks fine as far as I can see. I have done usual things, restart the EMQX addon and MQTT integration, rebooted Home Assistant.

I am at a loss as to why this has happened and how I can fix it. Can anyone, please point me in the right direction to get my devices back on line?

2

I have the SMLight SLZB-06 as well, have this issue before.

What fixes for me, unplug the SMLight, could to 3, plug it back.

3

I would start with the EMQX MQTT broker error logs.

1 Like
4

Thanks, haven’t done this yet, but I can communicate and connect with the devices through the Zigbee2MQTT addon, so I am not sure that is where the issue lies. My device is connected via Power of Ethernet.

5

From what info you shared Z2M is not communicating with the MQTT integration. That points to the broker. The HA and Addon logs will help identify the issue.

1 Like
6

Thanks… Do you mean the log that is in the EMQX addon page?

I don’t see any errors there:

----------------------------------------------------------
 Add-on: EMQX
 The most scalable open-source MQTT broker for IoT. An alternative for the Mosquitto add-on
-----------------------------------------------------------
 Add-on version: 0.7.7
 You are running the latest version of this add-on.
 System: Home Assistant OS 16.2  (aarch64 / qemuarm-64)
 Home Assistant Core: 2025.10.0
 Home Assistant Supervisor: 2025.10.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
[12:49:28] INFO: Configuring timezone (Australia/Sydney)...
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-emqx: starting
s6-rc: info: service init-emqx successfully started
s6-rc: info: service emqx: starting
s6-rc: info: service emqx successfully started
s6-rc: info: service legacy-services: starting
[12:49:28] INFO: Starting EMQX...
s6-rc: info: service legacy-services successfully started
EMQX_PLUGINS__INSTALL_DIR [plugins.install_dir]: /data/emqx/plugins
EMQX_RPC__PORT_DISCOVERY [rpc.port_discovery]: manual
EMQX_NODE__DATA_DIR [node.data_dir]: /data/emqx/data
EMQX_NODE__COOKIE [node.cookie]: ******
EMQX_NODE__NAME [node.name]: [email protected]
Listener tcp:default on 0.0.0.0:1883 started.
2025-10-12T12:49:33.558432+11:00 [warning] msg: alarm_is_activated, message: <<"87.94% mem usage">>, name: high_system_memory_usage
Listener ssl:default on 0.0.0.0:8883 started.
Listener ws:default on 0.0.0.0:8083 started.
Listener wss:default on 0.0.0.0:8084 started.
Listener http:dashboard on :18083 started.
EMQX 5.8.7 is running now!

Should I be looking at a different log somewhere?

7

Something that stands out, from the EMQX log:

EMQX_NODE__NAME [node.name]: [email protected]

And this from within the Zigbee2MQTT add on settings page:

Screenshot 2025-10-12 at 14.31.29
Screenshot 2025-10-12 at 14.31.29920×1366 35.2 KB

Note server address.

I haven’t changed the server address at all, so I don’t know why this happened. I gather this needs to be changed in the addon configuration page as I see no way of updating the server address within the addon. So maybe here…

Screenshot 2025-10-12 at 14.34.11
Screenshot 2025-10-12 at 14.34.112026×1278 87.8 KB

The address is homeassistantonmac.local (this is a new home assistant server I am migrating to).

8

yeah, that was it … the address got changed somehow. Thanks for the feedback guys… it is really appreciated…

1 Like
9

I didn’t realize you were migrating to another device, but happy to assist!

Please consider marking my post above with the Solution tag. It will automatically place a check-mark next to the topic’s title which signals to other users that this topic has been resolved.

image

1 Like
10

Done and thanks again for responding.

11

Hate to come back again… but I am having a real hard time with this issue…

Now it seems as though EMQX is randomly crashing and restarting. This from the EMQX addon log:

Listener wss:default on 0.0.0.0:8084 started.
[os_mon] memory supervisor port (memsup): Erlang has closed
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
[19:14:45] INFO: Service EMQX exited with code 256 (by signal 9)
[19:14:46] INFO: Starting EMQX...
EMQX_PLUGINS__INSTALL_DIR [plugins.install_dir]: /data/emqx/plugins
EMQX_RPC__PORT_DISCOVERY [rpc.port_discovery]: manual
EMQX_NODE__DATA_DIR [node.data_dir]: /data/emqx/data
EMQX_NODE__COOKIE [node.cookie]: ******
EMQX_NODE__NAME [node.name]: [email protected]
[19:14:47] INFO: Service EMQX exited with code 256 (by signal 9)
[19:14:48] INFO: Starting EMQX...
12

What are you running HA /EMQX on ? Signal 9 points to the OS killing the process for lack of ram.

13

Not sure what was going on but it does seem stable now. I am running a bit of an unusual setup … home assistant running on mac via a UTM virtual machine. .

I also had the mosquitto broker add on installed but not running. I haven’t had any issues (as far as I know) since I deleted the mosquito addon from the add-on store.