#Problem with configuration and startup zigbee2mqtt. What I do wrong?

1 messages ยท Page 1 of 1 (latest)

polar iron
#

Hi, I'm having trouble getting zigbee2mqtt to work. I've tried various methods and tutorials, but nothing seems to help.

I'm using a "Sonoff Dongle Plus zigbee ZBDongle-E USB" connected to a Raspberry Pi 4 (8 GB).

I used to only use ZHA, and all Zigbee devices worked fine. Now, I have ZHA disabled. I installed Mosquitto broker and these are its Logs:

"[11:44:34] INFO: Successfully send discovery information to Home Assistant.
[11:44:35] INFO: Successfully send service information to the Supervisor.
2026-01-06 11:44:39: New connection from 172.30.32.1:47547 on port 1883.
2026-01-06 11:44:39: New client connected from 172.30.32.1:47547 as 2RbkwkUbPpG3EArGLunKNI (p2, c1, k60, u'homeassistant').
2026-01-06 11:45:15: New connection from 172.30.32.2:53388 on port 1883.
2026-01-06 11:45:15: Client <unknown> closed its connection."

I installed the Zigbee2MQTT add-on and these are its logs:

"[11:43:45] INFO: Preparing to start...
[11:43:45] INFO: Socat not enabled
[11:43:46] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
READ THIS CAREFULLY
Refusing to start because configuration is not valid, found the following errors:

I have already entered various data in the Zigbee2MQTT configuration and it is always there Same result.

Can anyone help me?

cobalt patio
#

To me that sounds like you didn't fill in the serial->adapter field

#

For you, that should be ember

#

Make sure you hit "Save" as well

polar iron
#

I've already tried it and it's the same:

"[12:03:57] INFO: Preparing to start...
[12:03:57] INFO: Socat not enabled
[12:03:58] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
READ THIS CAREFULLY
Refusing to start because configuration is not valid, found the following errors:

I also entered the port:

  • /dev/ttyUSB0
    and this one
  • /dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_d25e4e7d73f3ef11aa1abb1b6d9880ab-if00-port0

It doesn't work either.

cobalt patio
#

Port doesn't appear to be filled in on your screenshot

polar iron
#

Yes, I've tried without the port entered. Now with the port entered and still the same.

#

Maybe I have MQTT configured incorrectly?

cobalt patio
#

That error indicates an issue w/ your Z2M configuration

polar iron
#

Ehhh... I don't know what to do

cobalt patio
#

Can you paste the options configration YAML, by hitting dotsvertical -> Edit in YAML, selecting that and then pasting that between a code block (```)

#

If there's anything sensitive, you can edit that out

polar iron
#

You mean this data?

"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: {}
serial:
adapter: ember
port: /dev/ttyUSB0"

glass topaz
#

use /dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_d25e4e7d73f3ef11aa1abb1b6d9880ab-if00-port0 in portsetting

polar iron
#

I pasted it and still same result:

"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: {}
serial:
adapter: ember
port: >-
/dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_d25e4e7d73f3ef11aa1abb1b6d9880ab-if00-port0"

Logs:
"[12:37:42] INFO: Preparing to start...
[12:37:42] INFO: Socat not enabled
[12:37:43] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
READ THIS CAREFULLY
Refusing to start because configuration is not valid, found the following errors:

cobalt patio
#

Something is definitely up w/ the Z2M add on configuration persistence... it's not just a you issue, I just confirmed it as well.

I'd say for now, if you can edit /config/zigbee2mqtt/configuration.yaml to contain the correct serial section, that should get things moved to the next step

#

Maybe because most people go through onboarding entirely and don't do what you're doing

polar iron
#

I will try to go to the /config/zigbee2mqtt/configuration.yaml file and enter the port manually

cobalt patio
#

and adapter

glass topaz
#

perform a full reboot of haos after changing. not restart

polar iron
#

Before and after. Is everything okay?

cobalt patio
#

Do you want to force onboarding still? Looks like you may have already gone through it, but onboarding: true is still there

#

That might be toggled on in your settings

#

(Also a password is visible there, too)

glass topaz
#

yep, remove pics ๐Ÿ˜‰

cobalt patio
#

I'd remove baudrate: entirely as well instead of just removing the value

polar iron
#

๐Ÿ˜‹

#

Will reset HA

cobalt patio
#

But, also make sure any updates you make there make it to the add-on configuration panel too, since it will (at some point) rewrite that config

polar iron
#

Now I see a different screen after clicking on Zigbee2MQTT.

Progress is happening ๐Ÿ™‚

cobalt patio
#

Yeah, you do still have onboarding still forced on the left. If you haven't gone through that before, you should, but that should be flipped back to false afterward otherwise it'll keep popping up

polar iron
#

And now it's okey?

cobalt patio
#

seems reasonable

polar iron
cobalt patio
#

Credentials for mqtt look wrong

polar iron
#

In Add-ons or Devives? ๐Ÿ‘€

cobalt patio
#

You had a username/password set in your z2m config, right?

#

I assume that user/pass combo doesn't exist on Mosquitto

polar iron
#

In the Zigbee2MQTT configuration, in the mqtt tab, I should have the username and password from this...? I must be doing something wrong.

cobalt patio
#

You really shouldn't need to provide any of that if you're using the Mosquitto add-on on the same system

#

It should be using the addons user

polar iron
#

Guys. It works!! Finally. Thank you so much for your help. I wouldn't have been able to do anything without manually entering Zigbee2MQTT in the configuration file, and you guys came up with the idea.