Device paired successfully but no communication with zigbee2mqtt

Configuration Zigbee
1

Hi,

I have a strange problem that I can’t seem to solve

BTW I’m using hassio 0.101.3 and zigbee2mqtt addon 1.7.1

I bought a gledopto downlight 9W (Model ID GL-D-004ZS) and paired successfully with zigbee2mqtt

zigbee2mqtt:info  2019-11-29T05:33:16: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_removed","message":"left_network","meta":{"friendly_name":"0x00124b001ef16597"}}'
zigbee2mqtt:info  2019-11-29T05:33:24: Device '0x00124b001ef16597' joined
zigbee2mqtt:info  2019-11-29T05:33:24: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":{"friendly_name":"0x00124b001ef16597"}}'
zigbee2mqtt:info  2019-11-29T05:33:24: Starting interview of '0x00124b001ef16597'
zigbee2mqtt:info  2019-11-29T05:33:24: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"0x00124b001ef16597"}}'
zigbee2mqtt:info  2019-11-29T05:33:35: Successfully interviewed '0x00124b001ef16597', device has successfully been paired
zigbee2mqtt:info  2019-11-29T05:33:35: Device '0x00124b001ef16597' is supported, identified as: Gledopto LED RGB + CCT downlight 9W  (GL-D-004ZS)
zigbee2mqtt:info  2019-11-29T05:33:35: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_successful","meta":{"friendly_name":"0x00124b001ef16597","model":"GL-D-004ZS","vendor":"Gledopto","description":"LED RGB + CCT downlight 9W ","supported":true}}'

I had to add it’s configuration in /zigbee2mqtt-1.7.1/node_modules/zigbee-herdsman-converters/devices.js to make it supported

{
    zigbeeModel: ['GL-D-004ZS'],
    model: 'GL-D-004ZS',
    vendor: 'Gledopto',
    description: 'LED RGB + CCT downlight 9W ',
    extend: gledopto.light,
    supports: 'on/off, brightness, color temperature, color',
},

