Ok, thx for this part but as I mentioned it doesn’t work. What should I show to community to get a help? I checked many times step by step that tutorial was done correctly. (only concern with login password issue but still it didn’t work regardless of log/pass). Devices work fine. As a noob i did everything possible.
Do you mean the MQTT user and password? That, if you’re using HAOS and the Mosquitto broker add-on, would be the user you created in HA for MQTT.
Well, the problem there is that you don’t have that line - or if you do it’s in the wrong place.
Please post your Z2M config correctly formatted.
Yes, but be aware that doing this will wipe the stick. You’ll need to ensure you’ve used ZHA’s backup option so you can recover if you want to go back.
2 Likes
HI, this is not my config (all lines in config are as described block by block by Smart Home Junkie). This what I pasted above is log report with lines related to “hardsman error” I don’t know even what hardsman is .
That’s the bit that handles the Zigbee stick.
Yes, and we need to see your config to help you fix it. Unless you don’t want this fixed?
1 Like
my log file:
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:
server: mqtt://core-mosquitto:1883
user: mqtt_user
password: xxxxxxxxxxx
serial:
port: >-
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230510172711-if00
adapter: ezsp
zigbee_herdsman_debug: false
Take a look at 11 here:
https://community.home-assistant.io/t/how-to-help-us-help-you-or-how-to-ask-a-good-question/114371/1
There was a link in my post, because pictures of code isn’t half as friendly as code as text. Click the link and have a read 
Code as text assumes that people see the world the way you do.
Sorry i saw “blue link” but mobile even didn’t start to open it and i forgot about this on desktop. To many things i do paralelly 
Now i see option for formatted code paste in forum. Simply it is not my world “coding”
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:
server: mqtt://core-mosquitto:1883
user: mqtt_user
password: xxxxxxxxxxxxxx
serial:
port: >-
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230510172711-if00
adapter: ezsp
zigbee_herdsman_debug: false
How are you running Z2M - as an add-on or a manual Docker container, or…?
normal add on, same way as mosquitto broker.
EDIT: I installed HAOS on Generic x86-64 platform to be more precise.
When you stopped using ZHA you removed that integration completely?
1 Like
No, only disabled. For obvious reasons i didn’t want to remove it having in mind that Sonoff Dongle-E is a bit risky with Z2M.
Then it’s possible that HA is still locking the stick for ZHA.
If i did a backup of ZHA and i uninstall it fully, and let’s assume that Z2M still will not work , if i reinstall ZHA backup should work without problem or i have to start from a scratch in ZHA??? Question is if ZHA backup is for a such purposes or it works only if already installed integration somehow stop to work and needs tonuse backup?
ZHA’s separate backup includes the stick, so all details of paired devices. Of course, if you’ve re-paired the devices for Z2M then those will need re-paired again.
Ok then i will do that and if this will not work i return for additional help .
Disabled should be sufficient. I disable/enable to switch between zha/z2m.
Thank again for help. Removing ZHA was a solution. In my case simple disabling it didn’t work. Now I start “unfortunately” rebuild ZB network but luckily only few devices.
1 Like