I run HAOS on an x86 mini PC.
My Zigbee coordinator is an SLZB-06 connected to the router via ethernet.
My HA supervisor and core are up to date as of this morning.
I have configured Mosquitto and Zigbee2MQTT successfully and have added about 10 devices over the last few weeks. They are properly exposed, can be controlled via Z2M or via HA without problem.
Last week I wanted to control (via HA) an Ikea Styrbar remote and ran into issues. I decided to remote it from HA and from Z2M and add it again. It was added to Z2M but not discovered in HA. I will point out that there is a loose time correlation between the last HA core/supervisor updates and this problem, but I’m far from confident they are correlated (I think Z2M problems started before but I want to mention all possible links). (also, this morning I updated core to its newest version in the hope of fixing things).
I read all I could on the web to try and understand the problem, rebooted Mosquitto, Z2M, HA multiple times.
Yesterday I realized the problem was deeper than just the Styrbar. I wanted to add a Sonoff ZB Mini R2 relay. Again, properly detected and controlled via Z2M, but not discovered by HA. So the problem is somewhere in-between.
Again I did my homework. Most of the info on the web dates from 2 years or so, and lots have changed since then, sadly, so the content is rarely relevant.
Here’s what I know. First, my Z2M configuration.yaml file (I confirmed that homeassistant is enabled as you can see):
version: 4
mqtt:
base_topic: zigbee2mqtt
server: mqtt://core-mosquitto:1883
user: xxx
password: xxx
serial:
port: tcp://192.168.xxxxxxxxxx
baudrate: 115200
adapter: zstack
disable_led: false
advanced:
log_level: info
channel: 11
network_key:
- 246
- 217
- 246
- 225
- 243
- 212
- 142
- 103
- 26
- 17
- 178
- 211
- 241
- 2
- 203
- 103
pan_id: 39593
ext_pan_id:
- 73
- 18
- 28
- 218
- 58
- 106
- 63
- 123
frontend:
enabled: true
port: xxxx
homeassistant:
enabled: true
legacy_action_sensor: true
discovery_topic: HomeAssistant
base_topic: zigbee2mqtt
force_disable_retain: false
include_device_information: false
keepalive: 60
maximum_packet_size: 1048576
reject_unauthorized: true
server: mqtt://core-mosquitto:1883
user: xxxx
version: 4
experimental_event_entities: true
In Z2M, going to Settings and then the Home Assistant tab, when trying to make changes (such as allowing experimental options) and clicking Submit, I get this message
z2m: Request ‘zigbee2mqtt/bridge/request/options’ failed with error: ‘Extension with name HomeAssistant already present’
That’s not good!
When I added the Sonoff relay yesterday evening, here’s what the Mosquitto log says:
[18:31:08] INFO: Successfully send discovery information to Home Assistant.
[18:31:09] INFO: Successfully send service information to the Supervisor.
However, when toggling any Z2M device (the un-discovered Sonoff or another, properly discovered device) I see this
2025-04-25 08:18:38: New connection from 172.30.33.3:57610 on port 1883.
2025-04-25 08:18:38: New client connected from 172.30.33.3:57610 as mqttjs_c497cd50 (p2, c1, k60, u'(username)').
2025-04-25 08:19:42: New connection from 172.30.32.2:41520 on port 1883.
2025-04-25 08:19:42: Client <unknown> closed its connection.
Note that the last two lines appear everytime I do something to any Zigbee device, and has been doing so ever since I started using my concentrator.
I’m at my wits’ end. Discovery was working perfectly, until it suddenly didn’t. I wonder if I broke something when I force removed the remote from Home Assistant.
I will point out that I have verified my Mosquitto syntax and configuration countless times, it’s properly configured according to the doc, and I changed nothing at all since it first worked.
Any help will be more than welcome.
2 posts - 2 participants
Read full topic
