Zigbee2MQTT SRSP - SYS - ping after 6000ms please help :(

mwav3 · December 29, 2021, 9:08pm

Its hard to tell exactly what’s wrong from the logs.

Some suggestions to try and troubleshoot are:
1- Check that the addon is set to the correct serial port for your device
2- Check you have the mqtt mosquitto addon up and running, and configured properly

Additional setup info is here

github.com

zigbee2mqtt/hassio-zigbee2mqtt/blob/083a7b233f4a545680dcbc94bef550cb17f850ef/zigbee2mqtt/DOCS.md#configuration

# Pairing
By default the add-on has `permit_join` set to `false`. To allow devices to join you need to activate this after the add-on has started. You can now use the [built-in frontend](https://www.zigbee2mqtt.io/information/frontend.html) to achieve this. For details on how to enable the built-in frontent see the next section.

# Enabling the built-in Frontend
Make sure your add-on options have the right settings. If you already had experimental options, you might now automatically get `new_api` set properly on update.

```yaml
frontend:
  port: 8099
experimental:
  new_api: true
```

Enable `ingress` to have the frontend available in your UI: **Supervisor → Dashboard → Zigbee2mqtt → Show in sidebar**. You can find more details about the feature on the [Zigbee2mqtt documentation](https://www.zigbee2mqtt.io/information/frontend.html).

# Configuration
The configuration closely mirrors that of `zigbee2mqtt` itself, with a couple of key differences:
1. Home Assistant requires add-on configuration in JSON format, rather than YAML. If you don't understand the difference, you can use a YAML-to-JSON converter.
2. An additional top-level `data-path` option is required. Set this to the path where you would like the add-on to persist data. Defaults to `/share/zigbee2mqtt`. Note that both `config` and `share` directories are mapped into the container (read-write) and are available to you.
3. If you are using groups or device-specific settings, you must use seperate files, and provide the paths to these files in their corresponding config options as described by the zigbee2mqtt docs. This is due to a limitation Home Assistant places on nested config levels.

This file has been truncated. show original

If still not working, try to enable the advance debug mode and check for additional log entries:

Enabling zigbee debug mode

If you want to troubleshoot in more depth problems with your zigbee devics, sometimes you must enable DEBUG option on Zigbee2mqtt startup. To do this you must set zigbee_herdsman_debug to true.

zigbee_herdsman_debug: true

Based on this line, one other thought is that there is an old incompatible config that the program is finding and trying to restore. You may want to temporarily move that file somewhere else and try and start fresh.

I use zigbee2mqtt in docker so don’t use the addon version, so hopefully if this doesn’t work someone who is more familiar can provide some more info.