#After upgrade to 2025.9.1 HA version, MQTT Broker and Z2M don't work
1 messages · Page 1 of 1 (latest)
They both work for me, so I think it's unrelated to the new HA version.
Check your z2m config. Set serial per device id instead of usb port. Do a full reboot.
Would that be for example: /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 ?? I'm also using via USB atm, so if better with id I'd also change it.
Yep
I've already serial per device id. In the MQTT devices, I see all the devices that were configured but no data comes from them, it sounds like all the devices were disconnected or out of order. Do I have to reconnect all the devices one by one ?
It seems I have this error : "failed to start zigbee-hersman"
can you post your z2m config?
data_path: /config/zigbee2mqtt
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: "-d -d"
log: false
mqtt:
base_topic: zigbee2mqtt
server: mqtt://core-mosquitto:1883
user: mosquitto
password: mosquitto
serial:
port: >-
/dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_9a5539d79749ef118befcd8cff00cc63-if00-port0
adapter: ember
look at serial: port: remove ">-"
i think that's why zigbee adapter fails to start.
data_path: /config/zigbee2mqtt
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: "-d -d"
log: false
mqtt:
base_topic: zigbee2mqtt
server: mqtt://core-mosquitto:1883
user: mosquitto
password: mosquitto
serial:
port: /dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_9a5539d79749ef118befcd8cff00cc63-if00-port0
adapter: ember
copy/paste
I can't remove it because if I try, when I record configuration, HA adds automatically ">-" at the beginning of the line and put the rest at the next line. I think it's because the size of text is too wide. It worked before upgrade of HA with this.
That's not a problem, the >- is a YAML concept for using a multi-line string and removing whitespace from the start and end of it
There should be more information than that. Can you share more logs?