is it working?
As I remember you have to configure this z2m addon to point out to your mqtt ip, port and provide username and password for mqtt broker.
If you are sure that mqtt broker is configured properly in z2m the only thing left to check is config for a coordinator. Maybe it is wrong port, or it doesn’t have permission to access it.
Nn a completely new HAOS machine I set up only MQTT and Zigbee2MQTT and now I have the error:
npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2024-04-02T16_44_39_134Z-debug.log [18:44:39] INFO: Handing over control to Zigbee2mqtt Core …
Zigbee2MQTT:error 2024-04-02 18:45:00: Error while starting zigbee-herdsman Zigbee2MQTT:error 2024-04-02 18:45:00: Failed to start zigbee Zigbee2MQTT:error 2024-04-02 18:45:00: Exiting… Zigbee2MQTT:error 2024-04-02 18:45:00: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter. (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31)*
at Generator.throw ()*
at rejected (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)* npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start: node index.js npm ERR! Exit status 1
*npm ERR! * npm ERR! Failed at the [email protected] start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
If you don’t want to show your Zigbee2MQTT configuration.yaml, ok. But you have to make adjustments.
Zigbee2MQTT thinks you have a CCxxxx adapter, but you have a silabs adapter.