How do I configure my add-on to use an external MQTT broker?
I was using Mosquito on a Raspberry long before getting started with Home Assistant, so I’ve just kept using it. However, when configuring the zigbee2mqtt add on, I get an error in the logs:
Refusing to start because configuration is not valid, found the following errors:
- must have required property 'mqtt'
Could you post the z2m log from the time you first start up z2m, too help.
Also, are you using ZHA as well?
If yes then both can not coexist in HA. choose one too control the zigbee netwok.
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/socat.sh
[23:55:38] INFO: Socat not enabled, marking service as down
cont-init: info: /etc/cont-init.d/socat.sh exited 0
cont-init: info: running /etc/cont-init.d/zigbee2mqtt.sh
cont-init: info: /etc/cont-init.d/zigbee2mqtt.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun socat (no readiness notification)
services-up: info: copying legacy longrun zigbee2mqtt (no readiness notification)
[23:55:39] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start
> node index.js
Zigbee2MQTT:info 2022-06-28 23:55:40: Logging to console and directory: '/config/zigbee2mqtt/log/2022-06-28.23-55-40' filename: log.txt
Zigbee2MQTT:info 2022-06-28 23:55:40: Starting Zigbee2MQTT version 1.25.2 (commit #unknown)
Zigbee2MQTT:info 2022-06-28 23:55:40: Starting zigbee-herdsman (0.14.34)
Zigbee2MQTT:error 2022-06-28 23:56:00: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-06-28 23:56:00: Failed to start zigbee
Zigbee2MQTT:error 2022-06-28 23:56:00: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-06-28 23:56:00: Exiting...
Zigbee2MQTT:error 2022-06-28 23:56:00: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:102:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:123:29)
at Zigbee.start (/app/lib/zigbee.ts:58:27)
at Controller.start (/app/lib/controller.ts:101:27)
at start (/app/index.js:109:5)
[23:56:01] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start
> node index.js
Zigbee2MQTT:info 2022-06-28 23:56:02: Logging to console and directory: '/config/zigbee2mqtt/log/2022-06-28.23-56-02' filename: log.txt
Zigbee2MQTT:info 2022-06-28 23:56:02: Starting Zigbee2MQTT version 1.25.2 (commit #unknown)
Zigbee2MQTT:info 2022-06-28 23:56:02: Starting zigbee-herdsman (0.14.34)
This caught my eye:
Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
This is from the docs:
If Zigbee2MQTT fails to start with a Texas Instruments LAUNCHXL-CC1352P-2/CC26X2R1 with Error: SRSP - SYS - version after 6000ms, you most probably have connected your device to a system that requires pressing the reset button (the one next to the USB connector) momentarily/shortly after connecting the USB cable. This issue has primarily been observed on x86 architectures only ( e.g., Intel NUC, HPE Microserver, i7 laptop), see also #2162. The procedure has to be repeated every time the adapter is re-connected and it's not clear yet, whether this can be fixed at all. It does not seem to occur on ARM based boards (Raspberry Pi, ODROID XU4).
The chip is a CC2652 and I am running HASP on a NUC. I did try pressing the reset button, but no difference.
Any ideas?
I do have a ConBee that I bought last year, should I abandon the Sonoff dongle and use that?
Sonoff dongle works fine for me, running the latest firmware.
Yours looks ok too. There are plenty of forum topics for “bad gateway” but no single solution by the look. The only time I have had it was after a reboot where I had left an ESP plugged into another port and the port number changed. I have got around that issue by using /dev/serial/by-id/... for the port rather than /dev/ttyUSB0, but that’s not your issue.
Dare I say uninstall reinstall :). Seems to have worked for some.
I did nothing for an hour and wanted to look at the logs again, and now it looks like Zigbee started. Even more curious, the UI was now live. (Meaning Zigbee started?)
So, I tried to pair a Zigbee light (Ikea). And I got these errors. (Sorry for the screen grab)
I only have success pairing things if they are within a metre or less of the controller. For globes and plugs I use an extension cord and place them about 25cm away from the controller.
I do have 4 station meshed wifi and a lot of devices - so I figure the 2.4GHz spectrum is a bit busy?
Yes, latest HAOS
Rebooting- No I hadn’t tried, but on your suggestion I rebooted. No difference.
I have been looking at suggestions from the link you provided. Which is why I keep coming back to this: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
which the tips in the link provided say is endemic to X86.
I also updated the firmware on the dongle.
The Sonoff dongle is new, and I also have a Conbee dongle plus a naked dongle that has a CC2531 chip, but I don’t recall where it came from. I kind of doubt that changing dongles would make any difference.
I am contemplating deleting Zigbee2MQTT and trying ZHA. Thoughts?
Here’s an idea. My HA is on an Intel NUC which the Zigbee2MQTT notes say may be a problem (X86).
I am running Mosquitto on a Raspberry Pi3 as my MQTT broker. (I was using NodeRed and MQTT long before I dipped my toes into Home Assistant, so I just kept using the broker on the Pi). What if I were to run another instance of HA on the Pi3 just to host my broker and the Zigbee dongle? My HA on the Nuc doesn’t care where the MQTT messages come from as long as they are on my local net.