`
The problem is that apart from the message that the gledopto downlight joined the network I get absolutely no communication between it and the zigbee gateway (CC2531)

I have the 6W version of this downlight (GL-D-003Z) and it communicates with no problem with zigbee2mqtt (actually I didn’t have to add an entry for it because it was already there in the default devices.js configuration)

This is the log of the (GL-D-003Z) :+1:

zigbee2mqtt:info  2019-11-29T05:36:43: MQTT publish: topic 'homeassistant/sensor/0x00124b001ea82c9a/linkquality/config', payload '{"unit_of_measurement":"-","value_template":"{{ value_json.linkquality }}","state_topic":"zigbee2mqtt/0x00124b001ea82c9a","json_attributes_topic":"zigbee2mqtt/0x00124b001ea82c9a","name":"0x00124b001ea82c9a_linkquality","unique_id":"0x00124b001ea82c9a_linkquality_zigbee2mqtt","device":{"identifiers":["zigbee2mqtt_0x00124b001ea82c9a"],"name":"0x00124b001ea82c9a","sw_version":"Zigbee2mqtt 1.7.1","model":"LED RGB + CCT downlight  (GL-D-003Z)","manufacturer":"Gledopto"},"availability_topic":"zigbee2mqtt/bridge/state"}',
zigbee2mqtt:info  2019-11-29T05:36:43: MQTT publish: topic 'homeassistant/light/0x00124b001ea82c9a/light/config', payload '{"brightness":true,"color_temp":true,"xy":true,"schema":"json","command_topic":"zigbee2mqtt/0x00124b001ea82c9a/set","state_topic":"zigbee2mqtt/0x00124b001ea82c9a","name":"0x00124b001ea82c9a_light","unique_id":"0x00124b001ea82c9a_light_zigbee2mqtt","device":{"identifiers":["zigbee2mqtt_0x00124b001ea82c9a"],"name":"0x00124b001ea82c9a","sw_version":"Zigbee2mqtt 1.7.1","model":"LED RGB + CCT downlight  (GL-D-003Z)","manufacturer":"Gledopto"},"availability_topic":"zigbee2mqtt/bridge/state"}'

I checked the database.db file and I have the 2 entries, first one is the 6W downlight GL-D-003Z which works well, second one is the 9W downlight GL-D-004ZS that sends no message to zigbee2mqtt

{“id”:4,“type”:“Router”,“ieeeAddr”:“0x00124b001ea82c9a”,“nwkAddr”:46426,“manufId”:0,“manufName”:“GLEDOPTO”,“powerSource”:“Mains (single phase)”,“modelId”:“GL-D-003Z”,“epList”:[11,13],“endpoints”:{“11”:{“profId”:49246,“epId”:11,“devId”:528,“inClusterList”:[0,3,4,5,6,8,768],“outClusterList”:[],“clusters”:{“genBasic”:{“attributes”:{“modelId”:“GL-D-003Z”,“manufacturerName”:“GLEDOPTO”,“powerSource”:1,“zclVersion”:1,“appVersion”:1,“stackVersion”:2,“hwVersion”:1,“dateCode”:“20131206”,“swBuildId”:“2.0.0”}}},“binds”:[]},“13”:{“profId”:49246,“epId”:13,“devId”:528,“inClusterList”:[4096],“outClusterList”:[4096],“clusters”:{},“binds”:[]}},“appVersion”:1,“stackVersion”:2,“hwVersion”:1,“dateCode”:“20131206”,“swBuildId”:“2.0.0”,“zclVersion”:1,“interviewCompleted”:true,“meta”:{}}

{"id":10,"type":"Router","ieeeAddr":"0x00124b001ef16597","nwkAddr":31567,"manufId":0,"manufName":"GLEDOPTO","powerSource":"Mains (single phase)","modelId":"GL-D-004ZS","epList":[11,13],"endpoints":{"11":{"profId":49246,"epId":11,"devId":528,"inClusterList":[0,3,4,5,6,8,768],"outClusterList":[],"clusters":{"genBasic":{"attributes":{"modelId":"GL-D-004ZS","manufacturerName":"GLEDOPTO","powerSource":1,"zclVersion":1,"appVersion":1,"stackVersion":2,"hwVersion":1,"dateCode":"20131206","swBuildId":"1.0.6"}}},"binds":[]},"13":{"profId":49246,"epId":13,"devId":528,"inClusterList":[4096],"outClusterList":[4096],"clusters":{},"binds":[]}},"appVersion":1,"stackVersion":2,"hwVersion":1,"dateCode":"20131206","swBuildId":"1.0.6","zclVersion":1,"interviewCompleted":true,"meta":{}}

Thanks

2

OK, So I was able to control the device manually in hassio by issuing the following command in the mqtt developper tool :

{“state”:“ON”,“brightness”:100, “color”: {“x”: 0.123, “y”: 0.123}}

So basically hassio doesn’t recognise this device, is there a way to add in a configuration file so when automatic device discovery is enabled it’s recognized.

I have 50 devices like this one so it would be hard to add each manually.

Thanks

3

Did you enable MQTT Discovery in home assistant?

4

I tried using discovery: true in the configuration file but the device doesn’t appear in hassio

5

This is not the same as “normal” discovery.

Do you have in your configuration.yaml

mqtt:
  discovery: true

Or

discovery: true

6

This is my full configuration.yaml file :

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

mqtt:
  broker: 192.168.31.226
  discovery: true

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

If I use the file above I can see GL-D-003Z models (Gledopto 6W downlight) in Hassio UI, but I can’t see GL-D-004ZS models (Gledopto 9W downlight PLUS)

If I edit the file like this

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

mqtt:
  broker: 192.168.31.226
  discovery: false

light:
  - platform: "mqtt"
    schema: "json"
    name: "Salle de Sport - Panel LED 01"
    state_topic: "zigbee2mqtt/Panel LED Plus"
    availability_topic: "zigbee2mqtt/bridge/state"
    brightness: true
    color_temp: true
    xy: true
    command_topic: "zigbee2mqtt/Panel LED Plus/set"
    rgb: true

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

I can see GL-D-004ZS in Hassio UI. But it will be cumbersome to do it manually for 100 devices (Gledopto Downlights and Xiaomi switches)

7

Can you not use a combination of both, discovery enabled and add manually the devices which are not found by discovery?

8

Nope,

Seems when discovery is set to true all manual configuration is bypassed.

If anyone can confirm.

9

I have same problems with Gledopto devices(
Also the devices are turn_on on startup, and I don't know how to fix it(