Skip to content

Commit dbc2863

Browse files
authored
Add some details on fails to start page (Koenkk#3233)
1 parent 5a51176 commit dbc2863

File tree

1 file changed

+17
-7
lines changed

1 file changed

+17
-7
lines changed

docs/guide/installation/20_zigbee2mqtt-fails-to-start.md

+17-7
Original file line numberDiff line numberDiff line change
@@ -12,20 +12,19 @@ Most of the time this is caused by Zigbee2MQTT not being able to communicate wit
1212

1313
Configure the `serial` section as described [here](../configuration/adapter-settings.md).
1414

15-
## Error: `SRSP - SYS - ping after 6000ms`
15+
## Error: `SRSP - SYS - ping after 6000ms` for zStack or `HOST_FATAL_ERROR` for EmberZNet
1616

17-
5 common reasons of this error:
17+
Common reasons for this error:
1818

1919
1. The port of your serial adapter changed.
20-
Check [this](../installation/01_linux.md#1-determine-location-of-the-adapter-and-checking-user-permissions) to find
21-
out the port of your adapter.
20+
Check [this](../installation/01_linux.md#1-determine-location-of-the-adapter-and-checking-user-permissions) to find out the port of your adapter.
2221
2. If you are using a CC2530 or CC2531; it is a common issue for this adapter to crash (due to its outdated hardware).
23-
Reflashing the firmware should fix the problem. If it happens often consider flashing the [source routing firmware](https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_Home_1.2/bin/source_routing) or upgrade to
24-
a [more powerful adapter](../adapters/README.md).
22+
Reflashing the firmware should fix the problem. If it happens often consider flashing the [source routing firmware](https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_Home_1.2/bin/source_routing) or upgrade to a [more powerful adapter](../adapters/README.md).
2523
3. Your adapter requires additional configuration parameters. Check [supported Adapters](../adapters/README.md) section to find out if your adapter requires extra parameters (eg. ConBee II / RaspBee II).
2624
4. Home Assistant's "Zigbee Home Automation" (ZHA) integration is enabled. Try to disable the ZHA integration and restart the Zigbee2MQTT add-on.
2725
5. Your hardware adapter is flashed with the router firmware and not with the coordinator firmware.
2826
6. Your network Zigbee adapter is not accessible over the LAN network.
27+
7. Another software on your machine (including Home Assistant integration) is interfering with USB devices (example: [HA EDL21 integration](https://www.home-assistant.io/integrations/edl21) trying to find a USB device).
2928

3029
## Verify that you put the correct port in configuration.yaml
3130

@@ -128,7 +127,7 @@ In case you see message like below when running `dmesg -w` you are using a bad p
128127
[44889.075627] Voltage normalised (0x00000000)
129128
```
130129

131-
When you have a SSD connected to the Pi, try connecting the adapter via a powered USB hub.
130+
Also try connecting the adapter via a powered USB hub (especially if you have an SSD connected to the Pi).
132131

133132
## Make sure the extension cable works
134133

@@ -190,7 +189,18 @@ The correct revision is: **E** like shown below.
190189

191190
All earlier version are not supported (these are development boards). Return this board to the seller immediately.
192191

192+
## EmberZNet coordinators only
193+
194+
See [EmberZNet errors](../adapters/emberznet.md#error-level).
195+
193196
## Multiple cheap USB-UART
194197

195198
If you have multiple devices connected that are running cheap USB-UART converters (CH341) they may be indistinguishable to your system, since they all possibly have the same idProduct, SerialNumber etc. so they will share the same /dev/serial/by-id.
196199
The easiest solution is to change one of your devices to something with a different uart-usb converter. The second solution would be swapping the whole converter or adding external EEPROM memory to a chip that does not have one (like CH341) so you would be able to add a serial number.
200+
201+
## MQTT v5 disconnecting
202+
203+
If you use an MQTT broker with version 5 of the MQTT specification, you may get disconnects when something is misbehaving.
204+
This can happen, for example, when "maximum packet size" is exceeded (large networks).
205+
206+
To remedy that, configure your broker accordingly, and check if Zigbee2MQTT has a corresponding setting to adjust too. See [MQTT configuration](../configuration/mqtt.md#server-connection).

0 commit comments

Comments
 (0)