It really is the same as people hiding their 10.X.X.X or 192.168.X.X IP-addresses, it does not serve a purpose. And, not so much for deconz adapters, but for Sonoff adapters it really helps to see if they are using a Dongle-P or a Dongle-E if they don’t hide the serial-by-id.
i have a conbee2 stick
So you had ZHA running when installing Z2M, right?
Have you tried to remove Z2M, reboot, make sure ZHA is not active and reinstall Z2M?
TBH I’m just guessing.
My config is not from my main HA, I also have a thin client and since I still had the Conbee II (switched to Sonoff P dongle) I tried some time ago to see whether I could get it working.
Now I was looking where/how the port is referenced but don’t find anything so only what is written in that example I posted was working.
I don’t know if this is crucial: the error message remains the same all the time, no matter what you have done… 
I just tried a complete reinstall of everything. Clean OS and all. ZHA not configured at all.
steps i took:
- Made a new user for mqtt
- installed and started mosquitto.
- Installed MQTT
3a. configed MQTT using the IP of the HA as broker
3b. configed MQTT to use the mqttuser account - Installed Z2M
- Copypasted the cofig
- rebooted HA
- started Z2M
- checked log
- considering tossing it out the window…
Log as follows, error seems to remain the same.
[14:50:03] INFO: Preparing to start...
[14:50:04] INFO: Socat not enabled
[14:50:11] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-08-18 14:50:24] info: z2m: Logging to console, file (filename: log.log)
[2024-08-18 14:50:25] info: z2m: Starting Zigbee2MQTT version 1.39.1 (commit #unknown)
[2024-08-18 14:50:25] info: z2m: Starting zigbee-herdsman (0.55.3)
[2024-08-18 14:50:26] error: z2m: Error while starting zigbee-herdsman
[2024-08-18 14:50:26] error: z2m: Failed to start zigbee
[2024-08-18 14:50:26] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-08-18 14:50:26] error: z2m: Exiting...
[2024-08-18 14:50:26] error: z2m: Error: spawn udevadm ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:284:19)
at onErrorNT (node:internal/child_process:477:16)
at processTicksAndRejections (node:internal/process/task_queues:82:21)
Of course in the end, MQTT is crucial for Z2M, but I don’t think this error has anything to do whether MQTT is running/configured.
I have done some searching and this problem is not new, obviously…
The problem is that you see all kind of configurations/ways of and with different coordinators.
I remember that I didn’t get it running right away either and with my Sonoff coordinator, I installed Z2M in a separate container, apart from HA.
I seem to have solved the problem. The solution seems to consist of tossing deconz out the window and using sonoff instead.